August 27, 2012 at 10:31 am
Should a subscriber database in a tranactional replication scenario be regularly backed up to control log file size?
The log file in a subscriber database is nearly twice the size as the log file on the Publisher. Shrinkfile didn't reduce the size very much, and I noticed their is no backup job. Do I need to backup the subscriber and create a backup job? Or is there a more appropriate way to control the log file size? Both the Publisher & Subscriber are set to Full recovery model.
August 27, 2012 at 1:39 pm
dan-572483 (8/27/2012)
Should a subscriber database in a tranactional replication scenario be regularly backed up to control log file size?The log file in a subscriber database is nearly twice the size as the log file on the Publisher. Shrinkfile didn't reduce the size very much, and I noticed their is no backup job. Do I need to backup the subscriber and create a backup job? Or is there a more appropriate way to control the log file size? Both the Publisher & Subscriber are set to Full recovery model.
A subscription database should be treated just as a publication database; regular backups, checking indexes, etc. If you are not taking log backups anyway, and don't mind reinitializing or recreating the subscription in the event that the publication database needs to be recovered... Why not just put it into Simple recovery? Of course, that depends on a lot of factors that only you can determine.
Jared
CE - Microsoft
August 27, 2012 at 2:04 pm
The plan we're looking at now is...
1) Change the subscriber to Simplle Recovery
2) Full Backup
3) Shrinkfile command.
The Publisher DB already has daily full backups and transaction log backups 4 times an hour.
Safe enough?
Dan
August 27, 2012 at 2:19 pm
dan-572483 (8/27/2012)
The plan we're looking at now is...1) Change the subscriber to Simplle Recovery
2) Full Backup
3) Shrinkfile command.
The Publisher DB already has daily full backups and transaction log backups 4 times an hour.
Safe enough?
Dan
As long as you shrink the file to a proper size. You don't want to be shrinking the file regularly... So only shrink it small enough to where it will be able to handle the transactions.
Jared
CE - Microsoft
August 27, 2012 at 2:45 pm
The size of the Publisher DB log file should be about right - thanks.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply