October 12, 2009 at 9:12 am
Hi,
I've inherited a working log ship configuration of a single database (OneO) on the primary server to a single database (also OneO) on the secondary server. This is occuring every 5 minutes (transaction log backup, copy and restore) and is primarily for availability and to minimise data loss.
I'm trying to configure log shipping for the same primary database (OneO) to a second database (OneO_Offline) on the same secondary server, to be used for offline querying. We want this to use RESTORE WITH STANDBY and to only restore once a day so that users don't see disconnection problems as the database restores.
I've got as far as having OneO and OneO_Offline both sucessfully taking restores, but these are using the same server agent restore job (LSRestore_server1_OneO) and thus are both on the same 5 minute schedule.
How can I go about getting the OneO_Offline database to restore with it's own job on a seperate, once a day, schedule without effecting the restore schedule that OneO uses?
So far I've configured this through the wizard. Looking around I've only been able to find examples of log shipping to 2 seperate servers, not twice to the same server and I'm getting a little confused as to what options have to be specified at server level and what need to be specified at database level.
Any assistance appreciated.
October 15, 2009 at 4:53 pm
WARNING: I have not tried this.
can you go to the log shipping page of the primary database,select secondary server instance and add another secondary, which will be the same instance but a different target database. You would then set a different destination folder and copy and load schedule so the log files went to a different location, the two copies did not run at the same time and you could load at different times. I would hope this would create new copy and restore jobs on the secondary, and you would have two copies of the logs on the secondary.
---------------------------------------------------------------------
October 16, 2009 at 12:25 am
I've tried configuring this through the wizard on the primary server, but it doesn't seem to accept 2 seperate copy and restore jobs for the same secondary. I have added a second log ship database on the secondary and have it working using the same copy and restore job, which means it's on the same schedule, so not a lot of use for my purposes.
I suspect that if this is achievable then it's going to have to be configured through T-SQL, but I can find lots of examples about log shipping to 2 secondary servers, but nothing about shipping to the same secondary twice.
Anyone tried this?
October 16, 2009 at 8:49 am
change of angle. could you possibly switch the log shipping for availability to use database mirroring, and the set up log shipping to one0_offline, restoring just once a day.
---------------------------------------------------------------------
October 16, 2009 at 9:09 am
I think the issue is that the filenames when they are copied are the same, and so the wizard fails.
My guess is that you would want to script out the log shipping jobs, the modify them to point to the server as a new copy of the backup files and new jobs to restore them to a different db.
My suggestion might be to set up the wizard to ship to another server. Then modify those jobs back to your first server, but make sure the names are changing on the files, or the location is changed from your first log shipping job.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply