Cloud Tier Promote From Fabricpool

[proud sentinel]

Hey guys so we have a 6node a300 cluster that has a volume with 6TB of data residing in fabricpool/storagegrid. We are doing a cleanup using Varonis to identify stale data and move it to another share, back it up to AWS, and then delete it.

To avoid missing obj false alerts, we decided to promote the vol from fabricpool back to the premise performance tier.
The scanner looks like it’s about 6% done as of this morning, running from yesterday morning.

If we proceed with the archival portion to relocate the files in the vol share to the destination spot to start the archival, while the scanner is still running, is that likely to cause issues?

Mgmt wants to move onto starting the archive even though the trigger and promote back to the local tier isn’t complete yet.

[left raptor]

You can do that.

I'd recommend 1) setting tiering policy to none so new data doesn't tier out, 2) set read promotion policy to all read, 3) if you really need to move data to warm tier use vol move.

The promote scanner is extremely slow.

[proud sentinel]

Got it! Thanks. I did set the vols to none for tiring policy before I did the promote, but wasn’t aware of the on-read flag. I’ll use that for this archival move and for the vols that contain a good bit of data in storagegrid.