Hi,
I have a question about using Arq to backup the content of disk images which might or might not be mounted at the time Arq starts the backup task.
When Arq starts a scheduled backup and the disk image is not mounted, the following message appears in the log:
arqcommitter[XXX]: ERROR [thread YYY] lstat(/Volumes/MyData) error 2: No such file or directory
arqcommitter[XXX]: ERROR [thread YYY] <BucketCommitter: <Bucket ....: /Volumes/MyData (0 ignored paths)>>: error calculating bytes to upload: Error Domain=UnixErrorDomain Code=2 "/Volumes/MyData: No such file or directory" UserInfo=0xXXXXXXXXX {NSLocalizedDescription=/Volumes/MyData: No such file or directory}
(where /Volumes/MyData is the path of the mounted disk image which I added as a Backup Folder in Arq).
The backup then proceeds normally to the other folders to be backed-up.
From previous discussions in the forum, I expected Arq to fail more graciously when a mount point I asked to backup was not available at the time the backup started.
Seeing those error messages I wonder whether that folder would then be considered deleted and potentially removed from S3 during a future trim.
Can you shed more light on how Arq is supposed to behave when the folder to backup is a volume mount point which might or might not be available (mounted) at backup start?
Arq is v 2.8.2.
Thanks for your help!