Re: [foxboro] 4MM Tape Problems

Bob,

this is a bit of a strange one. If you can tar files on and off of the tape
then it should be pretty safe to assume that the tape and drive are ok.

You should be able to read any of the backup tapes built by any of the
various flavored Foxboro scripts because they all use ufsdump to generate
the ufs tape, and use ufsrestore to read them. I know that the QF fixed a
problem with the blocking size to the tape and that you have to use the
restore script that is shipped with the QF to restore the workstation but
you should still be able to read the contents with ufsrestore. If you can
read the tape then you should be able to restore to a disk which is the same
size as the one archived. If the disk is a different size you will have to
edit the restore script - tar it to /tmp and comment out the restore_mddb
function call at the very end of the script, save and proceed.

Best regards. Rob.

>  -----Original Message-----
> From:         foxboro-bounce@xxxxxxxxxxxxx   On Behalf Of "Balmer, Robert
> D." <rbalmer@xxxxxxxxxxxxxxx>
> Sent: Thursday, April 03, 2003 11:43 PM
> To:   'Foxboro DCS Mail List'
> Subject:      Re: [foxboro] 4MM Tape Problems
> 
> 
> Rob
> Thanks for the email. I used the scripts in QF991274C to make the ba=
> ckup and
> to attempt the restore.  Checked all the normal stuff like you =
> said, and
> even checked to make sure I had purchased the correct tapes(ki=
> nda like is it
> plugged thing). I can tar files off my AW and tar them of=
> f on the off line
> machine. I am wondering if there is something wrong wi=
> th the script.
> Although I used the same scripts to rebuild an AW in 2000=
> .
> Bob Balmer
> 
> -----Original Message-----
> From: McLeish, Rob [mailto:=
> rob.mcleish@xxxxxxxxxxxx]
> Sent: Wednesday, April 02, 2003 9:48 PM
> To: =
> 'foxboro@xxxxxxxxxxxxx'
> Subject: Re: [foxboro] 4MM Tape Problems
> 
> 
> Ro=
> bert,
> 
> get a copy of QF991274C from the Foxboro web, install it and run=
>  the
> /usr/local/find_tape script. This will find the tape and point you =
> to the
> correct device (/dev/dsk/xxx). If it doesn't try running the add_=
> periphs or
> doing a boot -r to attach the tape. Once you have a tape driv=
> e that is
> working you should have no problems reading the tape, it's a b=
> ackup of an AW
> so use ufsrestore ivfs /dev/dsk/xxx 1 to read the root vo=
> lume you wont need
> to link the device to rst9. If you still can't get th=
> e find_tape to
> recognise the tape you might have to shutdown the worksta=
> tion to the prom
> level and do probe-scsi to check the tape.
> 
> One other=
>  thing to check is the type of tape and tape drive. You can read
> DDS1 (9=
> 0M) tapes in DDS1,2 or 3 drives but you can not go the other way so
> if y=
> ou have a backup on a DDS2 or DDS3 tape and you drive is DDS1 then your
> =
> stuffed.
> 
> 
> hope this helps.
> 
> Robert McLeish.
> Foxboro Australia.
> 
> =
> 
> >  -----Original Message-----
> > From:       foxboro-bounce@xxxxxxxxxxxxx   =
> On Behalf Of "Balmer, Robert
> > D." <rbalmer@xxxxxxxxxxxxxxx>
> > Sent:       Th=
> ursday, April 03, 2003 1:47 AM
> > To: 'Foxboro DCS Mail List'
> > Subject:=
>       [foxboro] 4MM Tape Problems
> >
> > In trying to satisfy the corporate IT=
> /IS requirements I have had to
> > come up with some method to check my b=
> ackup tapes.
> > So I  got a sparc 5 box off the internet, got me another =
> 4MM tape drive
> > just
> > like the units I use to backup our AW51 B's.
> >=
>  For what ever reason the unit I am using to check the tapes will not rea=
> d
> > the tapes made on either of my AW51B's.
> > I have also erased an old=
>  backup tape on the off line unit.  The AW51 B's
> > will not recognize th=
> at tape.  I wonder what I have set up wrong. Anyone
> > out
> > there have =
> a clue for this grayed moment of mine?
> > Thank You
> >
> > Robert Balmer
> =
> > Climax Molybdenum Co.
> > Applications Analyst/Programmer
> > Fort Madiso=
> n Iowa
> > 319 463 2206
> >
> > This message (including attachments) is for=
>  the designated recipient
> > only and may contain privileged, proprietar=
> y, or otherwise
> > confidential information. If you are not the intended=
>  recipient or
> > have received this message in error, please notify the =
> sender
> > immediately and delete the original. Any other use of this e-m=
> ail is
> > prohibited.
> >
> > Este mensaje (incluyendo los archivos adjun=
> tos) est=E1 dirigido s=F3lo al
> > receptor se=F1alado y puede contener i=
> nformaci=F3n de car=E1cter
> > privilegiada, privada o confidencial. Si u=
> sted no es el receptor
> > se=F1alado o bien ha recibido este mensaje por=
>  error, por favor
> > notifique inmediatamente al remitente y elimine el =
> mensaje original.
> > Cualquier otro uso de este mensaje de correo electr=
> =F3nico est=E1
> > prohibido.
> >
> >
> >
> >
> > ________________________=
> ______________________________________________
> > _
> > This mailing list =
> is neither sponsored nor endorsed by Invensys Process
> > Systems (formerl=
> y The Foxboro Company). Use the info you obtain here at
> > your own risks=
> . Read http://www.thecassandraproject.org/disclaimer.html
> >
> > foxboro =
> mailing list:             http://www.freelists.org/list/foxboro
> > to sub=
> scribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> > to=
>  unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =
> >
> 
> 
> 
> ____________________________________________________________=
> ___________
> This mailing list is neither sponsored nor endorsed by Inven=
> sys Process
> Systems (formerly The Foxboro Company). Use the info you obt=
> ain here at your
> own risks. Read http://www.thecassandraproject.org/disc=
> laimer.html
> 
> foxboro mailing list:             http://www.freelists.or=
> g/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxx=
> g?subject=3Djoin
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxx=
> rg?subject=3Dleave
> 
> This message (including attachments) is for the de=
> signated recipient only and may contain privileged, proprietary, or other=
> wise confidential information. If you are not the intended recipient or h=
> ave received this message in error, please notify the sender immediately =
> and delete the original. Any other use of this e-mail is prohibited.
> 
> =
> Este mensaje (incluyendo los archivos adjuntos) est=E1 dirigido s=F3lo al=
>  receptor se=F1alado y puede contener informaci=F3n de car=E1cter privile=
> giada, privada o confidencial. Si usted no es el receptor se=F1alado o bi=
> en ha recibido este mensaje por error, por favor notifique inmediatamente=
>  al remitente y elimine el mensaje original. Cualquier otro uso de este m=
> ensaje de correo electr=F3nico est=E1 prohibido.
> 
> 
> 
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
> 
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>  


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: