Solved

Micro vs Macro Pruning

  • 7 June 2022
  • 8 replies
  • 1890 views

Userlevel 3
Badge +11

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? 

icon

Best answer by Scott Moseman 8 June 2022, 18:41

View original

8 replies

Userlevel 7
Badge +23

@Mohit Chordia , here’s a breakdown:

Micorpruning is when individual blocks are deleted when no jobs in the deduplication store refer to them for their backups.  This is the normal pruning for dedupe.

Macropruning is when the entire store contains no unaged jobs, so all of the blocks in that store prune off all at once.  This normally occurs when a store is corrupt, and we lack access to the DDB itself.  Therefore, we prune nothing until ALL jobs in the store have aged logically.

Let me know if that clarifies!

Userlevel 3
Badge +11

@Mike Struening 

Thank you for the reply.

If we are using immutable storage for backups  , what type of Pruning will happen and what would be the impact on capacity usage due to this  ?

Will Micro Pruning work on Immutable target Storage ? 

Regards, Mohit

Userlevel 7
Badge +23

Is the WORM option on the CV side or the storage side?

On the CV side, those jobs can’t be pruned until their aged date (so micro/macro isn’t involved yet because nothing is aging).

Userlevel 3
Badge +11

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 ?

Userlevel 2
Badge +6

Hello @Mohit Chordia,

 

This will depend on what kind of WORM hardware you are using.  Is this Disk or Cloud WORM copies?  Are you using the CommVault WORM settings, or only the hardware immutability tools?

 

As a general rule, we can only Macro-Prune from WORM storage, and the Macro-Prune will only occur after the DDB is sealed and all data has met retention.  However depending on the type of WORM storage you are using, the Macro-Prune may be logical only with the storage performing the physical pruning.

Userlevel 6
Badge +18

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
 

Userlevel 3
Badge +11

@Scott Moseman 

Macro Pruning will happen automatically after the 3rd DDB is sealed or we need to do it manually .

Userlevel 6
Badge +18

@Scott Moseman

Macro Pruning will happen automatically after the 3rd DDB is sealed or we need to do it manually .


Macro Pruning happens automatically when Data Aging runs.

Configuring Micro Pruning
https://documentation.commvault.com/11.24/expert/9183_configuring_micro_pruning.html

You will want to disable Micro Pruning Support on the Cloud Storage.

Thanks,
Scott

Reply