HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 26

Related topics, About the Remote Snap replication feature, About the VDS and VSS hardware providers - vcenter

Page 26 highlights

Guidelines to keep in mind when performing a volume copy include: • The destination vdisk must be owned by the same controller as the source volume. • The destination vdisk must have free space that is at least as large as the amount of space allocated to the original volume. A new volume will be created using this free space for the volume copy. • The destination vdisk does not need to have the same attributes (such as disk type, RAID level) as the volume being copied. • Once the copy is complete, the new volume will no longer have any ties to the original. • Volume Copy makes a copy from a snapshot of the source volume; therefore, the snap pool for the source volume must have sufficient space to store snapshot data when performing this copy. Related topics • "Creating a volume copy" (page 71) • "Aborting a volume copy" (page 72) • "Viewing information about a volume" (page 104) • "Deleting schedules" (page 78) About the Remote Snap replication feature See "Using Remote Snap to replicate volumes" (page 121). About the VDS and VSS hardware providers Virtual Disk Service (VDS) enables host-based applications to manage vdisks and volumes. Volume Shadow Copy Service (VSS) enables host-based applications to manage snapshots. For more information, see the VDS and VSS hardware provider documentation for your product. About the Storage Replication Adapter (SRA) The SRA is a host-software component installed on a Microsoft Windows Server operating system that allows VMware vCenter Site Recovery Manager software to control certain aspects of the replication feature in storage systems. The presence of the SRA allows the disaster recovery software to automatically coordinate virtual-machine failover and failback between a protected data center and a disaster recovery site. About RAID levels The RAID controllers enable you to set up and manage vdisks, whose storage may be spread across multiple disks. This is accomplished through firmware resident in the RAID controller. RAID refers to vdisks in which part of the storage capacity may be used to achieve fault tolerance by storing redundant data. The redundant data enables the system to reconstruct data if a disk in the vdisk fails. Hosts see each partition of a vdisk, known as a volume, as a single disk. A volume is actually a portion of the storage space on disks behind a RAID controller. The RAID controller firmware makes each volume appear as one very large disk. Depending on the RAID level used for a vdisk, the disk presented to hosts has advantages in fault-tolerance, cost, performance, or a combination of these. TIP: Choosing the right RAID level for your application improves performance. The following tables: • Provide examples of appropriate RAID levels for different applications • Compare the features of different RAID levels • Describe the expansion capability for different RAID levels 26 Getting started

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

26
Getting started
Guidelines to keep in mind when performing a volume copy include:
The destination vdisk must be owned by the same controller as the source volume.
The destination vdisk must have free space that is at least as large as the amount of space allocated to the
original volume. A new volume will be created using this free space for the volume copy.
The destination vdisk does not need to have the same attributes (such as disk type, RAID level) as the volume
being copied.
Once the copy is complete, the new volume will no longer have any ties to the original.
Volume Copy makes a copy from a snapshot of the source volume; therefore, the snap pool for the source volume
must have sufficient space to store snapshot data when performing this copy.
Related topics
"Creating a volume copy" (page 71)
"Aborting a volume copy" (page 72)
"Viewing information about a volume" (page 104)
"Deleting schedules" (page 78)
About the Remote Snap replication feature
See
"Using Remote Snap to replicate volumes" (page 121)
.
About the VDS and VSS hardware providers
Virtual Disk Service (VDS) enables host-based applications to manage vdisks and volumes. Volume Shadow Copy
Service (VSS) enables host-based applications to manage snapshots. For more information, see the VDS and VSS
hardware provider documentation for your product.
About the Storage Replication Adapter (SRA)
The SRA is a host-software component installed on a Microsoft Windows Server operating system that allows
VMware vCenter Site Recovery Manager software to control certain aspects of the replication feature in storage
systems. The presence of the SRA allows the disaster recovery software to automatically coordinate virtual-machine
failover and failback between a protected data center and a disaster recovery site.
About RAID levels
The RAID controllers enable you to set up and manage vdisks, whose storage may be spread across multiple disks.
This is accomplished through firmware resident in the RAID controller. RAID refers to vdisks in which part of the
storage capacity may be used to achieve fault tolerance by storing redundant data. The redundant data enables the
system to reconstruct data if a disk in the vdisk fails.
Hosts see each partition of a vdisk, known as a volume, as a single disk. A volume is actually a portion of the storage
space on disks behind a RAID controller. The RAID controller firmware makes each volume appear as one very large
disk. Depending on the RAID level used for a vdisk, the disk presented to hosts has advantages in fault-tolerance,
cost, performance, or a combination of these.
TIP:
Choosing the right RAID level for your application improves performance.
The following tables:
Provide examples of appropriate RAID levels for different applications
Compare the features of different RAID levels
Describe the expansion capability for different RAID levels