SQL Truncation Log cannot be Truncated when Database is in Full Mode

Creating Plans to Protect Data › How to Create a Windows Backup Plan › Review the Prerequisites and Considerations › SQL Truncation Log cannot be Truncated when Database is in Full Mode

Symptom

When the database is in the Full mode and a full database backup is performed, the SQL truncation log cannot be truncated.

Solution

To resolve this problem, add two registry values to enable Arcserve UDP run the BACKUP LOG command to back up the transaction log. This command marks the space, which is already written to database file, as reusable.

Follow these steps to add the registry value:

Open the registry table editor on the agent machine using the following command:
```
regedit
```
Navigate to the following keys depending on the agent-based or agentless backup:
For agent-based backup for both 32-bit and 64-bit OS, navigate to the following key on the agent machine:
```
HKEY_LOCAL_MACHINE\SOFTWARE\CA\Unified Data Protection\Engine\AFBackupDll
```
For agentless backup, navigate to the following key. Create the registry table value inside the VM that you want to back up after applying test fix T00000080 on the proxy server. If there is no such registry table key, create the complete key path.
- 32-bit OS:
```
HKEY_LOCAL_MACHINE\SOFTWARE\CA\Unified Data Protection\Engine\AFBackupDll
```
- 64-bit OS:
```
HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\CA\Unified Data Protection\Engine\AFBackupDll
```
Create the following two registry values and and for both set the value to 1:
- dword value named BackupSQLLog4Purge .
- dword value named ForceShrinkSQLLog
The registry value is added.

The solution is in effect when the next purge job occurs.