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

Related topics, Once the copy is complete

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 29 highlights

The following figure illustrates how volume copies are created. Creating a volume copy from a standard or master volume Source volume Transient snapshot Data transfer New volume 1. Volume copy request is made with a standard volume or a master volume as the source. 2. If the source a standard volume, it is converted to a master volume and a snap pool is created. 3. A new volume is created for the volume copy, and a hidden, transient snapshot is created. 4. Data is transferred from the transient snapshot to the new volume. 5. On completion, the transient volume is deleted and the new volume is a completely independent copy of the master volume, representing the data that was present when the volume copy was started. Creating a volume copy from a snapshot Master volume Snapshot(s) Data transfer New volume 1. A master volume exists with one or more snapshots associated with it. Snapshots can be in their original state or they can be modified. 2. You can select any snapshot to copy, and you can specify that the modified or unmodified data be copied. 3. On completion, the new volume is a completely independent copy of the snapshot. The snapshot remains, though you can choose to delete it. Figure 3 Creating a volume copy from a master volume or a snapshot Snapshot operations are I/O-intensive. Every write to a unique location in a master volume after a snapshot is taken will cause an internal read and write operation to occur in order to preserve the snapshot data. If you intend to create snapshots of, create volume copies of, or replicate volumes in a vdisk, ensure that the vdisk contains no more than four master volumes, snap pools, or both. For example: 2 master volumes and 2 snap pools; 3 master volumes and 1 snap pool; 4 master volumes and 0 snap pools. 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 on page 69 • Aborting a volume copy on page 70 • Viewing information about a volume on page 95 • Deleting schedules on page 75 HP P2000 G3 MSA System SMU Reference Guide 29

  • 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
HP P2000 G3 MSA System SMU Reference Guide
29
The following figure illustrates how volume copies are created.
Figure 3
Creating a volume copy from a master volume or a snapshot
Snapshot operations are I/O-intensive. Every write to a unique location in a master volume after a
snapshot is taken will cause an internal read and write operation to occur in order to preserve the snapshot
data. If you intend to create snapshots of, create volume copies of, or replicate volumes in a vdisk, ensure
that the vdisk contains no more than four master volumes, snap pools, or both. For example: 2 master
volumes and 2 snap pools; 3 master volumes and 1 snap pool; 4 master volumes and 0 snap pools.
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
on page 69
•
Aborting a volume copy
on page 70
•
Viewing information about a volume
on page 95
•
Deleting schedules
on page 75
Source volume
Transient snapshot
Data transfer
New volume
1. Volume copy request is made with a standard volume or a master volume as the source.
3. A new volume is created for the volume copy, and a hidden, transient snapshot is created.
4. Data is transferred from the transient snapshot to the new volume.
5. On completion, the transient volume is deleted and the new volume is a completely independent copy of
the master volume, representing the data that was present when the volume copy was started.
Creating a volume copy from a standard or master volume
Master volume
Snapshot(s)
Data transfer
New volume
1. A master volume exists with one or more snapshots associated with it. Snapshots can be in their original
Creating a volume copy from a snapshot
state or they can be modified.
2. You can select any snapshot to copy, and you can specify that the modified or unmodified data be copied.
3. On completion, the new volume is a completely independent copy of the snapshot. The snapshot remains,
though you can choose to delete it.
2. If the source a standard volume, it is converted to a master volume and a snap pool is created.