April 13, 2006 at 6:27 am
Here's the scenario. We have a SQL 2000 Cluster where the database is also Log Shipped to a secondary server for reporting. I want to create a Filegroup on the Cluster on the R drive, but the secondary server doesn't have R, it has D. My question is... what will happen? Will it break Log Shipping? Has anyone ever tried anything like this before? I can't afford to break Log Shipping because the database is large and it takes 2 days to set up again. Any help would be appreciated.
April 13, 2006 at 7:36 am
I beleive that log shipping will be broken, although i'm not sayig there isn't a way round it.
if i could ask - why does your database take 2 days to set up log shipping? i have a 1TB database and it only takes 6 hours
MVDBA
April 13, 2006 at 8:31 am
Our database is only 160 GB but it takes 1.5 hrs to back up, 5.5 hrs to copy the backup to the secondary, 2 hrs to restore plus the time to set up Log Shipping--I guess it's more like 10 hours. I just remember that the last time it was rebuilt I started it one day and had to finish the next 🙂
I think you're right about breaking log shipping too. Thanks.
April 19, 2006 at 3:50 am
Hi Linda,
do you use a backup software that compresses the backups on the fly? That should reduce the time for a new start at least to a half.
How often do you ship the log files, just once a day, or more often? I presume you are using the logshipping procedures that come with SQL Server, not your own? You will have to modify the restore-procedures to move the new filegroup to the existing disk...
regards
karl
Best regards
karl
April 19, 2006 at 3:54 am
redgate and imceda both provide backup compression tools to do this
imceda's sql litespeed is particularly good, but they've been bought out by quest, so the prices have gone up
MVDBA
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply