[cisco-voip] How does BARS "find" CM db?

[c3voip]

Looks like the problem was related to referencing the Publisher by IP
instead of hostname in the Data Source Server configuration.  Apparently if
the BARS server is a Publisher and is backing up itself it has to be setup
via hostname not IP.

 

Thanks,

-C

 

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Friday, July 31, 2009 10:26 AM
To: c3voip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] How does BARS "find" CM db?

 

BARS uses one of two methods:

1. check dbconnection0 in the registry
-or-
2. read all dbnames from sysmaster database and find the highest number
CCM03XX database

If BARS cannot locate a few things to verify:
1. verify the dbconnection0 registry key value is correct. it should point
to the latest ccm03xx database on the publisher
2. verify registry permissions allow the account that BARS uses to read this
registry key
3. verify database is named properly.  in sql query analyzer on the
publisher run:
select name from master..sysdatabases

this shows all database names.  ccm database should be named CCM03XX and it
is case sensitive.

4. SQL permissions prevent the BARS user account from reading
master..sysdatabases or prevent the BARS user account from accessing the CCM
database.  Stare and compare of SQL permissions would find this.

/wes

On Friday, July 31, 2009 8:54:20 AM , c3voip  <mailto:c3voip at nc.rr.com>
<c3voip at nc.rr.com> wrote:



I have an error message in my BARS backup log that states the following:

 

[02:00:03 AM]   Finding Cisco Unified CallManager database.

[02:00:03 AM]   [Error]   Could not find CM db on X.X.X.X

 

I am wondering what it is looking for to "find" the CM db.

 

Thanks,

-C

 

 

 



  _____  



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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090731/6546cdae/attachment.html>