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 message:
Code:
cp: /etc/objrepos/CuAt and /../etc/objrepos/CuAt are identical (not copied).
cp: /etc/objrepos/CuAt.vc and /../etc/objrepos/CuAt.vc are identical (not copied).
cp: /etc/objrepos/CuAtDef and /../etc/objrepos/CuAtDef are identical (not copied).
cp: /etc/objrepos/CuAtDef.vc and /../etc/objrepos/CuAtDef.vc are identical (not copied).
cp: /etc/objrepos/CuAtSav and /../etc/objrepos/CuAtSav are identical (not copied).
cp: /etc/objrepos/CuAtSav.vc and /../etc/objrepos/CuAtSav.vc are identical (not copied).
cp: /etc/objrepos/CuData and /../etc/objrepos/CuData are identical (not copied).
cp: /etc/objrepos/CuData.vc and /../etc/objrepos/CuData.vc are identical (not copied).
cp: /etc/objrepos/CuDep and /../etc/objrepos/CuDep are identical (not copied).
cp: /etc/objrepos/CuDv and /../etc/objrepos/CuDv are identical (not copied).
cp: /etc/objrepos/CuDvDr and /../etc/objrepos/CuDvDr are identical (not copied).
cp: /etc/objrepos/CuLk and /../etc/objrepos/CuLk are identical (not copied).
cp: /etc/objrepos/CuLk.vc and /../etc/objrepos/CuLk.vc are identical (not copied).
cp: /etc/objrepos/CuPath and /../etc/objrepos/CuPath are identical (not copied).
cp: /etc/objrepos/CuPath.vc and /../etc/objrepos/CuPath.vc are identical (not copied).
cp: /etc/objrepos/CuPathAt and /../etc/objrepos/CuPathAt are identical (not copied).
cp: /etc/objrepos/CuPathAt.vc and /../etc/objrepos/CuPathAt.vc are identical (not copied).
cp: /etc/objrepos/CuVPD and /../etc/objrepos/CuVPD are identical (not copied).
BOS Install: Could not copy customized device object classes to disk.
ID# OPTION
1 Continue
2 Perform System Maintenance and Then Continue
Enter ID number:
When I try continue, it fails and reboot.
Original LPAR is in normal state. I can create next mksysb backup, but during restore it ends with the same message.
I dont have much experince with direct ODM management, but CuDv looks normal too. It is accessible and odmget returns info.
Location: Asia Pacific, Cyberspace, in the Dark Dystopia
Posts: 19,118
Thanks Given: 2,351
Thanked 3,359 Times in 1,878 Posts
Please post the exact mksysb you ran for both backup and restore.
Also, don't forget to record the exit status for each, for completeness:
Code:
Exit Status
This command returns the following exit values:
Item Description
0 The command completed successfully.
1 An error in the mksysb command use occurred.
2 An error in the savevg command use occurred. The savevg is a link to mksysb.
3 An error occurred before any file systems were mounted.
4 Exit because of trap.
5 Exit because there was no space.
6 Exit because a volume group name was not valid.
root@asrv11lpar3:/ # nim -o define -t mksysb -a mk_image=yes -a mksysb_flags=-i -a source=asrv11lpar11 -a location=/nim/mksysb/mksysb--asrv11lpar11 -a server=master mksysb--asrv11lpar11
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 7909413 (7725 MB) Available = 210739520 (205801 MB)
Creating information file (/image.data) for rootvg.
Creating list of files to back up.
.
Backing up 123070 files..............................
51920 of 123070 files (42%)...............
123070 of 123070 files (100%)
0512-038 savevg: Backup Completed Successfully.
0042-008 NIMkid: Request denied - Method_req
root@asrv11lpar3:/ # echo $?
0
Define a Resource
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Resource Name [asrv11lpar11_mksysb]
* Resource Type mksysb
* Server of Resource [master] +
* Location of Resource [/nim/mksysb/mksysb--asrv11lpar11] /
NFS Client Security Method [] +
NFS Version Access [] +
Comments []
Source for Replication [] +
-OR-
System Backup Image Creation Options:
CREATE system backup image? no +
NIM CLIENT to backup [] +
PREVIEW only? no +
IGNORE space requirements? no +
EXPAND /tmp if needed? no +
Create MAP files? no +
Backup extended attributes? yes +
Number of BLOCKS to write in a single output [] #
(leave blank to use system default)
Use local EXCLUDE file? no +
(specify no to include all files in backup)
-OR-
EXCLUDE_FILES resource [] +
(leave blank to include all files in backup)
Create backup using snapshots? yes +
Backup encrypted files? yes +
Backup DMAPI filesystem files? yes +
Disable software packing of backup? no +
Use exclude_packing.rootvg file? no +
F1=Help F2=Refresh F3=Cancel F4=List
F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do
Define a Resource
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Resource Name [asrv11lpar11_spot]
* Resource Type spot
* Server of Resource [master] +
Source of Install Images [asrv11lpar11_mksysb] +
* Location of Resource [/nim/spot/] /
NFS Client Security Method [] +
NFS Version Access [] +
Expand file systems if space needed? yes +
Comments []
installp Flags
PREVIEW only? (install operation will NOT occur) no +
COMMIT software updates? no +
SAVE replaced files? yes +
AUTOMATICALLY install requisite software? yes +
OVERWRITE same or newer versions? no +
VERIFY install and check file sizes? no +
F1=Help F2=Refresh F3=Cancel F4=List
F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do
Install the Base Operating System on Standalone Clients
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[TOP] [Entry Fields]
* Installation Target asrv12lpar12
* Installation TYPE mksysb
* SPOT asrv11lpar11_spot
LPP_SOURCE [] +
MKSYSB asrv11lpar11_mksysb
BOSINST_DATA to use during installation [] +
IMAGE_DATA to use during installation [] +
RESOLV_CONF to use for network configuration [] +
Customization SCRIPT to run after installation [] +
Customization FB Script to run at first reboot [] +
ACCEPT new license agreements? [yes] +
Remain NIM client after install? [yes] +
PRESERVE NIM definitions for resources on [yes] +
this target?
FORCE PUSH the installation? [no] +
Initiate reboot and installation now? [yes] +
-OR-
Set bootlist for installation at the [no] +
next reboot?
Additional BUNDLES to install [] +
-OR-
Additional FILESETS to install [] +
(bundles will be ignored)
installp Flags
COMMIT software updates? [yes] +
SAVE replaced files? [no] +
AUTOMATICALLY install requisite software? [yes] +
EXTEND filesystems if space needed? [yes] +
OVERWRITE same or newer versions? [no] +
VERIFY install and check file sizes? [no] +
ACCEPT new license agreements? [no] +
(AIX V5 and higher machines and resources)
Preview new LICENSE agreements? [no] +
Group controls (only valid for group targets):
Number of concurrent operations [] #
Time limit (hours) [] #
Schedule a Job [no] +
YEAR [] #
MONTH [] +#
DAY (1-31) [] +#
HOUR (0-23) [] +#
MINUTES (0-59) [] +#
Open a console window? [no] +
Set the DISPLAY environment variable []
[BOTTOM]
F1=Help F2=Refresh F3=Cancel F4=List
F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do
All smit jobs ends with OK state.
This User Gave Thanks to Necronomic For This Post:
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:
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:
Thank you. I found this old page too. This is one of the few pages where exactly this error lines are.
Unfortunately that page didn't help me.
I setup all my LPARs same way. No errors during mksysb creation. So far I have test recovered only a third of my LPARs -> 1 insurmountable problem. I am a little scared that there will be more of this anomaly.
Content of my /etc/niminfo. But it is also same on other LPARs.
Code:
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=asrv11lpar11
export NIM_HOSTNAME=asrv11lpar11
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=asrv11lpar3
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_MASTERID=00F638414C00
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 127.0.0.1:loopback:localhost 172.31.216.41:asrv11lpar11 172.31.216.33:asrv11lpar3 "
export NIM_MOUNTS=""
export ROUTES=" default:0:172.31.216.1 "
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,
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)
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)
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)
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 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)
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)
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)
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)