Symptoms
Backup completes with warnings only for files containing special characters.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Backup completes with warnings only for files containing special characters.
- Comparison to run: Compare specific skipped filenames with cloud provider's documented restrictions.
- Pass condition: Test file appears and restores under a documented unambiguous name.
Why It Happens
Shares, backup jobs and replication paths each have their own permissions, destination rules and histories; a successful connection is not proof of complete content.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Destination rejects forbidden characters — investigate this first only if the local state or controlled comparison supports it.
- Path length limit exceeded — a second layer that may survive a simple restart and requires a targeted check.
- Case-insensitive collision at target — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Keep a mapping of old and new names and do not bulk-rename live shared projects. NAS interfaces may report job-level success while individual file operations, permissions, path mapping or remote copies still differ. Verify at the file level and distinguish the original from a restored copy. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare specific skipped filenames with cloud provider's documented restrictions. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare specific skipped filenames with cloud provider's documented restrictions. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Make a copy of one offending file with a compliant test name. | This can expose or rule out destination rejects forbidden characters without changing several settings together. |
| Inspect the deeper layer | Assess destination object-name rules and path normalization. | Use the evidence to separate path length limit exceeded from case-insensitive collision at target; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether path length limit exceeded is consistent with the evidence. If not, investigate case-insensitive collision at target rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Backup completes with warnings only for files containing special characters. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare specific skipped filenames with cloud provider's documented restrictions. Do not erase logs or reset the device yet. Make a copy of one offending file with a compliant test name. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Check backup log for exact name and path, not just warning count. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. Test file appears and restores under a documented unambiguous name. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider destination rejects forbidden characters, path length limit exceeded and case-insensitive collision at target separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare specific skipped filenames with cloud provider's documented restrictions. Assess destination object-name rules and path normalization. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Plan a reversible rename mapping before migrating many files. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. Test file appears and restores under a documented unambiguous name. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating destination rejects forbidden characters as certain before running the comparison: Compare specific skipped filenames with cloud provider's documented restrictions.
- Trying several changes at once, such as modifying path length limit exceeded and case-insensitive collision at target simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Keep a mapping of old and new names and do not bulk-rename live shared projects.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Test file appears and restores under a documented unambiguous name.
- Repeat the original failing action under equivalent conditions: Backup completes with warnings only for files containing special characters.
- Run the control again: Compare specific skipped filenames with cloud provider's documented restrictions.
- Check the positive pass condition: Test file appears and restores under a documented unambiguous name.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Assess destination object-name rules and path normalization. Plan a reversible rename mapping before migrating many files.
Collect job ID, anonymized path, protocol, client version and relevant error excerpts without uploading private file contents or exposing NAS management to the public internet.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare specific skipped filenames with cloud provider's documented restrictions.
- Preserve the corrected behavior: Test file appears and restores under a documented unambiguous name.
- Keep tested offline or immutable copies of critical data, record job exclusions, and periodically restore a small sample into a separate test location.
- Review configuration or hardware changes that could reintroduce destination rejects forbidden characters.
Frequently Asked Questions
Does this symptom prove destination rejects forbidden characters?
No. Start with the controlled comparison: Compare specific skipped filenames with cloud provider's documented restrictions. Only treat destination rejects forbidden characters as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Assess destination object-name rules and path normalization. That helps determine whether path length limit exceeded or case-insensitive collision at target fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Test file appears and restores under a documented unambiguous name. Keep a record of the working state for future troubleshooting.