You need to identify which commands must be run to perform the maintenance window tasks.
Which commands should you run? (To answer, drag the appropriate commands to the correct tasks. Each command may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
Correct Answer:
Explanation/Reference:
Explanation:
Start-DatabaseAvailabilityGroup
Use the Start-DatabaseAvailabilityGroup cmdlet to reincorporate one or more previously failed members of a database availability group (DAG).
EXAMPLE 1
This example starts the Mailbox server MBX2 in the DAG DAG1.
Start-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
Stop-DatabaseAvailabilityGroup
Use the Stop-DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.
EXAMPLE 1
This example stops the Mailbox server MBX2 in the DAG DAG1.
Stop-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
The Stop-DatabaseAvailabilityGroup cmdlet is used during a datacenter switchover. This cmdlet is used to mark one or members of the DAG as failed (also known as stopped).The Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of
DagOnly.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Primary Active Manager (PAM)
Microsoft Exchange Server 2013 includes a component called Active Manager that manages the high availability platform that includes the database availability group (DAG) and mailbox database copies. Active Manager runs inside the Microsoft Exchange Replication service (MSExchangeRepl.exe) on all Mailbox servers.
On Mailbox servers that aren’t members of a DAG, there is a single Active Manager role: Standalone Active Manager. On servers that are members of a DAG, there are two Active Manager roles: Primary Active Manager (PAM) and Standby Active Manager (SAM). PAM is the Active Manager role in a DAG that decides which copies will be active and passive. PAM is responsible for getting topology change notifications and reacting to server failures. The DAG member that holds the PAM role is always the member that currently owns the cluster quorum resource (default cluster group). If the server that owns the cluster quorum resource fails, the PAM role automatically moves to a surviving server that takes ownership of the cluster quorum resource. In addition, if you need to take the server that hosts the cluster quorum resource offline for maintenance or an upgrade, you must first move the PAM to another server in the DAG. The PAM controls all movement of the active designations between a database’s copies. (Only one copy can be active at any specified time, and that copy may be mounted or dismounted.) The PAM also performs the functions of the SAM role on the local system (detecting local database and local Information Store failures).
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
Failover the databases that are hosted on the Mailbox server by using this command:
In computing, failover is switching to a redundant or standby computer server, system, hardware component or network upon the failure or abnormal termination of the previously active application,[1] server, system, hardware component, or network. Failover and switchover are essentially the same operation, except that failover is automatic and usually operates without warning, while switchover requires human intervention.
At server level, failover automation usually uses a "heartbeat" cable that connects two servers. As long as a regular "pulse" or "heartbeat" continues between the main server and the second server, the second server will not initiate its systems. There may also be a third "spare parts" server that has running spare components for "hot" switching to prevent downtime. The second server takes over the work of the first as soon as it detects an alteration in the "heartbeat" of the first machine. Some systems have the ability to send a notification of failover.
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.
Set-ServerComponentState <ServerName> – Component ServerWideOffline – State Inactive Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive -Requester Maintenance to place the server into maintenance mode.
STEPS
1. All mounted databases on the server undergoing maintenance must be activated on another servver.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
The question is asking you to failover the databases
2. All message queue on the server undergoing maintenance must be empty before maintenance can begin
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.
3. The server undergoing maitenance must be prevented from becoming a PAM.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Primary Active Manager (PAM)
4. Database copies on the server undergoing maintenance must not be activated while maintenance is occurring.
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Performing maintenance on DAG members
Before performing any type of software or hardware maintenance on a DAG member, you should first place the DAG member into maintenance mode. This involves moving all active databases off the server and blocking active databases from moving to the server. It also ensures that all critical DAG support functionality that may be on the server (for example, the Primary Active Manager (PAM) role) is moved to another server and blocked from moving back to the server. Specifically, you should perform the following tasks:
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Draining -Requestor
Maintenance to begin the process of draining all Unified Messaging calls.
Run Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN> to redirect messages pending delivery in the local queues to the Mailbox server specified by the Target parameter.
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $True to move all active databases currently hosted on the DAG member to other DAG members.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive -Requester Maintenance to place the server into maintenance mode.
To verify that a server is ready for maintenance, perform the following tasks:
Run Get-ServerComponentState <ServerName> | ft Component,State -Autosize to verify the server has been placed into maintenance mode
Run Get-MailboxServer <ServerName> | ft DatabaseCopy* -Autosize to verify the server is not hosting any active database copies.
Run Get-ClusterNode <ServerName> | fl to verify that the node is paused.
Run Get-Queue to verify that all transport queues have been drained.
After the maintenance is complete and the DAG member is ready to return to service, you can take the DAG member out of maintenance mode and put it back into production by performing the following tasks:
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance to designate that the server is out of maintenance mode.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Active -Requestor Maintenance to allow the server to accept Unified Messaging calls.
Run Resume-ClusterNode <ServerName> to resume the node in the cluster, which enables full cluster functionality for the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $False to allow databases to become active on the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Unrestricted to remove the automatic activation blocks.
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Active -Requester Maintenance to resume the transport queues and allow the server to accept and process messages.
http://technet.microsoft.com/en-us/library/aa998651(v=exchg.150).aspx
Explanation/Reference:
Explanation:
Start-DatabaseAvailabilityGroup
Use the Start-DatabaseAvailabilityGroup cmdlet to reincorporate one or more previously failed members of a database availability group (DAG).
EXAMPLE 1
This example starts the Mailbox server MBX2 in the DAG DAG1.
Start-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
Stop-DatabaseAvailabilityGroup
Use the Stop-DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.
EXAMPLE 1
This example stops the Mailbox server MBX2 in the DAG DAG1.
Stop-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
The Stop-DatabaseAvailabilityGroup cmdlet is used during a datacenter switchover. This cmdlet is used to mark one or members of the DAG as failed (also known as stopped).The Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of
DagOnly.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Primary Active Manager (PAM)
Microsoft Exchange Server 2013 includes a component called Active Manager that manages the high availability platform that includes the database availability group (DAG) and mailbox database copies. Active Manager runs inside the Microsoft Exchange Replication service (MSExchangeRepl.exe) on all Mailbox servers.
On Mailbox servers that aren’t members of a DAG, there is a single Active Manager role: Standalone Active Manager. On servers that are members of a DAG, there are two Active Manager roles: Primary Active Manager (PAM) and Standby Active Manager (SAM). PAM is the Active Manager role in a DAG that decides which copies will be active and passive. PAM is responsible for getting topology change notifications and reacting to server failures. The DAG member that holds the PAM role is always the member that currently owns the cluster quorum resource (default cluster group). If the server that owns the cluster quorum resource fails, the PAM role automatically moves to a surviving server that takes ownership of the cluster quorum resource. In addition, if you need to take the server that hosts the cluster quorum resource offline for maintenance or an upgrade, you must first move the PAM to another server in the DAG. The PAM controls all movement of the active designations between a database’s copies. (Only one copy can be active at any specified time, and that copy may be mounted or dismounted.) The PAM also performs the functions of the SAM role on the local system (detecting local database and local Information Store failures).
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
Failover the databases that are hosted on the Mailbox server by using this command:
In computing, failover is switching to a redundant or standby computer server, system, hardware component or network upon the failure or abnormal termination of the previously active application,[1] server, system, hardware component, or network. Failover and switchover are essentially the same operation, except that failover is automatic and usually operates without warning, while switchover requires human intervention.
At server level, failover automation usually uses a "heartbeat" cable that connects two servers. As long as a regular "pulse" or "heartbeat" continues between the main server and the second server, the second server will not initiate its systems. There may also be a third "spare parts" server that has running spare components for "hot" switching to prevent downtime. The second server takes over the work of the first as soon as it detects an alteration in the "heartbeat" of the first machine. Some systems have the ability to send a notification of failover.
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.
Set-ServerComponentState <ServerName> – Component ServerWideOffline – State Inactive Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive -Requester Maintenance to place the server into maintenance mode.
STEPS
1. All mounted databases on the server undergoing maintenance must be activated on another servver.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
The question is asking you to failover the databases
2. All message queue on the server undergoing maintenance must be empty before maintenance can begin
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.
3. The server undergoing maitenance must be prevented from becoming a PAM.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Primary Active Manager (PAM)
4. Database copies on the server undergoing maintenance must not be activated while maintenance is occurring.
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Performing maintenance on DAG members
Before performing any type of software or hardware maintenance on a DAG member, you should first place the DAG member into maintenance mode. This involves moving all active databases off the server and blocking active databases from moving to the server. It also ensures that all critical DAG support functionality that may be on the server (for example, the Primary Active Manager (PAM) role) is moved to another server and blocked from moving back to the server. Specifically, you should perform the following tasks:
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester
Maintenance to begin the process of draining the transport queues.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Draining -Requestor
Maintenance to begin the process of draining all Unified Messaging calls.
Run Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN> to redirect messages pending delivery in the local queues to the Mailbox server specified by the Target parameter.
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from being and becoming the PAM.
Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $True to move all active databases currently hosted on the DAG member to other DAG members.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the server from hosting active database copies.
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive -Requester Maintenance to place the server into maintenance mode.
To verify that a server is ready for maintenance, perform the following tasks:
Run Get-ServerComponentState <ServerName> | ft Component,State -Autosize to verify the server has been placed into maintenance mode
Run Get-MailboxServer <ServerName> | ft DatabaseCopy* -Autosize to verify the server is not hosting any active database copies.
Run Get-ClusterNode <ServerName> | fl to verify that the node is paused.
Run Get-Queue to verify that all transport queues have been drained.
After the maintenance is complete and the DAG member is ready to return to service, you can take the DAG member out of maintenance mode and put it back into production by performing the following tasks:
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance to designate that the server is out of maintenance mode.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Active -Requestor Maintenance to allow the server to accept Unified Messaging calls.
Run Resume-ClusterNode <ServerName> to resume the node in the cluster, which enables full cluster functionality for the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $False to allow databases to become active on the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Unrestricted to remove the automatic activation blocks.
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Active -Requester Maintenance to resume the transport queues and allow the server to accept and process messages.
http://technet.microsoft.com/en-us/library/aa998651(v=exchg.150).aspx
