We are excited to announce the release of Kasten K10 version 6.0, the latest and most advanced version of our industry-leading platform that provides enterprise-grade Kubernetes data protection and application mobility. This release helps customers scale their cloud native data protection efficiently. Kubernetes deployments are growing at an unprecedented rate. Gartner predicts that by 2027, more than 90% of global organizations will be running containerized applications in production. However, today’s market conditions are scarred with financial uncertainty and a shortage of cloud native skills. Therefore, you must ensure operational efficiencies are in place to unleash the full potential of your cloud native environments while protecting your data. Additionally, security remains an imperative as organizations focus on keeping their businesses running. With this release, we also continue to innovate in this growing ecosystem, so that you can take advantage of the best-of-breed inn...
Get link
Facebook
X
Pinterest
Email
Other Apps
Storage Decision Guide for Microsoft 365 Backups
Get link
Facebook
X
Pinterest
Email
Other Apps
The first Version of Veeam Backup for Microsoft 365 (V1) was released on Nov. 29, 2016. I was involved in the very first projects with the new product. Over the years, we saw a huge growth in customers and in product features as well. Due to the growth in data, usage and customer numbers, we adjusted our backup components to fit new needs. Over the last years of being a subject matter expert for Veeam Backup for Microsoft 365, I was able to collect a lot of experience I want to share with you.
In my customer meetings, I receive nearly the same questions regarding repository type and sizing every time. Let’s start with some basics about Veeam Backup for Microsoft 365 repositories.
Veeam Backup for Microsoft 365 repository overview
It’s free, scalable and has been crash-tested over many years.
Running a database as a repository is completely different than using a file-based repository like we use in Veeam Backup & Replication. That’s also a reason why you can not use a Veeam Backup & Replication repository to store Veeam Backup for Microsoft 365 backup data on it.
The requirements are way stricter and there is a gap in flexibility as well.
Storage performance makes the difference
With version 4 of Veeam Backup for Microsoft 365, we introduced the backup to object storage feature for better scalability and flexibility. A better data compression was an improvement as well due to the object storage compression we can leverage. The local repository compression rate went up to 10% and object storage compression rate went up to 55%. Sidenote: There is no deduplication for Veeam Backup for Microsoft 365 repositories because of the underlying jet database.
I want to add that, technically, NAS-Devices are supported and it’s possible to use them as a repository over SMB, but there are too many disadvantages to go into that topic deeper (see compare-matrix below). NAS storage is also only under experimental support. Please see [KB2976](https://www.veeam.com/kb2976) for more details.
Deduplication devices or local disks with an enabled deduplication option are not supported!
What does this mean for our repository choice?
We can choose between two options:
Local repository: Disks directly attached to the backup proxy. Depending on your proxy type, physical or virtual, the disk can be a virtual disk, iSCSI attached disk or a directly attached physical disk.
Object storage: Storage based on cloud protocols for S3 or Blob. Object storage can be rented over public cloud providers (Azure, AWS, IBM Cloud, Wasabi, Backblaze and many more!) but it is also possible to use the S3 protocols on a supported on-premises device running in your own data center.
Pros and cons of local storage vs. object storage
PROS
CONS
Local Repository
Existing storage can be used;
Storage costs are very transparent;
Data is on premises and can be backed up with Veeam Agent or Veeam Backup & Replication to a different location (3-2-1 Rule);
Inflexible extension of storage;
Size limitations of filesystem;
Performance issues with bigger repositories (<60 TB);
Lower data compression (up to 10%);
Object Storage
Flexible and “infinite” storage;
Higher data compression (up to 55%);
Pay what you need;
Better performance;
No limitations;
Back up copy to archive cloud storage (S3 Glacier, Azure Archive);
Pay what you need;
Additional costs for restores (depending on cloud storage vendor!);
Repository type
Scalability
Performance
Costs
File compression
3-2-1 Rule
Local Repository
***
***
***
**
***
NAS Devices
*
**
****
**
*
Cloud-Object Storage
*****
*****
***
*****
****
On-Prem Object Storage
****
*****
***
*****
**
If you want to back up a small-to-midrange environment, depending on your user quantity and storage amount (up to 2,000 users with over a maximum of 60 TB of data), you can start with an on-premises repository. As already mentioned, NAS devices are not considered as a recommendation.
You can start directly with the on-premises resources you have.
If you don’t have storage resources available or want to be as flexible as possible, it makes sense to have a deeper look at object storage vendors. They are very reliable and can be a cheap alternate to an on-premises device. The environmental size does not matter.
Object storage is the preferred choice of many of our customers because of its reliability, the better compression and a higher performance.
If you are looking for more information on how to set up the repository or what the best practices for your needs are, please check out the resources below:
For those of us who have been in the business of backing up data for a while, we’re used to making copies of data on different types of media. I won’t date myself by mentioning reel-to-reel tapes, but the journey started with tape and then backing up data to block/file-based disk storage came along. More recently, a new kid on the block has become a popular destination for backed up data, object storage. Veeam started to use object storage as a target when we released Veeam Backup & Replication 9.5 Update 4 in January 2019 by introducing our use of AWS S3 compliant object storage via the Capacity Tier. A year later, we launched Veeam Backup & Replication v10 which featured support for object locking to provide data immutability for object storage. Immutability provides protection from ransomware attacks by locking the objects which prevents them from being modified or deleted by malicious software or humans. Today, Veeam Backup & Replication is protecting hundreds of petab...
Before Veeam Backup & Replication v11, the product used SQL Server to create and store its configuration database. It has always been possible to use SQL Server Express to store a Veeam Backup & Replication, however, this version of SQL Server had some critical limitations. In the 2022 version of SQL Server Express, the most relevant limitations were: Use of one socket or four cores Use of only 1.4GB per instance 10GB limit for databases In an environment of 500 machines or fewer, these limitations may not have an impact, but if you have a large backup environment, you had to migrate to one of the paid SQL Server versions to avoid these limitations. You can check the limits for each version of SQL Server 2022 by clicking this link . For V12 and with scalability, performance and licensing cost in mind, Veeam introduced the possibility of using PostgreSQL as a configuration database. PostgreSQL is a relational database management system that’s been used for over 35 years...
update notice: The information in this blog post has been updated on April 1st, 2022. Since Veeam Backup & Replication version 10, it’s possible to back up NAS shares with the SMB (CIFS) and NFS protocol. One of the challenges with backing up large file shares is doing so in a consistent state. This blog post shows how to create a consistent backup of an SMB share hosted on a NetApp ONTAP based storage. NetApp storage snapshot, Microsoft VSS snapshot or Storage Integration? Veeam offers three ways to back up a NetApp ONTAP SMB share in a consistent state. With NetApp storage integration From a NetApp storage snapshot (without integration) With Microsoft remote VSS snapshot Using the storage integration is the easiest way to get the latest state with very few configuration steps. Using an alternative snapshot path allows complex scenarios like backing up from a SnapMirror/SnapVault location but it involves scripting or a schedule on NetApp to create and delete t...
Comments
Post a Comment