After upgrading from 6.9.5 to 6.10.0 Hotfix2 the backup jobs which were successful when running 6.9.5 after the upgrade are not working any more and every job is reported as fail. The log reports: Destination cannot be mounted on the system.
If someone have this problem any help will be appreciated.
Are your backup jobs set up on the source system or the destination system?
What backup protocol are you using?
Are you specifying the remote system by it's name or are you using it's IP address?
I use rsync backup jobs set up on the destination, and the backup jobs worked fine after I upgraded that system to 6.10.0. I just upgraded the source system today, so I'll find out tomorrow if there is an issue related to the source.
The backup jobs are type remote Windows timestamp source is with hostname, and the jobs are on the destination device and the backup date is stored on it The destination is actually updated to 6.10.0. I have checked the credentials and connection between the destination and source the connection is ok. On a failed job when Test connection button is used the result is connection failed when passwrd is retyped the result is successful connection. After that when the job run for a minute is reported as failed with the error state from the previous post. Clearly in the logs after some digging is visible the status of all jobs with the old firmware are good and after the update everything is failed.
To me is a firmware bug even there are tho hotfixes by now. In addition I am running disk test now just in case. In other setup the firmware did not report 2 drvies failed. And after system access problems and manual disk test they poup up as bad. Regards
The backup jobs are type remote Windows timestamp source is with hostname, and the jobs are on the destination device and the backup date is stored on it
Probably not something I would run into, since I use rsync and IP addresses. Are the sources hosted on Windows PCs?
One test you might try is modifying one job to use the IP address, and see if that works.
Thank you for the time spent on this matter. So after couple of tests ended up with after changing either the source or the destination of the job with ip address instead of hostname used. The jobs are completed successfully. Changing the hostname with hostname.local also solves the problem because we are in AD environment.
We will monitor the jobs these days but for now it seems ok.
