This feature might get included in the next release." "The solution could offer better reporting." "Its price could be improved." "It's hard to predict the usage on the storage. However, for the other users who are on the local email server at that time, the solution is not able to capture the backup." "When you are working in the Cloud security is very important." "They can provide a dashboard for sizing. We have many users in management and approximately 50 other users who are using Office 365 of which Veeam is able to capture the backup. It should have a better user interface." "We have found that there is a limitation in this solution where it only takes the backup of users who are using Office 365 Enterprise email IDs. That's the main thing why it is not very user-friendly. It has a lot of scrolling and doesn't give you a complete overview when needed. Its user interface should be more user-friendly. It should have a better user interface for selecting what you want to back up so that you get a more clear overview of the sites that are there and the ones that you want to combine in a backup. You should see it immediately on the screen. For example, for the URL, you need to hover over the title or the name of the site. It works, but it is not always very clear. That said you can easily create regular expression match rules on the objectID property to create groups in any granularity."When you add a new site for backup, it gives you a notice that there is a new site, but the way you select that and configure that could be slightly better. This property is an unique GUID for each user and thus a randomized number with statistically equal distribution of starting numbers/letters (HEX) over your user base. Create dynamic groups and leverage the dynamic rules based on the objectID property. You can split your user base easily into even groups with Dynamic User Membership in Azure Active Directory. Use the dynamic groups as a source for your backup jobs and the groups will be automatically updated on Azure AD side. This is a best practice for splitting jobs for all user based services, like Exchange Online and OneDrive for Business. You can add excludes to the job to avoid backup up items that you do not want to backup (blacklisting). until you assign them to the appropriate job.Īs this job needs to enumerate all your Microsoft 365 objects, this is only recommended for smaller organizations with a limited amount of objects. With this you can catch newly created users, Teams, SharePoint sites, etc. You can create a catch-all job which will backup all items which are not yet processed by any other job. Otherwise you can select single teams or create PowerShell scripts to protect Teams based on names. Each Team will count as 3 objects (Exchange, SharePoint and Teams itself) for the sizing.
Be aware that this is only recommended if you have a small number of Teams in your organization and you will not exceed the configuration maximums. To protect all current and future SharePoint sites in an organization, you can choose to backup the organization object and then select only to process “Teams”.
This way data objects are only stored once in the repository, even when linked on two objects within Microsoft 365. Most Teams data lies in SharePoint, so it it recommended to backup Teams to the same repository as the Teams Sharepoint sites. Similar to the Microsoft Exchange mailbox protection there is an option to select individual sites in the backup job as shown in the picture below: Veeam Backup for Microsoft Office 365 provides you an option to protect the complete SharePoint farm, as a best practice in the single job you can add up to 50 SharePoint sites. It’s recommended to create multiple jobs based on group if the environment is 500+ mailboxes, the backup job based on group object are easy to manage for backup and restore operations and provides the good performance.įor example The jobs can be created based on the departments in the Organization, Veeam Backup for Microsoft Office 365 also provides you options to exclude the mailboxes from the backup job in event users left the organization you can easily exclude the mailbox from backup job processing as shown in the picture below. We have the following workloads protection in Veeam Backup for Microsoft Office 365: In this section, we will discuss the best practice about backing up the different workloads. Veeam Backup for Microsoft Office 365 offers multiple options to create the backup job to protect the environment.īackup job can be created based on following objects:Ĭonfiguring a single backup job is appealing, but the maintenance of a single backup job is challenging because of the following potential risks: In this section we will discuss job configuration, options to create the backup job as well as the best practice for the backup job configuration.
0 kommentar(er)
