Hello,
Iiran into a problem with the LHR and Backup Copy Jobs over WAN.
If the copy is aborted because the WAN link had a dropout, the job cannot be continued.
I always get the error message: Failed to pre-process the job .... a backup file is immutable
Since I don't want to make a new full for WAN backups, I currently have the following workaround:
- Remove Immutable Flag
- Move files to new folder
- Rescan the repository
- Backup Copy Job --> perform map backup files
- run the CopyJob
I hope this helps another People.
Greetings Falk
-
- Veeam ProPartner
- Posts: 59
- Liked: 40 times
- Joined: Jan 08, 2013 4:26 pm
- Full Name: Falk
- Location: Germany
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Issue with LHR and WAN Copy
Hi Falk,
Thanks for sharing the workaround with the Community! By default, a failed backup copy task is retried 5 times within one job session, perhaps increasing a number of retries would be an alternative workaround in this case? And one more question: how did you come to the conclusion that the retrieved error is triggered due to unstable connection?
Thanks!
Thanks for sharing the workaround with the Community! By default, a failed backup copy task is retried 5 times within one job session, perhaps increasing a number of retries would be an alternative workaround in this case? And one more question: how did you come to the conclusion that the retrieved error is triggered due to unstable connection?
Thanks!
-
- Veeam ProPartner
- Posts: 59
- Liked: 40 times
- Joined: Jan 08, 2013 4:26 pm
- Full Name: Falk
- Location: Germany
- Contact:
Re: Issue with LHR and WAN Copy
Hi Petr,
my customer has the connection problems more often with the smaller sites. Most of the time the line is OK again after a few minutes. Most of the time the interruptions stay under 1 hour.
With the old backup copies to a normal repository, the copy process could be resumed again. But with the Immutable repository, the Immutable flag is set on the files.
The only option would be to not set the Immutable flag if the copy was successful. But if you don't use Per VM Files, this is again a risk for the successful VMs.
The workaround is not pretty but it works and fortunately the interruptions don't happen that often.
Regards, Falk
my customer has the connection problems more often with the smaller sites. Most of the time the line is OK again after a few minutes. Most of the time the interruptions stay under 1 hour.
With the old backup copies to a normal repository, the copy process could be resumed again. But with the Immutable repository, the Immutable flag is set on the files.
The only option would be to not set the Immutable flag if the copy was successful. But if you don't use Per VM Files, this is again a risk for the successful VMs.
The workaround is not pretty but it works and fortunately the interruptions don't happen that often.
Regards, Falk
Who is online
Users browsing this forum: No registered users and 64 guests