71505: Acronis Cyber Protect: SQL database logs are not truncated

use Google Translate

Gilt für: 

Operating Systems: 

Last update: 16-12-2022

Symptoms

The SQL database transaction logs are not decreasing in size after being truncated via Application-Aware backup, even though MMS logs show truncation was performed:

2021-10-10T18:54:18:107-05:00 16136 I00000000: service_process(14868): TruncateLogOf: Local881 start

2021-10-10T18:54:18:248-05:00 16136 I00000000: service_process(14868): TruncateLogOf: Local881 done

Cause

The transaction logs do not reduce in size during truncation, as the truncated space is not deallocated.

Solution

To deallocate the free space and successfully truncate the logs, perform a shrink operation in SQL Server Management Studio:

You can only perform the shrink operation on the transaction log file if there is free space on the log file. However, free space will be available most of the time after truncating the inactive part of the transaction log.

 

  1. Right-click the database and select Tasks > Shrink > Files in the drop-down menu.

  2. In the Shrink File page, change the File Type to Log.

  3. Select the transaction log file you want to shrink.

  4. Under Shrink action, select one of the options:

    • Release unused space: Releases unused space to the operating system, thus reducing the file size without moving any data.
    • Reorganize pages before releasing unused space: Releases unused space to the operating system while trying to relocate rows to unallocated pages and shrink the log to a predefined value.

    • Empty file by migrating the data to other files in the same filegroup: Moves all data from the selected log file to other files in the same filegroup and attempts to delete the empty file later.

  5. Click OK to initiate the shrink operation.

 

Tags: