BUG REPORT: In NetBackup 6.5.x, resource allocations are not being released after duplications.

Problem

BUG REPORT: In NetBackup 6.5.x, resource allocations are not being released after duplications.

Error Message

[No context] [EMMProvider::doSetUnmounting] setUnmounting returns 4000002
[No context] [isCriticalMDS] MDS returned a critical error 4000002

[Debug] NB 51216 mds 143 PID:4704 TID:36 File ID:111 [No context] 1 [is_mds_rb_env_consistent] job_type mismatch, jobType = 1, job_type = 9

Solution

Bug: 1287859

Details:   If an allocated drive used by a backup job is followed by a duplication job, the resource will not be released after the duplication job completes.  

For example:  A backup job is using the drive. The job type associated with the drive resource is 1 (backup). The job completes and a duplication job is granted the resource . If NetBackup uses the same drive resource for the duplication writer (job type = 9). The NetBackup process mds has the new job type (9), but nbrb has the old one (1). Because nbrb is not persisting the new one, calls to deallocate fail with 4000002 and the resource never gets deallocated.  This may be seen in the log file examples below.

Log Files:
The nbrb log file (originator ID 118) will show:
05/30/08 07:20:05.865 PID:4707 TID:10 [No context] [EMMProvider::doSetUnmounting] setUnmounting returns 4000002
05/30/08 07:20:05.865 PID:4707 TID:10 [No context] [isCriticalMDS] MDS returned a critical error 4000002
05/30/08 07:20:05.865 PID:4707 TID:10 [No context] [DriveOperationProvider::cleanup] setEMMDriveUnloadStarting returns 4000002
05/30/08 07:22:01.143 PID:4707 TID:10 [No context] [EMMProvider::doSetUnmounting] setUnmounting returns 4000002
05/30/08 07:22:01.143 PID:4707 TID:10 [No context] [isCriticalMDS] MDS returned a critical error 4000002
05/30/08 07:22:01.143 PID:4707 TID:10 [No context] [DriveOperationProvider::cleanup] setEMMDriveUnloadStarting returns 4000002

The nbemm log file (originator ID 111) will show:
5/30/08 07:20:05.861 [Debug] NB 51216 mds 143 PID:4704 TID:6 File ID:111 [No context] 1 [is_mds_rb_env_consistent] job_type mismatch, jobType = 1, job_type = 9
05/30/08 07:22:01.139 [Debug] NB 51216 mds 143 PID:4704 TID:36 File ID:111 [No context] 1 [is_mds_rb_env_consistent] job_type mismatch, jobType = 1, job_type = 9

Workaround:
To release allocations:
1. Immediately prior to shutdown of the NetBackup processes run:
# /usr/openv/netbackup/bin/admincmd/nbrbutil -resetAll

2. Recycle the NetBackup processes:
# /usr/openv/netbackup/bin/goodies/netbackup stop

# /usr/openv/netbackup/bin/goodies/netbackup start

Please apply the appropriate release update to resolve this issue.

ETA of Fix:
The formal resolution to this issue (Etrack 1287859) is included in the following patch release:
  • NetBackup 6.5 Release Update 3 (6.5.3)
This release is available at the support web site at:
 http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)