Whilst it’s called a rule, I prefer to call it the minimum amount of effort you should invest in your backups.ģ Copies of data, this can include your production, but it’s better when you don’t. To start at the beginning, you should aim to do the 3-2-1-1-0 rule. If that bandwidth is shared between site to site and WAN then WAN accelerator would make sense if you’re planning on uploading to cloud-based object storage too.Ĭurrently we are not so confident in our Backup System so it's time to do it from scratch but do it in a propper way. This checks your backups for general consistency, but you could also leverage SureBackup to perform a fully isolated (sandbox type) restore of your servers. See first option “storage-level corruption guard” Maintenance Settings - User Guide for VMware vSphere () RE the backup checking, yes there’s built in functionality for backup health checks :) As Veeam can still read the data (since it encrypted it after all), it doesn’t impact data efficiency for compression and deduplication. So let’s start with, what is your provisioned bandwidth between the sites? and how much of it is in use, so we can understand how much bandwidth is available.Īs for security, I’d encrypt every backup that isn’t going to a deduplication device, better safe than sorry. One such scenario was seeing 1Gbps speeds, but with only a few hundred Mbps of bandwidth consumed on the actual WAN link.Īnything 1Gbps+, don’t use a WAN accelerator. This won’t provide better than native speeds, but it will provide similar speeds at a reduced effective throughput. This will typically provide greater effective speeds vs native transfers.ġ00Mbps-1Gbps: Use high bandwidth mode if working with a WAN accelerator. <100Mbps: Use low bandwidth mode if working with a WAN accelerator. Hi BCJ can offer advantages, depending on your bandwidth between the sites. I don’t have a lot of direct to object happening right now, although there are one or two…. You know….as I was typing that, I was questioning if I was correct but figured somebody would correct me if needed. □ĭirect to Object going to Wasabi will do that as well in v12. You don’t have to use SOBR to take advantage of Immutability. If you’re using the same backup server to coordinate it all, then a single bucket may be fine, but I’d probably use a bucket for Serbia and one for Austria if there is a need for a SOBR in Austria.Īs Chris mentioned, you could also have direct backup to object or direct copy to object storage, but for me, I would utilize a SOBR so that I could take advantage of immutability within Wasabi. Note that you may not want to use the same bucket. If you have data in Serbia that needs to go to Austria, then I’d setup the reverse as well. If there is nothing that needs to be backed up at the Serbia site, then I would setup a backup at the primary site, and setup a SOBR at the secondary site with a copy job to copy the backup data to Serbia and also copy to Wasabi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |