If you have a bucket on SGWS and you have a ILM policy to say keep 1 month on the GRID and then archive out to S3.. What is the process to rehyrdrate the bucket ?
#Archiving to S3
latent hatch
surreal birch
Hey Greg, apologies no one has jumped on this one. Let me do some digging and see if I can get you an answer. One observation here is that our documentation does do a good job of explaining how to tier to a cloud storage pool, using ILM rules/policies but not how to bring it all back 😄
surreal birch
Hey @latent hatch so whilst this is not well documented (I've given that feedback to our docs team), essentially you would update your ILM policy. You would be updating your ILM policy to remove the ILM rule that is moving data to the cloud storage pool and at the same time, add a new rule that would move the data back.
Once there is no data in the cloud storage pool, you can then again, update the ILM policy to remove the rule that was design to move the data back. From there you would be free to remove the cloud storage pool if you wanted too (as long as no ILM rules are referencing it).
Of course keep in mind there may be costs from your cloud provider for the actions of moving the data back into your local storage grid.
latent hatch
hey Ross, So i found out the customer has configured an Archive Node which they are using as Cloud Storage Pools were not available at the time. I assume everything in the AWS S3 bucket which has been archived will need to be bought back into the grid via the Archive node?
surreal birch
Similar concept really, ILM rules ultimate dictate what data is sent where, so if they have data that was archived via the Archive Node, then they can use ILM rule changes to move things else where (like back into the grid) back via the Archive node.
surreal birch
I have also got some additional info for you from an Archive Gateway perspective.
If you want to move the data that was archived via Archive Gateway then the general process is as follows.
Change ILM to place those objects in a different Storage Pool, and then wait for ILM to bring back all the objects from the Archive Node and then disable the TSM (if applicable) connection through the old Grid Topology view. You can watch using the Nodes tabs to look at the Archive Node and see the number of objects on it start dropping as ILM works through it.
Unfortunately, just as a reminder, there is no way to decommission an Archive Node from a grid. It just has to hang around for now. Known issue that our StorageGrid development team are aware of.
latent hatch
Awesome thanks @surreal birch that’s super handy information!