When initially starting up Data Protection, the MCS status always seems to be down which causes the backups to fail. I have discovered that I can work around the issue by logging in to Data Protection as root after it has finished booting and stopping then starting the avagent init.d script. This is quite annoying and appears to be a simple timing issue. Can you please look into this? Please let me know if you need any additional information. Thanks.
./avagent stop SCRIPT : ./avagent PARAMETERS : stop This is a VDP appliance. Avamar avagent configuration: Avamar home : /usr/local/avamarclient avagent : /usr/local/avamarclient/bin/avagent.bin list of agents : /usr/local/avamarclient/etc/avagent-list common options : /usr/local/avamarclient/etc/avagent-flags library path : /usr/local/avamarclient/lib:/usr/lib/vmware-vix-disklib/lib64: Number of file proxies : 8 Number of image proxies : 8 Configured agents: name vardir pin ---- ------ --- proxy-1 var-proxy-1 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin,unix.pin proxy-2 var-proxy-2 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-3 var-proxy-3 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-4 var-proxy-4 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-5 var-proxy-5 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-6 var-proxy-6 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-7 var-proxy-7 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin proxy-8 var-proxy-8 vmwfile-linux.pin,vmwfile-windows.pin,vcbimage-linux.pin,vcbimage-windows.pin,vdrmigration.pin 8 agents running. Asked agents to stop. ... stopped. .... all avagents stopped avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-1/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-1/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-2/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-2/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-3/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-3/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-4/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-4/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-5/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-5/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-6/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-6/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-7/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-7/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags avagent Info <5008>: Logging to /usr/local/avamarclient/var-proxy-8/avagent.log avagent Info <5174>: - Reading /usr/local/avamarclient/var-proxy-8/avagent.cmd avagent Info <5174>: - Reading /usr/local/avamarclient/etc/avagent-flags .... unregistered all agents! ./avagent start