Setting up Log Shipping under fire

Compresses, encrypts, secures and monitors SQL Server backups.

Moderators: JonathanWatts, Chris Auckland, eddie davis, Colin Millerchip, Brian Harris, james.billings, RBA, petey

Setting up Log Shipping under fire

Postby RichardRayJH » Sun Jan 12, 2014 7:53 pm

I've got a production db that has users in it from 6:00 AM to 11:00 PM and runs batch processes from 11:30 PM to 1:00 AM. After that it does maintenance jobs to be RTG at 6:00 AM the next morning.

I want to set up log shipping. I've got another server ready to go, but I'm not clear on just what the steps are when the db is in production like that.

Does the target server need to have RedGate Backup Pro installed?

When should I take the backup that goes on the second server to be the basis for the log shipping?

How do I insure that the shipping starts up smoothly if the database is in use?

Am I making this harder than I need to? :-)
-
Richard Ray
Jackson Hole Mountain Resort
Teton Village, WY
RichardRayJH
 
Posts: 13
Joined: Mon Sep 21, 2009 9:49 pm
Location: Teton Village, WY, USA

Postby petey » Mon Jan 13, 2014 2:55 am

Does the target server need to have RedGate Backup Pro installed?

Yes it does.

When should I take the backup that goes on the second server to be the basis for the log shipping?

Usually off production hours so as not to affect your users' activities, but that would depend on how long the backup would take and if your production server has more than adequate CPU and disk I/O to spare for the backup.

How do I insure that the shipping starts up smoothly if the database is in use?

You can take full and transaction log backups even when the database is in use.
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
petey
 
Posts: 2233
Joined: Sun Apr 24, 2005 12:34 pm


Return to SQL Backup 7

Who is online

Users browsing this forum: No registered users and 0 guests