Issue in nbdeployutil causes valid data to be ignored when default time frame is being used

  • Article ID:100041822
  • Modified Date:
  • Product(s):

Problem

An issue has been discovered with nbdeployutil in version 8.1 when using the default time frame setting (90 days) which means valid data is being ignored and not being displayed in the report.

Error Message

none

Cause

nbdeployutil ignores client folders which contain valid data if no start date/end date is being specified

Solution

The explicit use of start date/time and end date/time prevents this issue.

Syntax to gather data
nbdeployutil --gather --start="dd/mm/yyyy hh:mm:ss" --end="dd/mm/yyyy hh:mm:ss"

Example
nbdeployutil --gather --start="11/01/2012 12:00:00" --end="27/01/2018 12:00:00"

Syntax to generate report
nbdeployutil --report --start="dd/mm/yyyy hh:mm:ss" --end="dd/mm/yyyy hh:mm:ss" --capacity <destination_folder>

Example
nbdeployutil --report --start="11/01/2012 12:00:00" --end="27/01/2018 12:00:00" --capacity /veritas/var/global/reports/20180129_145659_nbumaster


It is however important to run the "gather" switch and the "report" switch separately and not togther as shown below:

nbdeployutil --report --gather --start="dd/mm/yyyy hh:mm:ss" --end="dd/mm/yyyy hh:mm:ss" --capacity <destination_folder>

as otherwise the "report" switch reverts back to the default time frame and does not report all valid data.

 



The issue is being tracked in ET3938395 and may get addressed in a future version.

Was this content helpful?

Get Support