HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 22

Related topics, About volumes, About hosts - hosts not discovered

Get HP P2000 PDF manuals and user guides View all HP P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

Related topics • Configuring dynamic spares on page 47 • Managing dedicated spares on page 53 • Managing global spares on page 60 • Using the Provisioning Wizard on page 57 • Creating a vdisk on page 59 • Viewing information about a vdisk (page 92) or all vdisks (page 91) About volumes A volume is a logical subdivision of a vdisk, and can be mapped to controller host ports for access by hosts. A mapped volume provides the storage for a file system partition you create with your operating system or third-party tools. The storage system presents only volumes, not vdisks, to hosts. A vdisk can have a maximum of 128 volumes. You can create a vdisk that has one volume or multiple volumes. • Single-volume vdisks work well in environments that need one large, fault-tolerant storage space for data on one host. A large database accessed by users on a single host that is used only for that application is an example. • Multiple-volume vdisks work well when you have very large disks and you want to make the most efficient use of disk space for fault tolerance (parity and spares). For example, you could create one 10-TB RAID-5 vdisk and dedicate one spare to the vdisk. This minimizes the amount of disk space allocated to parity and spares compared to the space required if you created five 2-TB RAID-5 vdisks. However, I/O to multiple volumes in the same vdisk can slow system performance. When you create volumes you can specify their sizes. If the total size of a vdisk's volumes equals the size of the vdisk, you will not have any free space. Without free space, you cannot add or expand volumes. If you need to add or expand a volume in a vdisk without free space, you can delete a volume to create free space. Or, you can expand the vdisk and then either add a volume or expand a volume to use the new free space. You can use a volume's default name or change it to identify the volume's purpose. For example, a volume used to store payroll information can be named Payroll. You can create vdisks with volumes by using the Provisioning Wizard, or you can create volumes manually. Related topics • About vdisks on page 20 • About volume mapping on page 23 • About volume cache options on page 24 • Volume topics in Provisioning the system on page 57 • Changing a volume's name or OpenVMS UID on page 54 • Changing a volume's cache settings on page 55 • Viewing information about a volume on page 95 About hosts A host identifies an external port that the storage system is attached to. The external port may be a port in an I/O adapter (such as an FC HBA) in a server, or a port in a network switch. The controllers automatically discover hosts that have sent an inquiry command or a report luns command to the storage system. Hosts typically do this when they boot up or rescan for devices. When the command from the host occurs, the system saves the host ID. The ID for an FC or SAS host is its WWPN. The ID for an iSCSI host is typically, but not limited to, its IQN. You can also manually create entries for hosts. You can assign a name to a host to make it easy to recognize for volume mapping. For a named host, you can also select a profile that specifies whether the host allows use of LUN 0 for mappings. A maximum of 64 names can be assigned. 22 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
22
Getting started
Related topics
•
Configuring dynamic spares
on page 47
•
Managing dedicated spares
on page 53
•
Managing global spares
on page 60
•
Using the Provisioning Wizard
on page 57
•
Creating a vdisk
on page 59
•
Viewing information about a vdisk (
page 92
) or all vdisks (
page 91
)
About volumes
A
volume
is a logical subdivision of a vdisk, and can be mapped to controller host ports for access by
hosts. A mapped volume provides the storage for a file system partition you create with your operating
system or third-party tools. The storage system presents only volumes, not vdisks, to hosts. A vdisk can have
a maximum of 128 volumes.
You can create a vdisk that has one volume or multiple volumes.
•
Single-volume vdisks work well in environments that need one large, fault-tolerant storage space for
data on one host. A large database accessed by users on a single host that is used only for that
application is an example.
•
Multiple-volume vdisks work well when you have very large disks and you want to make the most
efficient use of disk space for fault tolerance (parity and spares). For example, you could create one
10-TB RAID-5 vdisk and dedicate one spare to the vdisk. This minimizes the amount of disk space
allocated to parity and spares compared to the space required if you created five 2-TB RAID-5 vdisks.
However, I/O to multiple volumes in the same vdisk can slow system performance.
When you create volumes you can specify their sizes. If the total size of a vdisk’s volumes equals the size of
the vdisk, you will not have any free space. Without free space, you cannot add or expand volumes. If you
need to add or expand a volume in a vdisk without free space, you can delete a volume to create free
space. Or, you can expand the vdisk and then either add a volume or expand a volume to use the new
free space.
You can use a volume’s default name or change it to identify the volume’s purpose. For example, a volume
used to store payroll information can be named Payroll.
You can create vdisks with volumes by using the Provisioning Wizard, or you can create volumes manually.
Related topics
•
About vdisks
on page 20
•
About volume mapping
on page 23
•
About volume cache options
on page 24
•
Volume topics in
Provisioning the system
on page 57
•
Changing a volume’s name or OpenVMS UID
on page 54
•
Changing a volume’s cache settings
on page 55
•
Viewing information about a volume
on page 95
About hosts
A
host
identifies an external port that the storage system is attached to. The external port may be a port in
an I/O adapter (such as an FC HBA) in a server, or a port in a network switch.
The controllers automatically discover hosts that have sent an
inquiry
command or a
report luns
command to the storage system. Hosts typically do this when they boot up or rescan for devices. When the
command from the host occurs, the system saves the host ID. The ID for an FC or SAS host is its WWPN.
The ID for an iSCSI host is typically, but not limited to, its IQN. You can also manually create entries for
hosts.
You can assign a name to a host to make it easy to recognize for volume mapping. For a named host, you
can also select a profile that specifies whether the host allows use of LUN 0 for mappings. A maximum of
64 names can be assigned.