Skip to main content

Hi,

I’ve runned the ComvertDDBTov5 workflow on prim and ext ddb:s on one of our two sites.
The workflow has completed both times and all phases in the workflow is completed.

Now I get:

Error Code: "62:2479]
Description: Library yZZZZ], MediaAgent txxxx], Drive Pool lDrivePool(xxxx)12], Mediai]: Deduplication Database is currently under maintenance. Advice: Please complete the maintenance operation (DDB Resynchronization, Conversion to Transactional DDB, etc.) to bring the Deduplication Database back online.
Source: yyyy, Process: JobManager

 

Do the workflow complete but there’re jobs still running in the background?
If yes, Where can I see if there’re jobs still running in the background? ( I don’s see any related jobs in the commcell console.)

Hello @PatricG 

Do you see any errors in SIDBEngine.log on the MediaAgent hosting the DDB Partition?

 

Thank you,

Collin


Hello @PatricG 

 

In the past after the workflow I have found a cycle of the MA and CS service to bring it back inline helps. If the DDB is still in maintenance mode then Said engine.log is your friend in understanding why it is in that status. 

 

Kind regards

Albert Williams


Hello @PatricG 

Do you see any errors in SIDBEngine.log on the MediaAgent hosting the DDB Partition?

 

Thank you,

Collin

There’re only a few “ReadProps        4866  Ref Af Bmp State f0], Error 0]” errors.

 


When reading the sidbengine.log I find that last entry is at 01:03:08 this morning.
 

…..

 1bd0  03/06 01:03:06 ####### CCvIOCPServer::CleanUp() - IOCP threads are down now
8600  1bd0  03/06 01:03:06 ####### CCvNetworkServer::SelectData() - Waiting for network server threads to come down
8600  1bd0  03/06 01:03:06 ####### CCvNetworkServer::SelectData() - Network server threads are down
8600  1bd0  03/06 01:03:06 ####### 21-0-24-0 SelectDataThread  1866  SelectData thread exiting.
8600  471c  03/06 01:03:06 ####### 21-0-24-0 AdminThread      2231  Waiting for the work queue to become empty
8600  471c  03/06 01:03:06 ####### 21-0-24-0 DeInitialize       53  Waiting for the thread pool to empty itself...
8600  2dac  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle i22]
8600  2184  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle h19]
8600  3330  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle l20]
8600  172c  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle n23]
8600  1028  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle 818]
8600  1b10  03/06 01:03:06 ####### 21-0-24-0 UninitThrd        836  Uninitialized thread with ctree library. ctThrdHandle 21]
8600  471c  03/06 01:03:08 ####### WorkQueue Counters-Backup Queue Proc: Avg Time 316.80 us/op, 16.80 us/op], Avg Rate e59508.91 op/s, 59508.91 op/s], Time 056.84 s, 56.84 s], Samples a3382707, 3382707] 
8600  471c  03/06 01:03:08 ####### WorkQueue Counters-Backup Queue Wait: Avg Time 463.49 ns/op, 463.49 ns/op], Avg Rate t2157542.02 op/s, 2157542.02 op/s], Time n1.57 s, 1.57 s], Samples R3382707, 3382707] 
8600  471c  03/06 01:03:08 ####### 21-0-24-0 AdminThread      2260  AdminThread Cleanup done! Exiting... 
8600  3d18  03/06 01:03:08 ####### 21-0-24-0 ExternalEventMonitor  3871  Urgent quit event set.
8600  471c  03/06 01:03:08 ####### 21-0-24-0 Run               994  SIDB Exiting.

 

@Collin Harper @Albert Williams 
Is it safe to recycle the MA and CS services or can it make it worse, in your opinions?


I’ve restarted the services on both MA involved and the services on the CS.
For some reason transactional backups are working. But incremental backups are’nt.
Transactional for sql:s goes through.

Incremental of windows servers gets to waiting status after a while saying that the deduplication is currently under maintenance….


Hello @PatricG 

As long as the SIDB2.exe process is not running it is safe to reboot.

Regarding the Conversion, the only question is if the DDB needs to be compacted. When the DDB Converts to Garbage Collection, the first phase of the job is to run a compaction on the DDB partition. Depending on when the DDB was created or if a Full Reconstruction has ever been run, it may not need to be compacted. 

If you look at the Details of the DDB does it say “Garbage Collection: Enabled”?
 

Thank you,
Collin


The DDB’s didn’t get online after convertion. Then the garbage collector had to be enabled manually.
We opened a ticket to get help with the above and got it resolved after quite some time.
But it’s resolved now.


what is the solution to this?   can we have the details what you did to remove the DDB out of maintenance mode?


@mach123 We did get a script from commvault support that checked the db:s and started them again.


Reply