File Level Restore Failed after a Full Server Restore V8

[lukeroom]

Hello together,

We have a problem with a Single Files Restore with the option "Restore" in Veeam B&R V8. ( Case # 00693492)

Discription:
# Backup a Server
# Delete this Server
# Restore the complete Server complete (New mo-ref ID)
# Single File Restore Failed because veeam can´t find this server because he become a new mo-ref id after the full restore.

Additional Information:
Copy-To Option works not correct (Veeam can´t restore softlinks correct)(Case 00693488)
FTP in Single File Restore works not correct (date of files are incorrect after a restore)
Mapping of vmdisk don`t work (double PV´s because of lvm2)

Can everyone help us?
Thank and regards

[foggy]

Lukas, you're correct in that FLR to original location into a VM that was previously restored via full VM restore is not possible due to the changed moref of the restored VM. Have you tried the restore to another location option, which allows to select the newly restored VM as a restoration target?

[lukeroom]

Hi foggy,

we have this problem with other restore-options:
Copy-To Option works not correct (Veeam can´t restore softlinks correct)(Case 00693488)
FTP in Single File Restore works not correct (date of files are incorrect after a restore)
Mapping of vmdisk don`t work (double PV´s because of lvm2)

is that what you mean?

[foggy]

Yes, sorry for missing that. What if you start Instant Recovery of that VM and copy the required files from it?

[lukeroom]

Hey,
this is not an option for us.
We habe by the instant recovery option douple ip-address in our network.
And we have here also auditing problems. We musst automatically log als restore operations.
regards

[veremin]

You can uncheck "Connect to VM network" option and make VM both connect to an appropriate network and get different IP address manually later on. Thanks.

[lukeroom]

Thanks for the tip.
I know the workarounds / detours already. Thats not the problem

But as already mentioned:
And we have here also auditing problems. We musst automatically log als restore operations.

We can only log the restore, when we use the option "copy-to" or "restore".
But the restore operation doesn´t work after a full restore and the "copy-to" have problems with restore links.

[foggy]

As far as I can get from the Copy To option case notes, you were provided with a fix solves that issue. So can you use this option after applying the fix?

[lukeroom]

Hi,

my case escalate to next tier. I musst waiting for a reply.

Yes, when it work, we can use this option. (if another error is corrected with the link-restore Case# 00693488)

regards

[foggy]

Not sure there are other options available, given all your requirements. But let's wait for what the next tier engineer could suggest.

[lukeroom]

Good morning,

error is not resolved with patch 1.

regards

[foggy]

Lukas, do you mean the Copy To option issue you're provided with the fix for (within the case 00693488)?

[mikeely]

Steps to reproduce:

1. Delete VM (oops!)
2. Restore entire VM including registration
3. Try to do an FLR restore from a backup before VM was deleted

I've looked at the tool in KB2136 but it doesn't appear to be a good fit for this problem. Current workaround is just to restore the file elsewhere and manually copy it over, but ugh. What's the real solution?

[Mike Resseler]

Mike,

This is actually something I have never done before. Mostly I have a recovered (entire) VM and after that new backups are being taken. FLR then comes from newer backups. But the scenario is clear and I am not sure why this is failing.

1. What version of VBR are you using (including update version)
2. Was it instant VM recovery or entire (I assume entire VM)
3. VMware / Hyper-V
4. What is the exact error that you get when trying to do this?

[veremin]

So, you're trying to restore file to original location, when original location is gone (restored VM gets a new ID assigned and cannot be considered the same VM therefore) and get the said error? Thanks.

[mikeely]

1. What version of VBR are you using (including update version)
2. Was it instant VM recovery or entire (I assume entire VM)
3. VMware / Hyper-V
4. What is the exact error that you get when trying to do this?

1. VBR 9.5 Update 1 (RC)
2. Entire VM
3. VMware
4.

Code: Select all

Fault "ManagedObjectNotFoundFault", detail
"<ManagedObjectNotFoundFault xmlns="urn:vim25"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><obj
type="Virtual Machine">vm-1720</obj></ManagebObjectNotFoundFa
ult>"
The object 'vim.VirtualMachine:vm-1720' has already been deleted or
has not been completely created

[mikeely]

So, you're trying to restore file to original location, when original location is gone (restored VM gets a new ID assigned and cannot be considered the same VM therefore) and get the said error? Thanks.

Yes, exactly. I am looking for a way to teach Veeam that all the backups associated with the old VM should now be associated with the new VM with the exact same name. Update foo set indexid = newid where indexid = oldid. It can't be much harder than that. And will certainly be less troublesome than being confronted by the likes of this two years from now (screenshot from the "Choose the virtual machine" pane in the FLR wizard):


Imagine having this happen a couple times and then having to try and remember "which iteration of testdb.noc was this backup taken from?"

Far better to have the option (not automatic, but the option) to merge backup families.

[foggy]

Hi Mike, you can match VM IDs in Veeam B&R database with the help of support.

[Delo123]

How should Veeam know it's the same vm? Just by the name?
If one deletes a VM and creates (restores) a new now, this will be visible from the next backup (as in the screenshot), so you know from this point on it's a new vm. Even in 2 years you will still be able to see that, since the restore points before belong to the old vm. Don't really see the issue here.

[mikeely]

How should Veeam know it's the same vm?

As I said, by configuring Veeam to see it that way. I don't expect it to Just Happen.

Don't really see the issue here.

Perhaps you were only looking but you did not see.

[Delo123]

Hi Mike,

You are right, i actually missed the part where you said you would like to trick Veeam to think it's actually the same VM, my bad! Let's see if you will get it working

[mikeely]

Where is any of this trickery? I restore a VM from a backup. That's the same VM. VMWare indexes it differently, which makes sense. From a functional perspective they are the same VM and it makes sense to be able to configure Veeam to see this when needed.