• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (6)

1 Gabriel.Menini commented Permalink

Hello, we issue MKSYSBs through NIM. Will be possible to launch a MKSYSB from NIM using this feature? <div>&nbsp;</div> Do NIM and the target LPAR need both to be at TL3 SP1 (in case AIX7)?

2 cggibbo commented Permalink

Hi Garbriel, <div>&nbsp;</div> Yes, mksysbs via NIM do support snapshots. Both the NIM master and the client must be running AIX 7.1 TL3 SP1 (or AIX 6.1 TL9). <div>&nbsp;</div> You will see "Create backup using snapshots?" in the 'smit nim_mkres/mksysb' smit panel. <div>&nbsp;</div> Cheers. <div>&nbsp;</div> Chris

3 spen commented Permalink

are there any issues running mksysb from nim master and creating OS b/u of a PowerHA client? NIM sometimes get confused on PowerHA clients? Clients can be AIX61TL9 through and including AIX71TL3 with NIM at AIX71TL3?

4 Gabriel.Menini commented Permalink

Hello, Chris. The snapshot option is working perferct, here. In your opinion, what are the pros of using -T when performing MKSYSB? I mean, we launch them with '-Tip' flags and the final size is almost the same. Maybe, the advantage comes when considering the integrity of the backed up files.... Regards.

5 cggibbo commented Permalink

Hi Gabriel, yes the advantage is related to file integrity.

6 killerid commented Permalink

Just upgraded to 6100-09-02. I see the snapshot lvs created as above. The NIM server however adds them to the list of files to back up. THen fails to back them up cause they dissappear. NIM needs an update to handle these a little more gracefully. Sweet technology. I'll ignore the warnings, and just add them to my default exclude.rootvg. <br /> eg: <br /> 0512-003 savevg may not have been able to archive some files. <br /> The messages displayed on the Standard Error contained additional <br /> information. <br /> backup: 0511-449 An error occurred accessing ./dev/fslv02: A file or directory in the path name does not exist. <br /> backup: 0511-449 An error occurred accessing ./dev/fslv03: A file or directory in the path name does not exist. <br /> backup: 0511-449 An error occurred accessing ./dev/fslv04: A file or directory in the path name does not exist. <br /> backup: 0511-449 An error occurred accessing ./dev/fslv05: A file or directory in the path name does not exist. <br /> backup: 0511-449 An error occurred accessing ./dev/fslv06: A file or directory in the path name does not exist.

Add a Comment Add a Comment