Create snapshot volume
You create a snapshot volume to provide host access to a snapshot image of a volume or snapshot consistency group. You can designate the snapshot volume as either read-only or read-write.
About this task
A read-only snapshot volume provides a host application with read access to a copy of the data contained in the snapshot image, but without the ability to modify the snapshot image. A read-only snapshot volume does not have associated reserved capacity.
A read-write snapshot volume provides the host application with write access to a copy of the data contained in the snapshot image. It has its own reserved capacity that is used to save any subsequent modifications made by the host application to the base volume without affecting the referenced snapshot image.
The process to create a snapshot volume is a multi-step procedure:
Step 1: Review members
You can select either a snapshot image of a base volume or a snapshot consistency group. If you select a snapshot consistency group snapshot image, the member volumes of the snapshot consistency group appear for review.
Step 2: Assign to host
You select a specific host or host cluster to assign it to the snapshot volume. This assignment grants a host or host cluster access to the snapshot volume. You can choose to assign a host later, if needed.
Before you begin
Valid hosts or host clusters exist under the
Hosts page.Host port identifiers must have been defined for the host.
Before creating a DA-enabled volume, verify that your planned host connection supports the Data Assurance (DA) feature. If any of the host connections on the controllers in your storage array do not support DA, the associated hosts cannot access data on DA-enabled volumes.
About this task
When you assign volumes, keep these guidelines in mind:
A host's operating system can have specific limits on how many volumes the host can access.
You can define one host assignment for each snapshot volume in the storage array.
Assigned volumes are shared between controllers in the storage array.
The same logical unit number (LUN) cannot be used twice by a host or a host cluster to access a snapshot volume. You must use a unique LUN.
- On the Assign to Host dialog box, select the host or host cluster that you want to assign to the new volume. If you want to create the volume without assigning a host, select Assign later from the drop-down list.
- Select the access mode. Choose one of the following:
- Read/write – This option provides the host with read/write access to the snapshot volume and requires reserved capacity.
- Read only – This option provides the host with read-only access to the snapshot volume and does not require reserved capacity.
- Click Next , and do one of the following:
- If your snapshot volume is read/write, the Review Capacity dialog box appears. Go to Step 3: Reserve capacity .
- If your snapshot volume is read only, the Edit Priority dialog box appears. Go to Step 4: Edit settings .
Step 3: Reserve capacity
You must associate reserved capacity to a read/write snapshot volume. System Manager suggests the volumes and capacity based on the properties of the base volume or snapshot consistency group. You can accept the recommended reserved capacity configuration or customize the allocated storage.
About this task
You can increase or decrease the reserved capacity for the snapshot volume as needed. If you find that the snapshot reserved capacity is larger than you need, you can reduce its size to free up space that is needed by other logical volumes.
Step 4: Edit settings
You can change the settings for a snapshot volume such as its name, caching, reserved capacity alert thresholds, and so on.
About this task
You can add the volume to solid-state disk (SSD) cache as a way to improve read-only performance. SSD cache consists of a set of SSD drives that you logically group together in your storage array.
What happens next?
System Manager creates the snapshot volume in a normal state.
If the snapshot volume shows in a pending state, the base volume is a member of an asynchronous mirror group completing a synchronizing operation.