Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell Solutions Enabler 10.0.0 TimeFinder SnapVX CLI User Guide

PDF

Secure snaps

For arrays running HYPERMAX OS Q2 2017 or higher, secure snapshots is an optional setting for SnapVX targetless snapshots that prevent accidental or intentional deletion of snapshots. Terminating a secure snapshot while the retention period is in effect is not allowed. When the retention time is reached the snapshot is automatically terminated only if there are no existing links or restore sessions. Extending the retention period is allowed but reducing it is not allowed. A traditional snapshot can be converted to a secure snaphot, but a secure snapshot may not be converted to a traditional snapshot. All SnapVX operations and rules for traditional snapshots regarding restores, linked target operations, and automatic expiration also apply to secure snapshots.
CAUTION:

When implementing secure snaps a user should determine how many snapshots on an array must be secure. The user should consider using secure snaps only on certain critical volumes, or only on a subset of the snapshots, to capture particular points-in-time that are critical to the business, Length of retention time should also be considered as part of the secure snapshot implementation. As always, proper planning and system sizing is crucial, no matter the types or number of snapshots that will exist in an environment.

Secure snapshots may only be terminated after they expire or by customer-authorized Dell EMC Support. Refer to Knowledgebase articles 498316 and 499975 for additional information.

Secure snapshots rules and allowable Solutions Enabler operations:

  • The secure expiration time is available at the snapshot level.
  • If the secure expiration time expires and the snapshot has no links or restore session, the snapshot is automatically deleted by the system.
  • If the secure expiration time expires and the snapshot has link to a device or has a restore session, the snapshot is automatically deleted by the system only after the linked target is unlinked or the restore session is terminated.
  • If the secured snapshot expiration time expires and the snapshot is linked to a device or has a restore session, the snapshot is no longer secured and is identified as expired.
  • A regular snapshot can be converted to secure snapshot by specifying a secure expiration time.
  • A secure expiration time can only be extended forward in time and not set back in time from the current setting.
  • A secure snapshot can be restored, renamed, linked, unlinked, set copy mode, and terminate a restore.
  • A secure snapshot that fails can be terminated.

Solutions Enabler operations not allowed on secure snapshots:

  • Terminating the snapshot if it is activated.
  • Setting time to live (TTL) on the snapshot
  • Setting the secure expiration time back in time from the current setting

Secure snapshot rules and restrictions on VMAX arrays running HYPERMAX OS5977 Q217SR or higher (applies to FBA and CKD devices):

  • New secure snapshots cannot be created when the SRP (Storage Resource Pool ) is above the RC (Reserve Capacity).
  • Secure snaps are unique in the handling of host writes and snapshots when SRP or Replication Data Pointer Cache limits are reached. Secure snaps are intended for use in cases where protecting specific point-in-time images are considered the highest priority. When Reserved Capacity of an SRP is reached and a host write to a source volume requires a new allocation in the SRP, secure snaps (unlike traditional snaps) are allowed to grow past the Reserved Capacity limit of the SRP. Preserving the secure snaps also takes priority over host writes to those source volumes in the event the entire SRP runs out of available capacity. This is the intent of secure snapshots. For example, in the event of an intentional attack or a runaway application on a system, that is using up all of the available capacity, preserving the secure snaps allows the user to restore from the secure snaps once the situation has been resolved.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\