HP3000-L Archives

July 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Paveza, Gary" <[log in to unmask]>
Reply To:
Paveza, Gary
Date:
Tue, 3 Jul 2001 09:13:04 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (77 lines)
It's funny you mention this.  I've been talking to quite a few people, our
backup vendor included, and it seems that it is fairly unusual to validate
backups.  We validate ALL our backups.  Everytime.  We also try to do them
to a different tape drive then they were written with.  DDS drives
especially seem to get out of alignment and so, when the drive finally
fails, the new one can't read the tapes.  

I'm also a big fan of creating BULDACCT jobstreams to rebuild each and every
account on the system.  Of course, this requires some work on the part of
the system admin to maintain, but it works well.  I have a jobstream which
issues the BULDACCT for each account, renames the BULDJOB1 and BULDJOB2 to
ACCOUNT.BULDJOB1.SYS and ACCOUNT.BULDJOB2.SYS.  It also does one large
buildjob which it renames to MACHINE.BULDJOB1.SYS and MACHINE.BULDJOB2.SYS.
This has saved me a lot of trouble as well.


-------------------------------------------------------------
Gary L. Paveza, Jr.
Production Support Analyst - Lead
(302) 761-3173 - voice
(877) 720-2970 - pager

        -----Original Message-----
        From:   Simonsen, Larry [SMTP:[log in to unmask]]
        Sent:   Tuesday, July 03, 2001 9:07 AM
        To:     [log in to unmask]
        Subject:        [HP3000-L] tape drive error logs.

        We were bit by a tape drive failure last week.  As a result of the
change of
        the tape drive, DAT in flavor,  a disc drive failed to spin up and
we lost 1
        days work of data.  At month end and quarter end this is quite
expensive.
        This has shed many questions as to the reliability of the hp 3000
system and
        questions the use of 3000s at our facilities.  the new tape drive
would not
        read the old backup tapes and so the CE after replacing the disc
drive
        retrofitted the old tape drive back into the system so that a
restore could
        be done.  The hp engineer stated on site that the drives usually
last only
        18 months and this drive had been in the system for 30 months.  A
few
        questions come out of this experience.

        1.      since predictive support tools do not reference the tape log
files
        is there a telesup utility which can to identify tape problems.
        2.      should we regularly ( every year) change the DAT drive for a
new
        one?
        3.      the restore after the system came up used the directory;
create
        option.  It appears that the posix directories do not have the
correct
        permissions on them. Is there a way to reset them?
        4.      since these systems are 918 systems with 2 4GB disc drives
which are
        ½ full what is the cost of adding a raid subsystem to these discs.
The
        drives do not need to be hot swappable but just recoverable in the
case of
        failure.

        Any suggestions for these type of small systems and reliability
would be
        very helpful.

        * To join/leave the list, search archives, change list settings, *
        * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2