Backup file locking "logic"

[pkelly_sts]

Came in to find a stalled replica job & failures on backup copy job & need to understand why.

Full info as follows:

Backup job started on 11/07 at 19:30, ended at 20:04

Backup copy job (to remote site) had "started" (scheduled) on 11/07 at 19:40 with first VM queued at 20:04
Two VM copies failed at 02:08 & 02:16 on 12/07 with error "The process cannot access the file because it is being used by another process". Both VMs failed after 5 retries.

Tape job (copying original backup files) started on 11/07 at 21:30 (scheduled start time) & completed by 21:44

Replica job (from backup copy at remote site) Started at 06:18 (this replica job is started by a post-job script on the backup copy job so can ONLY have started at the end of that job) on 12/07, was still stuck at 09:00 "Restore point found but is locked" for most VMs - only 2 VMs had "already replicated", all the rest were "Pending"

Assumed replica was holding onto backup files so gracefully cancelled replica job.

Hit "Sync Now" for backup copy job which immediately started syncing the remaining 2 VMs.

I know now that the backup copy job is going to be out of sync & will take 2 or 3 days to get itself back into sync (which drives me mad!).

So, who was locking what & why??

Considered opening a case but don't even know which job to open the case for at this point! :-/

[foggy]

Hi Paul, your best bet would be to open a case, indeed, so that the engineer could review the entire setup. You do not need to focus the case on any specific job, just mention the files locking issues and describe the situation. Logs for all the involved jobs would be required.

[pkelly_sts]

Thanks foggy. Now logged as #01850342