VDC 365 and 3-2-1-1-0 rule

[mamosorre84]

Hi all,

planning VDC for 365 with flex plan and variable license model, how is it possible to reach the golden rule 3-2-1-1-0?

-3 different copies of data: the first copy is the production data, so do we have to plan two backup copies? since it is not possible to create a backup copy job, do you suggest to create two backup jobs (with different target) for each object type?

-store the backups on 2 different media: the target available is only Azure blob, is this ok?

-store at least 1 of the copies at an offsite location: is it suggested to verify the production data location and configure the Azure blob in another region?

-store at least 1 of the copies offline: since the target repository is always immutable, I guess we are compliant

- no errors after backup recoverability verification: is it possible to automate this process (like surebackup) or do we have to manually test some restore?

Regards

Marco S.

[micoolpaul]

Hi Marco!

3-2-1-1-0 would look like the following with Flex:
3 copies of data: We store 3 copies of each object within the object storage, so from a durability perspective this gets you to the magic '3'. Your production M365 data is stored within 2 geos already so there's multiple copies in that regard.
2 different media: We backup data at an item-level from M365 into object storage so it's stored in a completely different mechanism to production.
1 copy offsite: You can store within various different geos supported
1 copy offline/immutable: Correct, the data is backed by our service-level immutability
0 Recovery errors: Correct at present it's manually testing restores.

You could take this further with VDC M365 Premium however:
3 Copies of data: Production Data, Express Data, Flex Data
2 Different Media: Production Data, Express Backups stored within M365 Tenant, Flex Backups stored within Veeam's platform
1 Copy Offsite: Express meets this alone by storing the data within the regions that M365 uses to store data, and then optionally you can use an alternate region for Flex
1 Copy Offline/Immutable: Express & Flex are both Immutable
0 Recovery Errors: Manual testing at this point in time.

We continue to develop more functionalities to enhance the above and will announce things as they're ready

[mamosorre84]

Hi Michael,

thank you for your reply..of course we are waiting for more and more features!

What do you mean with "Your production M365 data is stored within 2 geos already so there's multiple copies in that regard." ? is not M365 data LRS redundant?

Regarding the offsite copy, is it better to choose a different region for the repository than the one used for the production tenant?

Thank you

Marco S.

[micoolpaul]

Hi Marco,

I said Production M365 data, as in your actual M365 tenant, not Veeam Data Cloud itself.

I'd use a different region to the production tenant wherever possible for additional resiliency definitely