garbage with data integrity check

[PetrHanz]

Hi,

NBU 7.6 remove crcollect and uses clean of garbage through data integrity check (enable/disable in contentrouter or spa). I am lookup for information about process of the data integrity planning and schedulling. 

Manually start data integrity check ?

Sheduling data integrity check   ?

When is the DICH started ?

How long time these deleted images (bpexpdate + nbdelete) will remain in MSDP as garbage images, by default ? 

Many thanks, Petr

[Marianne]

Have you tried the NetBackup Deduplication Guide  ?

I was curious reading your questions and searched the manual.

Found lots of interesting facts in Chapter 8:

Under About MSDP queue processing : 
... By default, queue processing occurs every 12 hours, 20 minutes past the hour.
Primarily, the transaction queue contains clean-up and integrity checking
transactions. ....

About MSDP data integrity checking
... NetBackup performs some of the integrity checking when the storage server is idle.
Other integrity checking is designed to use few storage server resources so as not to
interfere with operations.

About the MSDP data removal process
...
...
If you manually delete an image that has expired within the previous 24 hours, the
data becomes garbage. It remains on disk until removed by the next garbage
collection process. Garbage collection occurs during data integrity checking.

[PetrHanz]

Hello Marianne,

many thanks, I found these information at the manual.

So, how I can resolve free space in MSDP dedupe pool if  I cannot call manually garbage process ? I need do it now. I checked this at me lab but all *.bin files remains at puredisk pool and sched_queueprocess show me activity on 12:20.  NBU 7.6.0.2

In prevous version 7.5 crcollect with crcontrol resolve me problem.

[Marianne · Accepted solution]

Seems crcontrol is still there.

See p. 216:

Processing the MSDP transaction queue manually
Usually, you should not need to run the deduplication database transaction queue
processes manually. However, you can do so.
See “About MSDP queue processing” on page 216.
 

Steps are listed on p.217:

To process the MSDP transaction queue manually
1 On the MSDP storage server, run the following command:
  UNIX: /usr/openv/pdde/pdcr/bin/crcontrol --processqueue
  Windows: install_path\Veritas\pdde\Crcontrol.exe --processqueue

2 To determine if the queue processing is still active, run the following command:
  UNIX: /usr/openv/pdde/pdcr/bin/crcontrol --processqueueinfo
  Windows: install_path\Veritas\pdde\Crcontrol.exe --processqueueinfo
  If the output shows Busy : yes, the queue is still active.

3 To examine the results, run the following command (number 1 not lowercase letter l):
  UNIX: /usr/openv/pdde/pdcr/bin/crcontrol --dsstat 1
  Windows: install_path\Veritas\pdde\Crcontrol.exe --dsstat 1
  The command may run for a long time; if you omit the 1, results return more
  quickly but they are not as accurate.

[PetrHanz]

Hello Marianne

Many thanks. Ok, I will check it ... the problem could be out of MSDP and I will debug the problem.

Once again, many thanks for your quick response.