I have just logged this with Veeam support #02266249.
I have just changed from a trail license to a paid product.
I had Per-VM ticked in my repository, even though 30 out of 34 backup jobs only have a single server in them. When I applied my new Standard license, my jobs started failing with this error message:
- Code: Select all
1/08/2017 7:37:43 PM :: Job started at 1/08/2017 7:37:41 PM
1/08/2017 7:37:45 PM :: Building VMs list
1/08/2017 7:37:52 PM :: SERVER-NAME is no longer processed by this job. Make sure this change is intentional.
1/08/2017 7:37:52 PM :: VM size: 90.0 GB (35.1 GB used)
1/08/2017 7:37:53 PM :: Changed block tracking is enabled
1/08/2017 7:37:53 PM :: Error: Unable to use per-VM backup file chains due to a product license limitation.
1/08/2017 7:37:55 PM :: Job finished with error at 1/08/2017 7:37:55 PM
Ok so I can see from the comparison chart that Standard licenses don't support Per-VM chains. I can live with this limitation, but I'm struggling with the concepts of having to start my server backups from scratch.
I have tried the below in order to resolve the issue:
1) I un-ticked the repository / advanced / per-vm setting. - retried the job. = job failed
2 ) I created a new job, pointing to a copy of the .vbk files = job failed
3) I created a new repository and remapped the job to the new repository that has never been enabled for per-VM files = job failed .
4) I created a new backup job, pointing to the new repository = job worked = new backup chain.
How can I keep my backup chain, history going now that I have a new license. This is effecting 50 servers in 3 remote office backing up to our DC.
I don't have to complete full backups over the WAN again do I?