We currently are using DPM 2012 to back up our SQL server db’s. The issue we are facing with most of our larger databases, when restoring the databases to any other instance the transaction logs are extremely big, sometimes bigger that the data file itself. Db’s are being backup at least hourly. It is my understanding that truncation will occur on the transaction log. However, we would like to shrink the transaction file to allow us the restoring process easier. Is this a recommended course of action? When it will be best to perform? Should it be done manually, thru a SQL Maintenance Job or doing a DPMPre-Backup/Post-Backup script?Any Best Practices by Microsoft for this task.
↧