What is the actual difference between micro pruning and macro pruning in reference to DDB and data aging ?
In which scenario micro vs macro pruning is enabled and where i can check it in console or command center?
What is the actual difference between micro pruning and macro pruning in reference to DDB and data aging ?
In which scenario micro vs macro pruning is enabled and where i can check it in console or command center?
Best answer by Scott Moseman
Hardware WORM which is on the Storage Side.
How does micro pruning will work on Hardware WORM since the data is immutable ?
What would happen to DDB which is non immutable target storage ?
What would be the impact on capacity ? Do i need more storage capacity to store dedupe data in hardware worm as compared to non- worm hardware ? if yes Why and by how much ?
I suggest a call with your account team to deep dive.
However, in a nutshell...
When using hardware WORM (immutability) you can expect to use 3x your retention. You cannot micro prune, and since you must macro prune you need to seal the DDB occasionally. You will end up sealing the DDB at your retention period, and you will always need to have (2) DDB stores worth of data under WORM (immutable) protection. Not until the 3rd DDB store is sealed can you macro prune the 1st DDB store, thus why the space requirement of up to 3x your retention.
Note: With our HyperScale X and Metallic Recovery Reserve (aka MCSS) offerings we’re able to keep this space requirement down to 1x. This is because we control the complete data stack so there’s no hardware WORM required.
Thanks,
Scott
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.