Veritas Storage Foundation™ and High Availability Solutions ...
Veritas Storage Foundation™ and High Availability Solutions ... Veritas Storage Foundation™ and High Availability Solutions ...
48Storage Foundation and High Availability Solutions support for Solaris ZonesExporting VxVM volumes to a non-global zoneTo export VxVM volumes to a non-global zone1 Create a volume vol1 in the global zone:global# ls -l /dev/vx/rdsk/rootdg/vol1crw------- 1 root root 301, 102000 Jun 312:54 /dev/vx/rdsk/rootdg/vol1crw------- 1 root sys 301, 102000 Jun 3 12:54 /devices/pseudo/vxio@0:rootdg,vol1,102000,raw2 Add the volume device vol1 to the non-global zone myzone:global# zonecfg -z myzonezonecfg:myzone> add devicezonecfg:myzone:device> set match=/dev/vx/rdsk/mydg/vol1zonecfg:myzone:device> endzonecfg:myzone> commit3 Ensure that the devices will be seen in the non-global zone:global# zoneadm -z myzone haltglobal# zoneadm -z myzone boot4 Verify that /myzone/dev/vx contains the raw volume node and that thenon-global zone can perform I/O to the raw volume node.The exported device can now be used for performing I/O or for creating filesystems.VxVM devices in Solaris 10 global zonesOn the Solaris 10 operating environment, there are two physical nodescorresponding to each volume node entry, /devices and /dev, respectively, withthe same major and minor number. The physical nodes appear as follows:/devices raw volume node : /devices/pseudo/vxio@0:dgname,volname,minor_number,raw/devices block volume node : /devices/pseudo/vxio@0:dgname,volname,minor_number,blk/dev raw volume node : /dev/vx/rdsk/dgname/volumename/dev block volume node : /dev/vx/dsk/dgname/volumenameThe following example provides sample values in /devices:ls -l /devices/pseudo/vxio*vol1*brw------- 1 root sys 302, 66000 Mar 25
Storage Foundation and High Availability Solutions support for Solaris ZonesConfiguring Solaris non-global zones for disaster recovery4917:21 /devices/pseudo/vxio@0:mydg,vol1,66000,blkcrw------- 1 root sys 302, 66000 Mar 2517:21 /devices/pseudo/vxio@0:mydg,vol1,66000,rawThe following example provides sample values in /dev:ls -l /dev/vx/*dsk/mydg/vol1brw------- 1 root root 302, 66000 Mar 25 17:21 /dev/vx/dsk/mydg/vol1crw------- 1 root root 302, 66000 Mar 25 17:21 /dev/vx/rdsk/mydg/vol1Removing a VxVM volume from a non-global zoneThe following procedure removes a VxVM volume from a non-global zone.To remove a VxVM volume from a non-global zone◆Remove the volume device vol1 from the non-global zone myzone:global# zonecfg -z myzonezonecfg:myzone> remove device match=/dev/vx/rdsk/rootdg/vol1zonecfg:myzone> endzonecfg:myzone> commitConfiguring Solaris non-global zones for disasterrecoverySolaris Zones can be configured for disaster recovery by replicating the zone rootusing replication methods like Hitachi TrueCopy, EMC SRDF, Veritas VolumeReplicator, and so on. The network configuration for the Zone in the primary sitemay not be effective in the secondary site if the two sites are in different IP subnets.Hence, you need to make these additional configuration changes to the Zoneresource.To configure the non-global zone for disaster recovery, configure VCS on boththe sites in the global zones with GCO option.Refer to the Veritas Cluster Server Administrator’s Guide for more informationabout global clusters, their configuration, and their use.To set up the non-global zone for disaster recovery1 On the primary site, create the non-global Zone and configure its networkparameters.■Create the non-global zone on the primary site using the zonecfgcommand.
- 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 50 and 51: 50Storage Foundation and High Avail
- Page 52 and 53: 52Storage 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
<strong>Storage</strong> Foundation <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong> support for Solaris ZonesConfiguring Solaris non-global zones for disaster recovery4917:21 /devices/pseudo/vxio@0:mydg,vol1,66000,blkcrw------- 1 root sys 302, 66000 Mar 2517:21 /devices/pseudo/vxio@0:mydg,vol1,66000,rawThe following example provides sample values in /dev:ls -l /dev/vx/*dsk/mydg/vol1brw------- 1 root root 302, 66000 Mar 25 17:21 /dev/vx/dsk/mydg/vol1crw------- 1 root root 302, 66000 Mar 25 17:21 /dev/vx/rdsk/mydg/vol1Removing a VxVM volume from a non-global zoneThe following procedure removes a VxVM volume from a non-global zone.To remove a VxVM volume from a non-global zone◆Remove the volume device vol1 from the non-global zone myzone:global# zonecfg -z myzonezonecfg:myzone> remove device match=/dev/vx/rdsk/rootdg/vol1zonecfg:myzone> endzonecfg:myzone> commitConfiguring Solaris non-global zones for disasterrecoverySolaris Zones can be configured for disaster recovery by replicating the zone rootusing replication methods like Hitachi TrueCopy, EMC SRDF, <strong>Veritas</strong> VolumeReplicator, <strong>and</strong> so on. The network configuration for the Zone in the primary sitemay not be effective in the secondary site if the two sites are in different IP subnets.Hence, you need to make these additional configuration changes to the Zoneresource.To configure the non-global zone for disaster recovery, configure VCS on boththe sites in the global zones with GCO option.Refer to the <strong>Veritas</strong> Cluster Server Administrator’s Guide for more informationabout global clusters, their configuration, <strong>and</strong> their use.To set up the non-global zone for disaster recovery1 On the primary site, create the non-global Zone <strong>and</strong> configure its networkparameters.■Create the non-global zone on the primary site using the zonecfgcomm<strong>and</strong>.
Change language