Hi there
I have a Windows 10 Professional Computer.
I am using Task Scheduler to run two separate tasks - one is a nightly backup of work related files, and the other is a weekly backup of media files - each backup has its own external drive on a Linux computer (Ubuntu) mapped as windows shares at a remote location, and both are managed by Windows Task Scheduler. In the case of the D: drive the Action is -
"C:\Program Files\FreeFileSync\FreeFileSync.exe" with the argument "D:\Organisers\FFS configs\D-backup2015.ffs_batch". This batch file will run on the Windows desktop and also on the remote machine as a scheduled task.
In the case of the media drive the action is -
"C:\Program Files\FreeFileSync\FreeFileSync.exe" with the argument "D:\Organisers\FFS configs\Media.ffs_batch". This batch file will run on the Windows desktop but NOT on the remote machine as a scheduled task.
All the Scheduler settings are identical for these two Actions. The D: backup runs correctly but the media backup fails with an error in the FFS log as follows
Cannot find the following folders:
M:\
___________________________________________
Cannot read file attributes of "M:\".
ERROR_PATH_NOT_FOUND: The system cannot find the path specified. [GetFileAttributes]
4:20:01 PM Error: Cannot read file attributes of "M:\".
ERROR_PATH_NOT_FOUND: The system cannot find the path specified. [GetFileAttributes]
etc..
Yet, as I said it works perfectly well on the desktop. The Windows share M: drive files can be written and read on it and there are no errors when I look at the drive on the Linux machine.
I know it's a hard one, but has anybody had this problem?
Failure of night backup
- Posts: 2
- Joined: 16 May 2021
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
- Posts: 2
- Joined: 16 May 2021
Thanks Zenju - this was the problem:
"If you have mapped a network share to a local drive letter, and have set up Windows Task Scheduler to use a different user account, FreeFileSync will not be able to see the network mapping."
Voila!
Fixed!
Regards - Jeremy
"If you have mapped a network share to a local drive letter, and have set up Windows Task Scheduler to use a different user account, FreeFileSync will not be able to see the network mapping."
Voila!
Fixed!
Regards - Jeremy