MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

RE: Temporary tape errors



fixed

There is one advantage to a "21" over a *SAVSYS in BRMS. Speed. BRMS does
add some overhead, very worth it to me, but overhead nonetheless.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, March 04, 2014 10:04 AM
To: Midrange Systems Technical Discussion
Subject: Re: Temporary tape errors

There's no real advantage to a GO SAVE 21, versus the BRMS version of the
full system save. And I'd run the BRMS restore report and download the
spool file, just in case.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/04/2014 10:52 AM
Subject: Re: Temporary tape errors
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Thanks for chiming in.

The tape drive and whatnot swap would probably be scheduled for 5pm.

Regarding the full backup: Every morning at 3am we do the BRMS equivalent
of a SAVE21. Then, @4:45pm, when all billing for the next day is
finished,
we do an incremental backup of *ALLUSR libs and *SPLF.

That close enough? No incremental IFS at day's end. However, there's no
reason I couldn't run an actual SAVE21 at that time.



On Tue, Mar 4, 2014 at 10:45 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Jeff,

This is not such a big deal, what really is happening is the backplane
is
being replaced. They seem to think the problem is the backplane for the
tape. Could be. A full back up is in order before swapping the cage is
in
order, but I don't see it as a high risk procedure.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Mildenberger
Sent: Tuesday, March 04, 2014 9:35 AM
To: Midrange Systems Technical Discussion
Subject: RE: Temporary tape errors

Jeff,

We have an internal drive and the report shows lots of TTE's, I have
never
looked at this before so don't know if it has always been like this. The
report doesn't recommend replacing any media and we have not had any
issues
restoring anything off tape.

Scott

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Tuesday, March 04, 2014 6:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Temporary tape errors

I heard from my HW service provider this morning. They want to replace
the
internal 5755 drive, a 'cage', and wiring harness I think that's it,
but
he
may have said something else. I asked whether the replacement drive was
tested and would eliminate the Temporary Tape Errors ("TTE" for short).
They said it was tested, but no, the TTEs would not be eliminated.

I asked why should I change drives and still have TTEs? They said this
drive would have fewer errors. They have 15 systems in their data
center
and every internal tape drive has TTEs. Customers with internal tape
drives
also have TTEs. Systems with external tape drives (data center and
customers) don't have TTEs. Per them, TTEs on internal tape drives is
the
norm.

This *really* bothers me to think that it's acceptable in the midrange
world
to have TTEs on internal tape drives. I'm really interested in whether
anyone on this list that is using internal tape drive for backup would
check
their *VOLSTATS via the PRTERRLOG command and report.

I have yet to give them the OK to do this. When I do, I may say that I
want
to do it Friday at 5pm so if there is a catastrophic issue we have the
weekend to recover. (The last time they replaced the internal tape
drive
we
lost a hard drive upon restart.) Maybe I'm overreacting, but I am
amazed
at
how much my confidence in the HW has been shaken over the past couple of
months.
--
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.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact