![]() ![]() The main drawback to taking multiple full backups, is the Microsoft enforced throttling policies that apply when VB365 is fetching content from the Microsoft 365 tenant. As I’ve not discussed these previously, lets highlight some key drawbacks of these approaches: Backup Copy Methods Pre-V6 Multiple Full Backups Historically, we would need to achieve these three copies of data by either taking multiple full backups, or backing up the VB365 server after it had successfully taken a backup. As part of Veeam’s 3-2-1-1-0 backup best practices, we should have a minimum of three copies of data. VB365 v6 brought a strongly requested feature to the VB365 product, backup copies. ![]() New VB365 Feature: Backup Copies to ANY object storage Not only do I want to talk about these two features but, most importantly, how they are related to each other. Today I want to talk about not one, but two new features in Veeam Backup for Microsoft 365 (VB365) v7, these are: Immutability, and Backup Copies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |