Backup Mirrored databases SQL 2005 issues.
-
We need to find a way to Backup our Mirrored databases on SQL 2005 without the transaction log files growing to a huge size. They do not truncate on Full backup as they should.The log files are currently 3-4 times bigger than the actual database.
This is causing a somewhat of a storage issue, not to mention the time being spent manually re/moving of old logs.
Can this be done in Mirrored Mode, High Performance mode, no Witness?
If not, can it be done with Transaction Log shipping?
We prefer to keep this machine free of 3rd party backup agents, that possibly address this issue...since it is production.
FYI-v. 9.00.2047 -SP1
Thanks
-
Full backups do not truncate the transaction logs, only transaction log backups do that. During a full backup, only enough of the transaction log is backed up to ensure a consistant restore (per BOL if I remember correctly).
Other than that, I am not sure. We don't have a mirrored SQL Server 2005 database at our site at this time.
-
Thanks for the input-
We are doing transaction log backups as part of maintenance, as well as shrinking.
The transaction logs remain bloated. All maintenance jobs are completing w/o error and we have no long running transactions going at this time, either....
-
so then, if your logs aren't the size you want them, do a search on this board for info on shrinking them... instead of someone answering the question here again. It has been answered in the past two weeks... and it works.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982 -
You might also want to look at using a third party backup tool such as Red Gate's SQL Backup which will perform the backup quicker, compress (and optionally encrypt) your backups saving you space and time.
--
James Moore
Red Gate Software Ltd
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply