I am experiencing some problems. I perfom a back up using the Disaster Recovery Web.
I have tried backing up the CCM configuration and the CAR_CDR information and only the CAR_CDR database.
Tha process is succesfully completed, I get the 2008-04-02-13-43-45_CCMPUBLISHERNAME_cdr_car_cdrrep.tar in my SFTP server. In the log there are no errors.
But when I try to untar the backup file I get thousands of errors qith the following description:
! C:\bkp sla 2008.04.02\2008-04-02-13-43-45_CCMPUBLISHERNAME_cdr_car_cdrrep.tar: It can't be opened \var\log\active\cm\cdr_repository\preserve\20080401\cdr_StandAloneCluster_01_200804012227_14358 (var\log\active\cm\cdr_repository\car\20080401\cdr_StandAloneCluster_01_200804012227_14358 --> \var\log\active\cm\cdr_repository\preserve\20080401\cdr_StandAloneCluster_01_200804012227_14358)
! C:\bkp 2008.04.02\2008-04-02-13-43-45_CCMPUBLISHERNAME_cdr_car_cdrrep.tar: The symbolic link points to a non-existing file.
In the .tar file the 2008-04-02-13-43-45_CCMPUBLISHERNAME_cdr_car_cdrrep.tar\\var\log\active\cm\cdr_repository\car\dateName files are empty.
Why are these data missing?
The 2008-04-02-13-43-45_bio-ccmpub_cdr_car_cdrrep\common\drf\CDR_CAR\cardb.bin file is 200MB.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...