Sponsored Content
Full Discussion: System recovery
Operating Systems AIX System recovery Post 302209409 by bakunin on Thursday 26th of June 2008 09:55:04 PM
Old 06-26-2008
It depends somewhat on the hardware you use:

You have to include the tape drive (more precisely: the tape drive device) into the boot list. You can do that ad-hoc in the boot menu or using the diag CD and booting from it. You can find a detailed description for your machine at the IBM site, even for older machines. Search for "Technical Overview" or "whitepaper" and the model number of your machine.

Once the tape drive is inthe boot list simply insert the mksysb tape into the drive and power on - the tape has a boot image and will restore the rootvg automatically. There are a few screens to answer, but they are pretty intuitive and straigtforward.

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. HP-UX

Automatic system recovery?

Hi all! I've a strange problem. I would use the GNU Make tool on HPUX 11.11. To archive this, i have compiled the sourcecode and renamed HP make in /usr/bin from make to make_old. Now i have make a softlink from /usr/local/bin/make (GNU version) to /usr/bin/make. All things here are ok, but... (1 Reply)
Discussion started by: coredump2003
1 Replies

2. AIX

make a recovery CD/DVD - system has no writable devices

Hi, Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system. The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw). I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies

3. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

4. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

5. UNIX for Advanced & Expert Users

fsck.gfs2 outputs "RG recovery impossible; I can't fix this file system"

I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck: fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Discussion started by: king_hippo
0 Replies

6. Cybersecurity

Password Recovery

Perderabo has made posted a good thread in the FAQ section here: Lost root password / Can't login as root | Unix Linux Forums | Answers to Frequently Asked Questions (6 Replies)
Discussion started by: norsk hedensk
6 Replies

7. Red Hat

ldap recovery

Is there a way to recover the ldap server if it crashes (4 Replies)
Discussion started by: nalcomis
4 Replies

8. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies

9. SCO

Need Help With System Recovery After HD Errors

Last week our legacy SCO OpenServer 5.0.6 server started showing "panic" errors about bad blocks/sectors on hard drive. I ran the badtrack command which fully checked the disk, and it identified 2 LBA sectors as bad, and it was unable to recover some of the data. Apparently the lost data had... (29 Replies)
Discussion started by: spock9458
29 Replies
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)
All times are GMT -4. The time now is 05:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy