So I'm working in Post Production and have large volumes of material to go through many processes before I can deliver it to the editor.
Part of what needs to happen is that all footage has to be transcoded. I usually queue this up overnight however one bottleneck is that even though it's all done the next morning, I still have to copy the material to a portable drive to deliver to the editor's machine which can take hours.
I know that the transcodes take hours, but not all night, so I figured I'd use FFS to compare the contents of the folders I designated as the output directory for my transcode batches on my master hard drive, to the contents of identically named folders on the portable transfer drive. I setup the job, did a test comparinson which copied nothing because both sets of folders were at the time empty as the transcodes hadn't been set off, and then I scheduled the batch job to take place at 1AM when I was confident that the transcodes would definitely be done.
This morning I was greeted with an error message stating that it couldn't find any of the folders on the transfer drive that I'd specified should be synchronised. The drive was mounted and I could see all the folders it claimed it couldn't find and also I'd actually had the synchronisation occur several times before that as I'd tested it both deliberately and accidentally (for some reason the automator job set off the actual sync operation when it opened calendar for me, but this was fine since the folders were empty anyway). Why was it able to do the sync several times over when I didn't need to, but suddenly couldn't find the folders on the transfer drive when it was crucial?
Why did my overnight sync fail to find the folders on a volume when it found them in the initial test
- Posts: 1
- Joined: 16 Dec 2020
-
- Posts: 2947
- Joined: 22 Aug 2012
When testing, you normally run that task under your user credentials.
If you are not very careful, your scheduled task may run under different user credential, generally the system user. Such different user may very well not have access rights to one or more of the locations involved in your sync.
Depending on how you mount your drives, the same may even hold when running your scheduled task under the same user credentials. In Windows, it is most likely to work if you connect based on IP-address, and have the user credentials for that network resource stored in the (Windows) Credential Manager.
If you are not very careful, your scheduled task may run under different user credential, generally the system user. Such different user may very well not have access rights to one or more of the locations involved in your sync.
Depending on how you mount your drives, the same may even hold when running your scheduled task under the same user credentials. In Windows, it is most likely to work if you connect based on IP-address, and have the user credentials for that network resource stored in the (Windows) Credential Manager.
