![]() ![]() Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication. All tape backups are stored offsite from the prod DC. You can control this setting with the VSANMaxSnapshotsNum (DWORD) registry value under the 'HKLM\SOFTWARE\Veeam\Veeam Backup and Replication' key on the backup server. My question is - does what I'm thinking make sense? Would there be anything you would do differently? This is my first major DR overhaul so looking at best practice for everything.Īlso, can a Linux repository also act as a tape server via SAS? Our current tape library is connected to the Server 2016 server via SAS. Tape backups would continue to run in the prod site. It is interesting to note the VB365 Proxy might not necessarily use the maximum bandwidth configured as this also depends on the Microsoft 365 throttling limiting the connection speed. My thought was to set up both the prod and DR site with Linux repositories with the DR site having immutability enabled and running VBR/VDRO on a separate Windows host in the DR site rather than the prod site. The best practice is to limit the maximum amount of bandwidth the VB365 Proxy can use. The goal is not to have failover to the DR site but rather offsite backup and immutability. I've just received a new server and have a good opportunity to set things up a little better. Currently, we have a single VBR server running on Server 2016 with a ReFS repo and monthly tape backups all in the same site. Do the math Repositories need to be sized to match the proxies that are in use. A backup proxy reads the source data that an organization backs up and transfers that data to the backup repository. ![]() I am looking at improving our backup infrastructure and adding a DR site. Several best practices for Veeam backup repositories are tied directly to the use of Veeam backup proxies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |