Solved
VEEAM Endpoint Backup - Restore issue
Posted on 2016-11-10
Hi all,
I am hoping you can help me. I have a customer that did not want to pay for a good backup solution. I pleaded and prodded to go with a backup to disk and cloud solution like Carbonite.But they declined because they are simply cheap. I warned them of the consequences but they insisted. Now I am in a situation where they forced me to use VEEAM's free Endpoint backup on a server. I have been doing BareMetal backups on a server before it was decommissioned in case something bad happened. The server was turned off and the cloud hosting company has turned off the server. We just found out there was a hidden database on the server that was turned off and the hosting company will not work with me to turn it back on so I can transfer it over to the new server.
My plan was to do a Bare Metal restore using the restore points I took of this server to a Hyper-V VM (I have done with before with this product and it worked fine.)
When I boot into VEEAM's PE environment I go through all the steps, put in the correct account to authenticate to the network share which holds the VEEAM restore points. I have about 20 restore points there and it can see them perfectly but the job fails.
The error message states, "Shared memory connection closed. Failed to download disk. Agent to process method (DataTransfer.SyncDisk) Exception from server. File does not exist. [Path of backup location]".
Has anyone seen this before? Attached is a screenshot
Things I know:
1. It's not a authentication issue.
2. I have tried multiple restore points. It is not just one restore point I get this error on.
3. I expanded the disk to 238 GB. I don't believe it is a space issue because I tried to restore the C drive which was only 80 GB
Any help is greatly appreciated.
veeam_error.png
I am hoping you can help me. I have a customer that did not want to pay for a good backup solution. I pleaded and prodded to go with a backup to disk and cloud solution like Carbonite.But they declined because they are simply cheap. I warned them of the consequences but they insisted. Now I am in a situation where they forced me to use VEEAM's free Endpoint backup on a server. I have been doing BareMetal backups on a server before it was decommissioned in case something bad happened. The server was turned off and the cloud hosting company has turned off the server. We just found out there was a hidden database on the server that was turned off and the hosting company will not work with me to turn it back on so I can transfer it over to the new server.
My plan was to do a Bare Metal restore using the restore points I took of this server to a Hyper-V VM (I have done with before with this product and it worked fine.)
When I boot into VEEAM's PE environment I go through all the steps, put in the correct account to authenticate to the network share which holds the VEEAM restore points. I have about 20 restore points there and it can see them perfectly but the job fails.
The error message states, "Shared memory connection closed. Failed to download disk. Agent to process method (DataTransfer.SyncDisk) Exception from server. File does not exist. [Path of backup location]".
Has anyone seen this before? Attached is a screenshot
Things I know:
1. It's not a authentication issue.
2. I have tried multiple restore points. It is not just one restore point I get this error on.
3. I expanded the disk to 238 GB. I don't believe it is a space issue because I tried to restore the C drive which was only 80 GB
Any help is greatly appreciated.
veeam_error.png
-
3
2
5 Comments
Active today
Hi
When I see this error, is regarding the Datastore where we trying to restore the VM.
Are all Veeam services running?
Have you import the Backup to the Veeam?
When I see this error, is regarding the Datastore where we trying to restore the VM.
Are all Veeam services running?
Have you import the Backup to the Veeam?
Active today
Hi
Just to let you know, that Veeam supports also the free edition.
So if tou need to open a support ticket in Veeam for this product, you can.
Just to let you know, that Veeam supports also the free edition.
So if tou need to open a support ticket in Veeam for this product, you can.
Hi,
Thanks for the reply, again this is the free VEEAM Endpoint backup. There is only 1 service installed on the Hyper-V host. This isn't the full suite. I have already opened a case with VEEAM but thought I would try here too. I am still scratching my head on this.
ANYONE?.. HELP! I need to get this database transferred over and can not do that without this restore.
Thanks for the reply, again this is the free VEEAM Endpoint backup. There is only 1 service installed on the Hyper-V host. This isn't the full suite. I have already opened a case with VEEAM but thought I would try here too. I am still scratching my head on this.
ANYONE?.. HELP! I need to get this database transferred over and can not do that without this restore.
Hi all,
I resolved my own issue. But I wanted to post this in case someone has the same issue.
The backup chain has corrupted. The reason being is that the chain's metadata did not align with the backup files themselves. This typically occurs when the merge process does not complete correctly usually due to some network issues or perhaps on the target storage side being unable to complete this process. In such cases, the metadata file does not get updated and which leads to the chain being corrupted.
What I had to do was rename my VBK file in the share the backup jobs were located in to be the correct name in the string. In my case. The correct file name should be "Backup Job AWHS-DC2016-10-12T003023.v
This took me like 12 hours to figure out so I hope it helps someone in the future.
My suggestion is to open a ticket with VEEAM and they will point you in the right direction.
I resolved my own issue. But I wanted to post this in case someone has the same issue.
The backup chain has corrupted. The reason being is that the chain's metadata did not align with the backup files themselves. This typically occurs when the merge process does not complete correctly usually due to some network issues or perhaps on the target storage side being unable to complete this process. In such cases, the metadata file does not get updated and which leads to the chain being corrupted.
What I had to do was rename my VBK file in the share the backup jobs were located in to be the correct name in the string. In my case. The correct file name should be "Backup Job AWHS-DC2016-10-12T003023.v
This took me like 12 hours to figure out so I hope it helps someone in the future.
My suggestion is to open a ticket with VEEAM and they will point you in the right direction.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Why should I virtualize? It’s a question that’s asked often enough. My response is usually “Why SHOULDN’T you virtualize?”
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365. In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Watch the software video of Kernel Import PST to Office 365 tools which can easily import PST and OST files to Office 365 for bulk mailboxes. The process of migration is simple and user can map source and destination mailboxes and easily import data…
A query can call a function, and a function can call Excel, even though we are in Access. This is Part 2, and steps you through the VBA that "wraps" Excel functionality so we can use its worksheet functions in Access.
The declaration statement de…
Suggested Courses
Course of the Month4 days, 11 hours left to enroll
587 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.