https://helpcenter.veeam.com/docs/backu ... acity-tier
"IMPORTANT
With both the Copy and Move policies, Veeam Backup & Replication copies and moves to the capacity tier only non-active backup files created more than 24 hours ago, which match the capacity tier configuration parameters. For details, see Backup Chain. To learn more about the capacity tier configuration, see Add Capacity Tier in the Veeam Backup & Replication User Guide."
I understand the reasoning behind this with the "Move" policy but I'm a little confused as to why we can't have the immediate copy. This is very frustrating. There are already so many restrictions on storing SQL plug in backups that we have had to work around and this one just hit us in the face. We are trying to keep all our immutable copies in Wasabi. We back up to local disk and then scale out to Wasabi. We use scale out repositories for pretty much everything and on our "normal" VM backups, as soon as it backs up we get a copy in the capacity tier. At the time of backup or very soon after, we have our production system, immutable copy, and third location copy all done. With the SQL plug-in, we want the same functionality. It isn't really "safe" these days to wait 24hrs before you have your data to an offsite location and have an immutable copy. I realize the article states that you can contact support if you want to use a hardened repository and can change the 24hr timeframe but that doesn't get the data offsite and then we have immutable copies in different locations. We don't like not having to wait to have an immutable and offsite copy, it feels like we're running with scissors. Is this going to be changed/improved?
"IMPORTANT
With both the Copy and Move policies, Veeam Backup & Replication copies and moves to the capacity tier only non-active backup files created more than 24 hours ago, which match the capacity tier configuration parameters. For details, see Backup Chain. To learn more about the capacity tier configuration, see Add Capacity Tier in the Veeam Backup & Replication User Guide."
I understand the reasoning behind this with the "Move" policy but I'm a little confused as to why we can't have the immediate copy. This is very frustrating. There are already so many restrictions on storing SQL plug in backups that we have had to work around and this one just hit us in the face. We are trying to keep all our immutable copies in Wasabi. We back up to local disk and then scale out to Wasabi. We use scale out repositories for pretty much everything and on our "normal" VM backups, as soon as it backs up we get a copy in the capacity tier. At the time of backup or very soon after, we have our production system, immutable copy, and third location copy all done. With the SQL plug-in, we want the same functionality. It isn't really "safe" these days to wait 24hrs before you have your data to an offsite location and have an immutable copy. I realize the article states that you can contact support if you want to use a hardened repository and can change the 24hr timeframe but that doesn't get the data offsite and then we have immutable copies in different locations. We don't like not having to wait to have an immutable and offsite copy, it feels like we're running with scissors. Is this going to be changed/improved?
Statistics: Posted by srlarsen — May 06, 2024 4:35 pm
