SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


LOGSHIPPING RE-ESTABLISHMENT


LOGSHIPPING RE-ESTABLISHMENT

Author
Message
Jai-SQL DBA
Jai-SQL DBA
SSC-Enthusiastic
SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)

Group: General Forum Members
Points: 134 Visits: 509
Hi,
I want to understand the Logshipping reestablishment Scenerio After a Failover.Below Mentioned are the details of the Environment for the Better Understanding.


Server A: Primary Server
Server B: Secondary Server

Logshipping established between A and B .

Server A Crashed.I have restored all the Pending Logs to Secondary Server and got it into a Consistent State and Its in Use from last few days .

Now My Server A is UP again and I want to make it as an Primary Server again and Server B as Secondary Again .

Now the main Questions are :

1.Can i just restore the Full Backup of Server B on Server A and change the Mode of B to no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.
Will that Work ??

2.Do I need to restore the Full Backup on Server A and then take a backup from A to B restoring a no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.

What is your Opinion on the above two Doubts .Please Advise
Orlando Colamatteo
Orlando Colamatteo
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15379 Visits: 14396
Jai-SQL DBA (9/26/2012)
Hi,
I want to understand the Logshipping reestablishment Scenerio After a Failover.Below Mentioned are the details of the Environment for the Better Understanding.


Server A: Primary Server
Server B: Secondary Server

Logshipping established between A and B .

Server A Crashed.I have restored all the Pending Logs to Secondary Server and got it into a Consistent State and Its in Use from last few days .

Now My Server A is UP again and I want to make it as an Primary Server again and Server B as Secondary Again .

Now the main Questions are :

1.Can i just restore the Full Backup of Server B on Server A and change the Mode of B to no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.
Will that Work ??

2.Do I need to restore the Full Backup on Server A and then take a backup from A to B restoring a no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.

What is your Opinion on the above two Doubts .Please Advise

Not sure if you were saying this already but to be clear, when you take the FULL backup from Server B you'll provide either the NORECOVERY or the STANDBY option as part of the BACKUP command. This will take the backup and make the DB inaccessible for writes all in one step ensuring you have all transactions from Server B to restore on Server A and that no new transactions will enter Server B while you're in the process of failing back.

Before you begin anything disable any Log Shipping or backup jobs still in place.

Here is a guide to help you with the rest of the details:

Changing Roles Between Primary and Secondary Servers

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Perry Whittle
Perry Whittle
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20696 Visits: 17244
Jai-SQL DBA (9/26/2012)
Hi,
I want to understand the Logshipping reestablishment Scenerio After a Failover.Below Mentioned are the details of the Environment for the Better Understanding.


Server A: Primary Server
Server B: Secondary Server

Logshipping established between A and B .

Server A Crashed.I have restored all the Pending Logs to Secondary Server and got it into a Consistent State and Its in Use from last few days .

Did you backup the tail of the log on the original primary and restore this?



Jai-SQL DBA (9/26/2012)
1.Can i just restore the Full Backup of Server B on Server A and change the Mode of B to no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.
Will that Work ??

2.Do I need to restore the Full Backup on Server A and then take a backup from A to B restoring a no recovery(Standby/Readonly) and Reconfigure the LOGSHIPPING from A to B.

What is your Opinion on the above two Doubts .Please Advise

You shouldn't need to restore any full backups if you made the switch correctly!

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Jai-SQL DBA
Jai-SQL DBA
SSC-Enthusiastic
SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)SSC-Enthusiastic (134 reputation)

Group: General Forum Members
Points: 134 Visits: 509
thx for responding but I just wanted to know the Following :

Date 1:A and B are working fine with Logshipping Between them
A is Primary and B is Secondary

Date 2:A went Crashed and B was made as Primary .

Date 3:A was established again and now we Need to use it as an Primary again.


Wat would be the Steps for Simplest turnover
Perry Whittle
Perry Whittle
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20696 Visits: 17244
Jai-SQL DBA (10/4/2012)
Date 2:A went Crashed and B was made as Primary .

Please provide details of the steps you took!




Jai-SQL DBA (10/4/2012)
Date 3:A was established again and now we Need to use it as an Primary again.

Please provide details of the steps you took!


Jai-SQL DBA (10/4/2012)
Wat would be the Steps for Simplest turnover

See above ;-)

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search