April 15, 2002 at 6:57 am
For disaster and recovery we are setting up a co-location. We will be setting up all co-location servers to match all production servers config. I am planning to use log shipping to synch our database all in SQL Server 2K.
Have anyone worked with log shipping before? Any suggestions how to set this up in the correct way. So far, We have been using backup to tape. Now, management realized the important of having an disaster and recovery plan and location.
I used logshipping only as part of my study guide and of course real life is quite different. I appreacite your input in advance.
Thanks.
April 15, 2002 at 8:44 am
I've had log shipping running in our SQL2K environment for about 6 months. We're log shipping 3 databases to and from the same server. I'm using a separate server as the monitor server.
The only problem I had during the setup is with file shares. The log backup directory on the source server needs to be explicitly shared, with your SQL service account having being granted access to it. Can't use hidden shares.
The only other issue is network bandwidth vs. log file size. The largest DB that I log ship is 50GB. I backup logs on it every 15 minutes, which are about 8-10 MB. These transfer without problem during the 15 minute intervals. However, one of my monthly maintenance jobs where I do a DB re-org generated a 24GB log file. Since we have a T1 between the sites that's not dedicated for log shipping, it takes about 24 or more hours to transfer this file. During that time, we're not in sync and vulnerable.
Other than that, I haven't had any major issues with it. Below is just a quick snapshot of our environment:
Source:
-SQL 2K Enterprise (SP2) on W2K Active/Passive cluster (SP2).
Target:
-SQL 2K Regular (SP1) on W2K Server (SP2).
Monitoring Server:
-SQL 2K Enterprise (SP2) on W2K Advanced Server (SP2).
Network Link:
T1 between the U.S. and Europe.
Log Shipping / backup interval:
15 minutes
April 15, 2002 at 8:50 am
Thank you for the info. I read about the sharing folder and play with it a little for the test. I will keep in mind the timing for the maintenace job in case I have to. Other than that I think is very similar to yours. My biggest db is around 69 GB and the regular one are about 3 GB, but they are 81 dbs to synch. Thank again, really appreciate the info.
June 20, 2002 at 10:53 am
Does the monitor server have to be SQL Enterprise, or can it be a SQL Standard?
If the primary is Enterprise, can the standby and monitor server be Standard?
June 20, 2002 at 11:23 am
Yes. From my understanding, only the source needs to be the Enterprise version. The monitor server and destination can be the normal SQL Server Edition.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply