January 27, 2010 at 3:13 pm
Hello,
I have a SQL 2005 DB that's about half a terabyte. We are backing up the logs every hour, and using double take as a DR solution. I do not have access to this standby server. I need to have a secondary server Hot for reporting. I would like to do log shipping to another server for replication. Does it make sense to turn off the hourly logs that we backup and rely on the Log Shipping process? The current logs that are hourly are around a gig in size. I have not done log shipping in 2005. If I ship out my logs to another server to be process in log shipping, what actions should I take. Should I stop the hourly log backup and rely on the logs I am shipping?
Thank you for all who respond.
David
January 27, 2010 at 3:21 pm
If you start logshipping the log backups done as part of that process should be the only log backups you do.
If you have other log backups not done by the logshipping backup job you will break your log backup chain and logshipping will fail.
---------------------------------------------------------------------
January 28, 2010 at 7:02 am
George,
Thanks for the reply. I will ensure that the logs that are shipping are the only set I am using...
David
January 28, 2010 at 2:57 pm
I agree with George. You can configure your log shipping in such a way that
it first writes to the Local/Primary server; Mention another directory in
the Standby server where the Copy process copies before applying. That way
you will have two physical copies, so if one gets corrupted you have another
image. That is how i have configured my production environment.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply