February 9, 2010 at 4:13 pm
I have two server one in California and the other one in NJ.I log ship data from NJ to California, and the logs are being restored every 1 minutes in California.On every weekend,we stop log shipping and run some maintainance jobs(DBCC CheckDB,REIndexing,...) in NJ,Which this cause the increase on the size of trasnaction log file,So at the end of maintainance job I truncate the transaction log file.Cuase of this I have to rebuild the log shipping every Weekend, and I have to transfer the backup files from NJ to Burbank(Which takes a long time,because the size of backup is 100GB).Is there any way that I can pass the rebuilding the logshipping on the weekend?
What will happen,if I do not stop log shipping and meanwhile run the maintainance job(DBCC CheckDB,DBReIndex,Backup,...)?
February 9, 2010 at 6:52 pm
If you transfer the rebuilds, those logs and the rebuilds, transfer to the standby. It's a lot, but it's probably less than sending over the full again.
February 9, 2010 at 8:04 pm
Thanks a lot for your reply.
Do You mean just sending the trasnasction logs that has been caused during the maintainance jobs?
February 10, 2010 at 8:42 am
Yes. You can't get around it. Either you send the changes through in the log with backups (log shipping), log reads (database mirroring), or a full backup (reset log shipping).
The reality is those changes need to move through and by truncating the log and trying to avoid sending a large log, you're still sending changes through with a new full backup.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply