Skip to main content
  • EN

Question about VEEAM licensing in the context of a storage/server migration project:
Old VEEAM server license:

  • Veeam Backup & Replication v12 Build 12.3
  • Subscription license for Enterprise Plus
  • 110 Instances (76 Used: 75 VM + 1 Server)

The new VEEAM server is not connected to the old storage or old server.

So the VM backup migration has to follow the VM server + storage migration: activate new backup for a VM when VM is migrated to new storage/servers. Whole process expected to take 2 months max.

Can we license the new VEEAM server with the same subscription without deactivating the old VEEAM server? Can we do it without deploying an Enterprise Server?
We will never pass above the number of currently used instances because a VM cannot be backed up on old and new at the same time.
Thanks,

Francis

Hi ​@frvandun ,

would it not be possible to migrate the old Server to the new on by using the configuration backup?

Then you can have the old and the new repository on the new Server and just migrate the Backup-chains via “V-Mover” to the new Storage without having to Backup Servers.

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120

 

Regards

Chalid

The other option you could do is request a trial license which you could utilise for the migration. 

For the purposes of migration..yes, you could use the same license. You would be going against EULA if you used a 2nd server and the same license as “double-dipping” so to speak. But, I agree with ​@CMF here and wonder why you’re not simply doing a config DB restore?

Hi ​@frvandun ,

would it not be possible to migrate the old Server to the new on by using the configuration backup?

Then you can have the old and the new repository on the new Server and just migrate the Backup-chains via “V-Mover” to the new Storage without having to Backup Servers.

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120

 

Regards

Chalid

This is what I would do if you can as it will not violate the license agreement.

For the purposes of migration..yes, you could use the same license. You would be going against EULA if you used a 2nd server and the same license as “double-dipping” so to speak. But, I agree with ​@CMF here and wonder why you’re not simply doing a config DB restore?

Thanks, it’s indeed only for migration.
Old VBR is connected to old SAN switches, old storage, old ESXi servers. The new servers to new SAN, storage, ESXi. There is no interconnection between old and new except over 1G IP network.  The VM’s will be migrated via swing host or network and then backup job will be activated.
PS: I did use config restore to copy all the jobs etc. but I redefined a new library and media pools. The config restore does not install the license.

Correct...to do the config restore, you have to install Veeam, import the license, then do the config restore. Sounds like you’re about all sorted.

For the purposes of migration..yes, you could use the same license. You would be going against EULA if you used a 2nd server and the same license as “double-dipping” so to speak. But, I agree with ​@CMF here and wonder why you’re not simply doing a config DB restore?

Thanks, it’s indeed only for migration.
Old VBR is connected to old SAN switches, old storage, old ESXi servers. The new servers to new SAN, storage, ESXi. There is no interconnection between old and new except over 1G IP network.  The VM’s will be migrated via swing host or network and then backup job will be activated.
PS: I did use config restore to copy all the jobs etc. but I redefined a new library and media pools. The config restore does not install the license.

Then you should be good and once you decom the old VBR server you are not “violating” the EULA. 😉

 
 
 
Terms & ConditionsAccessibility statement