Solved

One or more active DDB partitions for the storage policy copy are not available for use.

  • 18 February 2022
  • 1 reply
  • 1556 views

Badge +1

Problem with DDB

One or more active DDB partitions for the storage policy copy are not available for use.

Could anyone direct me to fix this problem?

2736 664 02/18 09:26:07 ### RecvAnyMsg: Unexpected message received. Waiting [4F000019], I have [9000102], Group [0]
2736 664 02/18 09:26:07 ### SendAndRecvMsg: RecvMsg returned failure. iRet [-1]
2736 664 02/18 09:26:07 ### PruneRecords: SendAndRecvMsg failed. iRet [-1]
2736 664 02/18 09:26:07 ### 5-3 PruneZRRecInt:2551 Failed to purge [3] primary SIDB records. Error [53006] [The network module failed to send/receive data.]
2736 664 02/18 09:26:07 ### 5-3 PruneZRRec:2293 Finishing zero reference record pruning. Attempts [1], iRet [53006]
2736 664 02/18 09:26:07 ### 5-3 DedupPrnPhase3:5247 Unable to remove unreferenced primary records from SIDB. Error [53006]
2736 664 02/18 09:26:07 ### stat-ID [Avg GetDirContents], Samples [48], Time [0.095575] Sec(s), Average [0.001991] Sec/Sample
2736 664 02/18 09:26:07 ### stat-ID [Avg CanPruneVolume], Samples [48], Time [40.450848] Sec(s), Average [0.842726] Sec/Sample
2736 664 02/18 09:26:07 ### stat-ID [Grp [00] Avg PruneRecords], Samples [47], Time [45.428341] Sec(s), Average [0.966560] Sec/Sample
2736 664 02/18 09:26:07 ### stat-ID [Grp [00] Avg GetPrunableRecs], Samples [49], Time [8.276203] Sec(s), Average [0.168902] Sec/Sample
2736 664 02/18 09:26:07 ### PRNCTLR DedupPrnThrd:4565 Detaching from engine [5] [Phase 3] Thread count [7].
2736 664 02/18 09:26:07 ### PRNCTLR DedupPrnThrd:4536 Leaving because there is no more work to do. Extra pruner [true].

icon

Best answer by Laurent 21 February 2022, 11:46

View original

If you have a question or comment, please create a topic

1 reply

Userlevel 6
Badge +15

Hi Luciano,

I’m not sure that you’re having the same issue as initial post in this thread.

Can you confirm that you have a ‘DDB reconstruction job’ and it failed ? Otherwise, we’ll ask a gentle moderator to split your post to a new thread.

Well, from the short part of the logs, and few background information, it’s quite difficult to assist.

I would answer that the priority would be to contact Commvault support and ask for assistance.

If you’re not in an emergency, we can then discuss on this topic here.

First, you have to identify the DDB, and if it is partitionned or not.

So, start from the job that reported this, identifiy what is the Storage Policy and then Storage Policy copy, and from here, navigate through your console to this Storage Policy/Storage policy copy, open its details, go to the Deduplication tab, and you should know the DDB this storage policy copy is using, from the DDB Information subtab, or Advanced subtab (DSP or GDSP).

Then navigate to that deduplication engine, and check for the status of it, or if you have multiple partitions, check each partition’s status. One is reported to be offline, so there you would find that one.

Then, of course, it’s important to check that the path hosting the DDB is online from a system point of view, and available.

Try this first and let us know the results.

Good luck,

Laurent.