Veeam tracks all VMs by unique moref ID. The upgrade process seems to have resulted in morefID changes. Thus, the jobs containing previously existed VMs failed. Once VMs were re-added to the job, everything started working as expected.

However, I should mention that typically in-place upgrade shouldn't lead to morefID changes.

Thanks.

1. No issues with that. Just make sure that the VB&R installation is protected. You can ensure it with the use of configuration backup.
2. How big your infrastructure is? We typically recommend using full SQL for infrastructures bigger than 1000 VMs.. Otherwise, SQL express is more than enough.

Thanks.

Moreover, I've created previously a script example to demonstrate how VMs can be backed up with the use of now available commands. Might be worth taking a look.

Thanks.

A small trick regarding usage of configuration backup.

If you have a network share, you can create a share disk, map it to instance of VB&R and use as a target repository for configuration backup. Should any disaster situation happen (VB&R server goes down, for instance), all you would need to do is to install Veeam on any other virtual/physcial machine and import previously backed up configuration.

Thanks.

@JaredBusch You're welcome. If any assistance with scripting is needed, feel free to reach me either here or on our community forums.

http://forums.veeam.com/

Thanks.

@LAH3385 on a machine that has Backup and Replication Free Edition installed.

The code is accompanied by detailed line by line description, and there are just a few lines that you need to change, such as Hyper-V server name, VM names, so it doesn't require any advanced scripting knowledge.