NAS Codex › QNAP › QNAP HBS 3 job completed with warning or failed: what QNAP says to check
QNAP HBS 3 job completed with warning or failed: what QNAP says to check
A Hybrid Backup Sync (HBS 3) job finishes as completed with warning, reports "Not all extended attributes are copied", or fails with "Folder pairs are invalid or inaccessible". QNAP has an FAQ for each of these. This page puts them together: what a warning means, how to see exactly which files had problems, and the fixes QNAP gives for the two named messages.
Written against: Hybrid Backup Sync 3 (QNAP FAQs last modified 2023-01-10, 2023-05-22 and 2023-12-07). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
In HBS 3, go to Jobs, click the Report icon for the job, open Job History and click Export File History as CSV for the run. The CSV lists each file with its status and the reason. For "Not all extended attributes are copied", edit the job and select Rules > Methods > Enable filters > Exclude symbolic links, and rename or move files whose names use characters the destination does not support. For "Folder pairs are invalid or inaccessible" after renaming an external drive, create a new job or change the drive's label back to the name in the job.
What "completed with warning" means
QNAP's FAQ says that when an HBS job is completed but comes with a warning, it may mean that the file system at the destination device or server does not support certain attributes. It could also mean that there are other conflicts or differences between the source and the destination for certain files, such as access permissions, ownership, modification time, or extended attributes.
QNAP adds that when a job is completed with warning, some files may have been skipped or may not have been fully transferred to the destination. So a warning is worth checking, not ignoring.
Step 1: see which files had problems
QNAP says to examine the job run's file history to find which files ran into problems and the reason for each:
- In HBS 3, go to Jobs.
- Identify the job to inspect. Under Action, click the Report icon. The Report window opens.
- Go to Job History and identify the job run to examine.
- Under Action, click the Export File History as CSV icon. A zipped file is downloaded to your computer.
- Unzip it and open the CSV file. QNAP says the details include the file name, size, status, the reason for the status, and the date and time.
Optional: keep only the failures in the file history
In the same Report window, QNAP describes File History Settings. There you can set the maximum number of most recent runs to keep records for and the maximum amount of time to keep records for. You can also select Do not keep records of transferred files; QNAP says this makes it easier to examine all the unsuccessful file transfers at once. Clear File History removes all existing records.
Warning: "Not all extended attributes are copied"
QNAP says this warning, after running a backup or sync job, has at least two possible causes: the destination does not support symbolic links, or the destination file system does not support certain special characters that appear in the source filenames.
Cause 1: symbolic links
QNAP NAS systems use symbolic links for the Recycle Bin (@Recycle), which appears in many folders. QNAP says the warning appears if the job destination does not support symbolic links, giving external drives that use the NTFS file system as an example. To exclude symbolic links from the job:
- Open HBS 3 and go to Jobs.
- Find the job with the warning. Under Action, click the Edit icon.
- Go to Rules > Methods, select Enable filters, then select Exclude symbolic links.
- Click Save, then click the Start icon to run the job again.
Cause 2: special characters in filenames
QNAP explains that if the source and destination file systems are different, filename conflicts may occur, because the file systems support different sets of characters. Its example: certain special characters allowed in NTFS are invalid in EXT4. The fix is to find the skipped files, using the CSV export from Step 1, and rename them so they no longer contain the special characters, or move or remove them from the folder. Then run the job again.
QNAP also gives a way to find skipped files over SSH: access the NAS via SSH and run grep -i skip /etc/config/qsync/logs/details/*, then look through the output for the skipped files.
Failure: "Folder pairs are invalid or inaccessible"
QNAP's FAQ covers this error for jobs that use an external drive as the source or destination. If you rename the external drive after creating the job, the job keeps the drive's old name and path. When the job runs, HBS cannot locate the drive, and the job fails with "Folder pairs are invalid or inaccessible".
QNAP notes that you cannot edit the source or destination device of a job after the job has been created. It gives two fixes: create a new job, which automatically uses the drive's current name, or change the drive's name back to the old name recorded in the failed job. To change the name back:
- Open HBS 3, go to Backup & Restore or Sync, click the failed job and note the external drive's name in the Destination field.
- Open Storage & Snapshots and go to Storage > External Storage.
- Click the external device, click Actions, then select Storage Information.
- Edit Label to match the name you noted, then click Close.
- Open File Station and check that the drive's name in the navigation panel is the same as the name in the HBS job.
You can then run the job in HBS 3 again.
Summary of QNAP's steps
- Any warning: export the job run's file history as CSV and read the status and reason for each file.
- "Not all extended attributes are copied": exclude symbolic links in the job's filters, and rename or move files with characters the destination does not support.
- "Folder pairs are invalid or inaccessible" after renaming an external drive: create a new job, or set the drive's label back to the name in the job.
When to stop and get help
Do not expect to fix a renamed-drive failure by editing the job: QNAP says a job's source or destination device cannot be edited after the job is created, so the fix is a new job or the drive's old name. If space does not come back after deleting a shared folder, see storage space not freed after deleting a shared folder.
Questions
What does completed with warning mean in QNAP HBS 3?
QNAP says the destination file system may not support certain attributes, or there are differences between source and destination for some files, such as permissions, ownership, modification time or extended attributes. Some files may have been skipped or not fully transferred.
How do I see which files an HBS 3 job skipped?
In HBS 3, go to Jobs, click the Report icon for the job, open Job History and click Export File History as CSV for the run. The CSV lists each file's name, size, status, the reason for the status, and the date and time.
Why does my HBS job fail with Folder pairs are invalid or inaccessible?
QNAP says this happens when an external drive used by the job was renamed after the job was created, so HBS cannot locate it. Create a new job, or change the drive's label back to the name recorded in the job.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.