Hi Rajamanivel,
Capacity Tier and Archive Tier are tools to help you both achieve 3-2-1 by having additional copies of your data on different and non-local storages, as well as helping to manage your local storage by tiering the data off to longer-term storage locations. One of the big benefits of Object Storage (S3) is that the management of the storage is handled by the S3 provider/system, and all the guarantees of data integrity that S3 offers help reduce your required maintenance and support to ensure you have stable, accessible, and safe off-site copies of your data should you be impacted by for example ransomware or a full site outage (e.g., massive hardware failures, etc).
Ultimately this is a decision that needs to be made by you and your team on how you best want to ensure you're having sufficient redundancy and protection of your backup data, and Object Storage is simply one of many ways that you can use to accomplish this, even in combination with other methods like backup to Tape or to other long-term storage appliances.
Veeam's Scale-out Backup Repository (SOBR) concept works to ensure that much of this is automated, that is, you point backups to a SOBR and the management of the data is handled automatically based on the rules you define. Our User Guide on Capacity Tier (and Archive Tier) gives some examples as to use cases where the tiering is applicable, but ultimately it's about ensuring you have redundancy, security, and reliability with ease of management.
In your specific example, Capacity Tier and Archive Tier (or one or the other as of 12.2) means you can offload (copy or move or both) your data to longer term storage to allow you to maintain your backup strategy while keeping on-premises storages (for example) free to host more data for short term restores, while placing the older restore points that you likely won't need as frequently but still have a requirement to keep on accessible storage with reliability and accessibility guarantees.
Capacity Tier and Archive Tier are tools to help you both achieve 3-2-1 by having additional copies of your data on different and non-local storages, as well as helping to manage your local storage by tiering the data off to longer-term storage locations. One of the big benefits of Object Storage (S3) is that the management of the storage is handled by the S3 provider/system, and all the guarantees of data integrity that S3 offers help reduce your required maintenance and support to ensure you have stable, accessible, and safe off-site copies of your data should you be impacted by for example ransomware or a full site outage (e.g., massive hardware failures, etc).
Ultimately this is a decision that needs to be made by you and your team on how you best want to ensure you're having sufficient redundancy and protection of your backup data, and Object Storage is simply one of many ways that you can use to accomplish this, even in combination with other methods like backup to Tape or to other long-term storage appliances.
Veeam's Scale-out Backup Repository (SOBR) concept works to ensure that much of this is automated, that is, you point backups to a SOBR and the management of the data is handled automatically based on the rules you define. Our User Guide on Capacity Tier (and Archive Tier) gives some examples as to use cases where the tiering is applicable, but ultimately it's about ensuring you have redundancy, security, and reliability with ease of management.
In your specific example, Capacity Tier and Archive Tier (or one or the other as of 12.2) means you can offload (copy or move or both) your data to longer term storage to allow you to maintain your backup strategy while keeping on-premises storages (for example) free to host more data for short term restores, while placing the older restore points that you likely won't need as frequently but still have a requirement to keep on accessible storage with reliability and accessibility guarantees.
Statistics: Posted by david.domask — Sep 02, 2024 7:50 am