Guest Files Restore Failed Since VeeamBR 13 Upgrade

[AlexLeadingEdge]

Case # 07960361

I have just gone to do my first file restore since the upgrade to VeeamBR 13 and the backup copies are failing to open, citing an issue with the Mount. The backups open but I'm unable to copy any files from the selected backup, the OK button is greyed out after I've select what folder I want it to go into. I also can't restore back to the original server, it times out and fails.

[Mildur]

Hi Alex

Regarding backup copies failing to open — our support team has noted that some backup files are missing. Please continue working with them so they can properly investigate the issue.

As for Copy To, it’s a documented limitation introduced with V13.

If the Veeam Backup & Replication console is launched on the backup server, the Copy to operation does not allow copying files to the backup server. You can only copy files to a network shared folder.

Best,
Fabian

[AlexLeadingEdge]

Hi Fabian,

As for Copy To, it’s a documented limitation introduced with V13.

Is that a bug or a feature?

[AlexLeadingEdge]

For security reasons the backup server is not a part of the domain, that way a computer virus on the domain can't destroy the backups (as recommended by Veeam!!!), so we have to save the files locally to the backup server then move them across to the domain using domain credentials. I did try the restore back to the original location using the domain credentials but it just hung and then timed out (and no cancel button so I had to wait for it to time out, thankfully there was a timeout otherwise I would have had to crash out of VeeamB&R 13).

Knowing this new limitation I was able to save the files to the backup server through the network using its UNC path name, and then copied them across to the domain. A bit painful!

[Mildur]

Hi Alex,

This was done intentionally, so it’s not a bug.
However, we’re currently exploring options to make it possible to re-enable this feature optionally for customers who still require this functionality.

For security reasons the backup server is not a part of the domain, that way a computer virus on the domain can't destroy the backups (as recommended by Veeam!!!)

For security purposes we also recommend using a dedicated management server with the backup console installed to manage the backup server. That would immediately resolve the “Copy To” situation.

In general, there’s no need for anyone to work directly on the backup server — doing so may only increases the risk of a “computer virus” becoming active on the backup server, especially if those user accounts have local administrative permissions.
Did you have considered the approach with a dedicated management machine?

Best regards,
Fabian