× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Yep - the IFS is the larger portion of the save. This box is a MIMIX
backup for our DB2 stuff and development box for programmers, but it also
backs up WAS and a Domino server. Our nightly backups of DB2 libs are
working day after day without a problem, but i've seen this same behaviour
on 3 Save 21 attempts in the past week. (twice with the same tape and once
with a different tape).





rob@xxxxxxxxx
Sent by:
midrange-l-bounce To
s@xxxxxxxxxxxx Midrange Systems Technical
Discussion
<midrange-l@xxxxxxxxxxxx>
04/22/2008 09:20 cc
AM
Subject
Re: Checking for IFS object damage
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






How long does your other part of the save take? On our systems it's not
unusual for IFS saves to take longer than *NONSYS type saves. Then again,
*NONSYS uses much less disk than IFS because of our unique setup. So, if
IFS is taking longer than maybe the sheer volume of IFS data is heating up
the drive or some such situation. Or pumping enough data to finally hit
that 1 in 10,000 possibility...
Bringing in the CE is probably your best bet.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





ChadB@xxxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/22/2008 09:08 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Checking for IFS object damage








OK, i'm familiar with dumping QSYS.LIB filesystem object descriptions to a
data file and checking against the object damage field to find damaged
objects, but how would I go about getting IFS objects from the other
filesystems into a file and checking to find out if any are damaged?

I have a Save 21 backup that is saving libraries fine, DLO objects fine,
then running for about 30 minutes on the SAV section of the procedure and
blowing up the tape drive description with an IO type error. I suspected
the media first, but then got the same results with a second tape. A CE
is
getting some hardware for later today, but i'm curious if something is
problematic on an IFS object.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.