Duncan Moore

And the cool thing, and I don't want to burn the whole hour on this one, but

There are some people that have rudimentary policy capabilities.

They tend to be ingest only, meaning when an object comes in, I can make a decision that says make three copies of this or make one copy of this.

Ours is doing this over the object's life automatically.

And even cooler is because we don't store the metadata with the object itself, you can go ahead and make a change to a policy two years down the road and say, listen, Dallas is my new cheapest data center.

I want my cheap and deep copies over there now.

I can change the policy.

This is where that 7 billion ILM evals a day comes in.

It'll go ahead, evaluate the metadata and go, these are the things that need to move.

Right?

And to tie that together with a 10.4 feature, we've even added an ILM simulator.

So you can say, what is going to happen if I actually change this rule?

Right?

Oh, really?

Am I going to move 15 petabytes across my most expensive network link?

That would be a bad idea, right?

That's pretty cool.

So yeah.

So now we can simulate ILM.

Yeah, we call that link cost groups.