Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
sharing tape drive
- Thread starter admincff
- Start date
ProbablyDown
MIS
If you smit mksysb, you have the option of backing up to a device or a file. back it up to a file, then move the file to the other server via ftp. Then place the file on a tape (should still be bootable).
Varify your data on the tape by entering the following (after the backup, of coarse):
(rewind the tape)
#tctl -f /dev/rmt0 rewind
(restore some rootvg data)
#restore -s4 -Tqvf /dev/rmt0.1 > /tmp/mksysb.log
Varify your data on the tape by entering the following (after the backup, of coarse):
(rewind the tape)
#tctl -f /dev/rmt0 rewind
(restore some rootvg data)
#restore -s4 -Tqvf /dev/rmt0.1 > /tmp/mksysb.log
AIXSPadmin
MIS
If you write a mksysb to a file and later write it to tape it will not be a bootable tape for a mksysb restore.
ProbablyDown
MIS
That's right... it isn't bootable... Thanks AIXSPadmin...
So if there is no tape device attched to the machine, there would be no way of creating a bootable tape for that machine. Placing the mksysb on tape would simply be a method of backup (perhaps for offsite storage)...
So if there is no tape device attched to the machine, there would be no way of creating a bootable tape for that machine. Placing the mksysb on tape would simply be a method of backup (perhaps for offsite storage)...
AIXSPadmin
MIS
Have never used this, but it is probably correct in the steps needed to create a bootable tape after the mksysb has been created. As I said I have never tried it, however, it seems that it would work.
*******************************************
Inspect mksysb === savevg script.
You will see what goes in the first three files.
If you have access to the machine in question, you can run the bits
that make the first three files, sending the output to files.
put these on the tape, as in the script.
then dd the mksysb (backup format) to the tape as file 4.
If you don't have access to the machine, you need another with the same
oslevel. Make the three files as above, then examine them. One will
have a backup file in it; restore it to a temporary directory; there
are files in this which must match exactly the missing bits. E.g.
check /bosinst.data, this has lv/fs sizes and names that will be made
before the restore occurs. There may be other files, so be careful.
The first time I did this, I missed a filesystem, so the restore tried
to shove it all in the / filesystem, it filled and I had to start over.
Get the desired files off your cd using the restore command.
Replace the duff ones, and remake the backup file.
Check out carefully the bs settings,
I *think* file 4 is written at bs=1024, but files 1 2 3 are written at
bs=512?
You have to change the bs on the tape drive
chdev -a block_size=512 -l rmtn
mt -f /dev/rmtn rewind
dd if=file1 of=/dev/rmtn.1 bs=512 conv=sync
dd if=file2 of=/dev/rmtn.1 bs=512 conv=sync
dd if=file3 of=/dev/rmtn.1 bs=512 conv=sync
then
chdev -a block_size=1024 -l rmtn
mt -f /dev/rmtn rewind
mt -f /dev/rmtn.1 fsf 3
dd if=mksysbfile of=/dev/rmtn.1 bs=1024 conv=sync
if you miss out the rewind and fsf 3, the tape might rewind anyway on
changing the block size, and you will overwrite files 1 2 and 3.
*******************************************
Inspect mksysb === savevg script.
You will see what goes in the first three files.
If you have access to the machine in question, you can run the bits
that make the first three files, sending the output to files.
put these on the tape, as in the script.
then dd the mksysb (backup format) to the tape as file 4.
If you don't have access to the machine, you need another with the same
oslevel. Make the three files as above, then examine them. One will
have a backup file in it; restore it to a temporary directory; there
are files in this which must match exactly the missing bits. E.g.
check /bosinst.data, this has lv/fs sizes and names that will be made
before the restore occurs. There may be other files, so be careful.
The first time I did this, I missed a filesystem, so the restore tried
to shove it all in the / filesystem, it filled and I had to start over.
Get the desired files off your cd using the restore command.
Replace the duff ones, and remake the backup file.
Check out carefully the bs settings,
I *think* file 4 is written at bs=1024, but files 1 2 3 are written at
bs=512?
You have to change the bs on the tape drive
chdev -a block_size=512 -l rmtn
mt -f /dev/rmtn rewind
dd if=file1 of=/dev/rmtn.1 bs=512 conv=sync
dd if=file2 of=/dev/rmtn.1 bs=512 conv=sync
dd if=file3 of=/dev/rmtn.1 bs=512 conv=sync
then
chdev -a block_size=1024 -l rmtn
mt -f /dev/rmtn rewind
mt -f /dev/rmtn.1 fsf 3
dd if=mksysbfile of=/dev/rmtn.1 bs=1024 conv=sync
if you miss out the rewind and fsf 3, the tape might rewind anyway on
changing the block size, and you will overwrite files 1 2 and 3.
- Status