NetApp HCI, Руководство пользователя

Страница: 15 / 363

storage is called a data protection relationship. The clusters are referred to as endpoints in which the volumes
reside and the volumes that contain the replicated data must be peered. A peer relationship enables clusters
and volumes to exchange data securely.
SnapMirror runs natively on the NetApp ONTAP controllers and is integrated into Element, which runs on
NetApp HCI and SolidFire clusters. The logic to control SnapMirror resides in ONTAP software; therefore, all
SnapMirror relationships must involve at least one ONTAP system to perform the coordination work. Users
manage relationships between Element and ONTAP clusters primarily through the Element UI; however, some
management tasks reside in NetApp ONTAP System Manager. Users can also manage SnapMirror through
the CLI and API, which are both available in ONTAP and Element.
See TR-4651: NetApp SolidFire SnapMirror Architecture and Configuration (login required).
You must manually enable SnapMirror functionality at the cluster level by using Element software. SnapMirror
functionality is disabled by default, and it is not automatically enabled as part of a new installation or upgrade.
After enabling SnapMirror, you can create SnapMirror relationships from the Data Protection tab in the Element
software.
Volume snapshots for data protection
A volume snapshot is a point-in-time copy of a volume that you could later use to restore a volume to that
specific time.
While snapshots are similar to volume clones, snapshots are simply replicas of volume metadata, so you
cannot mount or write to them. Creating a volume snapshot also takes only a small amount of system
resources and space, which makes snapshot creation faster than cloning.
You can replicate snapshots to a remote cluster and use them as a backup copy of the volume. This enables
you to roll back a volume to a specific point in time by using the replicated snapshot; you can also create a
clone of a volume from a replicated snapshot.
You can back up snapshots from a SolidFire cluster to an external object store, or to another SolidFire cluster.
When you back up a snapshot to an external object store, you must have a connection to the object store that
allows read/write operations.
You can take a snapshot of an individual volume or multiple for data protection.
Volume clones
A clone of a single volume or multiple volumes is point-in-time copy of the data. When you clone a volume, the
system creates a snapshot of the volume and then creates a copy of the data referenced by the snapshot.
This is an asynchronous process, and the amount of time the process requires depends on the size of the
volume you are cloning and the current cluster load.
The cluster supports up to two running clone requests per volume at a time and up to eight active volume clone
operations at a time. Requests beyond these limits are queued for later processing.
Backup and restore process overview for SolidFire storage
You can back up and restore volumes to other SolidFire storage, as well as to secondary object stores that are
compatible with Amazon S3 or OpenStack Swift.
You can back up a volume to the following: