old_rootvg is an alternate disk image - you cannot varyon it, you can wake it up with
(alt_disk_install -S hdiskx puts it asleep again) or you can boot from it by changing the boot list of your server to this disk.
Generally when a VG appears in the output of lsvg command, than its imported, if the same VG appears in output of lsvg -o than its imported and varied on.
To export does in this case not mean that it it's information is written somewhere so it is available for further use like you might know it from NFS or other things.
From the man page of exportvg:
Quote:
...
The exportvg command removes the definition of the volume group specified by the VolumeGroup
parameter from the system. Since all system knowledge of the volume group and its contents are
removed, an exported volume group can no longer be accessed.
...
hi,
when u have exported an VG it will removes the ODM details of VG(which is exported),but u will have /etc/filesystems details regaring to the VG.
through a command u can't check whether a VG is exported or not.
hi,
when u have exported an VG it will removes the ODM details of VG(which is exported),but u will have /etc/filesystems details regaring to the VG.
through a command u can't check whether a VG is exported or not.
Actually you wont if you haven't manually modified /etc/filesystems as the volumegroup export will remove the entries from /etc/filesystems and the import will add them.
Exactly exportvg will clean the ODM and remove entries in /etc/filesystems.
If you have some disks that are on the system not assigned to any VG
you can check if they were assigned to any VG by reading
Volume Group Descriptor Area on the disk
You can check with
it will show the contains of that disk. The exportvg will clear the odm and filesystem entries from that system but data is still there in the hdisk, you can attach that disk to any other system and run importvg. If
is done then only it will wipe out all the data from disk.