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

Creating a volume copy, To create a volume copy now

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

• Recurrence. Specify the interval at which the task should run. Set the interval to at least 2 minutes. The default is 1 minute. • Time Constraint. Specify a time range within which the task should run. • Date Constraint. Specify days when the task should run. Ensure that this constraint includes the Start Schedule date. • End Schedule. Specify when the task should stop running. 4. Click Reset Snapshot. If the task succeeded, the schedule is saved and can be viewed in the overview panel for the snapshot or system. 5. Make a reminder to unmount/unpresent/unmap the snapshot before the scheduled task runs. Creating a volume copy You can copy a volume or a snapshot to a new standard volume. The destination volume must be in a vdisk owned by the same controller as the source volume. If the source volume is a snapshot, you can choose whether to include its modified data (data written to the snapshot since it was created). The destination volume is completely independent of the source volume. The first time a volume copy is created of a standard volume, the volume is converted to a master volume and a snap pool is created in the volume's vdisk. The snap pool's size is either 20% of the volume size or the minimum snap-pool size, whichever is larger. Before creating or scheduling copies, verify that the vdisk has enough free space to contain the snap pool. For a master volume, the volume copy creates a transient snapshot, copies the data from the snapshot, and deletes the snapshot when the copy is complete. For a snapshot, the volume copy is performed directly from the source; this source data may change if modified data is to be included in the copy and the snapshot is mounted/presented/mapped and I/O is occurring to it. To ensure the integrity of a copy of a master volume, unmount/unpresent/unmap the volume or at minimum perform a system cache flush and refrain from writing to the volume. Since the system cache flush is not natively supported on all operating systems, it is recommended to unmount/unpresent/unmap temporarily. The volume copy is for all data on the disk at the time of the request, so if there is data in the operating-system cache, that will not be copied over. Unmounting/unpresenting/unmapping the volume forces the cache flush from the operating system. After the volume copy has started, it is safe to remount/re-present/remap the volume and/or resume I/O. To ensure the integrity of a copy of a snapshot with modified data, unmount/unpresent/unmap the snapshot or perform a system cache flush. The snapshot will not be available for read or write access until the volume copy is complete. If modified write data is not to be included in the copy, then you may safely leave the snapshot mounted/presented. During a volume copy using snapshot modified data, the system takes the snapshot offline, as shown by the Snapshot Overview panel. The volume copy's progress is shown in the Volume Overview panel. You can create a volume copy now or schedule the copy task. To create a volume copy now 1. In the Configuration View panel, right-click a volume and select Provisioning > Create Volume Copy. 2. In the main panel, select Now. 3. Set the options: • New Volume Name. Optionally change the default name for the destination volume. A volume name is case sensitive; cannot already exist in a vdisk; cannot include a comma, double quote, or backslash; and can have a maximum of 20 bytes. • Residing On Vdisk. Optionally change the destination vdisk. • With Modified Data. If the source volume is a snapshot, select this option to include the snapshot's modified data in the copy. Otherwise, the copy will contain only the data that existed when the snapshot was created. 4. Click Copy the Volume. A confirmation dialog appears. 5. Click Yes to continue; otherwise, click No. If you clicked Yes and With Modified Data is selected and the snapshot has modified data, a second confirmation dialog appears. HP P2000 G3 MSA System SMU Reference Guide 69

  • 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
69
•
Recurrence. Specify the interval at which the task should run. Set the interval to at least 2 minutes.
The default is 1 minute.
•
Time Constraint. Specify a time range within which the task should run.
•
Date Constraint. Specify days when the task should run. Ensure that this constraint includes the Start
Schedule date.
•
End Schedule. Specify when the task should stop running.
4.
Click
Reset Snapshot
. If the task succeeded, the schedule is saved and can be viewed in the overview
panel for the snapshot or system.
5.
Make a reminder to unmount/unpresent/unmap the snapshot before the scheduled task runs.
Creating a volume copy
You can copy a volume or a snapshot to a new standard volume. The destination volume must be in a
vdisk owned by the same controller as the source volume. If the source volume is a snapshot, you can
choose whether to include its modified data (data written to the snapshot since it was created). The
destination volume is completely independent of the source volume.
The first time a volume copy is created of a standard volume, the volume is converted to a master volume
and a snap pool is created in the volume’s vdisk. The snap pool’s size is either 20% of the volume size or
the minimum snap-pool size, whichever is larger. Before creating or scheduling copies, verify that the vdisk
has enough free space to contain the snap pool.
For a master volume, the volume copy creates a transient snapshot, copies the data from the snapshot, and
deletes the snapshot when the copy is complete. For a snapshot, the volume copy is performed directly
from the source; this source data may change if modified data is to be included in the copy and the
snapshot is mounted/presented/mapped and I/O is occurring to it.
To ensure the integrity of a copy of a master volume, unmount/unpresent/unmap the volume or at
minimum perform a system cache flush and refrain from writing to the volume. Since the system cache flush
is not natively supported on all operating systems, it is recommended to unmount/unpresent/unmap
temporarily. The volume copy is for all data on the disk at the time of the request, so if there is data in the
operating-system cache, that will not be copied over. Unmounting/unpresenting/unmapping the volume
forces the cache flush from the operating system. After the volume copy has started, it is safe to
remount/re-present/remap the volume and/or resume I/O.
To ensure the integrity of a copy of a snapshot with modified data, unmount/unpresent/unmap the
snapshot or perform a system cache flush. The snapshot will not be available for read or write access until
the volume copy is complete. If modified write data is not to be included in the copy, then you may safely
leave the snapshot mounted/presented. During a volume copy using snapshot modified data, the system
takes the snapshot offline, as shown by the Snapshot Overview panel.
The volume copy’s progress is shown in the Volume Overview panel.
You can create a volume copy now or schedule the copy task.
To create a volume copy now
1.
In the Configuration View panel, right-click a volume and select
Provisioning > Create Volume Copy
.
2.
In the main panel, select
Now
.
3.
Set the options:
•
New Volume Name. Optionally change the default name for the destination volume. A volume
name is case sensitive; cannot already exist in a vdisk; cannot include a comma, double quote, or
backslash; and can have a maximum of 20 bytes.
•
Residing On Vdisk. Optionally change the destination vdisk.
•
With Modified Data
. If the source volume is a snapshot, select this option to include the snapshot’s
modified data in the copy. Otherwise, the copy will contain only the data that existed when the
snapshot was created.
4.
Click
Copy the Volume
. A confirmation dialog appears.
5.
Click
Yes
to continue; otherwise, click
No
. If you clicked Yes and With Modified Data is selected and
the snapshot has modified data, a second confirmation dialog appears.