VMware NetApp FAS 2050HA Especificaciones descargar pdf (Pagina 28)

NetApp Deduplication for FAS and V-Series Deployment and Implementation Guide

4.11 DEDUPLICATION AND MULTISTORE (VFILER)

Starting with Data ONTAP 7.3, deduplication is supported with MultiStore. In Data ONTAP 7.3, the

deduplication commands are available only in the CLI of vFiler0; however, they allow any volume to be

included in the command arguments, regardless of which vFiler unit the volume is associated with.

Beginning with Data ONTAP 7.3.1, the deduplication commands are available in the CLI of each vFiler unit,

allowing each vFiler unit to be configured from within itself.

4.12 DEDUPLICATION AND SNAPLOCK

Starting with Data ONTAP 7.3.1, deduplication is fully supported with SnapLock, including both enterprise

and compliance modes. If implementing SnapLock and NetApp deduplication for FAS, the following items

should be taken into consideration:

A SnapLock volume with files committed to WORM can be deduplicated. Capacity savings will be

similar to savings where the files were not committed to WORM. Both deduplication and subsequent

undeduplication do not result in any changes to the SnapLock attributes or WORM behavior of the

volume or the file.

Deduplication is applied across WORM, WORM append, and non-WORM (normal) files.

Volume restore from a Snapshot copy is only permitted on SnapLock enterprise volumes. When a

volume restore occurs from a Snapshot copy with deduplicated data, the file system returns to the state

at which the Snapshot copy was created, including the state of deduplication, and the (WORM) status of

the volume and the files.

File folding will continue to function, irrespective of the WORM and deduplication status of the files.

For LockVault

™

: A Snapshot copy is permanent, meaning it can only be deleted after retention period.

There is no archive Snapshot copy created on the secondary until deduplication completes. If

deduplication is still running when next transfer attempts to begin, then the next transfer is delayed. So

deduplication on LockVault can result in the disruption of the transfer schedule on the primary. Avoiding

the mismatched schedule will allow for optimal capacity savings to be recognized.

Autocommit functions irrespective of the deduplication status of the files.

When using qtree SnapMirror, deduplication needs to be run separately on the source and destination.

The WORM property is carried forward by qtree SnapMirror. Switching on WORM or deduplication on

either end has no effect on the qtree SnapMirror transfers. Undoing deduplication will also have no

effect when done on either the source or the destination.

When using volume SnapMirror, the WORM property of the files is carried forward by volume

SnapMirror. Deduplication only needs to be run on the primary. Volume SnapMirror allows the

secondary to inherit the deduplication. Undoing deduplication can only be done after breaking the

volume SnapMirror relationship.

To revert to a previous release on a system hosting a volume that is deduplicated and has WORM data

on it, deduplication must first be undone (undeduplicated).

If you are reverting to a previous release that does not support deduplication with SnapLock volumes,

prior to Data ONTAP 7.3.1, you must first run the ―sis undo‖ command. If the ―sis undo‖ command is not

run prior to the revert operation, then an error message will be displayed stating that ―sis undo‖ must be

performed.

For additional details regarding SnapLock, refer to TR-3263, WORM Storage on Magnetic Disks Using

SnapLock Compliance and SnapLock Enterprise.

4.13 DEDUPLICATION AND METROCLUSTER

Both stretch MetroCluster and fabric MetroCluster are now fully supported with deduplication. When using

MetroCluster with deduplication, the following items should be taken into consideration:

Stretch MetroCluster with deduplication is supported on Data ONTAP 7.2.5.1 and 7.3.1 or later.

Fabric MetroCluster with deduplication is supported on Data ONTAP 7.2.5.1 and 7.3.1 or later.

Deduplication will have an impact on CPU resources as a result of extra disk write operations. The

increase is due to writing to two plexes. On most platforms the impact will be less than 10%. This

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 39 40

Comentarios a estos manuales

Sin comentarios

VMware NetApp FAS 2050HA Especificaciones Pagina 28

Comentarios a estos manuales

Relacionado con productos y manuales para Software VMware NetApp FAS 2050HA