MSDP Compaction slow
What goes on behind the scenes when a crcontrol --compactstart is issued?
My complaint is that it is really slow, and doesn't seem to make full use of the system's available resources. We hit a w...
Cycling netbackup services on the target host appears to have fixed the issue.
The only error I've found so far is a log entry inside the /<msdp>/log/spad/spad.log file.
March 11 20:31:05 WARNING [140351687415584]: 25062: NetWaitForRemote: getnameinfo(): Temporary failure in name resolution (err = -3)
I suspect this was caused due to the network being down when the host rebooted last, and NBU is set to autostart. The network problem was fixed, shortly after boot up and the host was verified to have name resolution and network connectivity, but NBU was not restarted. I'm guessing this is sort sort of bug in NBU.
