How to mksysb to a tape drive connected to a different LPAR? Post: 302400490

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Tape Drive Connected to a Sun Ultra 10/Solaris 2.7

I have a Sun Ultra 10/Solaris 2.7 with a differential SCSI card connected to a Supter DLt1 Tape Drive. When I boot the machine, and I do a probe-scsi-all in the very beginning of the boot process. It shows up correctly. If I wait for the boot process to proceed and then I do a probe-scsi-all, I get...

2. UNIX for Advanced & Expert Users

AIX 4.3 mksysb tape incomplete

anybody knows how to recover from a tape in AIX 4.3 from a IBM rs6000 170 system backup done only 97% ?

3. AIX

Restoring mksysb to vio lpar?

I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up. I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk...

4. AIX

savevg/tar/mksysb of server-A on remote tape drive possible ?

Every 3 months we have to do backups (smitth mksysb/lsmksysb + tar) on at least 30 workstations. We have to carry around 2 external tape drives to connect to them. It is a pain to do because it takes at least 3 days to do (evening/night shift) and users sometimes complain that there desk is not put...

5. AIX

Script: how to find out the label of a tape and if its an mksysb one ?

Hi, how can I find out though kron shell (aix 4.2) what the label of a tape is ? Also, how can I find out if that tape has been used for an mksysb and when ?

6. Solaris

Solaris 10 new fiber connected tape

Hello all, how can i see configured fc tapes in solaris system and how can i install a new fc shared tape device , thanks Best Regards

7. AIX

aix installation from mksysb tape

Hello, I am trying to install a server from a mksysb made on an other server but whit his proper image.data and bosinst.data, but after selecting boot from DLT tape and starting installation in normal mode with default setting, I get this error message : error / warning there is no disk...

8. AIX

mksysb to tape too slow...

had this p520 server connected to a DDS-3 4mm tape drive... running AIX 7.1 TL01 -- the latest release. mksysb -i -e /dev/rmt/1 ..tells me only 1% is done after over an hour ... I had no problems with th hardware and other connections... tar command to /dev/rmt/1 runs very fast .......

9. AIX

Restore mksysb image on cloned LPAR

Hi Folks, How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0) Let me know. Thank a lot.

10. AIX

Can I use mkdvd to create bootable DVD from mksysb on tape

Hi, Is it possible to use mkdvd to create a bootable DVD using a mksysb on tape as the source image? On the system concerned, we don't have enough free space to create the mksysb to file first, so would like to use the existing tape mksysb backup. The DVD disk/s will then be used to boot a...

LEARN ABOUT BSD

ht

HT(4)							     Kernel Interfaces Manual							     HT(4)

NAME

       ht - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NHT  ht_drives # TE16, TU45, TU77

       /etc/dtab:
	    #Name Unit# Addr   Vector Br Handler(s)	 # Comments
	    ht	  ?	172440 224    5  htintr 	 # tu 16 massbus tape

       major device number(s):
	    raw: 6
	    block: 0
       minor device encoding:
	    bits 0003 specify HT drive
	    bit  0004 specifies no-rewind operation
	    bit  0010 specifies 1600BPI recording density instead of 800BPI

DESCRIPTION

       The  tm-03/transport  combination  provides  a standard tape drive interface as described in mtio(4).  All drives provide both 800 and 1600
       bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.

FILES

       /dev/MAKEDEV	   script to create special files
       /dev/MAKEDEV.local  script to localize special files

SEE ALSO

       mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)

DIAGNOSTICS

       tu%d: no write ring.  An attempt was made to write on the tape drive when no write ring was present; this message is written on the  termi-
       nal of the user who tried to access the tape.

       tu%d:  not  online.   An  attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
       tried to access the tape.

       tu%d: can't change density in mid-tape.	An attempt was made to write on a tape at a different density than  is	already  recorded  on  the
       tape.  This message is written on the terminal of the user who tried to switch the density.

       tu%d:  hard  error  bn%d  er=%b	ds=%b.	 A tape error occurred at block bn; the ht error register and drive status register are printed in
       octal with the bits symbolically decoded.  Any error is fatal on non-raw tape; when possible the driver will  have  retried  the  operation
       which failed several times before reporting the error.

BUGS

       If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.

       The  system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
       console.

3rd Berkeley Distribution					 January 28, 1988							     HT(4)