[cisco-voip] BARS 4.0(11)

Tue Sep 9 11:19:24 EDT 2008

How big is your CDR database? And in a DR situation do you really want
it recovered ? How often do you use ART today to track something down in
CDRs?

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of David Iverson
Sent: Tuesday, September 09, 2008 10:42 AM
To: Wes Sisk
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] BARS 4.0(11)

The servers are not part of a domain. Following is the log file from the
CCM. The last line is where it just dies when going to stage CRS:

[12:20:25 PM]   Local machine name is Tbcpub.
[12:20:25 PM]   Local IP Address is 172.16.104.15.
[12:20:25 PM]   Service account is Backadmin.
[12:20:29 PM]   Backadmin has local administrative rights.
[12:20:29 PM]   Backup running with Low priority.
[12:20:29 PM]   Found 36756MB available on the boot partition for
staging the backup.
[12:20:30 PM]   
[12:20:30 PM]   Staging Cisco Unified CallManager target 172.16.104.15.
[12:20:30 PM]   Saving Cisco Unified CallManager version.
[12:20:30 PM]   Staging LmHosts file.
[12:20:30 PM]   Staging Hosts file.
[12:20:30 PM]   Staging CallManagerAttendant file.
[12:20:30 PM]   Staging security files from C:\Program
Files\Cisco\Certificates
[12:20:31 PM]   Staging IPMA configuration file.
[12:20:31 PM]   Finding Cisco Unified CallManager database.
[12:20:31 PM]   Verifying disk space for dumping database.
[12:20:31 PM]   Dumping Ccm0301 database on 172.16.104.15.
[12:20:37 PM]   Database backup verified.
[12:20:37 PM]   Staging database dump from 172.16.104.15 to staging
directory.
[12:20:37 PM]   Truncating transaction logs for Ccm0301 database on
172.16.104.15.
[12:20:38 PM]   Backing up URL Services Page.
[12:20:38 PM]   URL services page backed up successfully.
[12:20:38 PM]   Verifying disk space for dumping database.
[12:20:38 PM]   Dumping CDR database on 172.16.104.15.
[12:22:25 PM]   Database backup verified.
[12:22:25 PM]   Staging database dump from 172.16.104.15 to staging
directory.
[12:22:25 PM]   Truncating transaction logs for CDR database on
172.16.104.15.
[12:22:26 PM]   Staging files from C:\Program
Files\Cisco\CallDetail\CDR.
[12:22:26 PM]   Backing up Cisco Unified CallManager Registry.
[12:22:28 PM]   Backing up DCD Database.
[12:22:49 PM]   DC Schema information backed up successfully.
[12:22:49 PM]   DC Directory configuration file backed up successfully.
[12:22:49 PM]   UM Directory configuration file backed up successfully.
[12:22:49 PM]   DC Directory database backed up successfully.
[12:22:49 PM]   Verifying disk space for copying TFTP files.
[12:22:50 PM]   Staging TFTP files from C:\Program Files\Cisco\TFTPpath.
[12:23:38 PM]   Staging files from Alternate File Location C:\Program
Files\Cisco\TFTPpath\Desktops\320x212x16.
[12:23:38 PM]   Staging DSN information from 172.16.104.15.
[12:23:39 PM]   Staging BAT CSV files.
[12:23:40 PM]   Staging BAT Template files.
[12:23:51 PM]   Saving Cisco services type.
[12:24:06 PM]   Successfully backed up Cisco Unified CallManager on
172.16.104.15.
[12:24:06 PM]   
[12:24:06 PM]   Staging Cisco Customer Response Solutions target
172.16.104.18

...and nothing. 

	----- Original Message ----- 

	From: Wes Sisk <mailto:wsisk at cisco.com>  

	To: David Iverson <mailto:cosmicmessenger at comcast.net>  

	Cc: cisco-voip at puck.nether.net 

	Sent: Tuesday, September 09, 2008 9:05 AM

	Subject: Re: [cisco-voip] BARS 4.0(11)

	a bit of insight:
	BARS on CM contacts the BARS client/stub/target running on CRS.
The client on CRS should generate logs providing some insight.  Those
logs may provide insight on the reason for failure.  CSCef13462 is
notorious for this.  Does that workaround make any difference for you?

	Given the sudden start these may be relevant:
	CSCsb02046 - BARS may not work when servers are members of a
windows domain
	CSCsh40943 - bars fails to backup when target location too large

	Snippets from the CRS BARS log (or lack thereof) would provide
more insight.

	/Wes

	David Iverson wrote: 

	My BARS quit backing up the remote server successfully and TAC
can't find anything wrong. Solution: uninstall and upgrade to the latest
version.

	What happens during the normal process is that BARS is running
on CCM and can back up that server with no problem. When it goes to
backup CRS, it just sits there and churns until I kill the process. I
have removed and readded the server IP/authentication and it validates.
I even rebooted CRS cleanly. I have been told by 2nd level that the
barbicomm.dll file checked out clean. Has anyone else run into this? I
hate the reinstall/reboot approach to solving what looks like a simple
problem with an overlooked solution.

	Regards,

	David

________________________________

	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080909/203432a3/attachment-0001.html>