When performing a backup of any type, the following error message is received in the backup report:
The message suggests that the corresponding file is not found within the user home when the backup process attempts to re-locate the file.
To resolve the issue, check to see if there are any hardware or I/O issue with the corresponding volume.
For Servosity Pro running on Windows, check under [Control Panel] > [Administrative Tools] > [Event Viewer] if any disk related errors can be found. If a disk error is found, perform a check disk on the corresponding partition by entering the command "chkdsk /f" in command prompt.
Linux / Unix:
For Servosity Pro running on Linux / Unix, depending on the distribution, you could try entering the command "cat /var/log/messages" and verify if an error could be found. If a disk error is found, please perform a checkdisk on the corresponding partition by enter the command "/sbin/fsck" and "/sbin/e2fsck" (with the partition un-mount).
If the User Home in concern is a network drive, check on the network setting of the corresponding drive, verify if the "Log on" account of the Online Backup Scheduler Service has sufficient permission. Alternatively, instead of "Local System", please try running the Online Backup Scheduler Service with a Windows account that has sufficient permission right(s) to access the network drive.
- Please follow the instructions below:
- Open [Control Panel] -> [Administrative Tools] -> [Services] -> [Online BackupScheduler] -> [Log on]
- Select the [This Account] option
- Enter the Login Credentials
- Restart the [Online Backup Scheduler] service
If no hardware or I/O issue are found on the corresponding volumes or the permissions are correct for the network path. Please request that the file index be rebuilt on the backup server side. You can do this by submitting a support ticket to email@example.com
We will need to temporarily disable the backup schedule. Then remove the index files for this backup set and run a profile rebuild job to re-generate them. Once the rebuild job completes, We will re-enable the backup schedule and see if that resolves the issue on the next backup job.