Skip to main content
  • EN

I am running a daily configuration backup, as I should. :-) It is saving to my default repository, which in my case is a locally attached drive on my VBR server. (in fact, I had to do a configuration restore once, so I know that process works).

But I just realized I don’t have a tape job, that copies the configuration backup to tape, in case of full on disaster and the building burns down to slag. And I guess I am drawing a blank, because I am a bit unsure how to set that up.

Do I just need  to do a Tape job, choose a “Files” backup, go to my VBR server, and choose the “VeeamConfigBackup” folder? What about the “VBRCatalog” folder? Anything else I need?

A better way to do this? Obviously I would want this run every day, so it goes onto a tape every day, and once a week, we send all tapes that are FULL offsite for storage.

Sorry if these seem like stupid questions.

Not a stupid question at all, this is actually a good idea.

To get your configuration backup on tape, just create a File-to-Tape job and point it to the folder C:\ProgramData\Veeam\Backup\ConfigBackup. That’s really all you need. The VBRCatalog isn’t critical, since it can be rebuilt if needed, but you can include it if you want to save some time later. The important part is the ConfigBackup. Run the job daily, right after the config backup task, and keep sending your full tapes offsite as you already do. That way you’ll always have what you need to restore your Veeam server even in a total loss.

In a disaster scenario, you’ll first need to bring up a new Veeam server, connect your tape library, run an inventory/catalog on the tapes, and then you’ll be able to restore the configuration backup file and get your environment back.

Not a stupid question at all, this is actually a good idea.

To get your configuration backup on tape, just create a File-to-Tape job and point it to the folder C:\ProgramData\Veeam\Backup\ConfigBackup. That’s really all you need. The VBRCatalog isn’t critical, since it can be rebuilt if needed, but you can include it if you want to save some time later. The important part is the ConfigBackup. Run the job daily, right after the config backup task, and keep sending your full tapes offsite as you already do. That way you’ll always have what you need to restore your Veeam server even in a total loss.

In a disaster scenario, you’ll first need to bring up a new Veeam server, connect your tape library, run an inventory/catalog on the tapes, and then you’ll be able to restore the configuration backup file and get your environment back.

That path only works if that is where the config backups are going - you would need to point the file to tape to the directory for your repository to complete this properly.

Also you might want to look in to object storage like Wasabi to send a copy there as well.  Cannot have too many copies.

Yeah, sorry. You should check the configuration to see where it’s sending the file.

Not a stupid question at all, this is actually a good idea.

To get your configuration backup on tape, just create a File-to-Tape job and point it to the folder C:\ProgramData\Veeam\Backup\ConfigBackup. That’s really all you need. The VBRCatalog isn’t critical, since it can be rebuilt if needed, but you can include it if you want to save some time later. The important part is the ConfigBackup. Run the job daily, right after the config backup task, and keep sending your full tapes offsite as you already do. That way you’ll always have what you need to restore your Veeam server even in a total loss.

In a disaster scenario, you’ll first need to bring up a new Veeam server, connect your tape library, run an inventory/catalog on the tapes, and then you’ll be able to restore the configuration backup file and get your environment back.

OK. In my case, the path is F:\Backup\VeeamConfigBackup, but I get what you mean. I will set a tape job to get that folder, and the VBRCatalog folder (why not, it’s only 12G). Oh, and I’ll have my DBA set up a SQL backup job to write out a BAK of the SQL DB to “VeeamDBBackups” folder, too. Why not, right?

 

Thanks!

Exactly, 12 GB is trivial compared to the peace of mind it gives 😁

I like to point at ​@Chris.Childerhose suggestion once more to backup the config to any offsite S3 storage like Wasabi. This gives you even more flexibility since you’d be able to restore that to everywhere without having to worry about tape restore or even having tape drives available.

 

What many of my customers do: They point the config backup to Wasabi (since we’re a partner) and in case of a DR scenario they re-install a VBR environment in Azure or a private cloud (which can be a DR site from yours as well) and restore the config quickly to have access to the external repositories.

 

I basically like tapes and they a very reliable but the have the simple limitation of “hardware” which is needed for any kind of restore scenario that kills a bit of flexibility.

 

Best

Lukas

3-2-1-1-0 rule right ​@lukas.k 👍 

It is easier to recover from object than tape.

Terms & ConditionsAccessibility statement