12.07.2015 Views

Veritas Storage Foundation™ and High Availability Solutions ...

Veritas Storage Foundation™ and High Availability Solutions ...

Veritas Storage Foundation™ and High Availability Solutions ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

52<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 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 comm<strong>and</strong>s are not supported in non-global zoneAll administrative tasks, such as resizing a volume, adding a volume to a volumeset, <strong>and</strong> file system reorganization, are supported only in the global zone.Consequently, administrative comm<strong>and</strong>s, such as fsadm, fsvoladm, <strong>and</strong> vxassist,<strong>and</strong> administrative ioctls are not supported in the non-global zone by both VxFS<strong>and</strong> 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 <strong>and</strong> CQIO are not supportedQuick I/O <strong>and</strong> Cached Quick I/O are not supported by VxFS in non-global zones.Package <strong>and</strong> patch installation in non-global zonesTo ensure that the package <strong>and</strong> patch updates applied to <strong>Veritas</strong> 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 <strong>and</strong> the file system should be mountedat the time that you run patchadd, pkgadd, or the CPI installation scripts.Package <strong>and</strong> patch removal with non-global zone configurationsIf non-global zones are part of the system configuration <strong>and</strong> 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 comm<strong>and</strong>s:global# zlogin myzonemyzone# umount /dev/odm

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!