Truncating Database Transaction Log Files - Cisco CRS-1 - Carrier Routing System Router Administration Manual

Chapter 10 Managing Cisco CRS Historical Reporting
Step 4
Step 5

Truncating Database Transaction Log Files

Note
If the system determines that purging is necessary, it will purge both databases of
data that is older than the number of days specified in this field.
From the drop-down list in the Purge data older than N months field, keep the
default (13 months) or specify the required number of months.
If the system determines that purging is necessary, it will purge both databases of
data that is older than the number of months specified in this field.
Click Purge Now.
The databases are purged, and the Purge Now area refreshes.
The db_cra_log.ldf database transaction log file can become very large. This log
file is stored in the <CRSSQLServerInstallationDirectory>\Data directory (for
example, c:\Program FIles\Microsoft SQL Server\MSSQL$CRSSQL\Data) on
any CRS Server with an Historical Datastore component.
The Cisco CRS runTruncateHistDBLogs command line tool can truncate this
file to a size that you specify. You can run this command from a Microsoft
Windows command window.
The runTruncateHistDBLogs command can spend up to 5 minutes per database
log file performing the truncation. If you are substantially truncating a log file,
this time limit may not allow the command to truncate the log file to the size that
you specified. In this case, rerun the runTruncateHistDBLogs command to
truncate the log files to the desired size.
To ensure that the truncated log files are updated with current information,
perform a complete backup of the CRS databases and log files after executing the
runTruncateHistDBLogs command.
The syntax for the runTruncateHistDBLogs command is:
runTruncateHistDBLogs {"db_cra" | "tempdb"} size
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
Truncating Database Transaction Log Files
10-11