Today, Veeam is announcing v2 which takes our solution to a completely new level by adding support for Microsoft SharePoint and Microsoft OneDrive for Business. When we released version 1.5 in 2017, we added automation and scalability improvements which became a tremendous success for service providers and larger deployments. When Veeam introduced Veeam Backup for Microsoft Office 365 in November 2016, it became an immense success and Veeam has continued building on top of that. (ii) configure daily Veeam incremental backups of App servers, Web Server and SQL OS with maybe full backups monthly and keep clean down incrementals each month.Microsoft Office 365 adoption is bigger than ever. (i) kill the daily SQL full backup plan and move to Veeam full as the complete backup solution for all the SQL Databases (Content, Config, Master etc.)? I am considering at a high level maybe the following might be a good idea but wanted to get your thoughts: The SQL servers have Veeam agents installed (I assume since Backup of Cluster Shared Volumes are not supported by VeeamĪnd as the SQL VMs are in a Microsoft failover cluster and utilise bus sharing and share the same SQL DATA,SQL LOG and SQL Backup VMDK files.) Note: There is a separate cluster shared volume for SQL Data, SQL Log, SQL Backup on the SAN. Onsite IT have just put in place Veeam to backup the 6 SharePoint servers (2 x app, 2 x web, 2 SQL) but it looks like there is no application aware backups going on, no truncating of logs files etc.Īnyone here using Veeam to backup their on premise SharePoint SQL Cluster and can share how you are backing it up with Veeam? The guy who originally setup SharePoint setup a full SQL backup to happen each night but the log files had ballooned (esp sharepoint config and main database) as there were no transaction log backups scheduled. Taking on a new customer that has had a recent SharePoint 2019 install hosted on ESXi.
0 kommentar(er)
