Symantec NetBackup status code 2026 to status code 2030

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 2026 to Status Code 2030 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2026
Message: Allocation status request delete failed
Explanation: The NetBackup mds component was unable to modify an allocation
status record for this job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
¦ The mds unified logging files (OID 143) from the master server at debug level 2.
¦ The nbrb unified logging files (OID 118) from the master server at debug level 3.

NetBackup status code: 2027
Message: Media server is not active
Explanation: This job requires a media server that is not currently available.
Recommended Action:
Do one or more of the following:
¦ Verify that the media server that is required for this allocation is running.
¦ If this is a tape job, verify that ltid is running on the media server. If a media
server has gone offline and returned online, a delay of several minutes may
occur before a job can use that media server.
¦ Use the vmoprcmd command to show the state of the media server. If the job
is trying to access a disk storage unit, verify that the nbrmms process is running
on the media server. If the job is trying to access a tape storage unit, verify
that ltid is running on the media server.

NetBackup status code: 2028
Message: Media is reserved
Explanation: The NetBackup mds component cannot allocate media because
another job has that media exclusively reserved.
Recommended Action: If multiple duplication jobs are attempting to use the
same tape media for read, each reserves the media. NetBackup should allow more
than one job to get a reservation for the tape media.
This error is internal. Check the following logs to help identify the problem:
¦ The mds unified logging files (OID 143) from the master server at debug level 2.
¦ The nbrb unified logging files (OID 118) from the master server at debug level 3.

NetBackup status code: 2029
Message: EMM database is inconsistent
Explanation: Aninconsistency in the NetBackup database is preventing allocations
for this job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
¦ The mds unified logging files (OID 143) from the master server at debug level
2.
¦ The nbrb unified logging files (OID 118) from the master server at debug level
3.
Run the nbrbutil -resetall command to get the NetBackup allocation database
back into a consistent state. Note that this command cancels all jobs including
those that are currently running.

NetBackup status code: 2030
Message: Insufficient disk space or high water mark would be exceeded
Explanation: Insufficient disk space is available to run this job.
Recommended Action: Try the following possible solutions:
¡ If there are images on the disk that can be expired, expire them, and run
nbdelete to delete the images from disk.
¡ It may be that NetBackup is creating disk images more quickly than they are
expiring. If so, modifications to policies may be necessary to change the rate
of image creation/expiration for the disk.
¡ It may be helpful to lower the high water mark and/or low water mark for the
disk group.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *