Solved: BARS data (when replacing publisher server)

master001 · ‎03-29-2007

Hi there,

I gonna replace the publisher server and then connect the new publisher with the existing subscriber.

My question is:

When I run BARS and choose the data source server, should I choos both publisher and subscriber server?

Or just publisher server?

I read the BARS document as follows,

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00807a78ce.html

And "Replacing Servers During the Upgrade" as follows, http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/upgrade/upg413/replace.htm

Those documents don't include the detailed information.

Thanks.

Rob Huffman · ‎03-29-2007

Hi Qinghao,

You can identify the Sub as a backup target but its not a must unless you have different files in the TFTP folder that are not in the Publisher database. The Backup Target designation is usually for CRA,CER Servers etc. So 9 times out of 10 just the Publisher!

**For subscriber databases that are configured for backup, BARS backs up only TFTP files and CDR/CMR files.**

The following list shows the data that is backed up and restored for the Cisco CallManager publisher database:

Hosts and LMhosts files

Latest Cisco CallManager publisher database

DC Directory LDAP directory

For Cisco CallManager 3.3.x DirectoryConfiguration.ini from C:\dcdsrvr.

For Cisco CallManager 4.0(x) or later UMDirectoryConfiguration.ini.

Directory schema files avvid_schemaV*.txt

Publisher and subscriber configuration information to replication.ini file.

Cisco CallManager version to version.ini file.

If the option to backup CDR is chosen, CDR database and CDR/CMR flat files from Local CDR Path

TFTP files from C:\Program Files\Cisco\TFTPPath (the default path)

TFTP files from alternate file locations

Cisco Bulk Administration Tool (BAT) files-templates from C:\CiscoWebs\BAT, CSV files from C:\BAT and the BATversion.asp file.

HKLM\Software\Cisco Systems, Inc. (registry keys)

Cisco CallManager DSN

Security files (certificates) from under C:\Program Files\Cisco\Certificates. This applies only to Cisco CallManager 4.x or later.

LDAPConfig.ini for IPMA configuration.

From this good doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00805e6496.html#wp43860

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎03-29-2007

Hi Qinghao, Thanks man!

Good stuff, you are halfway there! The db replication problem and DC directory health problem are most likely related;

Interpreting the Results

The validation results display in the Upgrade Assistant Summary window. At the top of the window, a report summarizes the results for all modules and displays which modules failed, which modules produced warnings, and which modules passed. A link to the folder that contains all log files, including the Upgrade Assistant Summary report, displays also.

To identify a problem with the failed validation module, review the following information that displays in the Summary window:

The first link points to the log file that specifies the error or warning.

Click the first link and search for the error or warning; for example, ERR: or WARN: .

The second link points to the corrective action file that describes the log file error message and recommends the corrective action.

Click the second link to open the corrective action file. Search the corrective action file for the error message that is noted in the log file. Review the description and corrective action.

--------------------------------------------------------------------------------

Caution After you correct all problems that the utility identifies, Cisco strongly recommends that you run the utility again on every server in the cluster before you begin the upgrade.

--------------------------------------------------------------------------------

Obtaining the Log File

You can obtain the results from the utility in the following directory:

C:\Program Files\Common Files\Cisco\Logs\UPGRADEASST (for example, UPGRADEASST-05-15-2003_13.47.58)

To access the log file, click the Summary file.

--------------------------------------------------------------------------------

Tip A link to the log file displays in the Summary window for every failed validation module. To access the log file, click the link in the Summary window.

The Summary.html file, which is the Upgrade Assistant Summary report, provides the exact same information that displays in the Upgrade Assistant Summary window.

Each time that you run the utility, the utility creates a new log folder and new set of log files. The utility does not remove the log files, even if you uninstall the utility. You erase the log files when you reimage the server or manually delete the files.

From this good doc;

Using Cisco CallManager Upgrade Assistant Utility 4.1(3) for Cisco CallManager Release 3.3(5) and Later Releases

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide09186a00803f5c59.html#wp262763

**This db replication between Pub and Sub(s) is broken**

The publisher database server upgrade requires that all call-processing processes that the server handles fail over to the configured subscriber servers. Database replication must exist prior to the upgrade, so failover occurs.

This utility verifies the database replication status for all subscriber servers in the cluster. This utility validates that the database contains the latest information about the system. Validation results include Running, Idle, Failed, or Succeeded.

Have a look at this doc for the method to fix the db replication issue;

Using DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL Subscription

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801e7ddf.shtml

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎03-29-2007

Hi Qinghao,

You can identify the Sub as a backup target but its not a must unless you have different files in the TFTP folder that are not in the Publisher database. The Backup Target designation is usually for CRA,CER Servers etc. So 9 times out of 10 just the Publisher!

**For subscriber databases that are configured for backup, BARS backs up only TFTP files and CDR/CMR files.**

The following list shows the data that is backed up and restored for the Cisco CallManager publisher database:

Hosts and LMhosts files

Latest Cisco CallManager publisher database

DC Directory LDAP directory

For Cisco CallManager 3.3.x DirectoryConfiguration.ini from C:\dcdsrvr.

For Cisco CallManager 4.0(x) or later UMDirectoryConfiguration.ini.

Directory schema files avvid_schemaV*.txt

Publisher and subscriber configuration information to replication.ini file.

Cisco CallManager version to version.ini file.

If the option to backup CDR is chosen, CDR database and CDR/CMR flat files from Local CDR Path

TFTP files from C:\Program Files\Cisco\TFTPPath (the default path)

TFTP files from alternate file locations

Cisco Bulk Administration Tool (BAT) files-templates from C:\CiscoWebs\BAT, CSV files from C:\BAT and the BATversion.asp file.

HKLM\Software\Cisco Systems, Inc. (registry keys)

Cisco CallManager DSN

Security files (certificates) from under C:\Program Files\Cisco\Certificates. This applies only to Cisco CallManager 4.x or later.

LDAPConfig.ini for IPMA configuration.

From this good doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00805e6496.html#wp43860

Hope this helps!

Rob

master001 · ‎03-29-2007

Hi Rob,

Thanks. You are very helpful.

Now the publisher server(CCM3.3(5)) has been replaced. The IP phone has been registered to it.

My next step is upgrading PUB and SUB server from 3.3(5) to 4.1.(3).

Now I run CCM upgrade assisstant, there are two issues:

1. PUB shows "database replication status validation failed"

2. SUB shows "DC Directory healthy status validation failed"

Do you have any idea? Thanks.

Rob Huffman · ‎03-29-2007