LOG Shipping

Question

LOG Shipping

Jeetendra

SSCrazy

Points: 2076
More actions
September 9, 2009 at 11:17 pm

#210466

Hi All,
After setting up the Log SHipping is it possible to change the Schedules of the Backup / Copy / Restore Jobs.
What would be the effect of the same.
Another question is suppose we need to test the Secondary server & carry out the DR drill and all users are shifted from Primary to secondary Servers.
After this drill is it necessary to copy the full backup from the Primary Server to the secondary for reinstating the Log Shipping
OR
Just copy the latest TLogs from the Primary Server and restore it to the secondary Server.
Please do let me know.
Kindest Regards,
Jeetendra

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

ps. One Orange Chip Points: 29422 More actions · Answer 1

Jeetendra (9/9/2009)
Hi All,
After setting up the Log SHipping is it possible to change the Schedules of the Backup / Copy / Restore Jobs.

Yes you can change the schedule of the backup/copy/restore jobs.

Another question is suppose we need to test the Secondary server & carry out the DR drill and all users are shifted from Primary to secondary Servers.
After this drill is it necessary to copy the full backup from the Primary Server to the secondary for reinstating the Log Shipping
OR
Just copy the latest TLogs from the Primary Server and restore it to the secondary Server.
Please do let me know.

copy the t-log from the primary with norecovery (tail log) and apply to secondary. This would also leave the primary in restoring stage.

You need to setup log shipping from your secondary (new primary) to primary(new secondary). use the same share for placing t-log backups. while setting up log shipping, select "no, the database is initialized" because it's already in restoring mode and you can apply t-log backups going forward from secondary to primary.

refer:http://deepakrangarajan.blogspot.com/2007/06/role-change-in-sl-2005-log-shipping.html

Pradeep Singh

Jeetendra SSCrazy Points: 2076 More actions · Answer 2

Hi ,

Thanks a lot for the reply...!!!

Just have some dounts regarding the same...

I wanna carry out the drill where I will just Make my Production Server Down & restore the Last Tlog on my Secondary Server & bring it online.

All users from the application will now test whether they can See (READ) the data from the Secondary Server.

They won't change anything.

Now if suppose i have to restart the Log shipping then :-

1. is it possible to take the Tlog backup from the Primary Server & restore it to secondary by making the database as Read / Only again.

OR

We have to again take the Full DB Backup and start all over again.

Kindest Regards,

Jeetendra

ps. One Orange Chip Points: 29422 More actions · Answer 3

Now if suppose i have to restart the Log shipping then :-
1. is it possible to take the Tlog backup from the Primary Server & restore it to secondary by making the database as Read / Only again.
OR
We have to again take the Full DB Backup and start all over again

1. you fail over to secondary so that users can see the data from secondary. Implement log shipping here making your secondary as primary and primary as secondary.

2. Once your drill is over, again implement log shipping by failing over from secondary to primary.

Also go through the link in my previous post.

Edit - You dont need to restore full backup each time, you can do it from the existing database state only.

Pradeep Singh

vkundar Hall of Fame Points: 3431 More actions · Answer 4

You can allow the secondary server to assume the primary server role provided that you selected the Allow database to assume primary role option for the secondary server during the initial configuration. You need chek the logins and users in secodary server and they shoul have the same permission as on the primary server.

Refer BOL for more information on "Changing Roles Between Primary and Secondary"

Cheers,

Got an idea..share it !!

DBA_Vishal

kchant Ten Centuries Points: 1231 More actions · Answer 5

Alternatively, depending on what resources you have on site , it may be possible for you to so an Open File backup of the database files of your Secondary database (when no restores are taking place) and restore them in another location, this way your Log Shipping configuration can be left undisturbed (and also means you can do whatever you want to with the the newly restored database).

For SQL 2000 you can simply attach the database files once you've restored them to another location, with SQL 2005 it's slightly more complicated as you have to create an exact copy of your Secondary database first (e.g. with exact file sizes) and then restore the files from your Secondary database over the top of the newly created ones...