Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 14, 2016 5:32 PM
hello all,
I see that the script StartDAGServerMaintenance Mode only stop the HighAvailibitity. Is this right to shutdown the Server.
and what does this mean: Is this because we have only 2 Servers?
MX1:
Database 'User' does not have enough copies configured to meet the validation criteria.
') (Database='DB1', Reason='There were maintenance prerequisite check failures for database 'DB1' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy Count: 2. Detailed error(s):
MX1:
Database 'DB1' does not have enough copies configured to meet the validation criteria.
') (Database='DB2', Reason='There were maintenance prerequisite check failures for database 'DB2' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy Count: 2. Detailed error(s):
[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Get-ServerComponentState mx1 | ft component, state -autosize
Component State
ServerWideOffline Active
HubTransport Active
FrontendTransport Active
Monitoring Active
RecoveryActionsEnabled Active
AutoDiscoverProxy Active
ActiveSyncProxy Active
EcpProxy Active
EwsProxy Active
ImapProxy Active
OabProxy Active
OwaProxy Active
PopProxy Active
PushNotificationsProxy Active
RpsProxy Active
RwsProxy Active
RpcProxy Active
UMCallRouter Active
XropProxy Active
HttpProxyAvailabilityGroup Active
ForwardSyncDaemon Inactive
ProvisioningRps Inactive
MapiProxy Active
EdgeTransport Active
HighAvailability Inactive
SharedCache Active
MailboxDeliveryProxy Active
RoutingUpdates Active
RestProxy Active
DefaultProxy Active
Chris
All replies (10)
Thursday, July 14, 2016 5:56 PM ✅Answered
My understanding is that script is depreciated.
Here's an article for Exchange 2013, I think it's still valid for Exchange 2016.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!
Friday, July 15, 2016 6:10 AM ✅Answered
Hi Chris,
Welcome to our forum.
By this issue, please run the following command to find FWS, then check the connection between FWS and DAG members:
Get-DatabaseAvailabilityGroup <DAG Name> | FL *witness*
Then run the following command to check DAG network:
Get-DatabaseAvailabilityGroupNetwork –Identity <DAG name>
And test database replication for DAG members:
Test-ReplicationHealth –Identity <Servername>
In addition, please run AD replication manually, then to have a try.
Best Regard,
Jim Xu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Jim Xu
TechNet Community Support
Friday, July 15, 2016 6:51 AM ✅Answered
Thanks for answer
Ed Crowley write. Should we also stop
HubTransport and ServerWideOffline ???
DatabaseCopyActivationDisabledAndMoveNow
DatabaseCopyAutoActivationPolicy
As with the script, Maintenance Mode is used to tell Exchange that a particular server should not be available to service clients. In a mailbox server, an administrator will typically perform a switchover to another server (if the server to be put in maintenance mode is hosting active database copies) and then use the Set-MailboxServer and Set-ServerComponentState cmdlet to put it into maintenance mode, preventing the active copies from being activated and disabling the Transport services:
Set-ServerComponentState <> -Component HubTransport -State Draining -Requester Maintenance
Suspend-ClusterNode <>
Set-MailboxServer <> -DatabaseCopyActivationDisabledAndMoveNow $True (this can be done manually by moving the active database copy(ies) to another server)
Set-MailboxServer <> -DatabaseCopyAutoActivationPolicy Blocked
Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance
This cmdlet also applies to Client Access Servers which, when placed into maintenance mode, stops the server from acknowledging load balancer heartbeats and disables all proxy services.
Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance
Chris
Saturday, July 16, 2016 7:36 AM
Hi chris,
You should stop all server components, include HubTransport, ServerWideOffline and so on.
If the issue persist, please refer to my steps to troubleshoot DAG.
Best Regard,
Jim Xu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Jim Xu
TechNet Community Support
Thursday, January 19, 2017 1:12 AM
I'm confused... if the script is depreciated why has it been included in the Exchange 2016 $exscripts\StartDagServerMaintenenance.ps1
Thursday, January 19, 2017 5:29 AM
None of us know the answer to that, sorry.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!
Thursday, January 19, 2017 7:19 AM
:) Thanks Ed
Thursday, January 19, 2017 7:23 AM
You're welcome. Happy to have helped.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!
Wednesday, March 21, 2018 2:43 PM
Hi.
This recent Technet Article advises to use the StartDagServerMaintenance.ps1 script (So not deprecated), and include informations about DAG ActivationPreference change since Exchange 2016 CU2.
Manage Database Availability Groups
https://technet.microsoft.com/en-us/library/dd298065(v=exchg.160).aspx
David
MCSE, MCITP Exchange 2K7 & 2K10
Thursday, December 20, 2018 1:58 PM
we have tried this method, but it is not working when the server placed in <g class="gr_ gr_57 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="57" id="57">load</g> balancer. even when we restart FIPS service after the exchange server wide offline and it still accepting connections