testing backup tape drive

[sammysammy]

Hi,

I want to test whether the newly installed tape drive is working in a remote Tru64 5.1B server.
When I executed the dump commandline, I got the following error:

# df -k
Filesystem 1024-blocks Used Available Capacity Mounted on
root_domain#root 524288 300925 212608 59% /
/proc 0 0 0 100% /proc
usr_domain#tmp 58195968 6332 56031432 1% /cluster/members/member0/tmp
usr_domain#usr 58195968 1875983 56031432 4% /usr
usr_domain#var 58195968 254874 56031432 1% /var
oracle_dmn#dev 1258291200 223293664 402271184 36% /u01
oracle_dmn#tst 1258291200 631619321 402271184 62% /u04
# /sbin/dump 0fu /dev/ntape/tape0_d0 /var
dump: Dumping from host myserver.com.au
dump: Date of this level 0 dump: Wed Apr 18 13:28:27 2007 EST
dump: Date of last level 0 dump: the start of the epoch
dump: Dumping usr_domain#var (/var) to /dev/ntape/tape0_d0
dump:
dump: Cannot open file-system file usr_domain#var
dump: Bad file system specification or bad file system. The raw device must
dump: be entered when the file system's pathname has not been entered in the
dump: fstab file. A bad file system is reported when the the magic number
dump: is not found in the super block.
main(): open(): No such file or directory
dump: The ENTIRE dump is aborted

What is happening and how to test whether the driver is working ok in this system?

Here is a list of tape drivers in the system:
# ls -l /dev/ntape/*
crw-rw-rw- 1 root system 19, 69 Jan 25 15:43 /dev/ntape/tape0
crw-rw-rw- 1 root system 19, 73 Jan 25 15:43 /dev/ntape/tape0_d0
crw-rw-rw- 1 root system 19, 75 Jan 25 15:43 /dev/ntape/tape0_d1
crw-rw-rw- 1 root system 19, 77 Jan 25 15:43 /dev/ntape/tape0_d2
crw-rw-rw- 1 root system 19, 79 Jan 25 15:43 /dev/ntape/tape0_d3
crw-rw-rw- 1 root system 19, 81 Jan 25 15:43 /dev/ntape/tape0_d4
crw-rw-rw- 1 root system 19, 83 Jan 25 15:43 /dev/ntape/tape0_d5
crw-rw-rw- 1 root system 19, 85 Jan 25 15:43 /dev/ntape/tape0_d6
crw-rw-rw- 1 root system 19, 87 Jan 25 15:43 /dev/ntape/tape0_d7
crw-rw-rw- 1 root system 19, 71 Jan 25 15:43 /dev/ntape/tape0c
#

Thanks
Sam

[sammysammy]

Here is further info about the hardware devices in this system:
# hwmgr -view devices
HWID: Device Name Mfg Model Location
------------------------------------------------------------------------------
10: /dev/dmapi/dmapi
11: /dev/scp_scsi
12: /dev/kevm
354: /dev/disk/dsk0c HP HSV200 IDENTIFIER=1
355: /dev/disk/dsk1c HP HSV200 IDENTIFIER=2
356: /dev/disk/cdrom0c TEAC DW-224E-C bus-2-targ-0-lun-0
357: /dev/disk/dsk2c COMPAQ LOGICAL VOLUME bus-4-targ-0-lun-0
358: /dev/random
359: /dev/urandom
360: /dev/ntape/tape0 HP Ultrium 3-SCSI bus-8-targ-3-lun-0
361: /dev/cport/scp0 HSV200 bus-0-targ-0-lun-0
362: /dev/cport/scp1 Smart Array 5300 bus-4-targ-32-lun-0

Sam

[Steven Schweda]

> dump: Cannot open file-system file usr_domain#var

It's not complaining about the tape drive.
It's complaining about the file system.

"man dump":

These commands cannot be used to archive AdvFS filesets. See vdump(8) for
the operations used to archive AdvFS filesets.


Try "vdump". "man vdump".

http://h30097.www3.hp.com/
http://h30097.www3.hp.com/docs/
http://h30097.www3.hp.com/docs/pub_page/doc_list.html
http://h30097.www3.hp.com/docs/pub_page/V51B_DOCS/V51B_DOCLIST.HTM
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/ARH96DTE/TITLE.HTM