Import actions for operating systems or volume managers
Table: Import actions describes the import action for each operating system or volume manager.
Note the following regarding import actions:
HP-UX logical volume manager is a virtual auto import. An HP system can have VxVM managed root disks and some LVM managed disks. In a system only restore, the LVM database (the /etc/lvmtab file) is restored. Without any action required by BMR, these disks and their volumes are available. If entries remain in the /etc/fstab file for the file systems, those file systems are available.
During a merge on Solaris systems or a merge on VxVM, BMR may remove entries in the /etc/fstab or /etc/vfstab files by commenting them out.
Veritas Volume Manager is an auto import. VxVM has the ability (a disk group option) to import disk groups automatically. If there are entries in the /etc/fstab and the /etc/vfstab files, the file systems are available without BMR having to take action.
Note the following for Windows imports:
Without import, only the drive letters that were recreated are assigned after restore.
With import, the drive letters assigned to volumes on Trusted disks are assigned to the same location after the restore. If the volume does not exist or has moved, you must edit the Mount Devices registry key.
Table: Import actions
OS and volume manager | What import means |
|---|---|
AIX logical volume manager | Run importvg at restore time or during first boot. |
HP-UX logical volume manager | Merge lvmtab, merge fstab. |
Linux | Merge fstab. |
Solaris | Merge vfstab. |
Veritas Storage Foundation for Windows | Assign drive letter by MountedDevices, run vxdg import. |
Veritas Volume Manager | Run vxdg import, merge fstab. |
Windows | Assign drive letter by MountedDevices. |