Skip to main content
  • EN

Hey folks,

I work for a Veeam Reseller/MSP and have a quick question about per-VM backup chains.

We have a tenant who's switching their local backups from legacy to per-VM format. On our end, all of our Cloud Connect repos are already set up for per-VM.

Once they make the switch locally, will their backup copy jobs to us just keep going with incrementals since our side is already per-VM? Or will this trigger a new full backup on the service provider side?

Ideally, we’re hoping the chain just continues without needing a new full. Just wanted to check if anyone’s been through this and can confirm.

Thanks!

The chains “should” continue as they are already set that way for the copy jobs.  The only thing to me that would be affected might be their local backup jobs.

I deal with VCC daily as I work at an MSP as well in Canada and this is how we have things configured since the new format has come out.

Thanks for the reply. This confirms it. I was just wondering how that would work. But i’m glad it will be an incremental backup moving forward for me.

Thanks for the reply. This confirms it. I was just wondering how that would work. But i’m glad it will be an incremental backup moving forward for me.

Not a problem. I deal with VCC architecture daily so if you have any other questions just post them.

The backup chain on their local repository is completely separate from the chain in the cloud repository. It will continue to be per-vm regardless of what they have set on their repository.

You shouldn’t see any new full being created as a result of their change.

Thank you for chiming in ​@Tommy O'Shea I am pretty confident now. 

Comment


Terms & Conditions