Differentials on Master

Just in case we overlook backing up Master after executing statements that m
odify it, we also have once a week full backups accompanied by a nightly dif
ferential using the NOINIT clause to append to the same backup device the fu
ll backups of Master are be
ing saved.
1. Should only full backups be made of Master, or are differentials in betwe
en full backups allowed?
Message posted via http://www.droptable.comThe systems dbs are usually way to small to do anything other than a FULL
backup. It can only take a few seconds to do a full backup on the Master
DB.
Andrew J. Kelly SQL MVP
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:be4f91128ce74dc3b75ac0d3674ed8ea@.SQ
droptable.com...
> Just in case we overlook backing up Master after executing statements that
> modify it, we also have once a week full backups accompanied by a nightly
> differential using the NOINIT clause to append to the same backup device
> the full backups of Master are being saved.
> 1. Should only full backups be made of Master, or are differentials in
> between full backups allowed?
> --
> Message posted via http://www.droptable.com|||My problem is disk space, and for redundancy appending one backup set on top
of another, so a full backup, on top of a full backup to the same backup de
vice using NOINIT, chews up needed disk space.
1. Should only full backups be made of Master, or are differentials in betwe
en full backups allowed?
2. From what I can tell (implied from your first response) that performing d
ifferentials on Master is allowed?
3. Restoring Master using differentials would not be any more dangerous that
restoring any other database using differentials, or is this a false statem
ent?
Message posted via http://www.droptable.com|||I suppose Diff's on Master is allowed. If you are that tight on disk space
you are in trouble and that should be remedied. Master DB is only a few MB
in size and there are lots of other things that can each up disk space
faster than a Master Full backup. Why are you appending them to the same
device then? If you create a new file for each backup you can delete the
old ones before you add the new one and never use more disk space than a
full cycle (how ever many days you want to keeps worth).
Andrew J. Kelly SQL MVP
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:7151d81a3055437b89361c204cb6fce1@.SQ
droptable.com...
> My problem is disk space, and for redundancy appending one backup set on
> top of another, so a full backup, on top of a full backup to the same
> backup device using NOINIT, chews up needed disk space.
> 1. Should only full backups be made of Master, or are differentials in
> between full backups allowed?
> 2. From what I can tell (implied from your first response) that performing
> differentials on Master is allowed?
> 3. Restoring Master using differentials would not be any more dangerous
> that restoring any other database using differentials, or is this a false
> statement?
> --
> Message posted via http://www.droptable.com