[cisco-voip] CAR and CDR Records

Mordechai m.rabinovich at nves.ca
Fri Oct 10 14:19:28 EDT 2008


You should definitely archive your cdrs to preserve them. If I remember
right the limit is just how many records it will keep before overwriting
them starting with the oldest. So you are in danger of quietly losing some
of your records. 

 

At the minimum you can backup your cdrs as flat files using built in tools.
You can still search through the records using something like grep. However,
if you need better querying options you need to import the records into some
off line database. You can use 3rd party solutions or what I do is import
the cdrs into a MS SQL using DTS package. Just copy a production DB to your
off line sql server.

 

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Micah Bennett
Sent: Friday, October 10, 2008 11:28 AM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CAR and CDR Records

 

Hello All

 

I was looking in some of my books to get a better understanding of the CDR
database stuff and I have a few questions.

 

My limit right now in CM is set for 2 million CDR records.  My alert is set
at 80%.  I have reached the 80% limit so I am getting alerts daily.

 

I know I can turn the alert % up, or I can ignore it and when it gets full
it will just start dropping off the oldest records.

 

I really would just like to save more records but I want to make sure it's a
safe thing to do especially with our high volume spikes and this is our busy
season.

 

The books I have say that the Call manager can safely store up to around 10
million records.  The default setting is 1.5 million.  Ours is at 2 million.

 

Right now at 1.6 million records (80% of 2 million) I have about 6 months of
Call manager CDR data.  I would like to keep a year of CDR records so I
would really like to bump that limit up to around 4 or 5 million records. 

 

We have two subscribers sending records back to our publisher.  We are on
CCM 4.2(3).

 

Is there anything I should watch out for in moving the limit this high?

 

Also, I have a lot of small flat files in the BAD directory on the
Publisher.  According to the documentation these are just corrupt CDR
records that could not be written to the database.

Is there a tool to fix these, or do they just need to be periodically
deleted so they are not taking up space.   

 

Thanks for any input.

Micah Bennett 

  _____  

From: James Buchanan [mailto:jbuchanan at ctiusa.com] 
Sent: Thursday, October 09, 2008 8:45 AM
To: Micah Bennett; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CAR and CDR Records

 

Hello,

 

That is correct. Only the CDR records are affected. 

 

Just a note-BARS does not backup the IPCC historical records. You have to
back those up doing a SQL dump.

 

Thanks,

 

James

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Micah Bennett
Sent: Thursday, October 09, 2008 8:43 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CAR and CDR Records

 

Something new for me today.  Got an email message from my systems that my
CDR records and CAR records on my Call manager cluster have reached the
specified threshold. 

I checked and the current settings are for 2 million rows with notification
at 80% full.  

I also found that the automatic purge is not currently set.  I am going to
set this for 365 days so we have the last year of data, but I wanted to
confirm that this only affects the Call Manager records and not the IPCC
Records.  My understanding is that all the IPCC records are stored in the
CRS database.  

Micah Bennett

Telecommunications Admin

Automated License Systems

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.7.6/1712 - Release Date: 10/7/2008
9:41 AM


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081010/63a29841/attachment-0001.html>


More information about the cisco-voip mailing list