You are attempting to resolve the database activation issue. You need to identify why the database copies are activated on EX3 instead of EX2.
Which command should you use? (To answer, select the appropriate options in the answer area.)
Hot Area:
Correct Answer:
Explanation/Reference:
Exchange 2013 Managed Availability
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/monitoring/exchange-2013-managed-availability.html
This tips describes the new Managed Availability feature present in Exchange 2013.
In Exchange 2013, native, built-in monitoring and recovery actions are included in a feature called Managed Availability. Managed Availability is the integration of built-in, active monitoring and the Exchange 2013 high availability platform, allowing Exchange to make a determination on when to fail over a database based on service health.
To view the health of a server, you use the cmdlets Get-ServerHealth to retrieve the raw health data and Get-HealthReport that operates on the raw health data and provides a snapshot of the health.
This example returns the server health for server MBX1:
Get-ServerHealth Server01
The following examples return a report on the health of the server. The second cmdlet narrows this report to the Store process:
Get-ServerHealth | Get-HealthReportGet-ServerHealth | Where {$_.HealthSetName -eq “Store”} Get-
HealthReport
Get-AvailabilityReportOutage
Use the Get-AvailabilityReportOutage cmdlet to return the daily downtime (if any) for each service entity and its overridden value (if set) to the overall reported availability for the day.
EXAMPLE 1
This example returns all outages that occurred the previous day. This cmdlet always returns outages for one day.
Get-AvailabilityReportOutage
EXAMPLE 2
This example returns all outages reported for Microsoft Outlook services at all sites on the selected day.
Get-AvailabilityReportOutage -ReportDate:"2011-12-05" -Identity:"Outlook*"
Get-HealthReport
Use the Get-HealthReport cmdlet to return health information related to the server you specify. You can use the health values to determine the state of the server.The cmdlet also returns an alert value that provides the specific state of your server.
This example retrieves health information about a server running Microsoft Exchange Server 2013.
Get-HealthReport -RollupGroup
The following list contains the health values that are returned:
Online
Partially Online
Offline
Sidelined
Functional
Unavailable
Get-ServerHealth
Use the Get-ServerHealth cmdlet to return health information related to the server you specify.
This example returns the server health for server Server01.
Get-ServerHealth -Identity Server01
The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned:
Degraded
Unhealthy
Repairing
Disabled
Unavailable
UnInitialized
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Explanation/Reference:
Exchange 2013 Managed Availability
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/monitoring/exchange-2013-managed-availability.html
This tips describes the new Managed Availability feature present in Exchange 2013.
In Exchange 2013, native, built-in monitoring and recovery actions are included in a feature called Managed Availability. Managed Availability is the integration of built-in, active monitoring and the Exchange 2013 high availability platform, allowing Exchange to make a determination on when to fail over a database based on service health.
To view the health of a server, you use the cmdlets Get-ServerHealth to retrieve the raw health data and Get-HealthReport that operates on the raw health data and provides a snapshot of the health.
This example returns the server health for server MBX1:
Get-ServerHealth Server01
The following examples return a report on the health of the server. The second cmdlet narrows this report to the Store process:
Get-ServerHealth | Get-HealthReportGet-ServerHealth | Where {$_.HealthSetName -eq “Store”} Get-
HealthReport
Get-AvailabilityReportOutage
Use the Get-AvailabilityReportOutage cmdlet to return the daily downtime (if any) for each service entity and its overridden value (if set) to the overall reported availability for the day.
EXAMPLE 1
This example returns all outages that occurred the previous day. This cmdlet always returns outages for one day.
Get-AvailabilityReportOutage
EXAMPLE 2
This example returns all outages reported for Microsoft Outlook services at all sites on the selected day.
Get-AvailabilityReportOutage -ReportDate:"2011-12-05" -Identity:"Outlook*"
Get-HealthReport
Use the Get-HealthReport cmdlet to return health information related to the server you specify. You can use the health values to determine the state of the server.The cmdlet also returns an alert value that provides the specific state of your server.
This example retrieves health information about a server running Microsoft Exchange Server 2013.
Get-HealthReport -RollupGroup
The following list contains the health values that are returned:
Online
Partially Online
Offline
Sidelined
Functional
Unavailable
Get-ServerHealth
Use the Get-ServerHealth cmdlet to return health information related to the server you specify.
This example returns the server health for server Server01.
Get-ServerHealth -Identity Server01
The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned:
Degraded
Unhealthy
Repairing
Disabled
Unavailable
UnInitialized
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
