Operating System - Tru64 Unix
1748269 Members
3463 Online
108760 Solutions
New Discussion юеВ

Re: Unable to verify data on DDS-3

 
SOLVED
Go to solution
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Hi Pieter. The first script references the tape drive:

RECOVERY=/appdb/recovery.log; export RECOVERY
TAPEDRIVE=/dev/rmt0h; export TAPEDRIVE
APPDBDIR=/appdb; export APPDBDIR
APPDBRECOVERY=/appdb; export APPDBRECOVERY
APPDIR=/app; export APPDIR

It has always worked in the past?
Kind Regards,
Phil.
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Now if i type command: file /dev/nrmt0h I receive:

/dev/nrmt0h: character special (9/1027) SCSI #0 SDT-9000 tape #0 (SCSI ID #1) (SCSI LUN #0) errors = 0/1 97000_bpi

Phil.
Pieter 't Hart
Honored Contributor

Re: Unable to verify data on DDS-3

Sorry Phil,
but you're mistaking.
the only statement refferencing output o the tapedrive is commented out

# find DS*.* -print | cpio -ocBvdum > $TAPEDRIVE
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Pieter I am confused. These scripts were written by a third party. Each morning I simply ran: tar tvf /dev/rmt0h this showed data written to the tape from the previous day?

From what I can see there are 2 CRON jobs:
[quote]
CRON

User mtms

50 19 * * 1-4 /mtms/bin/Nightly.jcl > /mtms/tmp/cron.out

00 23 * * 1-5 /mtms/bin/mailcron

00 17 * * 5 /mtms/bin/Weekly.jcl > /mtms/tmp/cron.out

00,15,30,45 00-17 * * 0-4,6 /mtms/usr/bin/monitor_BSC.sh > /dev/null

00,15,30,45 00-16,19-23 * * 5 /mtms/usr/bin/monitor_BSC.sh > /dev/null

00 00 * * 6 /mtms/bin/bscregen.sh

10 00 * * 6 /mtms/bin/mtmsextremove.dat

15 00 * * 6 /mtms/bin/mtmsprtremove.dat

20 00 * * 6 /mtms/bin/mtmswrkremove.dat

25 00 * * 1-5 /mtms/bin/logtiyup.sh

User Root:

15 4 * * * find /var/preserve -mount -mtime +7 -type f -exec rm -f {} \;

20 4 * * * find /tmp -mount -type f -atime +2 -exec rm -f {} \;

30 4 * * * find /var/tmp -mount -type f -atime +7 -exec rm -f {} \;

40 4 * * * find /var/adm/syslog.dated -depth -type d -ctime +5 -exec rm -rf {} \;

20 19 * * 1-5 /mtms/bin/kill_users.jcl

30 19 * * 0-4,6 /mtms/bin/rootcron.sh

30 23 * * 5 /mtms/bin/rootcron.sh

#0 3 * * 4 /usr/sbin/acct/dodisk > /var/adm/diskdiag &

30 2 * * * /mtms/bin/nightly1.jcl

# The next line stops bde

0 19 * * * /mtms/BDE/stop.sh

# The next line monitors and starts bde every 15 minutes

00,10,15,30,45 08-17 * * * /mtms/usr/bin/monitor_bde_up.sh > /mtms/BDE/monitor_log 2>&1

1 1 * * * test -x /usr/sbin/defragcron && /usr/sbin/defragcron -p >>/usr/adm/defragcron.log 2>&1
[/quote]

I have attached the scripts.
Many Thanks,
Phil.

Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Still having problems. file /dev/rmt0h displays: /dev/rmt0h: character special (9/1026) SCSI #0 SDT-9000 tape #0 (SCSI ID #1) (SCSI LUN #0) offline

What do I need to do to get the tape drive back online and have the ability to read to and write from it?

Many Thanks,
Phil.
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Update:
mt online returns:
/dev/nrmt0h online 1 failed: I/O error

Regards,
Phil.
Pieter 't Hart
Honored Contributor

Re: Unable to verify data on DDS-3

let's start at the hardware.
check scsi-jumper or switch-settings. is it id-1 ?
check termination on the scsi-bus. is there a terminator or is a jumper/switch on the drive so the drive supplies terminiation.

check LED's on the drive, do these say the unit is online? does it need cleaning?

check type / brand of cartridges. are these really DDS-3?
Is it by accident write-protected?

try an older cartridge which you know worked. does this work? (you want to be able to restore an old backup).
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Hi Pieter. OK I can now talk to the drive
(new + old media). I was working remotely so was not aware the tape had ejected (offline). Popped the tape back in mt online rane OK.

I ran tar cvf /dev/rmt0h /somefiles followed by mt rewind followed by tar tvf /dev/rmt0h

All commands executed OK.

I am confused regards the CRON jobs (backup routines) if they are not writing to tape?
Many thanks for your time and efforts.
Phil.
Pieter 't Hart
Honored Contributor

Re: Unable to verify data on DDS-3

About the scripts, a "#" normally denotes a comment-line or any other line that needs not be executed.
unless you use a special shell wich does interpret a line starting with "#", both in autobackup and weeklybackup the line using the tape is "commented out" and not executed.

so in the two lines :
tar -cvB -C /mtms . -C /mtmsdb . -C /mtmsdb1 . -C /mtmsdb2/mtmsdb1 .
and
# find /mtms /mtmsdb /mtmsdb1 -print | cpio -ocBvdum > $TAPEDRIVE

the tar is executed and outputs to a directory and the find is not executed.

NB! i'm also puzzled about the "set +x" at the beginning of the script.
I know the command "set -x" in a shell script, not "set +x"!
Philip Horan
Frequent Advisor

Re: Unable to verify data on DDS-3

Pieter I am confused by it all!! :)
Many Thanks,
Phil