Avatar of foxhelp
foxhelp asked on

Backup to SCSI tape drive stops at point it is going to write a file

I have a SCO OpenServer 5.0.6 system running BackupEdge software with a Quantum Model # STD2401LW DAT Tape drive and Adaptec SCSI Card 29160.  All of a sudden when doing a full system backup the backup stops when it reaches a file that actually has data in it.  
I tried changing the tape drive to another same model, I tried changing the SCSI card to another with same model, and I tried changing the board to another slot on the motherboard.  None of those things work.  It keeps doing the same thing.
Unix OS

Avatar of undefined
Last Comment
foxhelp

8/22/2022 - Mon
SOLUTION
David

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
foxhelp

It is not even logging an error from BackupEdge.  It just stops and hangs forever at the file when I look at the backup file that is created.
/usr/adm/messages and /usr/adm/syslog do not show any errors.
I will try tar.
SOLUTION
mikelfritz

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
David

It typically displays the file AFTER it has been written, so if there is a read error it will almost always be a different file. You need to look at the system logs to determine what file had a read problem (if any)
mikelfritz

I thought I said that - maybe not quite clear enough - sorry.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
mikelfritz

Also - with SCO I think the logs are under /var/adm/*
ASKER
foxhelp

One thing I forgot to mention and don't know if it makes a difference is that I can get a full listing of the contents of the tape and I can read the label so the reading part of it is working.  What is not working is writing to the tape.
ASKER
foxhelp

Here is the output of dfspace...
# dfspace
/         :     Disk space: 71736.42 MB of 75778.38 MB available (94.67%).
/stand    :     Disk space:   6.16 MB of  14.99 MB available (41.10%).

Total Disk Space: 71742.59 MB of 75793.38 MB available (94.66%).
Here is the result of the tar, it got stuck for hours after the second file.  Once this happens, I cannot kill the tar process or stop it in any way.  The only way is to reboot and remove the tape.
#tar cvf /dev/rStp0 /usr/aph
a /usr/aph/.profile 9 tape blocks
a /usr/aph/db/TBOCDT 27824 tape blocks

ONLY doing software compresses on BackupEdge not both.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
foxhelp

Thanks for having me try different things.  The problem was the SCSI cable.  It is working now.

Thanks,