Re: [Networker] Corrupt Data

Interesting.  We just had a client disk go bad (win2k) and it reported I/O 
errors in our published savegroup logs....although, looking at it again, the 
save sets were listed as Successful, it was the details that showed the errors. 
 So if you are counting on the Networker GUI to list it as Failed, I guess you 
would not see it.
--Ted
PS.  we publish to a website, have the notification script parse the logs and 
run an ftp job to a hosting server, then use a super generic perl script to 
search by pattern match and display in reverse chronological with date/time 
stamp the group completed.  ie.
dapsfp30z_08081042.txt -- Succeeded
dapsfp30z_08071015.txt -- Succeeded


>From "dapsfp30z_08081042.txt -- Succeeded":
Sun Aug  8 10:42:28 CDT 2004

savegroup: P06_1000 completed (dapsfp30z Succeeded)

--- Successful Save Sets ---

* dapsfp30z:C: savegrp: suppressed 1827 lines of output
* dapsfp30z:C: C:WINNTWindows Update Setup FilesMPLAY2U.CAB: The request could 
not be performed because of an I/O device error.
* dapsfp30z:C: C:WINNTWindows Update Setup FilesOEEXCEP.CAB: The request could 
not be performed because of an I/O device error.
* dapsfp30z:C: C:WINNTWindows Update Setup FilesREADME.CAB: The request could 
not be performed because of an I/O device error.
* dapsfp30z:C: C:WINNTWindows Update Setup FilesWAB.CAB: The request could not 
be performed because of an I/O device error.
* dapsfp30z:C: C:WINNTWindows Update.log: The request could not be performed 
because of an I/O device error.
* dapsfp30z:C: C:WINNTWINNT32.LOG: The request could not be performed because 
of an I/O device error.
* dapsfp30z:C: C:WINNT_default.pif: The request could not be performed because 
of an I/O device error.
dapsfp30z: C: level=full, 3980 MB 00:40:29 97722 files
* dapsfp30z:D: savegrp: suppressed 1495 lines of output
* dapsfp30z:D: D:usernvisionlayoutGM_PRODUCT_TREND.XNV: The request could not 
be performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutLTD_VDO_REV-OTHER.xnv: The request could not 
be performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutLTD_VDO_REV_TRND-CMG.xnv: The request could 
not be performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutLTD_VDO_REV_TRND-OTHER.xnv: The request could 
not be performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutLTD_VDO_REV_TRND.xnv: The request could not 
be performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutREG_REV_TREND.XNV: The request could not be 
performed because of an I/O device error.
* dapsfp30z:D: D:usernvisionlayoutREG_REV_TREND_TOT.XNV: The request could not 
be performed because of an I/O device error.
dapsfp30z: D: level=full, 4884 MB 00:39:34 48624 files
dapsfp30z: SYSTEM STATE: level=full, 16 MB 00:00:09 16 files
* dapsfp30z:SYSTEM DB: Removable Storage Database - rsmow: Exported the RSM 
database.
dapsfp30z: SYSTEM DB: level=full, 914 KB 00:00:13 10 files
dapsfp30z: SYSTEM FILES: level=full, 238 MB 00:01:01 1911 files
dalegp02: index:dapsfp30z level=full, 87 MB 00:00:10 141 files




-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Chad Smykay
Sent: Monday, August 09, 2004 11:09 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Corrupt Data


 On a side note:  Legato will backup corrupt data and is on the disk, this
is true.  However I just wanted everyone to know that if you have a disk
that is going bad Legato will not report any I/O read errors it gets from
the client as ANY type of failure.

We have seen some issues were a disk was going bad and Legato was logging
I/O errors to the daemon.log. It was unable to finish the backup of the bad
disk because it could not read the rest of it (for whatever reason, seek
timeout etc..) and ended up reporting it as a success.  So just FYI review
your daemon.log files every once and while :)


Chad Smykay, RHCE, LCNA
Systems Storage Administrator
Rackspace Managed Hosting (TM) - The Managed Hosting Specialist (TM)


-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] 
On
Behalf Of Andrew Rotramel
Sent: Monday, August 09, 2004 10:47 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Corrupt Data

Legato will back up whatever ones and zeros are on the disk you are backing
up.





"Ciolek, Ken" <Ken.Ciolek AT AIG DOT COM>@LISTMAIL.TEMPLE.EDU> on 08/08/2004
08:45:17 PM

Please respond to Legato NetWorker discussion
       <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>; Please respond to "Ciolek, Ken"
       <Ken.Ciolek AT AIG DOT COM>

Sent by:    Legato NetWorker discussion <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>


To:    NETWORKER AT LISTMAIL.TEMPLE DOT EDU
cc:

Subject:    [Networker] Corrupt Data


Will Legato backup corrupt data. Is it smart enogh to know if the data is
corrupt or not. I would say no but my management wanted me to confirm.

\

--
Note: To sign off this list, send a "signoff networker" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
 =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=



-----------------------------------------
The information in this email, and any attachments, may contain confidential
information and is intended solely for the attention and use of the named
addressee(s). It must not be disclosed to any person(s) without
authorization. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are not
authorized to, and must not, disclose, copy, distribute, or retain this
message or any part of it." If you have received this communication in
error, please notify me immediately.

--
Note: To sign off this list, send a "signoff networker" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=