One global store vs one store per kind of data

[pjguyot33]

Hello team,

I am using storeOnce to backup data (Commvault) deduplication is enabled at StoreOnce side.

I created 4 stores

VMware-store
File System-store
Databases-store
NDMP-store

I configured one store per kind of data, I was thinking of optimizing the dedup.
is it the same if I create only one Store and put all kind of data on it ? It will simplify the design especially on Commvault side.

for example global-store

Thanks !

[neutral]

Dear @pjguyot33,

Thank you for reaching out to HPE Forum.

The Best performance will be obtained by configuring a larger number of Catalyst stores with multiple backup streams for each
device, although this has a trade-off with the overall deduplication ratio.

1. If servers with lots of similar data are to be backed up, a higher deduplication ratio can be achieved by backing them all up to
   the same Catalyst store, even if this means directing different media servers to the same data type device configured on the StoreOnce appliance.
2. If servers contain dissimilar data types, the best deduplication ratio/performance compromise will be achieved by grouping
   servers with similar data types together into their own dedicated Catalyst stores. For example, a requirement
   to back up a set of exchange servers, SQL database servers, file servers, and application servers would be best served by
   creating four Catalyst stores; one for each server data type.

Hope this answers your query.

Yours Sincerely,

Ashik N S

[yilmazaydin · Accepted solution]

@pjguyot33 , hello. In addition to Ashik's valuable information, I will add that it is necessary to take into account the work of the housekeeping process.

StoreOnce Housekeeping is an important process in order to maximize the deduplication efficiency of the appliance. If data is deleted from the StoreOnce system (e.g. an image is expired), any unused chunks will be marked for removal, so space can be freed up (space reclamation). The process of removing chunks of data is not an inline operation because this would significantly impact performance. This process, termed ‘housekeeping’, runs on the appliance as a background operation.

Ensure that the housekeeping process has enough time to complete by not overloading the device. For example, running backup, restore, replication, and
StoreOnce Catalyst Store operations with no break (that is, 24 hours a day) can result in housekeeping never completing.

Housekeeping works on a per store basis and each store will manage and execute its own housekeeping queue. Having multiple stores can provide more parallel processing of overall housekeeping workload. Therefore, with a high load on the StoreOnce device, the housekeeping process will work faster in a scheme with multiple stores compared to a scheme with big one.

YA

[pjguyot33]

Thank you all, that's very clear.

[Sunitha_Mod]

Hello @pjguyot33, 

That's awesome! 

We are glad to know your concern has been addressed.