[Sparky]

I'm going to try to clone a current virtual I/O server (vios_1) to another set of identical hardware (vios_2).

I started on vios_1 with with:

backupios -file bu_1:/vio_bu/vios_1

but when I'm doing the installios from the hmc, I get the following:

cat /var/log/nimol.log
Feb  6 15:41:34 ioserver nimol:,info=LED 610: mount  -r hmc01-b2:/info/ioserverres/SPOT/usr /SPOT/usr,
Feb  6 15:41:35 ioserver nimol:,info=,
Feb  6 15:41:35 ioserver nimol:,-S,booting,ioserver,
Feb  6 15:41:35 ioserver nimol:,info=LED 610: mount  hmc01-b2:/info/ioserver_re/mksysb /NIM_BOS_IMAGE,
Feb  6 15:41:35 ioserver nimol:,info=LED 610: mount  hmc01-b2:/info/ioserver_re/bosinst.data /NIM_BOSINST_DATA,
Feb  6 15:41:35 ioserver nimol:,info=,
Feb  6 15:42:49 ioserver nimol:,-R,success,ioserver,
Feb  6 15:42:49 ioserver nimol:,info=extract_data_files,
Feb  6 15:42:49 ioserver nimol:,info=query_disks,
Feb  6 15:42:49 ioserver nimol:,info=extract_diskette_data,
Feb  6 15:42:50 ioserver nimol:,info=setting_console,
Feb  6 15:42:50 ioserver nimol:,info=initialization,
Feb  6 15:42:59 ioserver nimol:,info=verifying_data_files,
Feb  6 15:43:05 ioserver nimol:,info=,
Feb  6 15:43:06 ioserver nimol:,info=BOS install 1% complete : Making boot logial volume.,
Feb  6 15:43:07 ioserver nimol:,info=BOS Install: Could not create the hd5 logial volume.,

Any idea why the problem?

[moralebr]

Sparky,

Aparently, you are using some locked/unavailable disks on your mksysb restore procedure.

If you want clone your current VIOServer to another identical machine, try to do the following steps:

1. Using HMC, assign the second VIOServer disks to the current;

2. In "oem_setup_env" environment, use the "mirrorvg" command, using the second VIOServer disks as target disks (or second copy, whatever);

3. When all PP are synchronized (0 STALED PP in "lsvg rootvg" command), still in "oem_setup_env", use the "splitvg" command, removing the second copy of PP (the PP in second VIOServer disks);

4. Using HMC, unassign the second VIOServer disks from the current VIOServer;

5. Still using HMC, assign the second VIOServer disks to the second VIOServer;

6. Boot from those disks.

After these six steps, you are with two identical VIOServers in the network (caution with duplicated IP addresses).

Correct the configurations (hostname, IP address, remove improper device configuration...) and have fun

Regards,
Luciano Martins.

4.

[moralebr]

Ooops!

Just one comment: It isn't a official IBM support procedure. If doesn't work, forgot IBM Support help.

Regards,
Luciano Martins.

[Sparky]

It looks like your instructions would give me a second VIOs on the same hardware (P520). I actually am trying to bring up another P520 with the exact same setup.

Two purposes for this:
1) Verify we can recover our current production system.
2) Have an exact copy of production for testing.

Thanks

[ScriptDaddy]

Take a MKSYSB backup via NIM and restore it.

That's how we did it.

Ben