Administrators today are familiar with working on Exchange with database availability groups (DAG) and the multiple copies of mailbox stores they provide. One area of confusion around DAGs, however, is properly backing up DAG. And our team is happy to announce its support for backup and restore DAG (Database Availability Group) Environment. Frequent interaction with our partners during our webinars and social media platforms helped us understand the MSP market who are helping their clients in the Microsoft Exchange domain. Apart from supporting DAG, we are also supporting streaming and dump process for Exchange server DAG backup.
Here’s how it works…
The Active and Replicated databases are listed separately. Users have the flexibility to backup either a replicated database or an active database.
Also, you can select the option “All Databases” to configure both active and replicated databases in a single backup schedule. We also have the option of configuring the backups at server level and Database level. If a Storage Group/ Database is added to any backup schedule, then the respective Storage Group/Database can’t be added to another schedule. If needed, then deleting the Storage/Database added backup is recommended. And those Storage/Database can be added to new backup schedules.
We can backup the Replication or Active databases using the “Replication” OR “Active” option.If exchange server backups are configured as server level then the newly added databases are automatically added in the next backup schedules.
And on the restore front, we have two option: We can either restore the exchange server data directly from the backup server or we can restore the exchange server data locally after local restore we can upload to exchange server with the help of Vembu’s backup offerings.
Please do drop in your comments if you have any queries. I’ll answer them to the best of my knowledge.
