AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
When trying to restore a system backup using "tar" From an RS\6000 to another system with same profile and model I get "READ ERROR MEDia error asuming zeros...update (81). Ive tried different tapes and chaged block szize to (0) or (512). The machine do restore well daily backups. I suspect the host machine has the problem in the system backup proccess.I have not tried to restore the system backup in the host machine do to the fact that it may corrupt the original system.??
Try doing a tar tvf <tape_device> on the original system. That just list the contents of the tape without restoring anything. If it works there but not elsewhere then it could have something to do with the head(s) being out of whack on the original system's drive.
It wasn't clear from what you wrote when you say your daily backups do restore if you meant they restore to the same system or to other systems. If the latter then your issue is probably the backup itself rather than the tape or tape drive. For example if you're doing some sort of DB backup and using a 3rd party tool to feed to the backup it could be the data on the tape isn't purely tar. (NetBackup for example uses a modified version GNU tar but has add-ons to allow it to work with things such as Oracle RMAN or MS-SQL or MS-Hyper-V or any Windows backup).
What exact command stream do you use to do the daily backup and the one you're having problems with.
What command stream are you using to do the restores?
The daily backup restores well on the client machine.
The system backup is made with "Pro IV aplication menu commands and I have tried to restore it on the client machine at the c: promt with tar -cvf/dev/rmt0 and tar -xvf/dev/rmt0 and througth aplication menus, also using smit management tools.I dont want to really try any system or daily back tape on the host machine becaaus it is our server and do not really want to take any chances of corrupting it. I will investigate on the pro IV menu command and also go for changing the tape drive on the host machine even though the leds are fine. the tar tvf(device) on the client machine and no response but thank to you all for the attention recieved. I will post any other event in this situation soon.
tar cvf <dev> is used to WRITE to the device (you can also write to a file rather than a device).
tar xvf <dev> is used to READ from the device and WRITE to the target.
tar tvf <dev> is used to READ from the device and show what it contains without writing it to anything.
My suspicion is your application is NOT just doing a standard tar which is why you can't read it. What you COULD do is use tar to write the tape directly.
For example if the files you want to backup are in /mydir/mysubdir and your device is rmt0 as you indicate you could run:
tar cvf /dev/rmt0 /mydir/mysubdir
Notice that the device (or file) you are creating the archive on always follows the f option directly.
I usually use to restore a system backup by pressing 1 on the keyboard and selecting first boot device and console. Only system backups from 3 months ago are working. Also de an
# ls -l/dev/rmt0 on clone tape divice with last weeks system backup tape and got back
crw-rw-rw- 1 root system ...date...,so this means that the tape has the host system info. also tried today to boot to system tape with drive rmt0 blocks = 0 and the boot continued in varios atemps to the clone local boot process. Put back to 512 blocks since the host machine is also 512. Still have same problem.
The backup is mksysb, I have pin down the problem on the host RS/6000. I did the tcopy /dev.. on a recent sys backup and the mesage was short ""tape file 1 record 1 size 10240 end of tape reached. The same coomand on an older funtioning sys backup gave me a much longer result."" tape file 1, tape file 2, tape file 3 record 1 record 2 etc....
Even though no errors on tape drive diagnostics. I am recieving a refurbished one on monday and will replace it. If problem not solve will have to deal with corrupted programming or disk and will investigate it to solve or maybe even have to replace hard disk and restore with old sys backup and new data and prov4 aplication.???
The one with 4 sections is a correctly made mksysb tape. I shall not bother with the details (that date back to AIX 3).
Basically, the first tape section is to boot the system (kernel, device drivers), the second is information to recreate rootvg (./image.data; ./bosinst.data and ./tapeblksz).
the third section is empty that used to be a TOC (table of contents) when backup was done by inode; and the fourth is the largest - the actual files - and are written in table blocks of tapeblksz)
to list the information on a mksysb tape:
* simple way:
Lists or restores the contents of a volume group backup on a specified
listvgbackup [ -b blocks ] [ -f device ] [ -a ] [ -c ] [ -l ] [ -n ] [
-r ] [ -s ] [ -d path ] [ -B ] [ -D ] [ -L ] [ -V ] [ file_list ]
The listvgbackup command lists the contents of a volume group backup
from tape, file, CD-ROM, or other source and can be used to restore
files from a valid backup source. The listvgbackup command also works
for multi-volume backups such as multiple CDs, DVDs, USB disks, or
The listvgbackup -r and restorevgfiles commands perform identical
operations and should be considered interchangeable.
Hello everybody, I'm back. Due to a service contract with IBM, They came and tried to change the tape drive on the RS 6000 machine. Both atemps failed due to the fact that there refurbuished parts were in worst shape then the original one. At one time the machine would not boot due to an inproper soci cable atachment. So I scared away from there service. Due to the info given to me by this forum I kind of pin pointed the malfuntion at the host file or aplication software. It stops reading files after a specific data file called BA 701 .idx. So after the software loops awhile trying to read it then aborts. I will take a chance soon and run a verify Proiv files or ischk *.. I havent done it because if the hdisk is in bad shape I may get a freeze. so I am planning the operation for an apropiate period.
To be more precise the restoration of a system backup on my clone machine using Aix 4.3 and using using mksysb hangs up on the forth level when recovering data of volume group. The image.data , bosinst.data files and TOC seem to read fine.