But is that ideal? When the repository is small enough OK, but what if the customer has a lot of TBs of data and is using a long retention… Those backups can also easily be deleted like the one on the primary repository.Īnother option can be if you are using local storage or iSCSI storage as a repository, using a Veeam agent to backup all drives including your repository and putting that on another repository (Veeam Cloud Connect, VBR repository. In my opinion that is not a good solution : twice the network-traffic needed (not ideal if VBO365 is running on-premises and not in the public cloud) and is also not protected against malware. Then you have a second copy of your O365 data.
So the rule 3-2-1-1-0 should also be implemented in this case.Īn option could be : create a second job with the same settings as the primary job except writing to another repository. I know, Office 365 is running on high-available infrastructure but in case of ransomware or a hacker on your VBO365 server, all your backups can be deleted. There is no built-in option for creating backup copy jobs, so there is by my knowledge no option to copy the backups on your primary repository to a secondary repository. īut what with Veeam Backup for Office 365 ? Perfect in combination with Veeam Backup & Replication to save your backups as good as possible to protect them against ransomware, hackers. I hope you all read my post about the 3-2-1-1-0 golden rule - 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub.
0 kommentar(er)
