Rehydrating blocks from Fabric Pool

[thorny harness]

A customer recently asked me to free up space on their StorageGRID by rehydrating specific volumes that had been configured for cloud tiering (Fabric Pool).
You might assume that switching the cloud tiering policy from "Auto" or "Snapshot Only" to "None" would automatically rehydrate the data, but there are a few extra steps required to ensure everything is retrieved properly.
The good news is there are two available options to do this, and you can choose the one that best fits your scenario.
If anyone knows of other methods, feel free to share, I'd be happy to test them and update this blog post
I’ve documented the full process while running tests in the lab, in case anyone else needs to do the same:

➡️ https://www.sysadmintutorials.com/how-to-rehydrate-cloud-tiering-data-from-netapp-fabricpool/

[final nymph]

Non-optimized (no cold tier on dest aggr) Vol move or setting read retrieval policy to promote, but vol move is much faster.

The other way is set policy to none and retrieval policy to all read, then read all blocks client side

[thorny harness]

It depends if you want the volume to remain on the same aggregate 🙂 If you do, use the retrieval policy method, if you don't mind it moving, then vol move is a great option