Beruflich Dokumente
Kultur Dokumente
Abstract
This white paper describes EMC VNX
Snapshots. The paper reviews and explains
operations and best practices for the feature, as
well as limits and functions.
March 2015
Table of Contents
Executive summary .............................................................................. 5
Audience ............................................................................................. 5
Terminology ........................................................................................ 6
VNX Snapshots Technical Overview ...................................................... 7
How Snapshots work ................................................................................... 7
Snapshot granularity ............................................................................... 9
Snapshot Mount Point ............................................................................... 10
VNX operations.................................................................................. 11
Create a Snap ............................................................................................ 11
Create a Snap with AppSync ...................................................................... 13
Create a Snapshot Mount Point ................................................................. 13
Attach a Snapshot ..................................................................................... 15
Branching (snap of a snap)........................................................................ 15
Copy a Snapshot ................................................................................... 16
Snap of a Snapshot Mount Point ........................................................... 17
Detach a Snapshot Mount Point ............................................................ 19
Detach a Snapshot Mount Point with Snapshots ................................... 20
Destroy a Snapshot ................................................................................... 22
Consistency Groups................................................................................... 23
Attach a Consistent Snapshot ............................................................... 25
Branch a Consistent Snapshot .............................................................. 28
Rules for Consistency Groups ................................................................ 29
Restore...................................................................................................... 29
Restore with SnapView Snapshots and VNX Snapshots ......................... 30
Restore a LUN ........................................................................................ 31
Restore CGs........................................................................................... 33
Repurpose Snapshots ............................................................................... 33
Migrations ................................................................................................. 33
Migration considerations ...................................................................... 37
Limits ........................................................................................................ 37
Interoperability with other VNX features .................................................... 37
CLI .................................................................................................... 43
Create a Snapshot ..................................................................................... 44
Copy a Snapshot ....................................................................................... 44
Create a Snapshot Mount Point ................................................................. 45
Attach a Snapshot ..................................................................................... 46
Create a Cascading Snapshot .................................................................... 46
Detach a Snapshot .................................................................................... 47
Destroy a Snapshot ................................................................................... 47
List all VNX Snapshots for a LUN ................................................................ 47
Create a Consistency Group ....................................................................... 48
List Consistency Groups ............................................................................ 48
Create a Consistent Snapshot ................................................................... 49
Attach a Consistent Snapshot ................................................................... 49
SnapCLI............................................................................................. 49
Flush buffers ............................................................................................. 50
Create a Snapshot ..................................................................................... 50
Attach a Snapshot ..................................................................................... 50
Copy a Snap .............................................................................................. 50
Consistency Groups................................................................................... 50
Sample SnapCLI batch script ..................................................................... 51
Executive summary
VNX Snapshots is a VNX software feature that creates point-in-time
data copies. VNX Snapshots is used for data backups, software
development and testing, repurposing, data validation, and local rapid
restores. Unlike SnapView snapshots and clones, VNX Snapshots do
not consume large amounts of pool capacity. As a result, this feature is
preferred for modern data management.
This white paper describes all VNX Snapshots operations in detail.
Wherever possible, all aspects of the feature sets are presented visually.
The paper provides straightforward instructions for common functional
tasks. Most tasks are shown from the point of view of Unisphere
graphical user interface (GUI) and naviseccli command line interface
(CLI). You can also manage your VNX snapshots using EMC AppSync,
software that provides application consistent snapshots for Microsoft
Exchange and SQL Server, and provides crash-consistency for VMware
VMFS datastores. The AppSync GUI allows you to manage, configure,
catalogue, and schedule your VNX snapshots.
VNX Snapshots and SnapView will coexist on the same LUN.
Furthermore, SnapView clones, which use a different technology from
SnapView snapshots, will work with VNX Snapshots.
Audience
This paper is intended for EMC customers and EMC field personnel who
are familiar with VNX technology. The paper is intended to be used as a
main reference for VNX Snapshots technology.
Terminology
Snapshot granularity
Every VNX Snapshot has 8 KB block granularity. This means that every
write occupies at least 8 KB on the pool. The distribution of the 8 KB
blocks within a 256 MB slice (1GB in VNX OE for Block R32) is congruent
with the normal thin write algorithm.
Consider the following example. A LUN is snapped with a few blocks of
data. The new snapshot points at those blocks, just like the primary
LUN.
Figure 3: VNX Snapshot pointing at the same blocks with the LUN at
creation time
After a few moments, the primary LUN may receive an I/O that overwrites
block A. The first snapshot continues pointing to the original set of
blocks A, B, C, and D. After Snap2 is taken, it points to A`, B, C and D.
The next primary LUN I/O overwrites block D, and it now points to A`, B,
C, and D`.
10
A SMP is created for snapshots of a specific LUN. This means that each
SMP can be used only for snapshots of a single primary LUN.
To enable access to hosts, SMPs must be provisioned to storage groups
just like any typical LUN.
VNX operations
VNX Snapshots support the following operations.
Create a Snap
Creating a snapshot does not consume any pool space. The space starts
being used when new writes to the primary LUN or to the snapshot itself
arrive. Snapshots have a granularity of 8 KB, and their blocks are
tracked just like the blocks in thin LUNs. Every snapshot must have a
primary LUN, and that property never changes.
A primary LUN cannot be deleted while it has snapshots. In Unisphere,
you can delete a LUN that has snapshots by selecting an optional
setting that deletes the snapshots first.
To create a snapshot:
1. In Unisphere, select Storage > LUNs.
11
12
13
Figure 11: Unisphere right mouse click Snapshot Mount Point creation
Creating a SMP does not require any space from the pool.
Note: Each SMP is dedicated to a specific primary LUN. It is not possible
to attach snapshots from two different primary LUNs to a single SMP.
Therefore, a backup server that is backing up four different LUNs must
have four different SMPs provisioned to back up the snapshots of those
LUNs.
In Unisphere, you can provision the SMP to a host through either the
wizard or the SMP create screen.
In the CLI, you can provision the SMP to a host by using the Storage
Group command:
# To create a Snapshot Mount Point in CLI
naviseccli lun -create -type Snap -primaryLunName PrimaryLUN -sp B -l 60 \
-name SMP_name -allowInbandSnapAttach yes
# ^^ SMP LUN ID!!!
# When LUN ID is not provided at creation, VNX assigns one automatically.
# in that case, it needs to be looked up in order
# to provision the SMP to a storage group
# To provision the SMP to a Storage Group
naviseccli storagegroup -addhlu -gname "Storage Group 1" -hlu 60 -alu 60
CLI guidelines
14
Attach a Snapshot
Attaching is an asynchronous operation during which the SMP remains
available, but the I/O is queued. This means that that the host does not
have to rescan the SCSI bus to view the snapshot. The rescan is required
only to discover the SMP when it is first presented to the host.
15
Copy a Snapshot
A VNX Snapshot can be copied to another snapshot. The resulting
snapshot is a copy of the source except for the name. The allowReadWrite1 property is set to No on the copy.
The snapshot copy retains the source LUN properties and resides within
the same pool as the original snapshot. So, copying a snapshot
increases the snapshot count for a given production LUN by one.
This property is a security feature, preventing unauthorized mounting a snapshot for read/write operations.
16
17
The Source LUN property of the Cascading Snapshot has the name of the
SMP. It is possible to create multiple snapshots at this level, and
individually mount them.
18
19
The Last modify time to match the old Last modified time or
Creation time (if Last modified is empty) or remains the same, if
the snapshot had not been modified (as Snap2.2 has in Figure
17).
20
21
Destroy a Snapshot
Destroying (deleting) a snapshot reclaims space for reuse in the storage
pool. Reclaim is not instant, and is done by an internal process. This
internal process is throttled for better performance of the array and is
not sequential. This means that more than one snapshot can be
destroyed at one time. Multiple snapshot destructions start on a firstcome-first-served basis. VNX is tuned to destroy up to 16 snapshots
simultaneously on each Storage Processor (SP). Additional destruction
requests are queued until a destruction thread becomes available.
When a snapshot is in the "Destroying" state, it is still counted towards
the maximum number of snapshots. The snapshot name is changed to
Destroying_<timestamp> before it is destroyed. This way, a user can recreate a snapshot called, for example, "Monday_Backup_Snapshot"
immediately after executing a command to destroy the old snapshot
with the same name. This is especially useful for SnapCLI-based scripts.
Destroying a VNX Snapshot may generate a large amount of background
I/O as old blocks of data (which are unique to that snap) are removed
and the free space is reclaimed for the Pool. The amount of workload
generated on the SP and Pools is proportional to the number of
simultaneous deletions. The amount of time these deletions take to
complete depends on the amount of unique data on the snap. EMC
recommends snapshot deletions during periods of light load. Other
factors that may impact the performance of VNX Snapshots are:
22
frequency of VNX Snaps and their subsequent deletions will reduce the
background I/O load on the Pool.
VNX Snapshots with thick LUNs. A mode conversion (similar to converting
from thin to thick) will be triggered when the last snap is deleted. It is
preferable to make sure that there is always at least one snap remaining on
the Thick LUN if you plan on using snaps again. Alternatively, use Thin LUNs
instead.
Consistency Groups
A Consistency Group (CG) is an object that contains a list of primary
LUNs or SMPs (but not both) that are treated as a single entity for taking
snapshots.
A Consistent Snapshot is one snapshot of a collection of LUNs. When a
snapshot of a CG is initiated, all writes to member LUNs are held until
their snapshots have been created. A CG is primarily designed for LUNs
that belong to the same application.
Consistency Groups are not designed with the purpose of conducting an
action on multiple unrelated snaps for administrative purposes
(specifically detach/destroy). Using this process on unrelated LUNs in a
single consistency group can result in triggering a high level of
background I/O load on the pool.
For a CG, it is recommended that the number of IOPS provided by the
slowest drives in the pool should be equal to the number of IOPS
required by the host application. This ensures the host application is
not impacted if a part of the CG becomes inactive and the data is moved
down to the lowest tier.
Note: Application-aware consistency is achieved with AppSync product
that integrates with VNX Snapshots and VNX Snapshot CGs.
CGs take write-orderconsistent snapshots of a group of LUNs or SMPs.
CGs have a name and description. CGs can contain any non-private
pool-based LUNs, or SMPs. Figure 20 demonstrates the concept of
Consistency Groups.
23
24
25
26
27
28
Restore
Snapshots can be used to restore a primary LUN or a SMP. In other
words, the data in the LUN will be changed to match the data in the
snapshot. The classic use case for this operation is when recovering
from data corruption.
Restoring automatically creates a 'Restore point snapshot' to recover
from unintentional data corruption. Although restoring is not instant, it
29
is an online operation. While the LUN is being restored, its state shows
as Initializing, and is changed back to Ready after the restore is
complete. Although restoring is not instant, it is an online operation, in
the sense that the earlier point-in-time data is immediately available,
even while the restore operation occurs in the background. The user
only needs to perform an initial flush of the host buffers before starting
the process (just as you do when creating a snapshot), and then the rest
of the process is completely host transparent. While the LUN is being
restored, its state shows as 'Initializing,' and is changed back to 'Ready'
after the restore is complete.
Note: Restoring is also referred to as Protected Restore, because
restoring does not change the Restore Point snapshot. All its data is
protected so that the user can return to the point-in-time of the source
data if needed.
When restoring a SMP, the data from the source snapshot (the one
being restored) is placed onto the snapshot attached to a Mount Point.
Note: Restoring can change the LUN size if the source snapshot was
taken before the primary LUN expansion or shrinking.
EMC AppSync restores consistency groups and LUNs using a copy that is
catalogued during the execution of the snapshot.
Restore with SnapView Snapshots and VNX Snapshots
Since pool LUNs can have a combination of SnapView snapshots and
VNX Snapshots, it is possible to restore from either a SnapView
snapshot or a VNX Snapshot. Restore is supported for both cases.
30
Restore a LUN
Certain prerequisite steps must be performed from the host operating
system for a successful LUN restoration. Operating Systems often have
cached metadata pertaining to the LUN's file system. Restore operations
tend to confuse memory maps unless the cache is cleared.
This affects most operating systems. The following is a sample
procedure to restore a LUN from a VNX Snapshot. Microsoft Windows
operating system is used as an example.
Step 1
Stop application access to the LUN. Optionally, you may need to flush
application buffers.
Step 2
Flush the buffers for the drive by using SnapCLI.
Note: EMC recommends using SnapCLI for all other operating systems (if
an appropriate binary exists). Use native operating system methods
when SnapCLI binary is not available.
:: Windows
SnapCLI flush -o G:
:: Optionally, one could flush a physical drive, when it is not a "drive letter"
:: Note, this command makes sense only when the drive is mounted,
:: e.g. has a drive letter assigned
SnapCLI flush -o \\.\PhysicalDrive1
Step 3
Unmount the drive. For some versions of Windows, unmounting refers to
removing the drive letter. Windows 2012 has an option to turn the drive
offline. This can be done either from Disk Manager or from the CLI
(diskpart).
Note: Unmounting the drive guarantees that the host stops all I/O to the
LUN.
31
Status
------------Online
Online
Size
------100 GB
10 GB
Free
------38 MB
1024 KB
Dyn
---
Gpt
---
Step 4
Initiate the restore operation for the LUN from Unisphere or by using
naviseccli.
32
Repurpose Snapshots
Some snapshots may need to be repurposed for other use. For example,
when a primary LUN must be deleted, but one of its VNX Snapshots
need to be retained.
There are two ways to do that:
Migrate the SMP to another LUN before deleting the primary LUN.
Detach a snapshot and then restore the primary LUN (from that
snapshot).
o The primary LUN may have a different HLU than SMP, or
may even be presented to another host. Make sure to
check where the data is provisioned.
o In addition, the primary LUN has a different WWN from the
SMP. So, if any of your tools or scripts are using the WWN
of the SMP/primary LUN, they must be updated.
Migrations
One of the VNX Snapshot use cases is to promote a snapshot to be a
standard LUN. To do that, the snapshot must be attached, and then the
SMP can be migrated to another LUN.
If a migrating SMP has any snapshots associated with it (for example
Cascading Snapshots), all of them will be destroyed.
33
34
35
The LUN migration runs for some time. The speed of migration
depends on several factors such as the LUN priority, size of
PrimaryLUN1, and array load.
36
Migration considerations
Limits
37
38
Pool
LUN
Consistency Group
SMP
39
Snapshots are Auto-Deleted one at a time, because the system does not
have an ability to predict how many snapshots need to be deleted to
reach the low threshold.
Auto-Delete Thresholds
Figure 33 shows Auto-Delete thresholds.
determines whether the system should monitor the space used in the
Pool and Auto-Delete snapshots if required. When enabled, the
thresholds below are used for space monitoring. When disabled, the
threshold values are retained by the system but the pool space used is
not actively monitored.
40
Delete Eligibility
A busy snapshot is excluded from Auto-Delete or expiration destruction.
A snapshot is busy when:
It is attached to a SMP
It is involved in a restore
The Auto-Delete settings can be set in multiple places. Use the following
table for system rules.
Pool
LUN
On
On
On
On
VNX
Snapshot
On
Off
On
Off
On or Off
Off
On or Off
On or Off
Auto-Delete behavior
Snapshots are subject to destruction
This snapshot is exempt from
destruction
Snapshots are exempt from
destruction
All pool Snapshots are exempt from
destruction
41
Auto-Delete paused
When Auto-Delete is unable to find enough eligible snapshots to delete
to be able to reach the Low Threshold, a warning is posted.
To resolve the warning, perform one or several of the following actions:
Change thresholds
Snapshot Expiration
Every VNX Snapshot may have an optional expiration date. Expired
snapshots are destroyed at regular intervals. The VNX array scans for
expired snapshots once an hour (The Auto-Delete process does not
process destruction of expired snapshots. The destruction is handled by
another software layer.) When the expiration time is reached, the
snapshot may not be destroyed immediately. It is deleted by the
process started at the next running interval.
Setting an expiration date on a snapshot automatically disables AutoDelete. In CLI, the user must acknowledge a warning or overwrite it with o flag. In Unisphere, the user can set an expiration date only after AutoDelete is disabled (unchecked).
42
CLI
Unisphere Secure Command Line Utility, naviseccli, includes the 'snap'
command, and also options in the 'lun' command for VNX Snapshots.
[nasadmin@~]$ naviseccli -h SPA snap
Usage:
snap -create -res resource [-resType type][-name snapName][-descr description]
[{-keepFor number{h|d|m|y}|-allowAutoDelete {yes|no}}][-allowReadWrite {yes|no}]
[-ignoreMigrationCheck][-ignoreDeduplicationCheck]
snap -destroy -id snapName [-o]
snap -list [{-id snapName|[-resType type][-res resource]}][{-brief|-detail}]
snap -modify -id snapName [-name newName][-descr description]
[{-keepFor number{h|d|m|y}|-allowAutoDelete {yes|no}}][-allowReadWrite {yes|no}]
snap -copy -id snapName [-name newName][-ignoreMigrationCheck]
[-ignoreDeduplicationCheck]
snap -restore -id snapName [-bakName bakName][-res lunNumber][-o]
snap -attach -id snapName -res lunNumber
snap -detach -id snapName [-res lunNumber][-o]
snap -group -create -name cgName [-res lunNumber(s)][-descr description]
[-allowSnapAutoDelete {yes|no}]
snap -group -destroy -id cgName [-destroySnapshots]
snap -group -list [-id cgName][{-brief|-detail}]
snap -group -modify -id cgName [-name newName][-descr description]
[-allowSnapAutoDelete {yes|no}]
snap -group -addmember -id cgName -res lunNumber(s)
snap -group -rmmember -id cgName -res lunNumber(s)
snap -group -replmember -id cgName -res lunNumber(s)
snap -feature -info
16
43
Create a Snapshot
To create a snapshot, naviseccli requires the LUN ID, and not the LUN
name. Be sure to flush host buffers before creating a snapshot. See 0
Flush buffers for an example.
# Look up the LUN ID, if needed.
[nasadmin@~]$ naviseccli -h SPA lun -list -name Primary_LUN1 -default
LOGICAL UNIT NUMBER 10
Name: Primary_LUN1
Default Owner: SP B
Copy a Snapshot
As explained earlier, a copy of a snapshot does not inherit two
properties:
Name
44
45
Attach a Snapshot
There are two ways to attach a snapshot:
1. Attach a snapshot to a SMP by sending a command to the SMP
2. Attach a snapshot to a SMP by sending the command to the
snapshot
# attach via the lun command
[nasadmin@~]$ naviseccli -h SPA lun -attach -l 8155 -snapName Primary_LUN1_Snapshot
# attach via the snap command
[nasadmin@~]$ naviseccli -h SPA snap -attach -id Primary_LUN1_Snapshot -res 8155
# Note: in both cases 8155 is the LUN ID of the Snapshot Mount Point
If a snapshot does not allow read/write access, you will receive the
following error:
[nasadmin@~]$ naviseccli -h SPA snap -attach -id Primary_LUN1_Snapshot -res 8155
The properties of this snapshot do not allow it to be attached. Modify the snapshot
properties to allow it to be attached and retry the attach operation. (0x716d802e)
# To modify the Read/Write flag use this command:
[nasadmin@~]$ naviseccli -h SPA snap -modify -id Primary_LUN1_Snapshot \
-allowReadWrite yes
# And repeat attach
[nasadmin@~]$ naviseccli -h SPA snap -attach -id Primary_LUN1_Snapshot -res 8155
46
Detach a Snapshot
There are two ways to detach a snapshot:
1. Detach a snapshot by sending a command to the snapshot
2. Detach a snapshot by sending the command to the SMP
To detach using a lun command, use the name of the SMP. There are no
warnings.
[nasadmin@~]$ naviseccli -h SPA navi lun -detach -name PrimaryLUN1_SMP1
Destroy a Snapshot
[nasadmin@~]$ naviseccli -h SPA snap -destroy -id Primary_LUN1_Snapshot
Are you sure you want to perform this operation?(y/n): yes
Note: The getlun command does not show the VNX Snapshot
information.
47
If the LUN is a part of a CG, use that CG name to find the list of all LUNs:
[~]$ naviseccli -h SPA snap -list -res CG_name
Name: 2012-02-10 14:45:18
Description:
Creation time: 02/10/12 14:45:24
Source LUN(s): 4,5
Source CG: CG_name
State: Ready
Allow Read/Write: Yes
Modified: No
Allow auto delete: Yes
Expiration date: Never
Name: Backup Snapshot:2012-02-14 04:28:21
Description:
Creation time: 02/14/12 16:28:23
Source LUN(s): 4,5
Source CG: CG_name
State: Ready
Allow Read/Write: No
Modified: No
Allow auto delete: Yes
Expiration date: Never
To list snapshots for a single LUN (that is not a member of a CG) specify
the LUN ID or name with -res option.
48
SnapCLI
SnapCLI is the utility used on the host to manage snapshots and their
attachments to the SMPs. It uses in-band (FC or iSCSI) communication
with the array and thus does not require an IP connection to the Storage
Processor (SP).
SnapCLI is similar to the ADMSNAP utility in SnapView (ADMSNAP is not
used with VNX Snapshots). Both provide the same level of security in
that they can only manage snapshots of LUNs that they have access to,
based on the primary LUNs or existing SMPs exposed to the host. In
other words, the array administrator sets up the primary LUNs and/or
SMPs and puts them in the host storage group and then the host
administrator may use SnapCLI to manage snapshot creation,
destruction, attach and detach for those LUNs only.
Note: To run SnapCLI, run the SnapCLI command from its installation
folder, or modify the PATH to include the SnapCLI path. The default path
in Windows is C:\Program Files\EMC\Unisphere SnapCLI
49
Flush buffers
Like ADMSNAP, SnapCLI must be used to flush disk buffers before
creating or detaching a VNX Snapshot. This is especially important in
Windows environments.
:: Windows
SnapCLI flush -o G:
Create a Snapshot
:: Windows
SnapCLI create -s SnapCLI_snap1 -o \\.\PhysicalDrive1
:: Or address by the drive letter
SnapCLI create -s SnapCLI_snap2 -o G:
Attach a Snapshot
The following command attaches a snapshot to the first SMP available.
When there are many SMPs (that belong to the primary LUN), the first
available SMP is used (usually the one identified as the lower drive, e.g.
\\.\PhysicalDriveX).
:: Windows
SnapCLI attach -s SnapCLI_snap1 -f
Copy a Snap
An attached snapshot cannot be copied. Therefore, the request to copy
an attached snapshot will fail.
When a snapshot is not attached, it can be copied. You must specify
both the name of the Snap to be created and the name of the Snap to be
snapped.
:: Windows
SnapCLI copy -s SnapCLI_snap1_copy -b SnapCLI_snap1 -o G:
Consistency Groups
One main difference between SnapCLI and ADMSNAP is Consistency
Groups support. When creating VNX Snapshots, you can specify the
name of Consistency Group (CG) along with a list of LUNs. If the
specified CG does not already exist, it is created containing the LUNs
specified as members.
Note: If the specified Consistency Group already exists, the existing
members of the CG are replaced with the LUNs specified as members.
The storage system maintains the CG and member LUNs persistently.
50
:: Windows
:: Create a Consistent Snapshot, and a Consistency group (if it doesn't exist)
SnapCLI create -s Consistent_Snap -o T:,R: -c CG_name
51
VNX Snapshot
Definition
SnapView
Snapshot
Session
Create
Start
Attach
Activate
Detach
Deactivate
Primary LUN
Source LUN
Snapshot
Mount Point
Snapshot
Restore
Rollback
Delete
Delete a snapshot
Stop
Copy
-- N/A --
Consistency
Group
-- N/A --
In this context, besides LUNs, VNX Snapshots can be taken on a Consistency Group, or Attached Mount Point
Same as above
4
Same as above
2
3
52
Properties Detailed
Snapshot properties
Every snapshot has the following properties:
Snapshot
property
Name
Description
Description
Unique user friendly name.
This name can be used to
identify the snapshot in
management commands. The
array will generate a unique
name if it is not supplied
during the time of snapshot
creation.
User-created description
State
User
editable?
Yes
Yes
Value range
ASCII, all printable
characters (0x20
to 0x7E) with no
leading or trailing
spaces.
Maximum length:
255
ASCII, all printable
characters (0x20
to 0x7E) with no
leading or trailing
spaces.
Maximum length:
255
Timestamp
Timestamp or the
word "Never"
ASCII, all printable
characters (0x20
to 0x7E) with no
leading or trailing
spaces.
Maximum length:
64
ASCII, all printable
characters (0x20
to 0x7E) with no
leading or trailing
spaces.
Maximum length:
64
Initializing
Ready
Faulted
53
Snapshot
property
Allow
Read/Write
Modified
Source LUNs
Allow auto
delete
Expiration
Date
Description
User
editable?
Value range
Offline
Destroying
Yes/No
Yes
Yes/No
List
Yes
Yes/No
Yes
Timestamp
Description
Unique user friendly name
User
editable?
Yes
Yes
Value range
ASCII, all printable
characters (0x20
to 0x7E) with no
leading or trailing
spaces.
Maximum length:
64
Shared with all
LUN types (starts
high similar to
SnapView
Snapshot LUNs)
54
SMP property
Description
User
editable?
Value range
LUN Type
State Details
WWN
Current
Owner
Default
Owner
Auto Assign
Enabled
Allocation SP
Auto Delete
Active
Operation
Attached
Snapshot
Statistics
Allow Inband
Snap Attach
Snapshot Attach
LUN
ASCII
SPA, SPB.
Yes
SPA, SPB
SPA, SPB
SPA, SPB
Yes
Yes/No
Expanding
Shrinking
Attaching
Detaching
Maximum length:
255
Yes
Enabled
Disabled
55
Description
User
editable?
Total primary
capacity
Total snapshot
capacity
Metadata
Capacity
Value range
Total overhead
capacity
Total primary
subscription
Total snapshot
subscription
Total overhead
subscription
Yes
On/Off
Yes
0.01 - 99%5
GUI only allows whole numbers. CLI will accept decimal places.
56
Pool property
Auto-Delete
Pool Full Low
Water Mark
Auto-Delete
Pool Full
State
Auto-Delete
Snapshot
Space Used
Threshold
Enabled
Auto-Delete
Snapshot
Space Used
High Water
Mark
Auto-Delete
Snapshot
Space Used
Low Water
Mark
Description
also a size for convenience.
(Default: 95%)
Pool percentage full at which
auto-delete will stop
snapshot auto-deletion in the
pool. This value must be less
than the high water mark.
(Default: 85%)
The state of the pool full
auto-delete process for this
pool.
The Auto-delete Pool Full
State and Auto-Delete
Snap Used State states will
be aggregated into a single
state for reporting using the
GUI. Separate states for each
will be reported via the CLI.
Indicator that the system
should check the snapshot
space used high water mark
for auto-delete. (Default:
FALSE)
Total percentage snapshot
space used in the pool that
will trigger snapshot autodeletion in the pool. Shown
as a pool percentage full and
also a size for convenience.
(Default: 25%)
Total percentage snapshot
space used in the pool that
will stop snapshot autodeletion in the pool. This
value must be less than the
high water mark. Shown as a
pool percentage full and also
a size for convenience.
(Default: 20%)
User
editable?
Yes
Value range
0 - 98.00%6
Idle
Running
Could not
Reach LWM
System Paused
Failed
Yes
On/Off
Yes
0.01 - 99.00%7
Yes
0 - 98.00%8
GUI only allows whole numbers. CLI will accept decimal places.
GUI only allows whole numbers. CLI will accept decimal places.
8
GUI only allows whole numbers. CLI will accept decimal places.
6
7
57
Pool property
Auto-Delete
Snap Used
State
Description
User
editable?
Value range
Idle
Running
Could not
Reach LWM
System Paused
Failed
58