There are options on aggregate and volume levels. Compaction is enabled by default on aggregate and volume level for AFF. But in FAS you should enable it for aggregate. And after that all new volumes with space guarantee none will have compaction enabled. Here is more information from "Logical Storage Management Guide":
You can control inline data compaction on FAS systems with Flash Pool (hybrid) or HDD aggregates at the volume or aggregate level using the wafl compaction enable node shell command. Data compaction is disabled by default for FAS systems.
About this task
If you enable data compaction at the aggregate level, any new volume created with a volume space guarantee of none in the aggregate has data compaction enabled. Existing volumes are not enabled. Enabling data compaction on a volume on an HDD aggregate uses additional CPU resources.
Steps
1.
Change to the advanced privilege level: set -privilege advanced 2.
Check the data compaction state of volumes and aggregates for the desired node: node run –node node_name –command wafl compaction status -all 3.
Enable data compaction on the aggregate or volume. -
For aggregates:
node run –node node_name –command wafl compaction enable –A aggregate_name
-
For volumes:
node run –node node_name –command wafl compaction enable volume_name 4.
View the compaction statistics:
node run –node node_name –command wafl compaction stats
On Mon, Sep 26, 2016 at 11:24 PM, Tim McCarthy tmacmd@gmail.com wrote:
Have to disagree. I pulled up an ONTAP 9 simulator and did this exact test.
My source was a non compacted volume. Destination was non compacted. Result obviously is not compacted
There is an aggregate setting which makes all volumes created on that aggregate compacted. Set that on. I reran the mirror to that aggregate and the result was compared with a non compacted source.
For kicks I tried a version flexible mirror. It will not work to the aggregate with the compaction flag enabled.
Makes sense since only DP mirrors support compaction
Get Outlook for iOS https://aka.ms/o0ukef
On Mon, Sep 26, 2016 at 1:15 PM -0700, "Francis Kim" fkim@berkcom.com wrote:
Compaction setting is done at the volume, and not the aggregate level.
Francis Kim Cell: 415-606-2525 Direct: 510-644-1599 x334 fkim@berkcom.com www.berkcom.com
On Sep 26, 2016, at 12:29 PM, Tim McCarthy tmacmd@gmail.com wrote:
For the snap mirror to trigger compaction, the aggregate must have compaction enabled. Otherwise, it is just a SnapMirror transfer
Get Outlook for iOS https://aka.ms/o0ukef
On Mon, Sep 26, 2016 at 11:04 AM -0700, "Steiner, Jeffrey" < Jeffrey.Steiner@netapp.com> wrote:
Okay, I heard back. Engineering says that snapmirror and vol-move should
BOTH trigger compaction. If you didn't see savings, perhaps something about thin provisioning was not configured. The savings could have been there, they just weren't visible if the volume settings weren't correct.
*From:* Steiner, Jeffrey *Sent:* Friday, September 23, 2016 8:29 AM *To:* 'jordan slingerland' jordan.slingerland@gmail.com; NGC-fkim-berkcom.com http://ngc-fkim-berkcom.com/ fkim@berkcom.com *Cc:* toasters@teaparty.net *Subject:* RE: AFF and 4:1 guaranteed efficiency
I would guess that snapmirror is currently looking at the physical blocks on disk, whereas a vol-move is a step up the chain and it can look at block that are actually a block within a block.
I'll check with engineering and report back...
*From:* jordan slingerland [mailto:jordan.slingerland@gmail.com jordan.slingerland@gmail.com] *Sent:* Friday, September 23, 2016 10:26 AM *To:* NGC-fkim-berkcom.com http://ngc-fkim-berkcom.com/ <fkim @berkcom.com> *Cc:* Steiner, Jeffrey Jeffrey.Steiner@netapp.com; toasters@teaparty.net *Subject:* Re: AFF and 4:1 guaranteed efficiency
My understanding is that both are block based operations so it makes sense to me that the blocks would be put down on disk unchanged. Perhaps it has something to do with the fact that you may want to reverse the snapmirror back to the system that presumably does not have compaction enabled or support the feature, so the blocks are left uncompacted? If the vol move is within the same controller AFF the lack of backward compatibility is not a concern. Just a though, I don't know.
On Fri, Sep 23, 2016 at 10:57 AM, Francis Kim fkim@berkcom.com wrote:
Strange how compaction appears to work with vol move but not with snap mirror.
.
On Sep 23, 2016, at 4:39 AM, Steiner, Jeffrey < Jeffrey.Steiner@netapp.com> wrote:
A vol-move operation will cause compaction to happen. I know it's not ideal but at least its internal. Obviously a scanner is preferred but functionally it would be a lot like a vol move.
Likewise if you use FLI to import a LUN that will trigger all the efficiency features during the import.
Sent from my mobile phone.
On 23 Sep 2016, at 02:10, Jeffrey Mohler jmohler@yahoo-inc.com wrote:
Compaction in our testing can be good, really good...an additional 20% in many of our test data sets on top of everything else. (SSET diagnosis)
However, there are limitations on how you get data into AFF to get compaction...IE, you cant snapmirror it. It must transfer, as far as we're told today, via a host/file based migration. Be thinking bout this when you consider an AFF migration. It must be done outside on ONTAP.
We have pushed to get this fixed via a scanner/etc that reads and relays out the file based structure.
Jeff Mohler jmohler@yahoo-inc.com Tech Yahoo, Storage Architect, Principal (831)454-6712 YPAC Gold Member Twitter: @PrincipalYahoo CorpIM: Hipchat & Iris
On Friday, September 23, 2016 1:53 AM, Mike Gossett cmgossett@gmail.com wrote:
my sales guy basically said the guarantee works as follows - they don't hit the 4:1 target, they buy you whatever amount of shelf\ssd required to makeup shortfall.
The magic has to do with what they call "compaction" - writes <4KB (down to 512B/ea) are "compacted" into a single 4K block... this apparently adds to the std dedupe and compression they use.
On Thu, Sep 22, 2016 at 1:32 PM, jordan slingerland < jordan.slingerland@gmail.com> wrote:
Sales guys are promising me 4:1 dedup ratios on an AFF with ontap9. They say they grantee it. I have specifically asked what stipulation. In a VDI environment with linked clones, etc. Sales guy tells me none and even specifically says they can dedup compressed video or audio (mp3) 4:1.
I have A LOT of trouble believing that. So, 4:1 dedup guaranteed or what?
Any comments welcome. --Jordan
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/ mailman/listinfo/toasters http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters