CUCM 6.1.1.2000-3: issue with backup

[raziel78kain]

Hello,

we have a CUCM 6.1.1.2000-3.

We have tried to make a manual backup, but it has failed when it had to backup the component "CCMDB".

In the log file, we can read:

----------

----> BEGIN Standard Output
Stopping CAR services prior to taking DB backup
CDRREP: Invoking CAR Services deactivation Script
CDRREP: Checking CAR services status, please wait ...
CDRREP: Stopping Cisco CAR Scheduler
Service Manager is running
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
Cisco CAR Scheduler[STOPPING]
"Cisco CAR Scheduler" may take more time to stop.
Please check the status by using "list" command
Warning: Start and stop operation can be used
on "Cisco CAR Scheduler" only after it stops successfully
CDRREP: Could not stop Cisco CAR Scheduler
CDRREP: Exiting CAR services deactivate script with error code 99
CAR services failed to stop; backup cannot proceed until all CAR services are stopped. TERMINATING

----> END Standard Output

----------

Now, in Serviceability we can see that the service "Cisco CAR Scheduler" is in "Stopping", and we can't stop, start or restart the service.

Wha'ts wrong?

How can we restart the service?

Thanks in advance for your help.

Best regards.

[Rob Huffman]

Hi Raziel,

It looks like you are hitting this bug;

CSCsq11246 - CAR DRS fails as car does not deactivate services using FQDN

Backup fails during the "Invoking CAR Services deactivation Script" stage. CAR services can not be stopped and the backup fails.

Conditions:

Log File:

2008-04-28-12-55-29_b_cucmpub_ccm_ccmdb.log=================================

==============

======

Server : CUCMPUB

Feature : CCM

Component : CCMDB

Time Completed: 2008-04-28-12-56-45

Result Code : 101

Result String : ERROR

=====================================================

Stopping CAR services prior to taking DB backup

CDRREP: Invoking CAR Services deactivation Script

CDRREP: Checking CAR services status, please wait ...

CDRREP: CAR Scheduler initial status is - activated

CDRREP: CAR Web Service initial status is - activated

CDRREP: Deactivating Cisco CAR Scheduler using hostname CUCMPUB

CDRREP: Could not deactivate Cisco CAR Scheduler using HostName CUCMPUB

CDRREP: Deactivativating Cisco CAR Scheduler using HostIP 192.x.x.x

CDRREP: Could not deactivate Cisco CAR Scheduler using HOSTIP 192.x.x.x

CDRREP: Exiting CAR services deactivate script with error code 99

CAR services failed to stop; backup cannot proceed until all CAR services

are stopped.

TERMINATING

----> BEGIN Standard Output

Stopping CAR services prior to taking DB backup

Service Manager is running

Cisco CAR Scheduler[STARTED]

Service Manager is running

Cisco CAR Scheduler[STARTED]

CDRREP: Could not deactivate Cisco CAR Scheduler using HOSTIP 192.x.x.x

CAR services failed to stop; backup cannot proceed until all CAR services

are stopped.

TERMINATING

Workaround:

Manually stop CAR and the back up works.

Also  as a workaround please ask the customer to set the server name to  "CUCMPUB" from ccmadmin page as the hostname is CUCMPUB. Car uses the  hostname to deactivate the services before DRS starts.  Hence changing  the server name from ccmadmin pages would help customer schedule DRS  backups without manual intervention.

Also ideally we recommend  that the customer change the hostname in database as well as cli if they  change the server name at any point. Currently the server name in  database and cli does not match in the customer machine.

Cheers!

Rob

"Show a little faith, there's magic in the night" - Springsteen

[raziel78kain]

Hello Rob,

it doesn't seem to be the same bug...

In fact, the log file is different.

Regards.