Its sometime happened, our DC (Main Primary DB Instance) may be down due to some reasion and we have to start our log shipped Secondary Server which is at DR location, needs to act as Primary Server for smooth Production.
In my Example lets Primary Server is named as ‘PRIMARY’ and DB which is used for Log shipping at server ‘SECONDARY’ is VIRENDRATEST.
Now suppose I would like to change my PRIMARY Server’s production environment as a ‘SECONDARY’ and ‘SECONDARY’ as a PRIMARY. Below are the steps for same.
- First be sure, all applications hits are stopped to DB server. For same we have to contact Application Team/Production to STOP/DISABLE the services/Application, After confirmation from there let go ahead.
- Take Full BACKUP of PRIMARY Server’s DB.
- Run LS-Backup Job at Primary Server and Disable it.
- Run LS-Copy Job at SECONDARY Server , after complition of this, disable this job.
- Run LS-Restore job at Secondary Server and after completion of it, Disable it
- Now Take LOG Backup from PRIMARY server as using command as
BACKUP LOG VIRENDRATEST TO Disk=N’D:\LS_BACKUP\VIRENDRATESTLOG.BAK’ WITH NORECOVERY - Copy LOG Backup file(of Step 6) of PRIMARY at SCECONDARY server manually.
- At SECONDARY , restores last BACKUP LOG file with option WITH RECOVERY
- Now our SECONDARY Server’s DB is up for production and PRIMARY Server’s DB is in RESTORING mode
- Now Configure LOG SHIPPING again at SECONDARY as PRIMARY and PRIMARY as SECONDARY.
- Run LS-Backup Job at newly PRIMARY server.
- Refresh both servers instance, both server should be in sysn order with proper status.
- Check the Logshipping where its working properly or not
- Inform to Production team to Start/Enable all Application/Services
WikiDBA 