After Disaster Recovery, NetBackup jobID values are reset. This can cause irregularities in reporting in NOM, VBR and OpsCenter if "duplicate" job IDs are encountered.

Problem

Who is affected?

This issue may be experienced when all conditions below are TRUE:

• NetBackup Operations Manager (NOM), Backup Reporter (VBR) or OpsCenter is used to report on a NetBackup 6.5.x or 7.x master server
• A NetBackup catalog restore has been performed on this master server as part of a disaster recovery

What is the problem?

A single jobID stored in the database may point to more than one client's backup details.

Job uniqueness in VBR is a combination of the following factors – MasterServerName + JobID#

Job uniqueness in OpsCenter is a combination of the following factors – MasterServerName + ClientName + JobID#

If a jobID already known to VBR is captured from NetBackup, these jobIDs are NOT inserted into the VBR database; however, the relevant image information is inserted into the database. Querying the Job data in VBR for a certain jobID range would show the OLDER job information and would not sync up with recent information shown in the Activity Monitor for the same jobIDs.

If a jobID already known to NOM or OpsCenter is captured from NetBackup, these jobIDs UPDATE the existing information in the OpsCenter database; however, the old image information is persistent. Querying the Job data in OpsCenter for a certain jobID range would show the NEWER job information as shown in the Activity Monitor, as the OLDER data was lost when updated.

Solution

In a future release of NetBackup, job id information will be persistent and retained; jobid will not be reset after a disaster recovery.

Workaround

To avoid this issue, edit the value in the jobid file to a value larger than the last known "good" job ID prior to the disaster recovery.  This would resolve the issue going forward.

On Windows, the jobid file can be found in the following folder: <install_path>\NetBackup\db\jobs

On UNIX and Linux, the jobid file can be found in the /usr/openv/netbackup/db/jobs directory.

The NetBackup Database Manager service (at a minimum) needs to be stopped when making this change to ensure that new jobs will use the edited jobid file.