My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
I now see that the version on the old mksysb tape is 5200-03 and the version on CD and installed on the DR server I have is 5200-09.
Does this mean I need to use the older 5200-03 CD? If so how do I get it as we are missing CD1 of that set.
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT V7
restor
RESTOR(1M)RESTOR(1M)NAME
restor - incremental file system restore
SYNOPSIS
restor key [ argument ... ]
DESCRIPTION
Restor is used to read magtapes dumped with the dump command. The key specifies what is to be done. Key is one of the characters rRxt
optionally combined with f.
f Use the first argument as the name of the tape instead of the default.
r or R The tape is read and loaded into the file system specified in argument. This should not be done lightly (see below). If the key is
R restor asks which tape of a multi volume set to start on. This allows restor to be interrupted and then restarted (an icheck -s
must be done before restart).
x Each file on the tape named by an argument is extracted. The file name has all `mount' prefixes removed; for example, /usr/bin/lpr
is named /bin/lpr on the tape. The file extracted is placed in a file with a numeric name supplied by restor (actually the inode
number). In order to keep the amount of tape read to a minimum, the following procedure is recommended:
Mount volume 1 of the set of dump tapes.
Type the restor command.
Restor will announce whether or not it found the files, give the number it will name the file, and rewind the tape.
It then asks you to `mount the desired tape volume'. Type the number of the volume you choose. On a multivolume dump the recom-
mended procedure is to mount the last through the first volume in that order. Restor checks to see if any of the files requested
are on the mounted tape (or a later tape, thus the reverse order) and doesn't read through the tape if no files are. If you are
working with a single volume dump or the number of files being restored is large, respond to the query with `1' and restor will read
the tapes in sequential order.
If you have a hierarchy to restore you can use dumpdir(1) to produce the list of names and a shell script to move the resulting
files to their homes.
t Print the date the tape was written and the date the filesystem was dumped from.
The r option should only be used to restore a complete dump tape onto a clear file system or to restore an incremental dump tape onto this.
Thus
/etc/mkfs /dev/rp0 40600
restor r /dev/rp0
is a typical sequence to restore a complete dump. Another restor can be done to get an incremental dump in on top of this.
A dump followed by a mkfs and a restor is used to change the size of a file system.
FILES
default tape unit varies with installation
rst*
SEE ALSO dump(1), mkfs(1), dumpdir(1)DIAGNOSTICS
There are various diagnostics involved with reading the tape and writing the disk. There are also diagnostics if the i-list or the free
list of the file system is not large enough to hold the dump.
If the dump extends over more than one tape, it may ask you to change tapes. Reply with a new-line when the next tape has been mounted.
BUGS
There is redundant information on the tape that could be used in case of tape reading problems. Unfortunately, restor doesn't use it.
RESTOR(1M)