Good morning,
I have a backup copy job which is supposed to copy the previously created backup (whole job) to an S3 storage. The backup contains four virtual machines - the copy job is successful on two of them, but I get the following error on two other VMs:
26.05.2025 06:57:25 :: Processing XXX Error: Storage does not exist
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{622eace2-5ebb-47df-9186-db2c1ec7785d}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}.
I have been looking at the behavior for 14 days now, as I was hoping that after an active-full on the weekend the problem would be fixed - unfortunately not.
Any ideas what I could do?
-
- Influencer
- Posts: 11
- Liked: never
- Joined: Nov 21, 2012 12:37 pm
- Full Name: Marcel
- Contact:
-
- Veeam Software
- Posts: 2679
- Liked: 620 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Failed to restore file from local backup. VFS link: [summary.xml]
Hi marcy,
Thank you for the details on the situation and sorry to hear about the challenges.
A Support Case is the way to go here. Please open a Support case and be sure to include logs for Support to review, and share the case number here once created. (Use the 1st radio button to export from jobs, and export form the affected Backup Copy Job)
An active full potentially could have helped here, but it depends on what specifically is wrong with the storage -- the error tells "Storage does not exist" which seems like the backup file itself could not be reached, but it's unclear if it's the source backups or the backup copy's backups, so best to let Support check the logs to better understand the situation and what can be done.
Thank you for the details on the situation and sorry to hear about the challenges.
A Support Case is the way to go here. Please open a Support case and be sure to include logs for Support to review, and share the case number here once created. (Use the 1st radio button to export from jobs, and export form the affected Backup Copy Job)
An active full potentially could have helped here, but it depends on what specifically is wrong with the storage -- the error tells "Storage does not exist" which seems like the backup file itself could not be reached, but it's unclear if it's the source backups or the backup copy's backups, so best to let Support check the logs to better understand the situation and what can be done.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Bing [Bot] and 35 guests