On an HP Proliant DL385 Gen 10 I am trying to restore the OS drive with VEEAM and experiencing a problem. Each OS backup I have is in the VBM format.

I have created a VEEAM recovery media on a USB drive. When I boot to the VEEAM recovery media and attempt a disk restore, I get an error message saying that the VBM data files will not permit a restore. From within Winders Server 2019, I open VEEAM select home, backups and select the OS I would like to restore, the error message says I can not restore to a live machine. I nned to slect a different drive.

I thought I had a several good OS backups, but it seems I don’t understand the restore path.

I have been gong through the VEEAM site and much of what I have seen is based on VM, not bare metal restore.

Any assistance would be helpful !

Thank you

3 Spice ups

I assume you mean Windows server 2019.

The VBM file you have, will need any incremental files with it too, Veeam can also connect to a share to restore from there.

I would ask though, is a full OS restore necessary, what issue are you facing to need this if it’s bootable?

Everything is running fine on our Windows Server 2019 except our SQL Database with its unsupported ARMS application. We had errors with the ARMS application and I attempted an re-install, since we are no longer under a technical support contract. ARMS technical support will not preform any support unless we pay them $5300 for the year. I attempted the re-install, it first removed all present portions of the applications and then without the required password (ARMS Certificate) the application install fails. No, ARMS technical support will not provide any assistance, even the password. Our SQL ARMS database is still fine, just can’t access it through the required application. All data files and pertinent information is on a different drive, just the ARMS Database, programs and windows sits on the OS drive. I was thinking a OS restore to three days ago (last restore point), then restore the Database to before the error and all would be well. I’m open to suggestions

almost say the vbm which is the Veeam Backup Metadata is irrelevant… You want to make sure you have the .VBK file which is the full backup file. Then any .VIB files which are the incrementals up to the desired restore point. I haven’t had any luck restoring those lately from just a file folder, only from a Veeam repository.

EDIT: It must work though, I used to take backups using the agent direct to USB and then restore from USB using the Veeam restore media.

EDIT2: Does the server in question have access to any Veeam repository you could copy the .vbk and .vib files to? Could you create a disk or virtual disk somewhere that it has access to and then create a repository on that disk, then copy the files to it? For some reason that was the only thing I could do to get backups restored from the console for last several rounds of restore testing I did.

1 Spice up

Just a note that Veeam support is pretty good. They can certainly help you out here too.

4 Spice ups

Then I would say it isn’t fine.

Has this expired, if so restoring to 3 days ago, even if you succeed may only give you 3 days before there is an issue again,

Why not just restore the database, why does the whole OS need to be done?

You take a risk when you don’t pay for support, unfortunately there are times support is required. This may be one of them if this is a certificate issue.

The certificate has not expired, but the ARMS software installation guide requires a certificate password to complete the ARMS software installation.

The SQL database is without error. The problem is with the ARMS application that accesses the SQL database. That affects the Windows registry, windows services and the ARMS application folder. That why I am looking to restore the OS drive.

Its looking like we will have to pay support, even though we are winding down the use of the application.

Which Veeam product, version and edition ?

Was the backup you’re restoring from, a full backup or an incremental? Is it possible to post a (redacted if necessary) copy of the actual error?

I got more of a feeling that wrong product was used and/or expectations from other product is not the same as the one OP was looking at ?

Coz “Veeam” is a brand like “Microsoft” and they have like 29 different products (or variants).

We are using the Veeam back and replication, version 12.2, community edition. This is on a HP Proliant DL385 Gen 10 with Windows Server 2019.

With the help of this community I realized that I am trying to restore the OS with the wrong backup format. After searching, I do have the .VBK file. When I preformed the “Entire Computer” backup procedure, that file format of .VBK is used. I have two copies of this stored on an external drive, for offsite. I should be able to do a full restore from that backup.

I greatly appreciate the assistance I have received from this community!

Thank you!

2 Spice ups