HP StorageWorks P2000 HP StorageWorks P2000 G3 MSA System SMU Reference Guide - Page 30

Related topics, About the VDS and VSS hardware providers, About RAID levels

Get HP StorageWorks P2000 - G3 MSA Array Systems PDF manuals and user guides View all HP StorageWorks P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 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 mount 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 • Installing a license on page 40 • Creating a volume copy on page 68 • Aborting a volume copy on page 69 • Viewing information about a volume on page 90 • Deleting schedules on page 74 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 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 store 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. NOTE: 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 30 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
30
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 mount 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
•
Installing a license
on page 40
•
Creating a volume copy
on page 68
•
Aborting a volume copy
on page 69
•
Viewing information about a volume
on page 90
•
Deleting schedules
on page 74
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 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 store 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.
NOTE:
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