Migrating volumes from FAS to AFF

[Tony87]

Hi there,

We are in the middle of a data migration from FAS2650 to AFF220.

AFF220 nodes have been added to the FAS2650 cluster, so we are able to perform the data migration using volume moves.

I do notice new volumes created on the AFF filer have the following storage efficiency settings:

Schedule: -
Policy: auto
Compression: true
Inline Compression: true
Inline Dedupe: true
Data Compaction: true
Cross Volume Inline Deduplication: true
Cross Volume Background Deduplication: true

Volumes that I move from FAS -> AFF have the following settings:

Schedule: sun-sat@0
Policy: default
Compression: false
Inline Compression: false
Inline Dedupe: true
Data Compaction: true
Cross Volume Inline Deduplication: true
Cross Volume Background Deduplication: true

This means the volumes I moved from the FAS system do not have have compression enabled. What would be the best way forward here? Is it OK to enable compression on those volumes?

I think the way to go is the following but I would appreciate some guidedance or at least someone telling me this is OK to do..

1. Migrate volume FAS -> AFF using vol move

2. Change volume efficiency policy to "auto"

3. Enable compression on volume

4. Run a full volume scan using the following command: "volume efficiency start -vserver vs1 -volume VolA -scan-old-data true -all-data"

Thanks in advance!

Tony

[Mjizzini · Accepted solution]

The moved volume are not any special than a newly created one. The features are up to you to use. 

Your Action Plan looks good. just make sure to enabled deduplication on the volume if it was not already on.
Notes:
Deduplication only needs to be enabled and does not need to be running on the volume.
The compression scanner must be used to compress the existing data on the volumes present in AFF platforms.

Enabling data compression on a volume

[andris]

You also might find this KB useful:

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_maximize_storage_efficiency_post_AFF_ONTAP_9.x_migration

[Tony87]

Awesome, thanks for the replies 🙂

The KB mentions running a volume efficiency job with the compression and dedupe parameters on true.

volume efficiency start -vserver <vserver_name> -volume <vol_name>  -scan-old-data true -compression true –dedupe true

Is that still necessary if the volume efficiency config already has these parameters on true? 

My volumes looks like this now after change policy to auto, enabling compression and running volume efficiency start -vserver <vserver_name> -volume <vol_name>  -scan-old-data -scan-all

We are running Ontap 9.7

I think we're good?

xxxxxxx::> volume efficiency config -volume xxxxxxx
Vserver: xxxxxxx
Volume: xxxxxxx
Schedule: -
Policy: auto
Compression: true
Inline Compression: true
Inline Dedupe: true
Data Compaction: true
Cross Volume Inline Deduplication: true
Cross Volume Background Deduplication: true

xxxxxxx::> volume efficiency show -volume xxxxxxx -instance

Vserver Name: xxxxxxx
Volume Name: xxxxxxx
Volume Path: /vol/xxxxxxx
State: Enabled
Status: Idle
Progress: Idle for 10:58:23
Type: Regular
Schedule: -
Efficiency Policy Name: auto
Blocks Skipped Sharing: 0
Last Operation State: Success
Last Success Operation Begin: Tue Dec 08 10:17:05 2020
Last Success Operation End: Tue Dec 08 23:40:13 2020
Last Operation Begin: Tue Dec 08 10:17:05 2020
Last Operation End: Tue Dec 08 23:40:13 2020
Last Operation Size: 720.8GB
Last Operation Error: -
Changelog Usage: 9%
Logical Data Size: 882.3GB
Logical Data Limit: 640TB
Logical Data Percent: 0%
Queued Job: -
Stale Fingerprint Percentage: 0
Compression: true
Inline Compression: true
Constituent Volume: false
Inline Dedupe: true
Data Compaction: true
Cross Volume Inline Deduplication: true
Cross Volume Background Deduplication: true
Extended Compressed Data: true

xxxxxxx::> df -S xxxxxxx
Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed Vserver
/vol/xxxxxxx/
901954112 392520128 30% 384946240 30% 7573888 1% xxxxxxx