Exclude Exchange Databases from Auto-Provisioning in New DAG - Exchange 2019

Understanding the Scenario

We have set up a new Database Availability Group (DAG) dedicated to archiving mailbox data due to storage limitations in our primary DAG. However, we want to ensure that primary mailboxes remain on the old DAG and are not automatically provisioned on the new DAG, while only archive mailboxes use the new DAG.

Steps to Exclude Databases in the New DAG from Auto-Provisioning

Step 1. Identify the Database that has not to excluded from Auto-Provisioning.

First, Get the database that is part of your new DAG, as these are the ones you want to exclude from auto-provisioning for primary mailboxes.

This command lists a specific database on the new DAG and shows whether it's currently excluded from provisioning.

Step 2. Exclude the New DAG Databases from Auto-Provisioning.

Use the Set-MailboxDatabase cmdlet to exclude each database in the new DAG from being automatically selected when creating new primary mailboxes.

Replace "DB1-ARC" with the name of each database in the new DAG.

By setting IsExcludedFromProvisioning to $true, you ensure these databases are excluded from auto-provisioning when new primary mailboxes are created.

Step 3. Verify Exclusion of New DAG Databases.

After excluding the databases from auto-provisioning, verify that the exclusion has been applied successfully by running.

This will confirm that the new DAG’s databases are excluded from the provisioning process for primary mailboxes.

Step 4. Ensure primary mailboxes are provisioned on the Old DAG.

Ensure that the databases in the old DAG are included in auto-provisioning so new primary mailboxes will be created on those databases.

Replace "UserMailbox" with the mailbox you want to enable for archiving and "NewDAGDatabaseName" with the database on the new DAG where you want the archive mailbox to reside.

This ensures the databases in the old DAG remain available for new primary mailboxes.

1. Scenario Example: Expanding Archive Storage Without Affecting Primary Mailbox Provisioning
2. Scenario: The old DAG has reached storage capacity for primary mailboxes, and a new DAG has been set up with expanded storage solely for archive mailboxes. To ensure that the primary mailboxes stay on the old DAG and only archive mailboxes use the new DAG, administrators can exclude the new DAG databases from auto-provisioning while directing archive mailboxes to those databases.

By excluding the new DAG databases, we prevent them from being automatically selected for primary mailbox creation. Instead, they will only be used for archiving purposes, while primary mailboxes continue to be provisioned in the old DAG databases.

Best Practices for Managing Archive Mailboxes on a New DAG

• Monitor DAG performance: Keep an eye on the new DAG’s performance and storage usage as archive mailboxes grow.
• Regularly review auto-provisioning settings: Ensure that only the intended databases are included or excluded from auto-provisioning to maintain a balanced environment.
• Plan for future growth: If more storage capacity is required, consider expanding the new DAG or adding additional storage for the old DAG if the primary mailbox needs to increase.

Conclusion

By strategically excluding databases in the new DAG from auto-provisioning, you can ensure that primary mailboxes remain on the old DAG while the new DAG is dedicated to archiving. This approach provides a scalable solution for managing Exchange environments with distinct primary and archive mailbox storage.