The client can then simply create a mirror of current backups and/or off-load long-term backups to the secure object storage target. With AWS S3 or Azure Blob object storage, these GFS backups can be tiered further on into the Archive Tier for long-term retention and cost-optimization.īy leveraging Object Storage either from in-house (S3-compatible) or a public cloud vendor (such as AWS, Azure, Google, others), the service provider can provide off-site backup storage for the client. ![]() Second, the Backup Storage can be tiered to an Object Storage to provide an additional (immutable) copy of all backups or only to off-load GFS backups.First, the Backup Storage can be located on a Hardened Linux Repository providing immutability and ransomware protection.At the back-end the Backup Storage can be further on protected: The client can then simply point backup (or backup copy) jobs to it as a secure backup target destination. (option 1 in the diagram below)īy leveraging Veeam Cloud Connect, the service provider can assign a storage quota on their backup repository for the client. The storage exposed by the service provider can be one of the following options:Ĭloud repository. ![]() The service fundamentally exposes a storage space where customers can safely store their data. A Service Provider can build a Veeam-powered service to provide Off-Site Backup to their customers allowing them to support the 3-2-1 rule, without the need to invest on expensive infrastructure themselves, rather renting it as a service from a Service Provider. The general best practice and recommendation for data protection is to follow the 3-2-1 rule: three copies of your data, on two different media, one being off-site.įor most companies the biggest challenge is achieving the off-site copy. This site uses Just the Docs, a documentation theme for Jekyll. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |