So, what they did was protect the JET database itself with Veeam Backup & Replication. If you lose the JET database, you lose your backups. This still need to be protected from corruption on disk, as well as ransomware events and other security threats that can attack it. The JET Blue database isn’t just a simple backup item that sits in a company’s repository, it’s a full archive database storing the retrieved data from Office 365 Exchange Online, SharePoint Online, OneDrive for Business and Microsoft Teams data from a cloud-based instance of Office 365. #4 Protect the JET database used as repository If the proxy is doing the work seamlessly, it should move more data and faster. They strongly encouraged other organizations to do this fine-tuning of proxy threads as it ensures you’ll see better performance. The configuration of how much work the proxy server will do at a given time is super important since it may or may not improve performance for increasing or decreasing threads. This was a big lesson learned, and after this optimization the backups started performing much better as a whole. Breaking this out ensured that SharePoint wasn’t blocked by Exchange, for example, and they could apply more resources to Exchange since it had the bulk of the data and ensure it completed fast. Soon they scaled to five proxies, strategically spread across different portions of the Office 365 environment. While this was a good way to start, it wasn’t going to cut it long term, especially with the acquisition on the horizon. One VBO backup, one proxy server, and a simple SMB share repository on a storage server. Prior to the acquisition, they started with a simple backup configuration.
They were now looking at an extended use case including tens of TBs of email data (some structured, some not) that they had to find a way to size it appropriately to successfully back it all up. About six months later, they had to massively scale their environment due to a company acquisition that added 25% more users, but more importantly, many more applications from the Microsoft stack (Teams, OneDrive, SharePoint, Dynamics, Power BI) and users that had unlimited retention settings. Their retention policies were set to 15 months on all those 2,000+ users, and their organization only utilized Exchange and Skype. When they originally migrated to Office 365, they had about 2,200 users and 40TB of data. #1 When your environment is changing, change with it! Here’s a summary of what they had to say. A simple slide but packed with over 18 months of experience.
0 kommentar(er)
