Scenarios : Start / Stop DagServerMaintenance.ps1 Exchange 2010

“StartDagServerMaintenance.ps1 and StopDagServerMaintenance.ps1”

Above scripts is used to take a DAG member out of service for maintenance. It will move active databases off of the server and block databases from moving to that server. It will also make sure all critical DAG support functionality (e.g., the PAM role) that might be on the server is moved to another server, and blocked from moving back to the server. A second script, StopDagServerMaintenance.ps1, is provided to complete the operation and remove the blocks.

Overview:

As part of maintenance, it is necessary for certain critical resources that are being hosted on the mailbox server to be moved to other servers in the DAG in order to provide continued service availability and data protection. While it is desirable to have this process occur automatically, the differing nature of maintenance processes (patching versus hardware maintenance) preclude the possibility of automatic moves of these resources. In addition, there are consequences to this movement of critical resources not occurring in a timely fashion – if they are not moved off before the server becomes unavailable, this could result in a loss of availability, or worse yet, a loss of data.

The second best alternative is to have these resources move through a single administrator action that enables the server to be “freed up” for maintenance. As a consequence of this action, these resources must also be prevented from moving back to the server that is under maintenance. Once the maintenance is complete, this prevention must be removed.

The StartDagServerMaintenance.ps1 and StopDagServerMaintenance.ps1 scripts make possible the following management tasks:

  • Perform a controlled move of critical resources from one server to another specific server
  • Perform a controlled move of critical resources off of a particular server
  • Temporarily prevent critical resources from being moved to a particular server
  • Ensure that critical resource handling without any servers under maintenance is unchanged

Scenarios:

The StartDagServerMaintenance.ps1 and StopDagServerMaintenance.ps1 scripts can be used in the following scenarios:

Scenario 1: Move critical resources from a server prior to maintenance

The administrator may choose to move critical resources, including the PAM, off of a server that is going to be under maintenance. The administrator is able to specify that critical resources should be moved off of the server and the maintenance time, and the system attempts to move critical resources to other servers.

If the move is unsuccessful, critical resources continue to be hosted on the original server. If the move is successful, critical resources are prevented from moving back to the original server for the limited period of time specified by the administrator.

Scenario 2: Block critical resources from a server prior to maintenance

If critical resources are not hosted on the server that is going to be under maintenance, it may still be desirable to block critical resources from moving to that server. In this case, the administrator is able to specify the maintenance time, and the system prevents critical resources from moving to that server for the limited period of time specified by the administrator.

Scenario 3: Move critical resources to a particular server prior to maintenance

As part of a maintenance process, the administrator may choose to move critical resources, including the PAM, to a particular server that is not going to be under maintenance. The administrator is able to specify a particular destination for critical resources and the maintenance time, and the system will attempt to move critical resources to that destination.

If the move is unsuccessful, critical resources continue to be hosted on the original server. If the move is successful, critical resources are prevented from moving back to the original server for the limited period of time specified by the administrator.

Scenario 4: Remove critical resource blocking from a server after maintenance

If during the maintenance process, critical resources were blocked from moving to the server under maintenance, it may be that when the maintenance is complete that the critical resource block needs to be removed. The administrator then specifies the removal of the critical resource block, and critical resources are allowed to move to that server once again.

Scenario 5: Extend critical resource blocking for a server during extended maintenance

If critical resources were blocked for a period of time that was insufficient to cover the maintenance period, it may be that the critical resource block needs to be extended for a time in order to cover this period. The administrator then specifies the time for extension of the critical resource block, and critical resources are prevented from moving to that server for the new time period.

Advertisements
This entry was posted in Exchange Servers. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s