July 10, 2009 at 10:47 am
Currently I'm taking the backs of System databases along with user databases every day and log backup every hour. But I thinnk we do not need to take every 1 hr log backup for system databases.
Do I need to create a separate log backup job for system databases and daily twice? is that makes sense?
please advice me
July 10, 2009 at 11:03 am
I think a lot of this question is preference. master I only do full backups on, its little, and it really doesn't change. Yesterday's copy will be almost as good as todays 99.999% of the time, I'm willing toi risk that .001. As far as msdb, I think that one deserves to be treated mostly like a user DB in that it gets full backups and log dumps periodically through the day. Keep in mind what it stores:
1. Jobs and their associated history.
2. Records of all backups in the system, its a whole lot easier to restore a backup and associate log dumps if you don't have to do them one by one..
3. SSIS packages and history.
So I'd probably just leave it the way it was and decide, if/when I needed to do a master restore whether I cared enough to apply all the transaction log dumps.
CEWII
July 10, 2009 at 11:07 am
i think it goes to how much business data would be lost.
if the system crashed half an hour before the next log backup, and you had to restore to the last backup,how much actual work would have to be duplicated/redone by the business side of things? for example, although almost 4 hours of time went by, but only two records were entered that morning, then less frequent backups might be ok. the objective is to minimize duplication of work in the event of a real disaster, i think.
ask yourself the opposite question as well: if you are taking backups very frequently, are you really hurting yourself, or just minimizing the losses of business data by frequent log backups?
Lowell
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply