Module 6 Data Protection With Snapshots - Participant Guide
Module 6 Data Protection With Snapshots - Participant Guide
PROTECTION WITH
SNAPSHOTS
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Module 6 Data Protection with Snapshots
Snapshots Overview
Snapshots Overview
Pool
Disks
The Snapshots feature is enabled with the Local Copies license which enables
space efficient point-in-time snapshots of storage resources for block, file, and
VMware "data" vVols. The snap images can be read-only or read/write and used in
various ways. They provide an effective form of local data protection. If data is
mistakenly deleted or corrupted, the production data can be restored from a
snapshot to a known point-in-time data state. Hosts access snapshot images for
data backup operations, data mining operations, application testing, or decision
analysis tasks. The upcoming slides detail the feature architecture, capabilities,
benefits, and specifics of its operations and uses.
Caution: Snapshots are not full copies of the original data. Dell
Technologies recommends that you do not rely on snapshots for
mirrors, disaster recovery, or high-availability tools. Snapshots of
storage resources are partially derived from the real-time data in the
relevant storage resource. If the primary storage becomes
inaccessible, snapshots can also become inaccessible (not readable).
Storage resource
Production data access Snapshot image access
Parent pool
With Redirect on Write technology, when a snapshot is taken, the existing data on
the storage resource remains in place. The snapshot provides a point-in-time view
of the data. Production data access also uses this view to read existing data.
With Redirect on Write technology, when writes are made to the storage resource,
those writes are redirected. A new location is allocated as needed from the parent
pool in 256 MB slices. New writes are stored in 8 KB chunks on the newly allocated
slice. Reads of the new writes are serviced from this new location as well.
If the snapshot is writable, any writes are handled in a similar manner. Slice space
is allocated from the parent pool, and the writes are redirected in 8 KB chunks to
the new space. Reads of newly written data are also serviced from the new space.
Storage space is needed in the pool to support snapshots as slices are allocated
for redirected writes.
Because of the on-demand slice allocation from the pool, snapped thick file
systems transition to thin file system performance characteristics.
The table defines various combined snapshot capabilities for each of the Dell Unity
XT models. These combined limits have an interaction between each other. For
example, if a model 380 system had 20 LUNs and 20 file systems, each LUN and
file system could not have 256 user snapshots. The number of user snapshots
would exceed the maximum of 8000 for the system.
Snapshots consume space from the parent storage pool that the storage resource
uses. To prevent the pool from running out of space due to snapshots, there are
two options for automatically deleting the oldest snapshots. These options can be
set from the Properties page of the pool and selecting the Snapshot Settings tab.
One option triggers the automatic deletion that is based on the total pool space
consumed. Another option triggers the automatic deletion that is based on the total
snapshot space consumed. Either option can be used singularly, or they can both
be used in combination. Both options allow the configuration of a space threshold
value to start the deletion and a space threshold value for stopping the automatic
deletion. When a pool is created, the Total pool consumption option is set by
default. The option cannot be changed during pool creation but can be modified
after the pool is created. If both options are cleared, this setting disables the
automatic deletion of the oldest snapshots based on space that is used. Automatic
snapshot deletion is still configurable based on snapshot retention values.
Creating Snapshots
CG
LUNs
Snapshots are created on storage resources for block, file, and VMware. All are
created in a similar manner. For block, the snapshot is created on a LUN or a
group of LUNs within a Consistency Group. For file, the snapshot is configured on
a file system. For VMware, the storage resource is either going to be a LUN for a
VMFS datastore or a file system for an NFS datastore. When each of these storage
resources are created, the system provides a wizard for their creation. Each wizard
provides an option to automatically create snapshots on the storage resource.
Each resource snapshot creation is nearly identical to the other resources. For
storage resources already created, snapshots can be manually created for them
from their Properties page. As with the wizard, the snapshot creation from the
storage resource Properties page is nearly identical to the other resources.
More details on the snapshot creation within the block storage LUN creation wizard
and the file storage file system creation wizard are shown in separate topics. Each
topic also details the creation of manual snapshots from the LUN and file system
properties pages.
Snapshot Operations
CG
The operations that can be performed on a snapshot differ based on the type of
storage resource the snapshot is on. Operations on LUN-based snapshots are
Restore, Attach to host, Detach from host, Copy, Refresh, and Replicate.
Operations on file system-based snapshots are Restore, Refresh, and Copy.
Snapshot Schedules
• Internally, Unity systems use the UTC time zone for time and scheduling.
− The operating system, logs, schedules, and other features all use UTC.
• When you connect to Unisphere, the times that are displayed are adjusted by
Unisphere to the time zone of the browser.
• When changing time on the system, or the timing on a feature, it is stored
internally in UTC format.
• By default, Unity systems do not consider Daylight Savings Time (DST).
When you create a schedule, the time to take the snapshot is stored
internally in UTC time.
Because snapshot schedules are stored internally in UTC time, the time that a
snapshot is taken is not adjusted when Daylight Savings Time begins or ends.
Take Snapshot
To continue having snapshots taken at 1:00 AM local time, the operator must edit
the schedule.
Beginning with Dell EMC Unity OE 5.1, users can enable Time Zone support.
• Newly created schedules adjust automatically if the local time zone implements
Daylight Saving Time.
• NOTE: Schedules that were created before upgrading to OE 5.1 must be edited
one time to update the snapshot time.
Before enabling Schedule Time Zone support, the schedule appears as shown.
Beginning with Dell EMC Unity XT OE 5.1, the system supports a time zone option
to correct timing issues for snapshot schedules and asynchronous replication
throttling.
The setting applies to system defined and user created snapshot schedules. The
setting is not a system setting, and does not apply to other features such as logs or
FAST VP.
After upgrading to version 5.1, the schedule time zone is set to UTC Legacy. No
changes are made to schedules when upgrading.
If the user enables the time zone settings, the internal snapshot schedule is NOT
updated to the same absolute time. The user must check to see whether the
snapshot schedule must be updated after enabling time zone support.
To enable the feature, choose System Settings > Management > Schedule Time
Zone.
When Schedule Time Zone is enabled, the system updates the schedule with the
value that had been stored internally, in UTC time. The user must check the
schedule, and edit it if necessary.
In the example shown, the schedule must be edited to return the snapshot time to
its previous value, 1:00 AM.
LUNs
Attach
Multiple hosts attach
Multiple snapshots to snapshots for RO
capture different point-in- or RW access
time data states
It is also possible to copy a snapshot. In this example, the four o’clock snapshot is
copied. Other than having a unique name, the copy is indistinguishable from the
source snapshot and both capture identical data states.
Multiple hosts can be attached to any specific LUN snapshot or multiple snapshots
within the tree. When a host is attached to a snapshot for access to its data, the
attach can be defined for read-only access or read/write access. In the example, a
host attaches to the three o’clock snapshot for read-only access and the snapshot
remains unmodified from its original snapped data state. A different host is
attached to the four o’clock snapshot copy for read/write access. By default, the
system creates a copy of the snapshot to preserve its original data state. The user
can optionally not create the snapshot copy. When the snap is read/write attached,
its data state is marked as modified from its source.
LUN snapshots can easily be created in several ways. Within the wizard to Create
LUNs, there is an option to automatically create snapshots for the LUN based on a
schedule. The wizard contains a drop-down list selection that has three different
system defined schedules to select from to create the LUN snapshots. There is
also a snapshot retention value that is associated with each of the three schedules.
A customized schedule can also be created for use. The scheduler has the
granularity to configure a snapshot frequency by the hour, day, or week. A
snapshot retention policy can also be defined.
Note: Configuration fields that are annotated with a red asterisk are required.
For existing LUNs, snapshots are easily created from the LUN Properties page by
selecting the Snapshots tab. To create a snapshot of the LUN, select the + icon.
The snapshot must be configured with a name; by default the system provides a
name having a year, month, day, hour, minute, second format. Customized names
can also be configured. A Description field for the snapshot can be annotated as
an option. One of three Retention Policies must be configured. The default
retention configuration is the Pool Automatic Deletion Policy. It automatically
deletes the snapshot if pool space reaches a specified capacity threshold that is
defined on the pool. A customized retention time can alternately be selected and
configured for snapshot deletion on a specified calendar day and time. The other
alternative is to select the No Automatic Deletion option if the snapshot must be
kept for an undetermined amount of time.
Initial State
The Snapshot Restore operation rolls back the storage resource to the point-in-
time data state that the snapshot captures. In this restore example, a LUN is at a
five o’clock data state. It is restored from a snapshot with a four o’clock data state.
Attach
Attach
LUN
Before performing a restore operation, detach any host attached to the LUN
snapshot been restored. Also ensure that all hosts have completed all read and
write operations to the LUN you want to restore. Finally, disconnect any host
accessing the LUN. This action may require disabling the host connection on the
host-side.
Start Restore
Now the restore operation can be performed. From the four o’clock snapshot,
select the Restore operation. The system automatically creates a snapshot of the
current five o’clock data state of the LUN. This snapshot captures the current data
state of the LUN before the restoration operation begins.
Reconnect Hosts
The LUN is restored to the four o’clock data state of the snapshot. The hosts can
now be reconnected to the resources they were connected to before the restore
operation and resume normal operations.
Attach
Attach
Before the restore:
1. Detach hosts from LUN Perform Restore:
snapshots
1. Select snapshot Restore
2. Quiesce host I/O to LUN
To restore a LUN from a snapshot, access the Properties page for the LUN.
Attach
LUN
The first step is to select a snapshot to attach to. The next step is to select an
Access Type, either read-only or read/write. Then the host or hosts are selected to
be attached.
Attach
Perform Attach:
1. Select snapshot
2. Select Access Type Read-
only or Read/write
3. Select hosts
LUN
Next, the system optionally creates a copy of the snapshot if a read/write Access
Type was selected. The snapshot copy preserves the data state of the snapshot
before the attach. Finally, the selected host is attached to the snapshot with the
Access Type selected.
Attach
Attach
Perform Attach:
1. Select snapshot
2. Select Access Type Read-
only or Read/write
3. Select hosts
4. System optionally creates
copy of snapshot
LUN
5. Snapshot attached
To attach a host to a snapshot of a LUN, access the Properties page for the LUN.
The Snapshot Detach operation detaches a connected host from a LUN snapshot.
In this detach example, a secondary host is going to detach from the three o’clock
snapshot of the LUN.
Attach
Attach
LUN
Attach
Attach
LUN
Now the detach operation can be performed. From the three o’clock snapshot,
select the Detach from host operation.
Attach
Attach
The secondary host is detached from the three o’clock snapshot of the LUN.
Attach
To detach a host from a snapshot, first access the Properties page of the storage
resource.
The Snapshot Copy operation makes a copy of an existing snapshot that is either
attached or detached from a host. In this example, a copy of an existing four
o’clock snapshot is being made.
Attach
Attach
LUN
Attach
Attach
LUN
Snapshot Copied
A copy of the selected snapshot is made. The copy inherits the parent snapshot
data state of four o’clock and its retention policy.
Attach
Attach
2. Snapshot copied
3. Copy inherits parent data
LUN
state and retention policy
To copy a snapshot of a LUN, first access the Properties page of the LUN.
Attach
LUN
Next, from the Snapshots tab, a snapshot is selected and the snapshot operation
Attach to host is performed.
Attach
Attach
Dell EMC Unity tasks:
LUN
Now tasks from the host must be completed. The host must discover the disk
device that the snapshot presents to it. After the discovery, the host can access the
snapshot as a disk device.
Attach
Attach
Dell EMC Unity tasks:
File system
File system snapshots can easily be created in several ways. Within the wizard to
Create a File System, there is an option to automatically create snapshots for the
file system based on a schedule. File system snapshots that are created with a
schedule are read-only. The wizard contains a drop-down list selection that has
three different system defined schedules to select from to create the file system
snapshots. Each schedule includes a snapshot retention value. A customized
schedule can also be created for use. The scheduler includes the granularity to
configure a snapshot frequency by the hour, day, or week. A snapshot retention
policy can also be defined. Configuration fields that are annotated with a red
asterisk are required.
Snapshots of existing file systems are easily created from the file system
Properties page by selecting the Snapshots tab. A manually created file system
snapshot can be read-only or read/write. To create a snapshot of the file system,
select the + icon. The snapshot must be configured with a Name. By default the
system provides a name that is based on the creation time in a year, month, day,
hour, minute, second format. Customized names can also be configured. A
Description field for the snapshot can optionally be configured. One of three
Retention Policies must be configured. The default retention configuration is the
Pool Automatic Deletion Policy. That policy automatically deletes the snapshot if
pool space reaches a specified capacity threshold defined on the pool. A
customized Retention Time can alternately be selected and configured for
snapshot deletion on a specified calendar day and time within a year of creation.
The other alternative is to select the No Automatic Deletion option if the snapshot
must be kept for an undetermined amount of time. The Access Type section
requires configuration by selecting one of the two options for the snapshot; read-
only or read/write.
Initial State
The Snapshot Restore operation for a file system is similar to the restore operation
of a LUN. It rolls back the file system to a point-in-time data state that a read-only
or read/write snapshot captures. This example restores a file system from a
snapshot. The file system is at a five o’clock data state and is restored from a read-
only snapshot with a four o’clock data state.
File system
Disconnect Clients
Quiesce I/O
Before performing a restore operation, disconnect the client connected to the File
system snapshot been restored. Also quiesce I/O to the file system being restored.
Clients can remain connected to the file system but should close any opened files.
File system
Now the Restore operation can be performed. From the four o’clock snapshot,
select the Restore operation.
Current Data
State Snapped
The system automatically creates a snapshot of the current five o’clock data state
of the file system. It captures the current data state of the file system before the
restoration operation begins.
Connections and
I/O Resumed
The file system is restored to the four o’clock data state of the snapshot. The
connections and I/O to the resources can now be resumed for normal operations.
To restore a file system from a snapshot, access the Properties page for the
snapshot.
Initial State
The Snapshot Copy operation makes a copy of an existing file system snapshot
that is either read-only or read/write shared or unshared. In this example, a copy of
an existing four o’clock read-only snapshot is being made.
Select Snapshot
to Copy
Copy Created
The snapshot copy is created and is read/write. It also inherits the parent snapshot
data state of four o’clock and its retention policy.
To copy a snapshot of a file system, first access the Properties page of that file
system.
Initial State
File system
On the storage system, an NFS and or SMB share must be configured on the
read/write snapshot of the file system. This task is completed from their respective
pages.
File system
Now tasks from the client must be completed. The client must be connected to the
NFS/SMB share of the snapshot. After connection to the share, the client can
access the snapshot resource.
Initial State
File system
The first task for an NFS client is to connect to an NFS share on the file system.
File system
Access Snapshot
.ckpt
path
Similarly, the first task for an SMB client is to connect to an SMB share on the file
system.
.ckpt
path
Access to the read-only snapshot is established by the SMB client accessing the
Previous Versions tab of the SMB share. It redirects the client to the point-in-time
view that the read-only snapshot captures.
.ckpt Previous
path versions
2. Access the
2. Access the snapshot
File system snapshot previous
hidden .ckpt data path
versions tab
Through CVFS
The read-only snapshot is exposed to the clients through the CVFS mechanism.
Therefore the clients can directly recover data from the snapshot without any
administrator intervention. For example, if a user either corrupted or deleted a file
by mistake, that user could directly access the read-only snapshot. Then from the
snapshot the user can get an earlier version of the file and copy it to the file system
for recovery.
.ckpt Previous
path versions
NFS client tasks: SMB client tasks:
1. Connect to file system 1. Connect to file
NFS share system SMB share
2. Access the snapshot 2. Access the snapshot
hidden .ckpt data path previous versions tab
File system
Clients can recover data directly from the snapshot via CVFS
Dell Unity XT storage systems support creating snapshots of “data” (.vmdk) vVols
in Unisphere, Unisphere CLI, or REST API.
vVol snapshot restoration is also supported using Unisphere, Unisphere CLI, and
REST API.
• Snapshots that are created in vSphere using the VASA Provider can be
restored using vSphere, Unisphere, Unisphere CLI, or REST API.
• Snapshots that are created using Unisphere, Unisphere CLI, or REST API
cannot be restored using vSphere.
• Virtual Machines should be powered off before issuing a restore operation.
From Unisphere, you can create snapshots only for "data" vVols. Check the box to
select a data vVol. Then click the pencil icon to edit the selected virtual volume.
Select Snapshots
Create Snapshot
Initially, no snapshots exist for the vVol. Click the plus sign + to create a snapshot.
The system automatically generates a name for the snapshot. You can accept the
name, or enter a different name for the snapshot. Click OK to create the snapshot.
Select Snapshots
3. Select the Snapshots tab to view available snapshots for the data vVol.
Restore Snapshot
4. Check the box to select the wanted snapshot. From the More Actions drop-
down menu, select Restore.
Confirm Operation
5. Verify that the virtual machine is powered off, and click Yes to restore the vVol
from the snapshot.
1. Snapshots Overview
a. The Dell Unity XT Snapshots feature enables space efficient point-in-time
copies of storage resources for block, file, and VMware "data" vVols.
– The snap images can be read-only or read/write and used in various
ways.
– The production data can be restored from a snapshot to a known point-
in-time data state.
b. Snapshots of storage resources (LUNs, file systems, and VMware
datastores) are architected using Redirect on Write technology.
c. Snapshots can be scheduled at the time the storage resource is created, or
manually created from the resource properties page.
d. Snapshot operations include Restore, Attach to host, Detach from host,
and Copy, depending on the source storage resource.
2. LUNs and Consistency Groups Snapshots
a. Dell EMC XT Snapshots provide a mechanism for capturing a snapshot of
the multiple LUNs within a consistency group.
– The operation captures a write-order consistent image of the group of
LUNs.
– Multiple hosts can be attached to any specific LUN snapshot or multiple
snapshots within the tree.
b. Dell Unity XT system operations on LUN-based snapshots are Restore,
Attach to host, Detach from host, and Copy.
- The Restore operation rolls back the LUN or Consistency Group LUN
members to the point-in-time data state captured in the snapshot.
- The Snapshot Attach to host operation grants a host a defined access
level to a LUN snapshot.
- The Snapshot Dettach from host operation revokes the host access to
the LUN snapshot.
- The Copy operation makes a replica of an existing LUN snapshot which
inherits the parent snapshot data state and retention policy.
3. File System Snapshots
a. Dell Unity XT Snapshots provide a mechanism for capturing a snapshot of
file systems.
– Multiple snapshots of a file system capture different point-in-time data
states.
– Snapshots of file systems can be scheduled or manually created.
b. Snapshots of a file system can be created either as read-only or read/write,
and are accessed in different manners.
- Read/write snapshots of a file system can be shared by creating an NFS
or SMB share.
- The read-only file system snapshot is exposed to the client through a
checkpoint virtual file system (CVFS) mechanism that Snapshots
provides.
c. Dell Unity XT system operations on file system-based snapshots are
Restore and Copy.
- The Restore operation rolls back the file system to the point-in-time data
state captured in the read-only or read/write snapshot.
- The Copy operation makes a replica of an existing file system snapshot
that is either read-only or read/write shared or unshared.
4. Native vVol Snapshots
For more information, see the Dell EMC Unity Family Configuring
and managing LUNs, Dell EMC Unity: NAS Capabilities and Dell
EMC Unity Family Configuring vVols on the Dell EMC Unity
Family Technical Documentation portal at Dell Technologies site.