10-21-2008 05:33 AM - edited 03-15-2019 02:04 PM
Hello
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 ?
Regards
Manu
10-21-2008 08:22 AM
Hi Manu,
Maybe this bug?
CSCsk27160 Bug Details
DRS Status wrong if DRF Master service has been down in the past
Symptom:
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.
Conditions:
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.
Workaround:
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
Fixed
Severity
4 - minor
Last Modified
In Last Year
Product
Cisco Unified Communications Manager (CallManager)
Technology
1st Found-In
6.0(1.1000.37)
Fixed-In
6.1(0.9901.378)
6.0(1.2105.1)
6.1(1.1000.11)
Hope this helps!
Rob
10-21-2008 11:26 PM
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.
Regards
Manu
10-28-2008 04:54 PM
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.
Symptom:
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.
04-30-2009 10:21 AM
I also have the same problem and I am running version 6.1.3
11-04-2009 02:16 PM
Any update? I'm also having this problem on 6.1.3...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: