September 15, 2004 at 11:00 pm
Hi all,
I want to deploy Log shipping to sync a standby server with my production server. ( I have Win 2000 server with SQl server Ent. Edition and the network line is 380 KB/s).
The size of the production database is around 4 Gb.
The normal transaction log backed up after every 30 mins and its generate a volume of 25~30 MB of data. There would be no probs in trasporting the said data, but my problem is one of the Transaction log backup which has been taken after the full backup operation has been performed. the size of the log became around 1 GB.
Though I can reduce the dusration for transaction log backup to get the smaller chunks of transaction log, but still the volume of the data remian same.
Is it possible to truncate the transaction log before the backup OR avoid the transaction to be recoeded in the transaction log only for the backup operation for the Log shipping job ?
If any body deploy the Log shipping and encounter the same problem pleae share the solution or the status.
Thanx in advance....
September 17, 2004 at 12:27 am
You could use sql litespeed which produces compressed backups or use a zip program on the logs
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
September 21, 2004 at 10:38 am
Hello
My experience has been to
I would resume transaction log backups immediately after the full backup. When the full restore finished, I had a script generated that would apply logs on the warm spare. After running the script, I let my log ship routine run on auto pilot once again.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply