Full Discussion: Mksysb restore problem
Top Forums UNIX for Beginners Questions & Answers Mksysb restore problem Post 303040975 by Necronomic on Monday 11th of November 2019 10:33:20 AM
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 "

 
Test Your Knowledge in Computers #117
Difficulty: Easy
BSD (Berkley Software Distribution) is not an example of an OS derived from Unix.
True or False?

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
unshare_nfs(1M) 					  System Administration Commands					   unshare_nfs(1M)

NAME
unshare_nfs - make local NFS file systems unavailable for mounting by remote systems SYNOPSIS
unshare [-F nfs] pathname DESCRIPTION
The unshare command makes local file systems unavailable for mounting by remote systems. The shared file system must correspond to a line with NFS as the FSType in the file /etc/dfs/sharetab. OPTIONS
The following options are supported: -F This option may be omitted if NFS is the first file system type listed in the file /etc/dfs/fstypes. FILES
/etc/dfs/fstypes /etc/dfs/sharetab ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfssu | +-----------------------------+-----------------------------+ SEE ALSO
nfsd(1M), share(1M), attributes(5) NOTES
If the file system being unshared is a symbolic link to a valid pathname, the canonical path (the path which the symbolic link follows) will be unshared. For example, if /export/foo is a symbolic link to /export/bar (/export/foo -> /export/bar), the following unshare command will result in /export/bar as the unshared pathname (and not /export/foo): example# unshare -F nfs /export/foo For file systems that are accessed by NFS Version 4 clients, once the unshare is complete, all NFS Version 4 state (open files and file locks) are released and unrecoverable by the clients. If the intent is to share the file system after some administrative action, the NFS daemon (nfsd) should first be stopped and then the file system unshared. After the administrative action is complete, the file system would then be shared and the NFS daemon restarted. See nfsd(1M) SunOS 5.11 6 May 2003 unshare_nfs(1M)

Featured Tech Videos

All times are GMT -4. The time now is 09:18 PM.
Unix & Linux Forums Content Copyright 1993-2019. All Rights Reserved.
Privacy Policy