replication server: dumping & loading a db in warm standby 
Author Message
 replication server: dumping & loading a db in warm standby

Hi,

We have a warm standby situation and we know that at the standby db some
data are different from the primary. Don't ask me how that happened because
I don't know.
What I would like to do now is dump the primary database and load it at the
replicate site.
Is there anyone with experience in this?
I first want to shut down the ltm, dump the database, load the database,
start the ltm again and keep applications running that change the primary db
in the mean time.
Are there complications? Do we have to 'zero' the ltm truncation point at
the standby site or do anything else?

I hope to get some info, thanks in advance,

fred koene



Fri, 25 Apr 2003 03:00:00 GMT
 replication server: dumping & loading a db in warm standby

Hi Fred,

I have been in this situation more than once before ... but handling this will
be a bit tricky.
But I think you can try the following steps ....

1. Stop the replication between primary and replicate sites.
2. Make the ltm truncation point in primary to "0" using dbcc settrunc.
3. Dump the transaction log.
3. Clear the outbound and inbound queue for the particular connection.
4. Start the replication process (Start ltms, threads etc.) but keep the
connection to the replicate site suspended. This will ensure that the
replication goes through and data will get assembled in the Stable Queue but it
won't actually get applied to the replicate site.
5. Take the dump of the primary site and load it in the replicate site.
6. Start the suspended connection to the replicate site.

Please note that after you load the database at replicate end ... the rep server
connections will terminate if there are some duplicate entries going in. You can
do "resume connection with skip transaction" to ignore these errors.

This method will require some good timings ... better to do when there is
minimum activity on the primary server to reduce the level of transactions
between the dump/transfer/load sequence..

-Sukhesh

Quote:

> Hi,

> We have a warm standby situation and we know that at the standby db some
> data are different from the primary. Don't ask me how that happened because
> I don't know.
> What I would like to do now is dump the primary database and load it at the
> replicate site.
> Is there anyone with experience in this?
> I first want to shut down the ltm, dump the database, load the database,
> start the ltm again and keep applications running that change the primary db
> in the mean time.
> Are there complications? Do we have to 'zero' the ltm truncation point at
> the standby site or do anything else?

> I hope to get some info, thanks in advance,

> fred koene



Fri, 02 May 2003 12:31:21 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. warm standby replication database or server setting ?

2. Replication Server / Warm Standby / recovery procedures

3. Timestamp out of sequence while loading dump to standby server

4. Replication for warm standby

5. Replication to provide warm standby ?

6. Replication of image data in a warm standby environment

7. Warm Standby Replication

8. model db stuck in warm standby (Read Only)

9. SQL Server 7.0 Warm Standby Setup

10. Sql Server 7.0 - maintaining warm standby

11. Warm Standby Servers


 
Powered by phpBB® Forum Software