CM 6.0 - Master agent might still be processing this operation or may be do

Unanswered Question
Oct 21st, 2008


I've the following problem when i try to operate manual backup:

"... Master agent might still be processing this operation or may be down ..."

I try to stop and restart all DRF services (Cisco DRF Master, Cisco DRF Local) on both servers in my cluster ... without success !

Any idea ?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
rob.huffman Tue, 10/21/2008 - 08:22

Hi Manu,

Maybe this bug?

CSCsk27160 Bug Details

DRS Status wrong if DRF Master service has been down in the past


The Status bar in the Disaster Recovery System Backup displays:

Local Agent is not responding. This may be due to Master or Local Agent being down.

However the local agent and master agent are up and working correctly.


Occurs if at some point in the past you visited the Disaster Recovery System

web page while the Master Agent was down. After fixing the problem with the

Master Agent, the DRS web page still shows the error.


Restart Cisco Tomcat services (note this may impact other services on the server

that rely on Tomcat) or Reboot the server to clear the error. You can also just

ignore the error as long as backups are really working Status



4 - minor

Last Modified

In Last Year


Cisco Unified Communications Manager (CallManager)


1st Found-In






Hope this helps!


malosse Tue, 10/21/2008 - 23:26

Hello Rob

Many thanks for your update.

I haven't found this bug, but, i think this is my problem ;-)

Today, i'll try to stop and restart Tomcat, but the best way for me is to upgrade to 6.1(1.1000.11)

I'll inform you next.



jarogers2 Tue, 10/28/2008 - 16:54

I have the same symptom. Mine, however, is on a CUCM 6.1.1-200-3 so presumably a version where the issue is resolved.


Disaster Recovery Backup runs over and over again despite only being scheduled for twice a week. Upon completion of the backup, the process starts over immediately and does not allow for modification of the credentials/targets.

Cannot manually stop the service from GUI and CLI restart of the process yields the same result.

Only glaring issue I see is the customer also put the Sub to be backed up as well. Will update if I find a resolution. Restarting Tomcat did not resolve this particular issue.

cmcinally Thu, 04/30/2009 - 10:21

I also have the same problem and I am running version 6.1.3


This Discussion