We're here to help!

Moving Standby Server to New Premises

Follow

Question

How to resync the standby database when the server is being fork lifted to new location.

We are moving our standby server to new premises, it would take us to 10 to 20 days to put it back on track. So we would like to know the best options for stopping the service of synchronization temporarily by keeping the fact that the archive log max size is 50 GB and approximately around 6 - 10 GB log files are generated per day.

Do we need to disable the archive logs and dbvist sync job and start from scratch or do you have any other suggested approaches?

Answer

During the time that you are moving your standby database you will need to:

  1. Disable the Dbvisit sync job. Do not disable archive log mode on your primary server.

  2. When the standby server is operational again, then resync the standby database with the following option (you do not need to start from scratch):

    For Version 6.0:  https://dbvisit.atlassian.net/wiki/display/dbdc/Synchronize+Standby+Database+with+Dbvisit+Standby 

        For Version 7.0 : https://dbvisit.atlassian.net/wiki/display/UGDS7/Synchronize+a+Standby+Database 

        For Version 8.0:

        https://dbvisit.atlassian.net/wiki/display/DS8QSG/The+Synchronise+Standby+Database+Option 

 

Note: During this time, you DO NOT have a DR server for your primary database.

Arjen Visser December 20, 2013 20:36

Have more questions? Submit a request

Comments