I upgraded to v9.5 a few days ago. I run Backup Copy jobs to a Veeam cloud provider for DR replication purposes, and I had to wait for them to upgrade to 9.5 first. My issues:
#1 (MAJOR) - The Backup Copy process uploaded new Full backups for 2 VMs instead of incremental, and it did this 2x for one VM, 3x for the other. Now finally these are running incremental. It was a painful process, as these uploads spilled over into the workday and severely slowed internet access for the users. I have a case open, but don’t know if I’ll pursue it, as long as things run incremental as required.
#2 (MINOR) - Not sure how to describe this one. I have 4 sites. HQ has a number of hosts & VM backup jobs, the other 3 sites have 1 VM/backup job. As I upgraded each host to v9.5, a Components Update screen appeared which listed all Backup Copy jobs, and indicated “Legacy backup”, they needed to be upgraded.
I upgraded the jobs that pertained to the site being upgraded as I did each site, and that seemed to work.
Now all upgrades are done now, but each site thinks the Backup Copy jobs for the other sites still need to be upgraded. It still shows them as Legacy backup even though they are upgraded. Rescanning the repository doesn’t help. And if I try to run the upgrade again, it fails with an error that “Unable to map service provider side to tenant cache because it is already mapped...”
#3 (MINOR) – Probably a consequence of the previous issue. Backup Copy jobs show in duplicate, with one having a yellow mark, for any jobs that Veeam thinks are still in Legacy mode.
Previous versions of Veeam would had a “Remove from configuration” option but that’s not available anymore. I’m not clicking Delete from Disk until I talk to Support.
In summary – no issues so far with local backup, but cloud BC jobs have not gone well.