Storage Decision Guideline for Microsoft 365 Backups
<div> <img src="https://infracom.com.sg/wp-content/uploads/2022/06/storage-decision-guide-microsoft-365.jpg" class="ff-og-image-inserted" /> </div>
The first Edition of Veeam Backup for Microsoft 365 (V1) premiered on Nov. 29, 2016. I was mixed up in initial projects with the brand new product. Over the full years, we saw an enormous growth in clients and in product functions as well. Because of the growth in information, customer and usage figures, we adjusted our back-up components to match new needs. During the last yrs of being a topic matter specialist for Veeam Back-up for Microsoft 365 , I could collect a complete large amount of experience i wish to share with you.
In my own customer meetings, I have the same queries regarding repository kind and sizing each time nearly. Let’s focus on some essentials about Veeam Back-up for Microsoft 365 repositories.
<h3> <span id="Veeam_Backup_for_Microsoft_365_repository_overview"> Veeam Back-up <em> for Microsoft 365 </em> repository overview </span> </h3>
The repository is founded on a jet glowing blue database that is also used in several Microsoft products ( https://en.wikipedia.org/wiki/Extensible_Storage_Engine ).
It’s free, offers and scalable been crash-tested more than many years.
Owning a database as the repository is totally different than utilizing a file-structured repository like we used in Veeam Back-up & Replication. That’s also grounds why it is possible to not work with a Veeam Back-up & Replication repository to shop Veeam Back-up for Microsoft 365 back-up data on it.
Certain requirements are way stricter and there’s a gap in versatility as well.
<h3> <span id="Storage_performance_makes_the_difference"> Storage functionality makes the distinction </span> </h3>
With version 4 of Veeam Backup for Microsoft 365, we introduced the backup to object storage function for better scalability and flexibility. An improved data compression was a noticable difference as well because of the object storage space compression we are able to leverage. The neighborhood repository compression price went around 10% and object storage space compression rate went around 55%. Sidenote: There is absolutely no deduplication for Veeam Back-up for Microsoft 365 repositories due to the underlying jet database.
I wish to add that, technically, NAS-Gadgets are supported and it’s possible to utilize them as a repository more than SMB, but you can find way too many disadvantages to get into that subject deeper (see compare-matrix below). NAS storage space is under experimental support furthermore. Please notice KB2976 for additional information.
Deduplication devices or neighborhood disks having an enabled deduplication option are usually not supported!
<h3> <span id="What_does_this_mean_for_our_repository_choice"> What does this suggest for our repository option? </span> </h3>
We can select from two options:
<ul> <li> Local repository: Disks straight mounted on the backup proxy. Based on your proxy kind, virtual or physical, the disk could be a digital disk, iSCSI attached disk or perhaps a attached physical disk. </li>
<li> Object storage space: Storage predicated on cloud protocols for S3 or Blob. Object storage space could be rented over open public cloud suppliers (Azure, AWS, IBM Cloud, Wasabi, And many more backblaze!) but it can be possible to utilize the S3 protocols on a backed on-premises device running is likely to data center. </li>
</ul>
<h3> <span id="Pros_and_cons_of_local_storage_vs_object_storage"> Advantages and disadvantages of local storage versus. object storage space </span> </h3>
<figure class="wp-block-table aligncenter is-style-stripes">
<table class="has-fixed-layout"> <thead> <tr> <th class="has-text-align-left" data-align="left"> </th> <th> Advantages </th> <th> Downsides </th> </tr> </thead> <tbody> <tr> <td class="has-text-align-left" data-align="left"> Local Repository </td> <td> Existing storage may be used; <br /> Storage costs have become transparent; <br /> Data will be on premises and may be supported with Veeam Veeam or Broker Backup & Replication to a new location (3-2-1 Guideline); </td> <td> Inflexible expansion of storage; <br /> Size restrictions of filesystem; <br /> Performance problems with larger repositories (<60 TB); <br /> Lower data compression (around 10%); </td> </tr> <tr> <td class="has-text-align-left" data-align="left"> Object Storage space </td> <td> Versatile and “infinite” storage space; <br /> Increased data compression (around 55%); <br /> Pay the thing you need; <br /> Better overall performance; <br /> No restrictions; <br /> Back again up duplicate to archive cloud storage space (S3 Glacier, Azure Archive); </td> <td> Pay the thing you need; <br /> Additional charges for restores (based on cloud storage space vendor!); </td> </tr> </tbody> </table>
</figure>
<figure class="wp-block-table aligncenter is-style-stripes">
<table class="has-fixed-layout"> <thead> <tr> <th class="has-text-align-left" data-align="left"> Repository kind </th> <th class="has-text-align-left" data-align="left"> Scalability </th> <th> Efficiency </th> <th> Expenses </th> <th> Document compression </th> <th> 3-2-1 Principle </th> </tr> </thead> <tbody> <tr> <td class="has-text-align-left" data-align="left"> Local Repository </td> <td class="has-text-align-left" data-align="left"> *** </td> <td> *** </td> <td> *** </td> <td> ** </td> <td> *** </td> </tr> <tr> <td class="has-text-align-left" data-align="left"> NAS Devices </td> <td class="has-text-align-left" data-align="left"> * </td> <td> ** </td> <td> **** </td> <td> ** </td> <td> * </td> </tr> <tr> <td class="has-text-align-left" data-align="left"> Cloud-Object Storage </td> <td class="has-text-align-left" data-align="left"> ***** </td> <td> ***** </td> <td> *** </td> <td> ***** </td> <td> **** </td> </tr> <tr> <td class="has-text-align-left" data-align="left"> On-Prem Object Storage space </td> <td class="has-text-align-left" data-align="left"> **** </td> <td> ***** </td> <td> *** </td> <td> ***** </td> <td> ** </td> </tr> </tbody> </table>
</figure> If you need to back again up a small-to-midrange atmosphere, based on your user volume and storage amount (around 2,000 customers with over no more than 60 TB of information), you can begin having an on-premises repository. As mentioned already, NAS devices aren't regarded as a recommendation.
You can begin with the on-premises resources you have directly.
In the event that you don’t have storage space resources available or desire to be as flexible as you possibly can, it makes feeling to get a deeper look at item storage vendors. They’re very reliable and will be a inexpensive alternate to an on-premises device. Environmentally friendly size will not matter.
Object storage may be the preferred selection of quite a few customers due to the reliability, the higher compression and an increased performance.
In order to keep your computer data on-site because of regulations or your individual choice without losing the benefits of an object storage space, we recommend a storage space program with S3 integration. Compatibility checklist: https://www.veeam.com/alliance-partner-integrations-qualifications.html?programCategory=object )
If you are searching for a lot more information on how best to create the repository or what the very best practices to your requirements are, please browse the resources below:
Help Center Object Storage space: https://helpcenter.veeam.com/docs/vbo365/guidebook/vbo_osr.html?ver=60
Best-Exercise Repository: https://bp.veeam.com/vbo/guide/buildconfig/proxy-repo.html
Best-Practice Object Storage space: https://bp.veeam.com/vbo/tutorial/style/sizing/objectstorage.html
Best-Practice Neighborhood Disk Repository: https://bp.veeam.com/vbo/guide/style/sizing/diskrepo.html
Download a 30-time Trial offer of Veeam Backup for Microsoft 365 : https://www.veeam.com/backup-microsoft-office-365.html