Sponsored Content
Operating Systems AIX How to restore from mksysb backup Post 302321088 by filosophizer on Saturday 30th of May 2009 03:57:12 AM
Old 05-30-2009
Call IBM support seems to be the appropriate action.


> System not booting
> hardware error
> panel error code
> disk failure
> disk corruption
> o/s corruption
> where do you have the mksysb image ? CD/DVD or tape ?
> does the system has CD DVD drive or tape drive
 

10 More Discussions You Might Find Interesting

1. AIX

mksysb restore errors

goodafternoon people. here are a couple of error messages I get during restore of mksysb from a AIX F80 to a F50. I have verified blocksize and have set them to 1024 which matches both the systems. backup system is F80 and restore system is F50. Both are 4.3.3 ML10 level Upon executing via... (1 Reply)
Discussion started by: Student37
1 Replies

2. AIX

mksysb restore ( vgs on SAN disks)

I have my application vendor looking at this but I want to do my own investigation. I restored from mksysb and I see my vgs that contain my internal disks. But I do not see my vgs that contain disks from the SAN. This scares me .. {{ Ha, ha!! My AIX expert boss just told me I have nothing... (0 Replies)
Discussion started by: Skyybugg
0 Replies

3. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

4. AIX

mksysb restore - Wrong OS level for restore

Hi all, I am still working on my mksysb restore. My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored. 0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies

5. AIX

mksysb backup

hi we are having one rootvg in that we created one lv named mksysb_backuplv and normally script will run accordingly to take the backup in the cron,here i just want to know if any rootfilesystem was correpted like /usr or /tmp ,then how could i restore the particular filesystme from the... (1 Reply)
Discussion started by: senmak
1 Replies

6. AIX

Profile environment variables lost after mksysb restore

Hello. I restore an mksysb image (AIX 5.3 TL 11) from one model to another model of Power (power 5 to power 7). Everything seems good, but I lost environment variables of at least one of a user profile. The result of the "env" command show me great differences between two servers, first of them... (2 Replies)
Discussion started by: stephnane
2 Replies

7. 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. (1 Reply)
Discussion started by: snchaudhari2
1 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. AIX

AIX 7.2 MKSYSB Backup and Restore Best Practices?

Hello, Running AIX 7.2 on Power9 bare-metal (no LPAR and no NIM server), in the process of creating a guide on MKSYSB process. I understand that MKSYSB is a backup of the rootvg and we can exclude stuff via exclude.rootvg file, the rest of the data volumes are mapped to the system as LUNs via... (7 Replies)
Discussion started by: c3rb3rus
7 Replies

10. UNIX for Beginners Questions & Answers

Mksysb restore problem

Hello everybody, I have a little problem with my mksysb restore. My system: AIX 6100-09-11-1806. I make mksysb backup of my LPARs by NIM server. I am doing restore tests by NIM server on spare LPAR now. All LPARs were restored allright except for one. During restore it stops with this... (4 Replies)
Discussion started by: Necronomic
4 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 07:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy