Why Xackup may create a new Saved Location unexpectedly, and how to fix it

Summary

Xackup can create a new Saved Location even when one already exists, due to how location matching works during job migration/load.
This can lead to duplicate entries and, in some cases, a job appearing to freeze in the UI when Run is clicked.

Why this happens

Because the path check is an exact string comparison, small differences can prevent a match.

Common reasons matching fails

• Path case differences (\\NAS\Backup vs \\nas\backup)
• Trailing slash differences (\\NAS\Backup vs \\NAS\Backup\)
• Different path style for same target (UNC path vs mapped drive)
• Saved Location was deleted/recreated, but the job still references the old ID
• Minor formatting differences (for example, extra spaces)

Customer-visible symptoms

• New Saved Locations appear after opening or running jobs
• Duplicate-looking entries show up in Saved Locations
• A job points to an unexpected Saved Location
• A job appears to freeze in the UI when clicking Run

Customer workaround (recommended)

1) Create or fix the intended Saved Location

1. Open Saved Locations in the UI.
2. Create a new location or correct an existing one.
3. Ensure path and credentials are exactly what you want to standardize on.

2) Repoint the Job to that Saved Location

1. Open the job in Edit mode.
2. Go to backup destination/location settings.
3. Select the correct Saved Location from the list.
4. Save the job.

3) Clean up duplicates

1. Verify which Saved Location the job now uses.
2. Remove duplicate entries that are no longer referenced.
3. Re-open and run the job to confirm normal behavior.

Prevention best practices

• Standardize one path format (recommended: UNC path format).
• Avoid changing path text format casually (slashes/case/style).
• After migrations/imports, review key jobs and re-save them with the intended Saved Location.

Short support response

"Xackup matches Saved Locations by exact stored values. If the ID or path text does not match exactly, it may create a new Saved Location. One symptom can be a job appearing to freeze when Run is clicked. Fix by creating or correcting the intended Saved Location, editing the affected job to select that location, saving the job, and removing unused duplicates."