Skip to main content
Question

DDB file location for secondary copy on Cloud storage


Forum|alt.badge.img+7

Hello,

I want to setup secondary copy to cloud.

Primary copy is using local disk library and DDB with single partition with path X:\DDB
When I will create storage pool for cloud storage, should I create (or not) separate folder on disk X:\ for new pool DDB partition? For example X:\CloudDDB

There is recommendation from documentation that sounds strange for me: “When you create more than one storage pool using the same MediaAgent and DDB disk, make sure to specify the same DDB path. Do not create separate subfolders on the DDB disk for each storage pool.”
https://documentation.commvault.com/11.24/expert/12411_deduplication_building_block_guide.html

Maybe there is mistake? Two different DDBs pointing to same disk path?

Thanks.

4 replies

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • April 13, 2023

Hi @AndresL 

Not really sure how this statement in documentation is intended, but for every storage pool combined with it's own DDB I always use separate folders.

It is a separate engine/partition so I would say no thanks to any situation where DDB files will mixed together.

Side note: not sure what the current Q&I times are on your DDB, but by adding another DDB to the same disk please do keep an eye on the performance of the DDB and move a DDB to a dedicated disk if necessary.


Hyder
Vaulter
Forum|alt.badge.img+8
  • Vaulter
  • 86 replies
  • April 13, 2023

@AndresL that does sound a little unclear, I’ve submitted a request to check on the verbiage used

But go with what Jos said, that makes more sense, don’t mix it up in the same folder

I’ll let you know if I find something different


Forum|alt.badge.img+7
  • Author
  • Byte
  • 39 replies
  • August 19, 2024

Hello guys,

Want to resume this conversation. I do planning of new media agent setup, and found that newer “Deduplication Building Block Guide” (https://documentation.commvault.com/2023e/expert/deduplication_building_block_guide.html) says:

“You must use one deduplication database (DDB) path only for all the storage pools that are associated with the MediaAgent. The DDB path can be a drive or a folder in a drive on the MediaAgent computer. For example, if you used D:DDB as the DDB path for a storage pool that you created first for the MediaAgent, then you must use the same folder D:DDB as the DDB path for the next storage pools that you create.”

I read this like: Use single folder for all DDBs on media agent. Who knows maybe it works:)

Could you share please your experience, how you organize space for DDBs.

For example you have two huge physical SSD disks in hardware RAID1 array. Do you split this on multiple volumes/partitions, each per single DDB or you create single big volume and use separate folders? Or maybe single folder like mentioned in KB above?

Br,
Andrejs
 


Forum|alt.badge.img+7
  • Author
  • Byte
  • 39 replies
  • August 20, 2024
Jos Meijer wrote:

Hi @AndresL 

Not really sure how this statement in documentation is intended, but for every storage pool combined with it's own DDB I always use separate folders.

It is a separate engine/partition so I would say no thanks to any situation where DDB files will mixed together.

Side note: not sure what the current Q&I times are on your DDB, but by adding another DDB to the same disk please do keep an eye on the performance of the DDB and move a DDB to a dedicated disk if necessary.

Hello @Jos Meijer ,
You wrote “... for every storage pool combined with it's own DDB I always use separate folders.” 
Do you have in production multiple storage pools with respective multiple DDBs on single NTFS volume? If yes what is your experience, maybe problems? How big media agent is, i mean total single media agent DDBs and Library's size?

Br,
Andrejs


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings