Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Best sequence for server maintenance shutdown / reboot? Expand / Collapse
Author
Message
Posted Tuesday, December 29, 2009 1:10 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, May 1, 2014 7:26 AM
Points: 908, Visits: 2,804
Basic setup:
production server with active / passive clustering
prod DB is transaction replicated to a third server (pull subscription)

Current maintenance restart / reboot sequence (which is basically just rebooting the server itself with no real attention to replication or SQL Server) is causing replication errors and 2 am calls for me. Not good.

This is in an official maintenance window, so no access / stale data on reports server for a limited time is acceptable. Maintaining failover would be good but not an absolute.

I have ideas, but would love to hear some of your hands-on experience with this.

Thanks, everyone.
Post #840032
Posted Tuesday, December 29, 2009 2:01 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 19, 2012 4:00 PM
Points: 100, Visits: 168
What errors are you getting?


Post #840055
Posted Tuesday, December 29, 2009 2:13 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, May 1, 2014 7:26 AM
Points: 908, Visits: 2,804
The one I dealt with yesterday / last night was the fact that replication thought it was running, but no data was showing up on the subscriber since the reboot.

Log reader agent errors during publisher downtime / switch"
no replicated transactions are available
the process could not execute 'sp_replcmds' on 'production server'

On the distribution agent:
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

in distribution, seeing multiple messages of PK violations.

maintenance included index reorg / rebuild
Post #840066
Posted Wednesday, December 30, 2009 7:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 19, 2012 4:00 PM
Points: 100, Visits: 168
Thanks Pam for the response. What are you distribution and log reader agent profile parameters?


Post #840307
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse