There are a number of reasons why a node can go offline, before bringing the node back online the root cause must be found, else it is likely the node will go offline in in the future.
To find out why the node went offline and to bring it back online correctly you should open a Service Request with support as in-depth troubleshooting is needed.
clevya
117 Posts
0
July 21st, 2009 09:00
There are a number of reasons why a node can go offline, before bringing the node back online the root cause must be found, else it is likely the node will go offline in in the future.
To find out why the node went offline and to bring it back online correctly you should open a Service Request with support as in-depth troubleshooting is needed.
Regards,
Adam
Avamar Exorcist
462 Posts
0
July 26th, 2009 05:00
The logs rotate and get renamed so be sure to gather the ones dated from just before the node went offline
GSAN logs - to check for Avamar problems:-
/data01/cur/err.log
/data01/cur/gsan.log
Linux messages log - to check for hardware / OS issues:-
/var/log/messages