Hello, I just upgraded my Solaris 2.9 NetWorker server from 7.2.1 to 7.3 and now I get these errors on sporadic Unix filesystems. I see it on all flavors, AIX, Solaris, HP-UX. I found a solution in the error message guide that said to clear up some space in the /nsr directory for log purposes and I have done this. The strange thing is that it only occurs on typically 1 of the filesystems on the systems:
Does anybody have any ideas???
Thanks
NetWorker savegroup: (alert) Default completed, Total 28 client(s), 11 Failed, 1 Succeeded with warning(s), 16 Succeeded. Please see group completion details for more information.
Failed: artemis, david, deer, dorf, felicity, galleon, hoosier, oskie, starbuck, tapir, tribble Succeeded with warning(s): jaws05
Succeeded: ausccm, bigsky, blackcomb, dlavende, horns, icebat.bmc.com, ike, jackson, munin, pari, quazar, stowe, titan, wolf, zhadum, zurich
Start time: Sun Feb 12 21:54:37 2006
End time: Mon Feb 13 03:30:50 2006
--- Unsuccessful Save Sets ---
* artemis:/export/patrol Cannot determine status of backup process. Use mminfo to determine job status.
* david:/usr Cannot determine status of backup process. Use mminfo to determine job status.
* deer:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* dorf:/oradata Cannot determine status of backup process. Use mminfo to determine job status.
* felicity:/data3 Cannot determine status of backup process. Use mminfo to determine job status.
* galleon:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* hoosier:/var Cannot determine status of backup process. Use mminfo to determine job status.
* oskie:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* starbuck:/tmp Cannot determine status of backup process. Use mminfo to determine job status.
* tapir:/tmp/ccm Cannot determine status of backup process. Use mminfo to determine job status.
* tribble:/export/HOME Cannot determine status of backup process. Use mminfo to determine job status.
Does anybody have any ideas???
Thanks
NetWorker savegroup: (alert) Default completed, Total 28 client(s), 11 Failed, 1 Succeeded with warning(s), 16 Succeeded. Please see group completion details for more information.
Failed: artemis, david, deer, dorf, felicity, galleon, hoosier, oskie, starbuck, tapir, tribble Succeeded with warning(s): jaws05
Succeeded: ausccm, bigsky, blackcomb, dlavende, horns, icebat.bmc.com, ike, jackson, munin, pari, quazar, stowe, titan, wolf, zhadum, zurich
Start time: Sun Feb 12 21:54:37 2006
End time: Mon Feb 13 03:30:50 2006
--- Unsuccessful Save Sets ---
* artemis:/export/patrol Cannot determine status of backup process. Use mminfo to determine job status.
* david:/usr Cannot determine status of backup process. Use mminfo to determine job status.
* deer:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* dorf:/oradata Cannot determine status of backup process. Use mminfo to determine job status.
* felicity:/data3 Cannot determine status of backup process. Use mminfo to determine job status.
* galleon:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* hoosier:/var Cannot determine status of backup process. Use mminfo to determine job status.
* oskie:/data1 Cannot determine status of backup process. Use mminfo to determine job status.
* starbuck:/tmp Cannot determine status of backup process. Use mminfo to determine job status.
* tapir:/tmp/ccm Cannot determine status of backup process. Use mminfo to determine job status.
* tribble:/export/HOME Cannot determine status of backup process. Use mminfo to determine job status.