Processing the MSDP transaction queue manually
NetBackup maintains a queue for MSDP database transactions.
Usually, you should not need to run the deduplication database transaction queue processes manually. However, when you recover the MSDP catalog from a backup, you must process the MSDP transaction queue. Processing the transaction queue is part of a larger process.
By default, MSDP processs all Local and Cloud LSU database transaction queue. However, you can run queue processes by cloud LSU or local LSU individually by providing a cloud LSU dsid value. Use /usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu to get cloud LSU dsid value. If given disd value is "0", local LSU is processed.
To process the MSDP transaction queue manually
- On the MSDP storage server, run the following command:
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --processqueue --dsid <dsid>Windows:
install_path\Veritas\pdde\Crcontrol.exe --processqueue --dsid <dsid>--dsid is the optional parameter. Without disd value, all local and cloud LSU process the MSDP transaction queue.
- To determine if the queue processing is still active, run the following command:
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --processqueueinfo --dsid <dsid>Windows:
install_path\Veritas\pdde\Crcontrol.exe --processqueueinfo --dsid <dsid>If the output shows Busy : yes, the queue is still active.
--dsid is optional parameter. Without disd value, if any of local or cloud LSU is active, the command output is busy.
- To examine the results, run the following command (number 1 not lowercase letter l):
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat 1Windows:
install_path\Veritas\pdde\Crcontrol.exe --dsstat 1The command may run for a long time; if you omit the 1, results return more quickly but they are not as accurate.
More Information