<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David,<br>
<br>
At that step BARS on the pub is attempting to contact the BARS agent
running on the CRS server. I believe there is a log on the CRS server
as well. If not, there is at least a dcom agent. This is where we lose
some visibility - communication is strictly via DCOM between the
servers. In netstat output or packet capture can check for
communication between the servers. Then on the CRS server look for a
log from the local BARS agent. Also try restarting the BARS component
under component services and then test a backup.<br>
<br>
/Wes<br>
<br>
David Iverson wrote:
<blockquote cite="mid:003301c9128a$34732d00$0e06c90a@tki.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.3354" name="GENERATOR">
<div><font face="Arial" size="2">The servers are not part of a
domain. </font><font face="Arial" size="2">Following is the log file
from the CCM. The last line is where it just dies when going to stage
CRS:</font></div>
<div> </div>
<div><font face="Arial" size="2">[12:20:25 PM] Local machine name
is Tbcpub.<br>
[12:20:25 PM] Local IP Address is 172.16.104.15.<br>
[12:20:25 PM] Service account is Backadmin.<br>
[12:20:29 PM] Backadmin has local administrative rights.<br>
[12:20:29 PM] Backup running with Low priority.<br>
[12:20:29 PM] Found 36756MB available on the boot partition for
staging the backup.<br>
[12:20:30 PM] <br>
[12:20:30 PM] Staging Cisco Unified CallManager target 172.16.104.15.<br>
[12:20:30 PM] Saving Cisco Unified CallManager version.<br>
[12:20:30 PM] Staging LmHosts file.<br>
[12:20:30 PM] Staging Hosts file.<br>
[12:20:30 PM] Staging CallManagerAttendant file.<br>
[12:20:30 PM] Staging security files from C:\Program
Files\Cisco\Certificates<br>
[12:20:31 PM] Staging IPMA configuration file.<br>
[12:20:31 PM] Finding Cisco Unified CallManager database.<br>
[12:20:31 PM] Verifying disk space for dumping database.<br>
[12:20:31 PM] Dumping Ccm0301 database on 172.16.104.15.<br>
[12:20:37 PM] Database backup verified.<br>
[12:20:37 PM] Staging database dump from 172.16.104.15 to staging
directory.<br>
[12:20:37 PM] Truncating transaction logs for Ccm0301 database on
172.16.104.15.<br>
[12:20:38 PM] Backing up URL Services Page.<br>
[12:20:38 PM] URL services page backed up successfully.<br>
[12:20:38 PM] Verifying disk space for dumping database.<br>
[12:20:38 PM] Dumping CDR database on 172.16.104.15.<br>
[12:22:25 PM] Database backup verified.<br>
[12:22:25 PM] Staging database dump from 172.16.104.15 to staging
directory.<br>
[12:22:25 PM] Truncating transaction logs for CDR database on
172.16.104.15.<br>
[12:22:26 PM] Staging files from C:\Program
Files\Cisco\CallDetail\CDR.<br>
[12:22:26 PM] Backing up Cisco Unified CallManager Registry.<br>
[12:22:28 PM] Backing up DCD Database.<br>
[12:22:49 PM] DC Schema information backed up successfully.<br>
[12:22:49 PM] DC Directory configuration file backed up successfully.<br>
[12:22:49 PM] UM Directory configuration file backed up successfully.<br>
[12:22:49 PM] DC Directory database backed up successfully.<br>
[12:22:49 PM] Verifying disk space for copying TFTP files.<br>
[12:22:50 PM] Staging TFTP files from C:\Program Files\Cisco\TFTPpath.<br>
[12:23:38 PM] Staging files from Alternate File Location C:\Program
Files\Cisco\TFTPpath\Desktops\320x212x16.<br>
[12:23:38 PM] Staging DSN information from 172.16.104.15.<br>
[12:23:39 PM] Staging BAT CSV files.<br>
[12:23:40 PM] Staging BAT Template files.<br>
[12:23:51 PM] Saving Cisco services type.<br>
[12:24:06 PM] Successfully backed up Cisco Unified CallManager on
172.16.104.15.<br>
[12:24:06 PM] <br>
[12:24:06 PM] Staging Cisco Customer Response Solutions target
172.16.104.18</font></div>
<div> </div>
<div> </div>
<div><font face="Arial" size="2">...and nothing. </font></div>
<blockquote dir="ltr"
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">-----
Original Message ----- </div>
<div
style="background: rgb(228, 228, 228) none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>From:</b>
<a moz-do-not-send="true" title="wsisk@cisco.com"
href="mailto:wsisk@cisco.com">Wes Sisk</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>To:</b>
<a moz-do-not-send="true" title="cosmicmessenger@comcast.net"
href="mailto:cosmicmessenger@comcast.net">David Iverson</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Cc:</b>
<a moz-do-not-send="true" title="cisco-voip@puck.nether.net"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Sent:</b>
Tuesday, September 09, 2008 9:05 AM</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Subject:</b>
Re: [cisco-voip] BARS 4.0(11)</div>
<div><br>
</div>
a bit of insight:<br>
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?<br>
<br>
Given the sudden start these may be relevant:<br>
CSCsb02046 - BARS may not work when servers are members of a windows
domain<br>
CSCsh40943 - bars fails to backup when target location too large<br>
<br>
Snippets from the CRS BARS log (or lack thereof) would provide more
insight.<br>
<br>
/Wes<br>
<br>
David Iverson wrote:
<blockquote cite="mid:001c01c911f5$fa5c4320$0e06c90a@tki.local"
type="cite">
<meta content="MSHTML 6.00.2900.3354" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">My BARS quit backing up the
remote server successfully and TAC can't find anything wrong. Solution:
uninstall and upgrade to the latest version.</font></div>
<div> </div>
<div><font face="Arial" size="2">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.</font></div>
<div> </div>
<div><font face="Arial" size="2">Regards,</font></div>
<div><font face="Arial" size="2">David</font></div>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>