Does the upgrade to 9.5, reseed ?

[MichaelOZ]

we have experienced it before when we have done an upgrade to Veeam the WAN Copy Jobs are forced to reseed, I need to confirm that this will not happen with going from 9.0.0.1715 to 9.5 ?

can anyone confirm that has already done the update they haven't had to reseed the WAN Copy Jobs ?

thanks in advance

Michael.

[foggy]

Hi Michael, normally this shouldn't happen. Do you remember the actual reason that caused the need to re-seed the copy jobs? For example, enabling per-VM chains on the target repository requires active fulls to be performed (not the upgrade itself).

[ober72]

Hi Alexander,

If we enabled per-Vm's on the repositories my understanding is that all new jobs created and targeted to that repository going forward will be per-vm but existing will continue as they were before. I believe that this was the behavior when per-vm repositories were introduced on local repositories.

thanks

[foggy]

Active full on existing job also resulted in per-VM backup files from that moment on.

[ober72]

Ok that is good. Yes I remember the active fulls, I just got worried that all my existing jobs targeting that offsite repository would want to do automatic active fulls

thanks

[foggy]

No, only if you'd like to switch to per-VM.