including system and user databases in the same backup file

  • At my new job, they are basically doing 1 backup nightly that includes every user database on the server as well as all the system databases together into 1 large backup file each time. My old job made backups for each user database and then a backup that lumped all the system tables together. My question is which way is better?

  • Personally, each database has its own file and is timestamped so only 1 file ever exists in a backup set.

    Each time you want to do a restore you will need to know the file number from within the backup set that you want to restore. Personally I think that adds an extra step to something which in all honesty where you want to get the database back online quickly, slows you down that little bit.

    Also if your having to copy the bak file around the network and you only want to restore 1 DB, it would be quick to copy the DB on its own than every DB on the server.

    Thats my opinion, other may agree, disagree.

  • The other issue with having all the backups in one file is that you lose all the backups if that one file becomes corrupt.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply