Sponsored Content
Full Discussion: Mksysb restore problem
Top Forums UNIX for Beginners Questions & Answers Mksysb restore problem Post 303040899 by hicksd8 on Friday 8th of November 2019 12:11:20 PM
Old 11-08-2019
I'll start by saying that I'm not an AIX user or familiar with mksysb but I found this (old) page which has people discussing some of the exact same error lines that you are getting:

restore mksysb 5.2 ml01 - IBM: AIX - Tek-Tips

I don't know whether it is relevant (and apologies if it isn't) and I certainly can't help you further, but I'm sure there's more than enough AIX expertise on here to chip in if it is relevant.

Good luck with it.
These 2 Users Gave Thanks to hicksd8 For This Post:
 

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

How to restore from mksysb backup

system is not booting ... i want to restore from mksysb backup. (2 Replies)
Discussion started by: AIXlearner
2 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

"Please mount volume 2 on /dev/rmt0.1" message during mksysb restore

Dear all First of all, my English not so good. We have p52a (production server) and p52a (test server). Tape drives are VXA2. When both servers were AIX 5.3, mksysb on production server and restoring to test server was OK. The production server was AIX 5.3 and recently upgraded to... (3 Replies)
Discussion started by: fifa15pc
3 Replies

9. AIX

Restore file from mksysb file

Hello, I have a mksysb backup OS image. I can restore the file from there, but the issue is the restored file include the whole path :confused: listvgbackup -f /backup/xxx/mksysb.xxx.20190316 -r -s -d /home/aaa/ ./home/bbb/nohup.out I plan to restore nohup.out from /home/bbb/nohup.out to... (5 Replies)
Discussion started by: Phat
5 Replies

10. 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
captoinfo(1)						      General Commands Manual						      captoinfo(1)

NAME
captoinfo - convert a termcap description into a terminfo description SYNOPSIS
captoinfo [-vn width] [-V] [-1] [-w width] file . . . DESCRIPTION
captoinfo looks in each given text file for termcap descriptions. For each one found, an equivalent terminfo description is written to standard output. Termcap tc capabilities are translated directly to terminfo use capabilities. If no file is given, then the environment variable TERMCAP is used for the filename or entry. If TERMCAP is a full pathname to a file, only the terminal whose name is specified in the environment variable TERM is extracted from that file. If the environment variable TERM- CAP is not set, then the file /etc/terminfo is read. -v print out tracing information on standard error as the program runs. -V print out the version of the program in use on standard error and exit. -1 cause the fields to print out one to a line. Otherwise, the fields will be printed several to a line to a maximum width of 60 charac- ters. -w change the output to width characters. FILES
/etc/terminfo Compiled terminal description database. TRANSLATIONS FROM NONSTANDARD CAPABILITIES
Some obsolete nonstandard capabilities will automatically be translated into standard (SVr4/XSI Curses) terminfo capabilities by captoinfo. Whenever one of these automatic translations is done, the program will issue an notification to stderr, inviting the user to check that it has not mistakenly translated a completely unknown and random capability and/or syntax error. Nonstd Std From Terminfo name name capability ----------------------------------------------- BO mr AT&T enter_reverse_mode CI vi AT&T cursor_invisible CV ve AT&T cursor_normal DS mh AT&T enter_dim_mode EE me AT&T exit_attribute_mode FE LF AT&T label_on FL LO AT&T label_off XS mk AT&T enter_secure_mode EN @7 XENIX key_end GE ae XENIX exit_alt_charset_mode GS as XENIX enter_alt_charset_mode HM kh XENIX key_home LD kL XENIX key_dl PD kN XENIX key_npage PN po XENIX prtr_off PS pf XENIX prtr_on PU kP XENIX key_ppage RT @8 XENIX kent UP ku XENIX kcuu1 KA k; Tek key_f10 KB F1 Tek key_f11 KC F2 Tek key_f12 KD F3 Tek key_f13 KE F4 Tek key_f14 KF F5 Tek key_f15 BC Sb Tek set_background FC Sf Tek set_foreground HS mh Iris enter_dim_mode XENIX termcap also used to have a set of extension capabilities for forms drawing, designed to take advantage of the IBM PC high-half graphics. They were as follows: Cap Graphic ----------------------------- G2 upper left G3 lower left G1 upper right G4 lower right GR pointing right GL pointing left GU pointing up GD pointing down GH horizontal line GV vertical line GC intersection G6 upper left G7 lower left G5 upper right G8 lower right Gr tee pointing right Gr tee pointing left Gu tee pointing up Gd tee pointing down Gh horizontal line Gv vertical line Gc intersection GG acs magic cookie count If the single-line capabilities occur in an entry, they will automatically be composed into an acsc string. The double-line capabilities and GG are discarded with a warning message. IBM's AIX has a terminfo facility descended from SVr1 terminfo but incompatible with the SVr4 format. The following AIX extensions are automatically translated: IBM XSI ------------- ksel kslt kbtab kcbt font0 s0ds font1 s1ds font2 s2ds font3 s3ds Additionally, the AIX box1 capability will be automatically translated to an acsc string. Hewlett-Packard's terminfo library supports two nonstandard terminfo capabilities meml (memory lock) and memu (memory unlock). These will be discarded with a warning message. NOTES
This utility is actually a link to tic(1), running in -I mode. You can use other tic options such as -f and -x. The trace option is not identical to SVr4's. Under SVr4, instead of following the -v with a trace level n, you repeat it n times. SEE ALSO
infocmp(1), ncurses(3NCURSES), terminfo(5) This describes ncurses version 6.1 (patch 20180127). AUTHOR
Eric S. Raymond <esr@snark.thyrsus.com> and Thomas E. Dickey <dickey@invisible-island.net> captoinfo(1)
All times are GMT -4. The time now is 10:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy