Hello,
I am wondering what I am doing wrong or if what I am seeing is normal
behavior.
I have manual log shipping in place (via SQL LiteSpeed).
We have a replicated database log shipped to a DR server in another
location. When I fail over to the DR site, I can still see the publications
on both sites (however the DR site is not set up for replication). When I
fail back to the main site, I lose replication for the database and all of
my agents fail upon restarting them.
Has anyone run into this and come up with a solution?
We have to fail over to the DR site next weekend for building maintenance
and I don't want to have to rebuild replication.
Thanks so much.
~lb
You might want to restore your databases with the keep replication switch.
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
"Lonnye Blake Bower" <lbower@.excellerx.com> wrote in message
news:eZclO86MFHA.4092@.tk2msftngp13.phx.gbl...
> Hello,
> I am wondering what I am doing wrong or if what I am seeing is normal
> behavior.
> I have manual log shipping in place (via SQL LiteSpeed).
> We have a replicated database log shipped to a DR server in another
> location. When I fail over to the DR site, I can still see the
publications
> on both sites (however the DR site is not set up for replication). When I
> fail back to the main site, I lose replication for the database and all of
> my agents fail upon restarting them.
> Has anyone run into this and come up with a solution?
> We have to fail over to the DR site next weekend for building maintenance
> and I don't want to have to rebuild replication.
> Thanks so much.
> ~lb
>
2012年3月11日星期日
订阅:
博文评论 (Atom)
没有评论:
发表评论