1/21/2024 0 Comments Veeam backup server best practicesIn a world of “incremental forever” backups, the network is sometimes forgotten, because of the low bandwidth requirements of the “incremental forever” approach. Networking is a key factor in ensuring the Hardened Repository can help achieve recovery point objectives (RPO, how much data maximum can be lost) and recovery time objectives (RTO, how much time a restore would take). Start with two rack units, 12 data disks and two disks for the operating system. If you have a small environment, don’t worry. With Veeam native data reduction plus XFS space saving (block cloning), that can be up to 100 PB logical data in one rack with a backup speed up to 420 TiB/h. A rack full of high-density servers give around 8 PB native capacity. That approach scales linearly, because with each new Hardened Repository node, there is more CPU, RAM, RAID, network, disk space and IO performance. Future blog posts will cover topics such as preparation and planning, securing a Linux system and integrating into Veeam Backup & Replicationįor those who are impatient, use (high-density) servers with internal disks. This blog post will show how to select and prepare the environment for a physical server that will later be used as Hardened Repository. Hardened Repositories help to ensure immutability for Veeam backups while meeting the 3-2-1 rule and combining Hardened Repositories with other immutable options like object lock on object storage or WORM tapes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |