Solved

new global deduplication database separation

  • 23 June 2021
  • 2 replies
  • 709 views

Userlevel 2
Badge +7

Hi All,

i have created some new GDSP and i notice that DDB are separate in 3 ID by type of backup (Files, Databases and VM)

i have created this commserve (CS2) in FR20.11.22, (currently the commserve is in FR20.11.55).

i have another commserve CS1 in the same version 11.20.55 but created in SP16. on this CS1 when i create a new GDSP there is only one ID for the DDB.

Why i can’t create a DDB like in the CS2 ?

How can i have the same type of DDB on all my Commserve ? 

Do they need to run a converison script ? or a patch ?

Kind regards,

Christophe

icon

Best answer by Stuart Painter 23 June 2021, 14:39

View original

2 replies

Userlevel 7
Badge +15

Hi @christophe 

Thank you for the question.

Horizontal scaling was introduced to leverage better dedupe performance by separate agents, but under a single global DDB.

This involves creating separate DDBs for the 3 agents, Files, DBs and VMs as data from the same agent dedupes more effectively with data from the same agent. Data across different agents does not dedupe as well.

Please take a look at these links to see how horizontal scaling is leveraged in SP20.

Moving Clients from a Full Deduplication Database to a New Deduplication Database

Media Management Configuration: Deduplication

You may need to move clients to a new DDB in order to achieve horizontal scaling of the DDBs.

Thanks,

Stuart

Userlevel 2
Badge +7

Hi Stuart,

it’s exactly what i’m looking for !!! many thanks.

 

Kind regards,

Christophe

Reply