We have the reverse situation .
There are some windows clients in our environment that showed error in
backing up the system state etc.
We had a discussion with the managers and got a general weaver to not backup
the system state.
After a long search we found that there is no working directive to not
backup the system state.
So we experimented a lot. We found that in most cases a reboot of the client
was enough to reset the backup so it would backup the system state.
Also we found that when you install networker on a client you get a question
to activate a journal. By saying no to this journal we saw that the number
or problems with backing up the system state also decreased.
We now actively monitor the system state and issue a request for reboot to
the manager of the client-server with the issue.
p.s.
strangly enough a reboot does not work in 100% of the cases
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Howard, Patrick
Sent: Friday, August 24, 2007 11:38 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] System State - Storage node - BCV
We just has a little bit of a scare with our Storage Node. It went into
perpetual reboot, whereby it wouldn't stop rebooting itself.
Windows 2k3 / Networker 7.2.1
Long story short, is, it was due to a corrupt hive on our box. We got
past it with the help of Microsoft. However we resorted back to a
System State from 2005, since this system state wasn't getting backed
up.
We have a Client for our Storage Node with ALL, but not all was getting
backed up.
Is there an issue with this. Now that the server is back up, i was able
to run a backup with system state: in it and that backed up no problem.
Any insight? Suggestions?
We use this storage node for our BCV's
<http://www.anntaylor.com/>
Patrick S. Howard
Ann Taylor
476 Wheelers Farm Road
Milford, CT 06460
(203) 283-8772 direct
(646) 660-0426 mobile
(203) 878-3836 fax
patrick_howard AT anntaylor DOT com
www.anntaylor.com <http://www.anntaylor.com/>
______________________________________________________________________
The information in this email (including any attachments) is confidential
and may be legally privileged. Access to this e-mail by anyone other than
the intended addressee is unauthorized. If you are not the intended
recipient of this message, any review, disclosure, copying, distribution,
retention, or any action taken or omitted to be taken in reliance on it
(including any attachments) is prohibited and may be unlawful. If you are
not the intended recipient, please reply to or forward a copy of this
message to the sender and delete the message, all attachments, and any
copies thereof from your system and destroy any printout thereof.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
