When a Microsoft SQL database is set to use the Full recovery model, the transaction logs will not be purged or removed until a full back up is performed.
If a full back up of all the transactions is required, a full back up of the Deep Security Manager database and a shrink of the transaction logs should be done on a regular basis.
Meanwhile, if a back up of all the transactions is not required, then it is recommended that the back up method be switched from Full to Simple.
Do the following:
- Create a full backup.
- From the SQL server, find the DSM database. Right-click the database, go to Properties > Options.
- Under Recovery model, select Simple.
- Right-click the DSM database.
- Click Tasks > Backup. Select a destination to save the backup.
- Verify the following should be set:
- Database: DSM database
- Recovery model: Simple
- Backup Type: Full
- Right-click the DSM database again. Click Properties > Options. Under Recovery model, select Full.
- Shrink the transaction log. This task could take a long time. Do this during off-peak hours.
- Right-click the DSM database. Click Tasks > Shrink > Files.
- Under Database Files and File groups section, select Log for the File Type.
- Under Shrink action, select Reorganize pages before releasing unused space. Indicate a file size (Example: 10 MB).
- Restrict the database growth.
- Right-click the DSM database. Click Properties > Files.
- Select the DSM under Log Type File.
- Edit the Autogrowth value by clicking the button.
- Edit the value of the Maximum File Size (e.g. 20 GB).