Skip to main content
  • EN

Hello!

I’m currently running VBR CE v11.0.0 on Windows Server 2012 R2.  We are only backing up a total of 4 VMs.

My initial task was to move a couple of the backups to a new backup repository.  But, the ‘move’ functionality apparently isn’t available in v11.  Rather than try to upgrade our current instance of Veeam, I’d like to just install a the newest version of VBR CE on a new instance of Windows Server.

My question is: Keeping in mind the difference in versions, should I be able to take a backup of the DB config and import it to the new Veeam install as suggested here?  If the difference in versions is an issue, what’s the best way forward?

Once I have a new instance up-and-running, the ability to move the backups to new repositories should be available, I believe.

Please let me know if I can provide additional information.

Thanks!

Yes as per that link you can do the restore of the configuration backup as long as you are using the required version and same database format for the new install.

Hi, 

As @Chris.Childerhose said, shouldnt be an issue.

Just make sure, if you install a new VBR from scratch, to backup the config from the “old one” and migrate it to the new one.

Remark, stop and disable all the jobs before taking the lates config backup for migration.

cheers.

My thanks to you both!  I will give it a shot.

Hopefully a quick follow-up here is okay. . .

I didn’t really think about this before, but would there be any issues with just creating new jobs on the new instance -- as opposed to moving the existing jobs/backups?  I guess I’m asking to make sure there won’t be any conflict with components previously installed with the v11 installation (Transport, Hyper-V Integration, etc.).

As for our requirement/use case: we only backup VMs to restore from catastrophic failure, so as long as there is at least one full backup of each VM to restore from, that should be good (i.e., we’re not concerned with restoring from several days ago).

 

Thanks!

Hopefully a quick follow-up here is okay. . .

I didn’t really think about this before, but would there be any issues with just creating new jobs on the new instance -- as opposed to moving the existing jobs/backups?  I guess I’m asking to make sure there won’t be any conflict with components previously installed with the v11 installation (Transport, Hyper-V Integration, etc.).

As for our requirement/use case: we only backup VMs to restore from catastrophic failure, so as long as there is at least one full backup of each VM to restore from, that should be good (i.e., we’re not concerned with restoring from several days ago).

 

Thanks!

Yes you can recreate jobs on the new instance to start fresh without a doubt.  There is no need to restore if that is the route you will take.

Comment


Terms & Conditions