Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

226Configuring VCS to manage a Logical Domain using services from multiple I/O domainsConfiguring VCS to manage a Logical Domain using services from multiple I/O domainsAbout virtual disk multipathing for storage servicesVirtual disk multipathing (mpgroup) enables you to configure virtual disk on aguest logical domain to access its back-end storage path through more than oneI/O domain. This feature ensures that the virtual disk accessed by the guest logicaldomain remains accessible as long as services from one of the I/O domain areavailable.For example, if you set up a virtual disk multipathing (mpgroup) to access a physicaldisk from a shared storage (SAN) which is connected to more than one I/O domains,when the guest domain accesses that virtual disk, the virtual disk driver goesthrough one of the I/O domains to access the back-end storage. If the virtual diskdriver cannot connect to an I/O domain, then the virtual disk attempts to reachthe back-end storage through a different I/O domain.You must configure virtual disk multipathing (mpgroup) only if the storage back-enddevice exported to the guest domain is a LUN, Shared Disk, or CVM volume.Figure A-3shows a sample diagram for mpgroup with CVM VolumeT5440T5440GuestdomainGuestdomainmpgroup=datampgroup=dataCVM Volume CVM Volume CVM Volume CVM VolumeCVMCVMCVMCVMPrimaryAlternate I/OSFCFSHAClusterPrimaryAlternate I/ODMPDMPDMPDMPDataConfiguring virtual disk multipathing for LUN, Shared Disk, orCVM VolumeTo enable virtual disk multipathing (mpgroup), you must export a virtual diskback-end path from each I/O domain and add the virtual disks to a multipathinggroup (also known as mpgroup). The mpgroup is identified by a name and isconfigured when you export the virtual disk back-end path.
Configuring VCS to manage a Logical Domain using services from multiple I/O domainsConfiguring VCS to manage a Logical Domain using services from multiple I/O domains227To configure virtual disk multipathing1 Add the physical disk back-end path of the disk service to the primary domain.# ldm add-vdsdev mpgroup=data backend_path1 volume@primary-vds0where backend_path1 is the path to the virtual disk back-end from the primarydomain.2 Add the physical disk back-end path of the disk service to the alternate I/Odomain for disk added in step 1.# ldm add-vdsdev mpgroup=data backend_path2 volume@alternate-vds0where backend_path2 is the path to the virtual disk back-end from thealternate I/O domain.3 Export the virtual disk to the guest domain.# ldm add-vdisk disk_name volume@primary-vds0 ldom_namewhere disk_name is the name of the virtual storage device.where ldom_name is the name of the Logical Domain.Note: Do not set the value of the Options attribute to exclusive; excl. If setto exclusive, Logical Domain cannot use the multipathing functionality.For more details on configuring virtual disk multipathing, refer to the OracleVM server for SPARC Administration Guide.Virtual disk multi-pathing (mpgroup) configurations with DMPIf the disk exported to guest domain has more than one I/O path from each I/Odomain, install Veritas Dynamic Multi-pathing (DMP) in each I/O domain. Usethe DMP node name to configure the virtual disk multi-pathing (mpgroup) to thedisk exported to the guest domain.
Page 1 and 2:
Veritas Storage Foundationand High
Page 3 and 4:
Symantec Corporation350 Ellis Stree
Page 5 and 6:
■■■■■■■Hardware infor
Page 7 and 8:
ContentsTechnical Support .........
Page 9 and 10:
Contents9Chapter 4 Upgrading to 6.0
Page 11 and 12:
Chapter1About Veritas StorageFounda
Page 13 and 14:
About Veritas Storage Foundation an
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Chapter2Installing the products for
Page 151 and 152:
Installing the products for the fir
Page 153 and 154:
Installing the products for the fir
Page 155 and 156:
Chapter3Installing the productsusin
Page 157 and 158:
Installing the products using JumpS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Chapter4Upgrading to 6.0.3This chap
Page 165 and 166:
Upgrading to 6.0.3Upgrading to 6.0.
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176: Upgrading to 6.0.3Upgrading to 6.0.
Page 193 and 194: Upgrading to 6.0.3Verifying softwar
Page 195 and 196: Chapter5Uninstalling version 6.0.3T
Page 197 and 198: Uninstalling version 6.0.3Rolling b
Page 221 and 222: AppendixAConfiguring VCS to managea
Page 223 and 224: Configuring VCS to manage a Logical
Page 225: Configuring VCS to manage a Logical
show all

Veritas Storage Foundation and High Availability Solutions Release Notes

Create successful ePaper yourself

Delete template?

Save as template?