My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
Code:
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this problem and re-execute phase 3
or run "alt_disk_install -X" to clean up.
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 SUNOS
aset.restore
aset.restore(1M) System Administration Commands aset.restore(1M)NAME
aset.restore - restores system files to their content before ASET is installed
SYNOPSIS
aset.restore [-d aset_dir]
DESCRIPTION
aset.restore restores system files that are affected by the Automated Security Enhancement Tool (ASET) to their pre-ASET content. When ASET
is executed for the first time, it saves and archives the original system files in the /usr/aset/archives directory. The aset.restore
utility reinstates these files. It also deschedules ASET, if it is currently scheduled for periodic execution. See asetenv(4).
If you have made changes to system files after running ASET, these changes are lost when you run aset.restore. If you want to be abso-
lutely sure that you keep the existing system state, it is recommended that you back-up your system before using aset.restore.
You should use aset.restore, under the following circumstances:
You want to remove ASET permanently and restore the original system (if you want to deactivate ASET, you can remove it from schedul-
ing).
You are unfamiliar with ASET and want to experiment with it. You can use aset.restore to restore the original system state.
When some major system functionality is not working properly and you suspect that ASET is causing the problem; you may want to
restore the system to see if the problem persists without ASET.
aset.restore requires root privileges to execute.
OPTIONS
The following options are supported:
-d aset_dir Specify the working directory for ASET. By default, this directory is /usr/aset. With this option the archives directory
will be located under aset_dir.
FILES
/usr/aset/archives archive of system files prior to executing aset
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWast |
+-----------------------------+-----------------------------+
SEE ALSO aset(1M), asetenv(4), attributes(5)
System Administration Guide: Basic Administration
SunOS 5.10 11 Oct 1991 aset.restore(1M)