Yes you are right; i didnt read that properly. Regarding the Dedup Bug: In my case the Dedup Bug consumed about 900gb in a 1TB Volume, so 90 %. After i've done a "sis start -s /volname" only 100gb of the 1 TB Volume were filled.. Regards ... View more

Hi Have the same problem. The problem is a Dedup Bug. The fingerprint database fills up the place in the volume. Solution from Netapp Support: *************** Workaround     A cleanup of the fingerprint database on a volume impacted by this issue is accomplished by running the following command:     >  s <vol> Note: Potential exists for storage efficiency to be decreased after executing this manual work-around. Consult NetApp Technical Support before executing 'sis start -s' on the affected volume. This is a very long-running process as it is building a new copy of the Fingerprint Database (FPDB) and then purging the old to reclaim the volume space.     If the workload on the storage system imposed by running sis start -s is extremely large, a support engineer can guide the customer to use the following advanced-mode command on the impacted volume:     >  sis check –d <vol> Note: Dedupe operations for new data will not be performed while 'sis check -d' is running, expect when additional volume space is to be consumed while running this command. Free volume space equal to the size of the fingerprint database file is needed to run the sis check command. Ensure that there is sufficient free space prior to running sis check. Additionally, the -d option should always be used to clear any existing SIS checkpoints on the volume. The presence of a checkpoint will delay the results of the workaround and could also result in an out-of-space condition.     If possible, upgrade to a fixed release of Data ONTAP instead of executing the above commands/work-arounds. The FPDB's will be purged of stale records without having to run the above commands during the volume's next scheduled deduplication job. A maximum of 8 deduplication jobs can be executed at one time; subsequent jobs will be put in queue.   4.     Solution 5.      Users should upgrade to Data ONTAP release 8.1.2P4 or later. 6.      After upgrading to Data ONTAP release 8.1.2P4 or later, the first time deduplication is run on each volume it will automatically remove these stale fingerprints. During this time you may experience deduplication taking longer than expected. Subsequent operations will complete at normal operating times. This process of removing the stale fingerprints will temporarily consume additional space in both the deduplication enabled FlexVol volumes and their containing aggregates. 7.      If your FlexVol volume or the aggregate containing the FlexVol volume is 70% full or more it is recommended to run the "sis start -s /vol/<volname>" command for systems that are on 7-Mode or "volume efficiency start -vserver <vservername> -volume <volname> -scan-old-data true" command for systems that are running clustered Data ONTAP. This command will delete the existing fingerprint database and build a new one on the volumes and aggregates. This may be a long running operation; however it will not require additional space and will resolve any pre-existing issues with stale fingerprints. Deleting the deduplication metadata does not affect the savings already on disk or the access to the logical data. ************* ... View more

Thanks. yes, my intervall was also at 8 hours. I have 50,60 qtrees. Have set it to set it to 4 hours.  Should work now. ... View more

Thanks for advice. But I've seen today that the Alarms via DFM are now coming for the overused qtree quota. It was triggered late in the evening. It looks like it needs a few hours for this alarm event to notify. It took about 3-4 hours until it triggered the dfm alarm ("Qtree almost full" Event). Other "standard" DFM Eventalarms (ex. Volume Growth) doesnt show that "alarm latency" and are usually coming immediatly. But i can live with that "alarm latency" for this event for now. Best Regards + Thanks ... View more

Thanks. Helps me a lot. Question: When i create the Protection Policy (Step 6 - "Assumptions") i define schedules  for "Primary Data" Backup and "Primary data to Backup". Then again (Step 5 - "Create a Schedule") i create another scheduling at the Oncommand Level? What does that mean? Why there is another scheduling at the "oncommand" Level and what happens then...i mean we have already the scheduling at the Protection Policy which makes the Backup and then the Snapvault...? Best Regards ... View more

Thanks. Helps me a lot. Question: When i create the Protection Policy (Step 6 - "Assumptions") i define schedules  for "Primary Data" Backup and "Primary data to Backup". Then again (Step 5 - "Create a Schedule") i create another scheduling at the Oncommand Level? What does that mean? Why there is another scheduling at the "oncommand" Level and what happens then...i mean we have already the scheduling at the Protection Policy which makes the Backup and then the Snapvault...? Best Regards ... View more

Thanks. Helps me a lot. Question: When i create the Protection Policy (Step 6 - "Assumptions") i define schedules  for "Primary Data" Backup and "Primary data to Backup". Then again (Step 5 - "Create a Schedule") i create another scheduling at the Oncommand Level? What does that mean? Why there is another scheduling at the "oncommand" Level and what happens then...i mean we have already the scheduling at the Protection Policy which makes the Backup and then the Snapvault...? Best Regards ... View more