Veeam office 365 software#

To demonstrate that point, we will pair Veeam together with MinIO as a capacity tier to allow VeeamвЂ™s software to perform VBO. That is exactly what MinIO is and is why we fit so well with Veeam.

The result of these requirements is that Veeam is a natural pair for high-performance, software defined object storage. This becomes an important requirement as the data grows into to the Petabytes. COTS hardware = huge savings, familiarity and flexibility. This guarantees all backup operations are guaranteed to succeed. There is no caching or staging of data for asynchronous I/O. The S3 service provided by MinIO is resilient to any disruption or restarts in the middle of busy transactions. Data in MinIO is always readable and consistent since all of the I/O is committed synchronously with inline erasure-code, bitrot hash and encryption. Suffice to say - if the object storage implementation uses a metadata database, it is not well suited for handling backups. At 4MB, dedupe becomes ineffective, so Veeam architects recommend against it. At smaller object sizes, deletes become highly problematic and effectively disqualify any object store that employs such an approach. Because MinIO writes metadata atomically along with the object data, it does not require a database (Cassandra in most cases) to house the metadata. VeeamвЂ™s default is 1MB objects but supports anywhere from 256K to 4MB. This can have devastating effects if the plug gets pulled in the middle of your job and your database gets corrupted. One way slower object stores try to make shortcuts is to move to an eventual consistency model. Longer backup restore cycles would result in increased disruption to business. With the ability to read/write at speeds in excess of 160 GB/s in a single 32 node cluster, MinIO can backup and restore at speeds once considered impossible for object storage. There are a number of reasons but these four stand out: This is where modern object stores like MinIO are exceptionally well suited.

Traditional object storage architectures (think appliance vendors) are not up to the task here for a number of reasons.

First, backups and restores need to go quickly no matter the size. Office365 backups require performance.Object is the most scalable solution - whether in the public or private cloud. There is little debate around this point in architecture circles these days. In case you missed the first post, a quick recap of why Veeam and MinIO are such a good fit (if you didnвЂ™t skip to the technical bits). Veeam Backup for Microsoft Office 365 mitigates the risk of losing access to the entirety of the Office portfolio from email through to attachments and files ensuring ongoing availability to users and the business. Only a fraction of those firms do proper backups - exposing them to internal threats from malicious insiders, external threats from hackers and legal and compliance violations. Indeed, there are well over 215M Office 365 users today and 185M commercial customers. Even with the advent of Slack and applications, the email market continues to grow and remains the cornerstone communication mechanism for large enterprises capturing more and more mindshare with the advent of Office 365. An equally popular use case is Veeam Backup for Office (VBO). I n our first post we covered backups of VMware ESX. With the announcement that MinIO was Veeam Ready for Object last week we felt it would be helpful to circle back and talk about an additional use case.

Veeam office 365