In addition to restoring the Virtual I/O Server,
you might need to restore user-defined virtual devices (such as virtual device
mappings). For example, in the event of a system failure, system migration,
or disaster.
User-defined virtual devices include metadata, such as virtual
device mappings, that define the relationship between the physical environment
and the virtual environment. In situations where you plan to restore the Virtual I/O Server to a new or different
system (for example, in the event of a system failure or disaster), you need
to back up both the Virtual I/O Server and
user-defined virtual devices.
Before you start, restore the
Virtual I/O Server from tape, DVD, or
a remote file system. For instructions, see one of the following procedures:
- Restoring the Virtual I/O Server from
tape
- Restoring the Virtual I/O Server from
one or more DVDs
- Restoring the Virtual I/O Server from
the HMC using a nim_resources.tar
file
- Restoring the Virtual I/O Server from
a NIM server using a mksysb file
To restore user-defined virtual devices, complete the following steps:
- List all of the backed-up volume groups (or storage pools) by running
the following command:
restorevgstruct -ls
This command lists the files located in the /home/ios/vgbackups directory.
- Run the lspv command to determine which disks
are empty.
- Restore the volume groups (or storage pools) to the empty disks
by running the following command for each volume group (or storage pool):
restorevgstruct -vg volumegroup hdiskx
Where:- volumegroup is the name of a volume group (or storage
pool) from step 1.
- hdiskx is the name of an empty disk from step 2.
- Recreate the mappings between the virtual devices and physical
devices (including storage device mappings, shared Ethernet and Ethernet adapter
mappings, and virtual LAN settings) using the mkvdev command.
You can find mapping information in the file that you specified in the tee command
from the backup procedure. For example, /home/padmin/filename.
Subscribe to this information
