July 27, 2016 at 3:57 am
I am not good enough in Administration. My Primary Server was down in Log Shipping, so I applied last T-Log Backup of Primary database onto Secondary server and made it online for operations. Now, Primary Server is up, so please let me know the process to continue with Log Shipping as earlier.
July 27, 2016 at 5:06 am
Where is your DBA? Who created the log shipping in first place.
You have to configure log shipping back again, this might not be very complex, but you should be thorough on the subject of backup and restore.
July 27, 2016 at 5:26 am
Hi,
Not sure whether your comment questioned or tried to help me out in this regard... 🙂 We do not have core DBAs and in general, we handle by our own. But this is the first time, we got requirement for Log Shipping and I am fully aware of Backup and Restore methodology.
So ifIf you could able to let me the know the process to configure it back, it would be grateful.
July 27, 2016 at 8:33 am
Hi Ajay,
When you say 'as earlier' if you mean making the primary server to be used back again from your application, you would need to take the database back there.
To minimize downtime, you can setup log shipping reverse.
Please post if you are having any doubts
https://msdn.microsoft.com/en-gb/library/ms190640(v=sql.110).aspx
July 28, 2016 at 4:04 am
Hi Roshan,
Now, secondary Server is running fine, as I made it's database online. As our Primary Server is up and running now, I would like to make this Server as Logshippng Primary Server and make Secondary Server's database in standby mode, so that I will be able to continue Logshipping between two servers which I did earlier.
In simple words, I need to see the Logshipping functionality as ealrier (before Primary Sever gets down).
Please let me know, if my response gives any confusion.
July 28, 2016 at 8:10 am
So the current active version is server 2. This might have moved on with new transactions from application
so you need to sync server 1 first. To minimize down time you can set up log shipping in reverse from server 2 to server 1.
Once it is up to date you already know to fail over with tail log backup
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply