Depending on your data protection and backup needs, Data ONTAP provides a variety of features and methods for protection from accidental, malicious, or disaster-induced data loss.
|Data protection feature||Description|
|aggr copy||Fast block copy of data stored in aggregates
This feature enables you to quickly copy blocks of stored system data from one aggregate to another.
|Snapshot copy||Allows you to manually or automatically create, schedule, and maintain multiple backups (also called Snapshot copies) of data on a volume Snapshot copies use only a minimal amount of additional volume space, and do not have a performance cost.
If a user accidentally modifies or deletes crucial data on a volume with Snapshot enabled, that data can be easily and quickly restored from one of the last several Snapshot copies created.
You can also create clones of FlexVol volumes and Data ONTAP LUNs using Snapshot copies. For more details, see the Data ONTAP Storage Management Guide for 7-Mode.
|SnapRestore (license required)||Fast, space-efficient restoration of large volumes of data backed up to Snapshot copies
The SnapRestore feature performs on-request Snapshot recovery from Snapshot copies on an entire volume.
|SnapMirror (license required)||Volume-to-volume and qtree-to-qtree replication
This feature enables you to periodically make Snapshot copies of data on one volume or qtree, replicate that data to a partner volume or qtree, usually on another storage system, and archive one or more iterations of that data as Snapshot copies. Replication on the partner volume or qtree ensures quick availability and restoration of data, from the point of the last Snapshot copy, should the storage system containing the original volume or qtree be disabled.
If you conduct tape backup and archival operations, you can carry them out on the data already backed to the SnapMirror partner.
|SnapVault (license required)||Centralized backup of multiple qtrees on multiple storage systems by using Snapshot technology
This feature enables you to back up qtrees on multiple volumes and storage systems to a single SnapVault secondary storage system specialized for quick backup and restore of its sources.
You can also install the Open Systems SnapVault agent on Windows, Solaris, Linux, AIX, or HP-UX systems. This agent enables SnapVault to back up and restore data to these systems also.
If you conduct tape backup and archival operations, you can carry them out on the data already backed up to the SnapVault secondary storage system.
|Tape backup dump and restore commands||Allow you to back up Snapshot copies to tape
The dump command takes a Snapshot copy of the volume and then copies that data to tape. Because the Snapshot copy, not the active file system, is backed up to tape, Data ONTAP can continue its normal functions while the tape backup takes place.
For more information, see the Data ONTAP Data Protection Tape Backup and Recovery Guide for 7-Mode.
Fast block copy of data from one volume to another
The vol copy command enables you to quickly block copy stored data from one volume to another.
|SyncMirror (HA pair required)||Continuous mirroring of data to two separate aggregates
This feature allows for real-time mirroring of data to matching aggregates physically connected to the same storage system.
In case of an unrecoverable disk error on one volume, the storage system automatically switches access to the mirrored volume.
This feature requires an HA pair.
|nvfail option to the vol options command||Protection against data corruption by failures of nonvolatile RAM (NVRAM)|
|Virus scan support||Support for third-party virus-scanning software for files accessed by Common Internet File System (CIFS) clients|
|MetroCluster||Stretch MetroCluster provides site protection and supports replication up to 500 m. Fabric MetroCluster provides site protection and supports replication up to 100 km by using Fibre Channel (FC) switches.
The SyncMirror functionality is enhanced to provide continuous volume mirroring.
Note: Systems using synchronous SnapMirror might experience performance degradation. Hence, you should use MetroCluster for synchronous replication instead of synchronous SnapMirror.