Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

/var/opt/ignite/clients. You might remove the symbolic link to the host name because it
is recreated automatically. The LAN address must be all in uppercase and begin with 0x.
If you have already booted the client from the server, which caused it to create a new directory,
you can remove that directory before renaming the old directory. Do not delete the original directory
or you will lose the recovery information.
For example:
# cd /var/opt/ignite/clients
# mv 0x00108300041F 0x00108300042A
# rm old_hostname
Dealing with hot swappable disks during recovery.
See question “How do I deal with hot-swappable disk devices during recovery?” (page 22)
Why does archive_impact fail during make_net_recovery?
The PHCO_21185 patch issued for ksh(1M) causes corrupt parameter processing. The corruption
occurs when archive_impact is run as a part of a make_net_recovery command.
Software patch PHCO_21185 has been superseded by PHCO_22020. Remove patch
PHCO_21185 and install PHCO_22020 to correct this failure.
How can I restore VxVM DCO log volume groups?
The make_net_recovery/make_tape_recovery tools will create a recovery archive for a
client while preserving the configurations for all VxVM (VERITAS volume manager) volumes except
data change object (DCO) log volumes. After recovering from the archive, the DCO log volume
configurations are lost and must be reconfigured using VxVM commands. There are basically two
Frequently asked questions 47