Supported volume size
3020 - 1 TB
3040 - 3 TB
3050 - 2 TB
- Volume can never have crossed the maximum supported volume size to have the A-SIS deployed. Else A-SIS will fail. (Check the spec of Max volume size for rest of the filers)
- Active/Active configuration fail over is not supported.
- Enable license & start A-SIS on a flexible volume.
sis on volname
- Have it scheduled.
- Have it run on a existing volume.
- A-SIS dedup needs to be re-enabled on copied, restored, cloned & renamed volumes.
sis on path
- check volume dedup status.
- Space saved by dedup status.
- Stop current A-SIS during an operation.
- Disable A-SIS
sis off path
8 comments:
Faq's
Question: can you use VTL with this solution
Answer: No, NetApp Nearstore VTL will have its own dedup capability
Question: what algorithm is used to do the de-dupe
Answer: We do a checksum to compare blocks. Then we do a byte by byte compare to those blocks flagged as deduplicates to ensure that they are exactly the same.
Question: Is there a backup option (third-party vendor required?) that allows you to dump the FlexVol image to disk in a de-dup state? Can you do this with native dump on the FAS?
Answer: Dump to disk? You can use our own protocols (Vaulting & mirroring) to move/backup deduped data to secondary disk. Snapmirror is supported today and with the 7.3 release, deduplication will have unrestricted support for SnapVault
Question: Are there any issues using dedup and Enterprise Vault file Archiving?
Answer: It works with EV, and we are currently testing that environment in our labs and will have recommendations shortly (for #'s and %)
Question: What is the end-user's experience of deduped data...does the user see a pointer of sorts to the actual single instance of the deduped data?
Answer: The end user is unaware that the data is deduped. They see the same data before and after dedupe
Question: Any plans on offering dedupe technology across multiple volumes?
Answer: Yes, we are considering aggregate level dedupe for a future release
more points :
1. Dedup will be supported with OSSV in next data ontap releases.
2. Dedup is a background process. it consumes less than 5% of process
3. Dedup is performed at volume level. next release will be for Aggr level
4. Dedup is supported from 7.2.2
5. Dedup not supported in Vseries. R100, R150, FAS 250, FAS270, 800 & 900 series.
more pointsss :
6. Encryption with dedup is not currently supported.
7. R200, FAS 2000/3000/6000 beyond 900 series.
8. Dedup volume can be reverted to a non-dedup state
9. Database - 55 % space saving
Exchange PST - 30 %
10. Nearstore VTL does not support dedup.
11. NDMP re-expands the data as it moves to tape.
12. Snaplock will not be supported with dedup feature.
13. With snapmirroring, both source and destination should have the dedup license installed and adhere to the volume requirements to support dedup.
filer> sis start -s /vol/testvol
The file system will be scanned to process existing data in /vol/testvol.
This operation may initialize related existing metafiles.
Are you sure you want to proceed with scan (y/n)? y
Fri May 30 12:26:49 EDT [filer: wafl.scan.start:info]: Starting SIS volume scan on volume testvol.
The SIS operation for "/vol/testvol" is started.
filer> sis status
Path State Status Progress
/vol/testvol Enabled Active 317 MB Scanned
filer> sis status
Path State Status Progress
/vol/testvol Enabled Active 354 MB Scanned
filer> sis status
Path State Status Progress
/vol/testvol Enabled Active 371 MB Scanned
filer> sis status
Path State Status Progress
/vol/testvol Enabled Active 2614 MB Scanned
filer> sis status
Path State Status Progress
/vol/testvol Enabled Active 3454 MB Scanned
sis config -s auto /vol/as2
On flexible volume /vol/as2 deduplication is set to auto schedule. This means deduplication will be triggered by the amount of new data written to the flexible volume, specifically when there are 20% new fingerprints in the change log.
TITAN> sis config
Path Schedule
/vol/as1 auto
/vol/as2 auto
/vol/as3 auto
/vol/as4 auto
/vol/as5 auto
TITAN>
before.. the default config.
TITAN> sis config
Path Schedule
/vol/as1 sun-sat@0
/vol/as2 sun-sat@0
/vol/as3 sun-sat@0
/vol/as4 sun-sat@0
/vol/as5 sun-sat@0
3070 supports 6TB
6040 supports upto 10TB
6070 supports upto 14TB
Hello.
Your comment about Active/Active configurations is not entirely accurate with current versions of Data OnTAP. Quoted from TR-3505:
NetApp active-active controller configurations are supported with deduplication in the following manner:
In active-active state, where both nodes of the cluster are up and no takeover has been done, dedupe on each node will work independently of one another.
The total number of concurrent deduplication operations allowed on each node of an active-active configuration is eight.
Writes to the flexible volume have fingerprints written to the change log.
Upon failover to the partner node, there will not be any deduplication process running for the failed node. However, change logging for the failed node will continue to happen, and upon failback, normal deduplication operations will resume using the updated change log.
The resumed deduplication processes will start at the times scheduled for each volume or can be started manually.
While in failover mode, the deduplication operations of the local node will not be impacted.
Data ONTAP 7.2.X has no sis administration operations or deduplication function. However, starting with Data ONTAP 7.3, the following commands are supported for partner volumes in takeover mode: sis status, sis stat, sis on, sis off.
Also, starting with Data ONTAP version 7.3, for SnapVault with NetBackup™, block sharing is supported for partner volumes in takeover mode.
Since deduplication is a licensed option behind the NearStore option license, NetApp recommends having both nodes in an active-active controller configuration licensed with the NearStore option and with deduplication.
Deduplication does not add any overhead in an active-active configuration other than additional disk I/O.
UNDO deduplication.
Enter sis off .
Enter priv set diag.
Enter sis undo .
Post a Comment