I have scheduled a backup in the call manager. It reported an error in the log saying that could not verify db backup. The database is cdr database.
how to solve this error.
please find the backuplog attached.
09:00:00 PM] Local machine name is Callmanagerlink.
[09:00:00 PM] Local IP Address is 172.25.43.4.
[09:00:00 PM] Service account is Backadmin.
[09:00:00 PM] Backadmin has local administrative rights.
[09:00:00 PM] Backup running with Low priority.
[09:00:00 PM] Found 2816MB available on the boot partition for staging the backup.
[09:00:00 PM] Staging Cisco CallManager target 172.25.43.4.
[09:00:00 PM] Saving Cisco CallManager version.
[09:00:00 PM] Staging Hosts file.
[09:00:00 PM] Staging CallManagerAttendant file.
[09:00:01 PM] Staging IPMA configuration file.
[09:00:01 PM] Dumping Ccm0305 database on 172.25.43.4.
[09:00:10 PM] Database backup verified.
[09:00:10 PM] Staging database dump from 172.25.43.4 to staging directory.
[09:00:10 PM] Truncating transaction logs for Ccm0305 database on 172.25.43.4.
[09:00:11 PM] Dumping CDR database on 172.25.43.4.
[09:12:55 PM] [Error] Could not verify db backup.
[09:12:55 PM] Staging database dump from 172.25.43.4 to staging directory.
[09:12:55 PM] Truncating transaction logs for CDR database on 172.25.43.4.
[09:12:56 PM] Staging files from C:\Program Files\Cisco\CallDetail\CDR.
[09:12:56 PM] Backing up Cisco CallManager Registry.
[09:12:57 PM] Backing up DCD Database.
[09:13:36 PM] DC Schema information backed up successfully.
[09:13:36 PM] DC Directory configuration file backed up successfully.
[09:13:36 PM] UM Directory configuration file backed up successfully.
[09:13:36 PM] DC Directory database backed up successfully.
[09:13:36 PM] Staging TFTP files from C:\Program Files\Cisco\TFTPpath.
[09:15:13 PM] Staging files from Alternate File Location C:\Program Files\Cisco\Kaboom.
[09:15:13 PM] Staging DSN information from 172.25.43.4.
[09:15:14 PM] Staging BAT CSV files.
[09:15:14 PM] Staging BAT Template files.
[09:15:25 PM] Saving Cisco services type.
[09:15:40 PM] [Error] Could not backup Cisco CallManager successfully on 172.25.43.4.
[09:15:41 PM] Staging complete. Size of staging directory is 219MB.
[09:15:41 PM] Building archive on Tape.
[09:18:48 PM] Archive built successfully.
You might be hitting
Scheduled backups failing to backup files larger than 2 GB
You may shrank the DB.
Shrink CDR Transaction Log:
For this example
"//" delemits a comment line otherwise, this is the output from a cmd prompt where I executed steps
to shrink the CDR transaction log. Do not just copy/paste this output.
Type what I typed below and follow along on your system.
// now deal with the CDE database,
// In this case, the way CAR uses the ART database and attempts to bulk delete
// rows instead of using incremental delete or truncate has caused the transaction log
// to grow to a huge size. Checking the properties of the database shows that it has
// A large amount (1GB+) of free space.
1> use cdr
// purges current closed transactions from the transaction log. This is
// done by the backup utility when it runs at night and backs up the CDR database.
// If the customer is not backing up the CDR database or is running STIBack earlier
// than 3.5.18, then this exacerbates the large transaction log
1> backup log cdr with no_log
// now remove free space from database and transaction log before beginning to document
1> dbcc shrinkdatabase (cdr)
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
------ ------ ----------- ----------- ----------- --------------
13 1 368 96 360 360
13 2 96 63 96 56
(2 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your
// current size = number of 8KB pages used, so we start at
1768*8/1024=13.8MB for the
// and 544*8/1024=4.25MB for the transaction log
// now the problem on the customer system is that the transaction log
// is still very large with very few used pages, this is becuase the
// current pointer into the transaction log is near the end of the
// contiguous log so the unused space cannot be returned the OS. We
// have to fill up the transaction log and force the pointer to wrap
// back around to the beginning of the log, then the transaction log will
1> create table Test (test int DEFAULT NULL NULL)
1> insert into Test (test) VALUES (1)
(1 row affected)
1> declare @t integer
2> set @t = 0
3> use cdr
4> while (@t <= 100000)
6> update Test set test=1 where test=1
7> select @t = @t + 1
8> if ((@t % 500) = 0)
10> select @t
// you will see a lot of "(1 row affected)"
1> drop table test
// now try to shink the database and transaction log again
// now if you still have a large amount of free space go back to "1> create
DEFAULT NULL NULL)"
// and run through those again. I usually don't have much luck going 100000
at a time, so
set it 900000
// and go to lunch and come back. This will not cause a CPU spike, this
update takes ~1%
on the 733Mhz
// processor I'm working on. repeat everything between create
go until the
// transaction log shrinks.
stop and disable CSA if you have that running