Pausing Replication

Several times over the course of a month, our network admin team performs
necessary maintenance due to company moves and general growth. During this
time the connection between my Publisher and Distributor is disconnected. My
Subscriber and Distributor are on the same server. I have three
transactional publications set up and I would like to Pause them until the
connection is restored since I know when the connection is going down.
Is this the correct way to handle this?
From the Distributor in the enterprise manager drill down through the
replication monitor to the Distibution Agents and click on Stop Agent for
all of the publication that I have. Do I also have to Stop Agent on all of
the publications in the Log Reader Agents folder?
This also brings up the question of unplanned connection loss. If for some
reason the connection is lost late at night and I dont know about it until
the next morning do I have to recreate snapshots or re-initialize the
publication?
I would stop SQL Server agent, disable the jobs in the management folder and
then restart the agents. You should only have to stop the distributor or
merge agents.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Butler via droptable.com" <forum@.nospam.droptable.com> wrote in
message news:4FFDFDD1EDC20@.droptable.com...
> Several times over the course of a month, our network admin team performs
> necessary maintenance due to company moves and general growth. During
> this
> time the connection between my Publisher and Distributor is disconnected.
> My
> Subscriber and Distributor are on the same server. I have three
> transactional publications set up and I would like to "Pause" them until
> the
> connection is restored since I know when the connection is going down.
> Is this the correct way to handle this?
> From the Distributor in the enterprise manager drill down through the
> replication monitor to the Distibution Agents and click on "Stop Agent"
> for
> all of the publication that I have. Do I also have to "Stop Agent" on all
> of
> the publications in the Log Reader Agents folder?
> This also brings up the question of "unplanned" connection loss. If for
> some
> reason the connection is lost late at night and I don't know about it
> until
> the next morning do I have to recreate snapshots or re-initialize the
> publication?
|||Does it matter what order I do this in?
|||no, you can disable the jobs first, which will mean that if they are
scheduled they won't run the next time they are scheduled. However if they
are in continuous mode, you must stop them before or after disabling them.
Then you should bounce SQL Server agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Butler via droptable.com" <forum@.droptable.com> wrote in message
news:4FFEBB746E630@.droptable.com...
> Does it matter what order I do this in?

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?
Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:

> Is there a graceful best practice to temporarily pause log shipping so that
> unrelated Windows maintenance can be carried out on the servers?

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:
> Is there a graceful best practice to temporarily pause log shipping so that
> unrelated Windows maintenance can be carried out on the servers?

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:

> Is there a graceful best practice to temporarily pause log shipping so tha
t
> unrelated Windows maintenance can be carried out on the servers?