Hi,
i backed up a test LPAR using mksyb utility on AIX. and transferred it to NIM server via NFS.
I want to create a SPOT using this mksysb . Please explain me the procedure. And got something online, but that procedure is different.
Please respond.
Ok,
In order to do that you have to run the below on NIM
smitty nim_mkres --> select option mksysb
Define a Resource
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Resource Name [test-mksysb]
* Resource Type mksysb
* Server of Resource [master] +
* Location of Resource [YOUR-LOCATION] /
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)
Backup encrypted files? yes +
Backup DMAPI filesystem files? yes +
Disable software packing of backup? no +
Use exclude_packing.rootvg file? no +
Here Resource name is of your choice, reading your article I used test-mksysb. Server of Resource is "master" (NIM itself), now provide the location of actual mksysb.
This should be done within a minute.
Since you have define the mksysb as a resource, now you can use that to create a spot.
Creating a SPOT from existing mksysb.
smitty nim_mkres --> select spot
Define a Resource
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Resource Name [spot-test]
* Resource Type spot
* Server of Resource [master] +
Source of Install Images [test-mksysb] +
* Location of Resource [/export/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 +
Here I have used resource name as 'spot-test' (you can use anything), Server of resource is Master again. Source of install Image (here you select the mksysb you just created as resource- and it should be visible when you hit F4). You can specify a location for that spot.
This will take a few minutes to complete.
Follow the above procedure, and you will have a mksysb and spot.
use smitty nim_bosinst to install it on the client.
1 Like
Thanks for the quick response. Sorry actually i was confused, now your post made me realize what i did wrong. Spot got created successfully.
Thanks for your help. And i do not think the below warning is a problem. is that right ?
warning: 0042-001 m_mkspot: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: 1831-186 /mynfs/aixmksys/mksysimge not found in /etc/exports
ibmtech has already posted an excellent how-to, but i'd like to ask a question: why do you do the above?
At the NIM-master, issue "smitty nim", select "NIM Administration Tasks" from the menu, then start creating the mksysb from the NIM-master. This way you end up automatically with the mksysb being a NIM-resource. You don't need to pull it into the resource database like shown and neither do you need to transfer it to the NIM-master server. All this is done during the process.
I hope this helps.
bakunin
/PS: the warning means you got the NIM servers NFS somewhat confused. It is usually a very bad idea to NFS-export parts or super-parts of NIMs resources. Leave these alone and export other directories if you have to. NIM is famous for failing without a real understandable reason if you tinker with "/etc/exportfs".
bakunin
1 Like
For error like above. This is what IBM ask you to do
stopsrc -g nfs
cd /etc
remove any extra nim type of items in the exports file.
rm -rf xtab rmtab
cd /var/statmon
rm -rf state sm sm.bak
startsrc -g nfs
As Bakunin said, NIM is some times crappy.
1 Like
Thanks for your reply and suggestions. Actually your suggestion is good. But as i already created mksysb. I was looking for that type of solution. more over these are test boxes, which am exploring the NIM.
And I think you're correct regarding the error. I shouldn't ve exported the file system which used as resource for NIM.
Thanks much ibmtech and bakunin. Appreciate it.