Comprehensive data protection for all workloads
Post Reply
YoMarK
Enthusiast
Posts: 57
Liked: 8 times
Joined: Jul 13, 2009 12:50 pm
Full Name: Mark
Location: The Netherlands
Contact:

Veeam 12: being forced to upgrade backup chain format

Post by YoMarK »

Good day everyone,

I postponed the inevitable for some time, up until now I did not upgrade to new backup format.
However, now I have to because I have new backup jobs that can't be used in de backup copy jobs.

The main issue why I postponed.... I have a 350TB immutable XFS repository(year retention time) that is filled by periodic backup copy job(synthetic full's). It has about 130TB free. (And about 998TB used not accounting de-duplication)
I fear that upgrading jobs(a process that is well documented, so that is not the issue) will get me into trouble: a filled up repo without being able to do anything about it. I do not want to delete older backups, but I can't even fix it like that because it's immutable.
I feel that I have to gamble if it is "going to fit", and I do not like this.
Does anybody have tips&tricks? Any insights are appreciated.

Thank you in advance.
--Mark
Mildur
Product Manager
Posts: 10693
Liked: 2894 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam 12: being forced to upgrade backup chain format

Post by Mildur » 1 person likes this post

Hi Mark
will get me into trouble: a filled up repo without being able to do anything about it.
The upgrade is FastClone aware on XFS. Meaning it won't need additional space: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

I assume you have multiple backup jobs for 350TB? I suggest to run the upgrade on one job and then compare the storage usage before and after the upgrade.

Code: Select all

Veeam Backup & Replication uses Fast Clone for the following operations:
- To upgrade the backup chain format for backup copies created in the periodic copy mode.
I do not want to delete older backups, but I can't even fix it like that because it's immutable.
There is always an unofficial and not recommended workaround.
Remove the I flag from the backup files as root and you can delete the backup files.
But it should not be necessary. The upgrade uses FastClone to create the new backup chains.
I postponed the inevitable for some time, up until now I did not upgrade to new backup format.
We consider to make the upgrade mandatory for our next major release (v13). If so, then you won't be able to update to V13 if there are still old backup chains.

Best,
Fabian
Product Management Analyst @ Veeam Software
YoMarK
Enthusiast
Posts: 57
Liked: 8 times
Joined: Jul 13, 2009 12:50 pm
Full Name: Mark
Location: The Netherlands
Contact:

Re: Veeam 12: being forced to upgrade backup chain format

Post by YoMarK »

Hello Fabian,

Code: Select all

Veeam Backup & Replication uses Fast Clone for the following operations:
- To upgrade the backup chain format for backup copies created in the periodic copy mode.
Thank you! This is great!
It seems that my worries were for nothing. :)

--Mark
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Google [Bot] and 35 guests