HP-UX 11i v3 Persistent DSF Migration Guide

Backing Out From Migration

This section discusses how to back out the changes made during the migration steps above in case there are

any problems encountered during or after the migration. A new option (-L) to insf restores the legacy

configuration back onto the system and recreates the legacy DSFs as they were before. The following are the

steps to back out from a migration:

Step 1: Run insf –L. This command re-enables the legacy naming model and recreates the legacy

DSFs as they were before.

Step 2: Restore the ASCII files modified by iofind from the

/var/adm/iofind/logs/mmddyy

_hhmmss/backup/ directory to their original

directories.

Step 3: Restore the backup binary applications (if any).

Step 4: If LVM is used, see the LVM Migration from legacy to agile naming model HP-UX 11i v3 white

paper at http://docs.hp.com/en/hpux11iv3.html#LVM%20Volume%20Manager

for backing

out LVM migration (the LVM commands are vgextend and vgreduce). If whole disk

configuration is used and changes were made to /etc/fstab and

/stand/system, restore

the original /etc/fstab and /stand/system. A reboot might be required.

Step 5: Retry the original applications to verify that they are operating properly again. The original

applications work as before if everything has been restored as it was before. If this is the case,

the back out is successful. Otherwise, do recovery in Step 6.

Step 6: Restore the system from IUX Recovery Tape. (Perform this only if Step 5 fails)

Conclusion

To take advantage of the benefits of the agile naming model, HP recommends users migrate their affected

applications to use persistent DSFs. Users first need to understand the impact and define the changes to be

made. Some restrictions might apply initially and may prevent a full migration, but the coexistence with the

legacy naming model allows users to take a phased approach.