This blog discusses solutions for the two issues,which might be encountered while protecting high churn databases using DPM.
Incremental backup job triggered by DPM transfers transaction logs from SQL Server to the DPM Server.
One of the issues with this behaviour is, at times these transaction logs might be huge that they occupy considerable space on the SQL server where SQL DB is being stored. This issue can be resolved by replacing the folder location, where the transaction logs are stored, with the symbolic link pointing to cheaper disk location.
Transaction log files are stored in a folder name “DPM_SQL_POTECT\” + “SQL Server instance name\” + “Database name” + “_log.ldf\Backup\”. This folder is created at the same location as the log definition file location. DPM_SQL_PROTECT can be replaced by symbolic link which points to cheaper disk location.
Other issue is, at times the transaction log space might be filed up due to high churn. This might lead to transaction failure. This issue can be avoided by placing appropriate check on the transaction log space being filled. Whenever the transaction log space is about to fill flush the transaction logs to the place where backup job expects them to be located. The below example demonstrates the same.
Example: Create below alert which can flush the transaction logs as and when the transactions log space is about to be filled. These get copied to location where the DPM Job can pick the logs.
Create a Job as mentioned below
Check the Job ID
Assign the alert with relevant performance condition