Quantcast
Channel: SQL Server Manageability forum
Viewing all articles
Browse latest Browse all 1519

SQL Server - Database Transaction Log Backup. Appended or seperate files?

$
0
0

Dear All,

we have 30 productions databases in our SQL server. top big DBs are 60GB, 40GB, 8GB, 5GB and the rest are 1GB or less. we have incremental transaction-log backup set-up currently every-hour by separate file-names. so at every hour, there are 30 log backup files created, each one has its own unique names by having date-time stamp in file-name. so everyday we have 30 X 24 = 720 files created. We have retention period of 7 days for storing it on server.

Now is it a good practice to have log-files each one with its own individual name (like the current setup) or a single backup-file (without date-time stamp) for each of the databases and the incremental backup will just be appended on to it? so we will have always 30 txn-log backup files and it will just be growing every-hour when there is new incremental log-pages.

the reason is what i am thinking is with current setup, if there are 24 log-backup files for a DB, and if we need to go to the last state, we have to restore all 24 files one by one while making sure the sequence (assume we have a full DB backup once in a day). on the other hand with single txn log backup file, we just need to restore single file so it would be easy to manage and recovery is simple.

I will appreciate if you can help which option is better we can probably implement. Thanks you all.


Viewing all articles
Browse latest Browse all 1519

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>