Veritas Storage Foundation™ and High Availability Solutions ...
Veritas Storage Foundation™ and High Availability Solutions ... Veritas Storage Foundation™ and High Availability Solutions ...
52Storage Foundation and High Availability Solutions support for Solaris ZonesSoftware limitations of Storage Foundation support of non-global zonesCannot remove a volume configured in a non-global zoneAfter a volume node is configured in a Solaris non-global zone, the node cannotbe removed in certain Solaris releases. Solaris patch 122660-10 resolves this issue.Administration commands are not supported in non-global zoneAll administrative tasks, such as resizing a volume, adding a volume to a volumeset, and file system reorganization, are supported only in the global zone.Consequently, administrative commands, such as fsadm, fsvoladm, and vxassist,and administrative ioctls are not supported in the non-global zone by both VxFSand VxVM.A cluster-mounted VxFS file system is not supported as the root of anon-global zoneThe root of a non-global zone cannot currently be on a cluster-mounted VxFS filesystem.QIO and CQIO are not supportedQuick I/O and Cached Quick I/O are not supported by VxFS in non-global zones.Package and patch installation in non-global zonesTo ensure that the package and patch updates applied to Veritas products in theglobal zone are also propagated to the non-global zone, ensure that the non-globalzones are in a bootable state (installed/running). For example, to update thesoftware installed in a system, the disk group containing the root file system ofthe non-global zone should be imported and the file system should be mountedat the time that you run patchadd, pkgadd, or the CPI installation scripts.Package and patch removal with non-global zone configurationsIf non-global zones are part of the system configuration and the VRTSodm packageis installed, ensure that /dev/odm is unmounted in each non-global zone prior toVRTSodm package removal or product uninstallation. This ensures there are nonon-global zone odm module references that might prevent the global zone fromunloading the odm module.You can unmount /dev/odm in the non-global zone with the following commands:global# zlogin myzonemyzone# umount /dev/odm
Storage Foundation and High Availability Solutions support for Solaris ZonesSoftware limitations of Storage Foundation support of non-global zones53Root volume cannot be added to non-global zonesThe root volume cannot be added to non-global zones.Some Veritas Volume Manager operations can cause volume devicenames to go out of syncIf a volume is exported to a non-global zone, some Veritas Volume Manageroperations can cause the global and non-global volume device names to go out ofsync, which can create data corruption. This is because the Solaris operatingenvironment zone support is not aware of the devfsadm(1M) command, and thusthe zone configuration is not updated with any changes to the /dev or /devicesnamespaces.The following operations can cause device names to go out of sync:■■■■■■Removing a volumeImporting a disk groupDeporting a disk groupRenaming a disk group or volumeReminoring a disk groupRestarting vxconfigd or resetting the kernelTo prevent device names from to going out of sync, if a volume is exported to anon-global zone and an operation that can cause device names to go out of syncoccurs on that volume, remove the volume from the zone configuration using thezonecfg command and reboot the zone using the zoneadm command.See the zonecfg(1M) and zoneadm(1M) manual pages.Note: This issue applies to any Solaris device for which the /dev or /devicesdevice node is changed and has been configured in the non-global zone before thechange.The svc:/system/vxfs/vxfsldlic service is not enabled innon-global zonesWhen the VRTSvxfs package is installed on a host where the zone is configured,the svc:/system/vxfs/vxfsldlic service does not start automatically for theconfigured or installed non-global zones. As a result, the
- Page 1 and 2: Veritas Storage Foundationand High
- Page 4 and 5: Technical SupportContacting Technic
- Page 6 and 7: Support agreement resourcesIf you w
- Page 8 and 9: 8ContentsModifying the service grou
- Page 10 and 11: 10ContentsInstalling and configurin
- Page 12 and 13: 12ContentsSupported deployment mode
- Page 14 and 15: 14Overview of Veritas Storage Found
- Page 18 and 19: 18Storage Foundation and High Avail
- Page 20 and 21: 20Storage Foundation and High Avail
- Page 22 and 23: 22Storage Foundation and High Avail
- Page 24 and 25: 24Storage Foundation and High Avail
- Page 26 and 27: 26Storage Foundation and High Avail
- Page 28 and 29: 28Storage Foundation and High Avail
- Page 30 and 31: 30Storage Foundation and High Avail
- Page 32 and 33: 32Storage Foundation and High Avail
- Page 34 and 35: 34Storage Foundation and High Avail
- Page 36 and 37: 36Storage Foundation and High Avail
- Page 38 and 39: 38Storage Foundation and High Avail
- Page 40 and 41: 40Storage Foundation and High Avail
- Page 42 and 43: 42Storage Foundation and High Avail
- Page 44 and 45: 44Storage Foundation and High Avail
- Page 46 and 47: 46Storage Foundation and High Avail
- Page 48 and 49: 48Storage Foundation and High Avail
- Page 50 and 51: 50Storage Foundation and High Avail
- Page 54 and 55: 54Storage Foundation and High Avail
- Page 56 and 57: 56Storage Foundation and High Avail
- Page 58 and 59: 58Storage Foundation and High Avail
- Page 60 and 61: 60Storage Foundation and High Avail
- Page 62 and 63: 62Storage Foundation and High Avail
- Page 64 and 65: 64Storage Foundation and High Avail
- Page 66 and 67: 66Storage Foundation and High Avail
- Page 68 and 69: 68Storage Foundation and High Avail
- Page 70 and 71: 70Storage Foundation and High Avail
- Page 72 and 73: 72Storage Foundation and High Avail
- Page 74 and 75: 74Storage Foundation and High Avail
- Page 76 and 77: 76Storage Foundation and High Avail
- Page 78 and 79: 78Storage Foundation and High Avail
- Page 80 and 81: 80Storage Foundation and High Avail
- Page 82 and 83: 82Storage Foundation and High Avail
- Page 84 and 85: 84Storage Foundation and High Avail
- Page 86 and 87: 86Storage Foundation and High Avail
- Page 88 and 89: 88Storage Foundation and High Avail
- Page 90 and 91: 90Storage Foundation and High Avail
- Page 92 and 93: 92Storage Foundation and High Avail
- Page 94 and 95: 94Storage Foundation and High Avail
- Page 96 and 97: 96Storage Foundation and High Avail
- Page 98 and 99: 98Storage Foundation and High Avail
- Page 100 and 101: 100Storage Foundation and High Avai
<strong>Storage</strong> Foundation <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong> support for Solaris ZonesSoftware limitations of <strong>Storage</strong> Foundation support of non-global zones53Root volume cannot be added to non-global zonesThe root volume cannot be added to non-global zones.Some <strong>Veritas</strong> Volume Manager operations can cause volume devicenames to go out of syncIf a volume is exported to a non-global zone, some <strong>Veritas</strong> Volume Manageroperations can cause the global <strong>and</strong> non-global volume device names to go out ofsync, which can create data corruption. This is because the Solaris operatingenvironment zone support is not aware of the devfsadm(1M) comm<strong>and</strong>, <strong>and</strong> thusthe zone configuration is not updated with any changes to the /dev or /devicesnamespaces.The following operations can cause device names to go out of sync:■■■■■■Removing a volumeImporting a disk groupDeporting a disk groupRenaming a disk group or volumeReminoring a disk groupRestarting vxconfigd or resetting the kernelTo prevent device names from to going out of sync, if a volume is exported to anon-global zone <strong>and</strong> an operation that can cause device names to go out of syncoccurs on that volume, remove the volume from the zone configuration using thezonecfg comm<strong>and</strong> <strong>and</strong> reboot the zone using the zoneadm comm<strong>and</strong>.See the zonecfg(1M) <strong>and</strong> zoneadm(1M) manual pages.Note: This issue applies to any Solaris device for which the /dev or /devicesdevice node is changed <strong>and</strong> has been configured in the non-global zone before thechange.The svc:/system/vxfs/vxfsldlic service is not enabled innon-global zonesWhen the VRTSvxfs package is installed on a host where the zone is configured,the svc:/system/vxfs/vxfsldlic service does not start automatically for theconfigured or installed non-global zones. As a result, the
Change language