Professional Documents
Culture Documents
• Explain the difference between volume reserve and snapshot reserve and how they are related
• Describe how Snapshots operate, and the impact it has on a the Volume’s Volume and Snapshot Reserve
• What is a Page?
• A fixed amount of data
• A page is a set of preformatted collections of allocated
and unallocated logical blocks, (allocation units).
• What is a logical block / cluster unit / allocation unit?
• In terms of Pages, a logical block (sometimes called an
Allocation Unit, or AU) is a group of records on a
storage device that is defined by the formatting of the
file system. This should not be confused with the
physical blocks at the disk level or storage device pages
• NOTE: Sometimes “block” is used interchangeably
with the word “page”. Be aware of the context of the
discussion when the word block or page is used
Volume Snapshots
• Snapshots
• Represents the contents of a volume at the time of creation
• Snapshots are mountable like any other Volume
• Snapshots have unique IQNs – derived from the source volume with the date appended
• ACL/Access Policy Association is inherited, but changeable
• Operating Systems mount a Snapshot just like any other iSCSI Target Volume
• Since the Snapshot appears identical at the block level, your Operating Systems may or may not allow you
to mount the Snapshot from the same host if the source Volume is also mounted
• Windows – Yes
• Can mount R/O Snapshots if source Volume is not mounted on same host
• Can mount R/W Snapshots, even if source volume mounted on same host
• Linux – Yes
• Can mount R/W Snapshot in R/W or R/O mode
• Can mount R/O Snapshot even if source volume is mounted
• VMware – Yes, but needs re-signatured before usable
• NetWare – No
• Borrowed snapshot trimming – delete oldest snapshots that have borrowed space
• Trimming rule – remove deleted volumes before any snapshots are deleted to reclaim space
• Command Syntax
• volume select <VOLUMENAME> snapshot create-now [description <String>] [<online | offline>] [<read-only |
read-write>]
• Creating a Snapshot with the CLI
• Login as a Group, Pool or Volume Administrator
• Identify the volume name, if necessary using the volume show command
• Enter the command to create the snapshot from the Group or Volume Select submenu
• volume select <VOLUMENAME> snapshot create-now
• View the snapshot
• volume select <VOLUMENAME> snapshot show
• CLI Syntax
• volume select <VOLUMENAME>
snapshot delete <SNAPSHOTNAME>
• From the CLI
• Confirm the snapshot name
• Delete the snapshot - volume select
<VOLUMENAME> snapshot delete
<SNAPSHOTNAME>
• Confirm the removal of the desired
snapshot name
• CLI Syntax
• volume select MyVolume schedule create <name> type <once | hourly | daily> start-time <String>
[end-time <String>] [max-keep <1-512>] [frequency <String>] [start-date <String>] [end-date
<String>] [repeat-interval <String>] [partner <String>] [<read-write | read-only>] [<enable |
disable>]
• From the CLI
• Use the online help & command tab completion for assistance as needed
• The example below shows the creation of two schedules:
• An hourly schedule that will occur every 15 min and retain 40 snapshots
• A Daily schedule that will occur every 12 hours and retain 4 snapshots
Compression
• You can enable compression of snapshots and/or replicas to decrease the amount of space used by data to
which you do not need access
• Compression is disabled by default on Dell EqualLogic arrays, because once you start compression you
are not able to cancel, only suspend the action
• Important considerations to keep in mind, as you determine when to start compression:
• You must be running supported firmware on a PS6210 or PS6610 array
• You can start, suspend, and resume compression, but you cannot cancel the operation when it has started
• When compression is paused, new snapshots are not compressed and previous compressed snapshots remained
compressed
• When compressed data is moved from one array to another, (such as during a “vacate” action) the data must be
rehydrated. This is often a permanent condition, though it may be eligible for compression if the destination supports it.
• Enabling Compression is
simple
• Simply Select the Eligible
Member and Click Start
Compression
• You must accept the terms in
the dialog box below
• If the snapshot data is accessed often enough, it may change the eligibility of the data to be compressed
• If compression eligibility changes, the rehydration could become permanent and the change would be
reflected in the volume compression statistics
• Volume Collections
• Logical container of Volumes
• Allow Snapshots & Replication to occur at the same time
• Can create Snapshot Collection & Replication for cross
volume consistency
• Not the same as Volume Folders
• Avoid placing volumes in multiple containers
• Snapshot Collections
• Snapshots of Volume Collections
• Can create Snapshot Schedule against Volume Collections
• Custom Snapshot Collections
• Creating Snapshots across multiple volumes without using
a Volume Collection
• CLI
• collection create <NAME> <volume1>, [volume,
…,volume8] [description “<text>”]