Hi Team,

We have DPM 2007. recently we noticed that the C Drive space is building up. this was due to the SQL transaction longs which has been increased up to 400 GB. It seems the transactions logs are not being truncated. im not very sure this was like this since the day we deployed DPM 2007. Now i need to enable transaction log truncation and keep C drive free. Please help me on this.

We use tape drive for long term backup and Disk for short term. i have added some snapshot for your reference. please help me on this.

Thank you.

Hi,

The log size does not necessarily reflect what is being used.  Once the log grows, it will not shrink unless you shrink it manually.

To see current "used size" and history of backups, run these sql queries.

USE DPMDB 
GO 
SELECT DB_NAME() AS DbName, 
name AS FileName, 
size/128.0 AS CurrentSizeMB,  
size/128.0 - CAST(FILEPROPERTY(name, 'SpaceUsed') AS INT)/128.0 AS FreeSpaceMB 
FROM sys.database_files; 

USE msdb
SELECT server_name, database_name, backup_start_date, backup_Finish_date, recovery_model, is_snapshot, database_backup_lsn
FROM backupset
where database_name like '%DPMDB%'
order by backup_start_date desc

You should also see events in the application event log detailing the backup.

Log Name:      Application
Source:        MSSQL$DR_INSTANCE
Date:          6/26/2015 10:28:32 AM
Event ID:      18264
Task Category: Backup
Level:         Information
Keywords:      Classic
User:          SYSTEM
Computer:      SQL3.Contoso.com
Description:
Database backed up. Database: DPMDB, creation date(time): 2014/05/12(04:39:58), pages dumped: 311, first LSN: 48:136:2, last LSN: 49:24:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{C2ADB894-F20C-44D0-A452-552E02FCAB2F}1'}). This is an informational message only. No user action is required.

Hi Mike,

We tried to backup the Log and run Shrink command. but it didn't work. instead its shrinking, the log size was increased. 

is there any special consideration to shrink the logs in DPM?

please advice.

Many Thanks.

Hi,

Can you please clarify exactly what you are protecting and how it's being protected.  If you are protecting the DPMDB as a SQL data source, the DPMDB is in simple recovery model.  DPM is not responsible for log truncation, SQL will perform that as per the below TechNet article. 

Transaction Log Truncation

Logs NEVER shrink unless done manually.

Truncation does not reduce the size of a physical log file. Reducing the physical size of a log file requires shrinking the file. For information about shrinking the size of the physical log file, see Shrinking the Transaction Log.