|
|
Posted by Greg D. Moore \(Strider\) on 05/11/06 15:31
"laststubborn" <arafatsalih@gmail.com> wrote in message
news:1147348989.967368.134060@j73g2000cwa.googlegroups.com...
> Thats the thing, I could not pass one time snapshot part. During the
> initial snapshot I had problems, Our application was locked and It was
> taking so long we had to cancel it. You said that there are ways around
> that how ? If you give me some help on that I really appreciate it.
Ah, now I better understand what you're talking about.
I'm a bit surpised with only 2000 transactions a day you can't fnid a quiet
time (perhaps on a weekend?) to make the snapshot.
Anyway, there's KB articles on MS on various ways of doing this (and I
believe SQL 2005 has options also that help.)
Anyway, if you CAN pause work for a shrot period of time, try something like
the following:
Do a full backup of DB on "Publisher".
Do a full restore WITH NORECOVERY on "subscriber"
Since this will take some time, you'll need to do the following (and up
until now you users could still use the system.)
Stop all access to the system
Do a transaction log backup from the "publisher"
Restore to the "subscriber", this time with RECOVERY
Setup replication, but say, "subscriber has data and schema"
Permit access to the system.
This is not guaranteed to solve your problem, but I've done it with success
before.
There's several catches to watch out for:
1) if you know your initial transaction log backup will take a long time, do
it w/o kicking folks out of the publisher and restore with NORECOVERY and
then do the transaction log backup a 2nd time (or 3rd, etc.) Trick is to
get that last transaction log backup/restore cycle as absolutely as short as
possible.
Setup as much of replication in advance as possible, i.e. setup the
publisher/distributer side of things before hand.
Script out as much as you can.
Finally.. be careful of IDENTITY columns. This is where things can break.
Note to, if you decide you need to make schema changes on the subscriber, do
this after replication is setup.
The above is not guaranteed to solve your problem but I've used it in
similar cases with success.
>
> Also any of you did a failover clustering? I will do this first time
> and I have some questions.
>
> Thanks
>
Navigation:
[Reply to this message]
|