Legacy Windows Backup Copy

[perjonsson1960]

Folks,

I still have ONE "Legacy Windows Backup Copy" job remaining. It is configured for Pruning, and should start at 11:45 pm. However, the job seems to disregard that setting, and the backup copy is done directly after the primary backup job has finished, during the night, thus behaving like a Mirror job. I am not complaining, because this is probably a good thing, but I am just wondering if this is an expected behaviour? This may have started with v12.1 or even 12.2, I'm not sure.

This particular backup copy job is for our physical file server cluster with about 20 TB data. It is a GFS chain on a hardened repo, and if I want to replace that job with a new backup copy job, I fear that a new GFS chain needs to be created, starting from scratch with a full backup? I don't know if the new job can "inherit" the old chain, and continue on that?

Kind regards,
PJ

[perjonsson1960]

A week has passed, and no reply. Perhaps I can find answers in the Help Center.

Kind regards,
PJ

[ybarrap2003]

Hi @perjonsson1960 This is what is available about "Upgrading Backup Chain Formats" in the Veeam documentation - https://helpcenter.veeam.com/docs/backu ... ml?ver=120 I would read this over. If you have any concerns open up a support ticket

Thanks,
Pete

[perjonsson1960]

Thanks!

After reading that, I guess that I am basically up shit creek without a paddle because of this:

"[For periodic copy mode] You can not upgrade the backup chain format of Windows agent failover cluster backups."

I guess I will have to delete the current Legacy Backup Copy Job, and let the chain go orphaned, and then create a new backup copy job, and start with a full backup copy of 21 TB, and lose the advantage of the dedupe in the old chain.

Or, I can simply keep the Legacy job until it is not supported anymore.

PJ

[perjonsson1960]

Folks,

Hello again!

Are Legacy Backup Copy jobs still supported if I upgrade to VBR v13.0?

Kind regards,
PJ

[perjonsson1960]

Folks,

Since I didn't get any reply in my old thread about this, I am creating a new one...

Are Legacy Backup Copy jobs still supported if I upgrade to VBR v13.0?

Kind regards,
PJ

[david.domask]

Hi Per,

Upgrade will be blocked if there are existing Legacy Backup Copy Jobs, so it should be planned to clear those prior to upgrade.

[perjonsson1960]

That is unfortunate... We have only one such job left, and for good reason; It is the agent backup copy job for our physical file server cluster, with around 21 TB data, and a GFS chain with 4 weekly, 12 monthly and 2 yearly full backups, on a hardened repo.
And as far as I can understand, this backup chain cannot be moved to a new job, because of this limitation:

"[For periodic copy mode] You can not upgrade the backup chain format of Windows agent failover cluster backups."

And perhaps it is not even possible to move a backup chain that resides on a hardened repo. So I guess we are up sh*t creek without a paddle with this one... I suppose we just have to delete the legacy job, and make the chain orphaned, and start anew with a 21 TB full backup, and lose the benefit of dedupe present in the old chain.

PJ