Symantec NetBackup status code 2046 to status code 2050

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 2046 to Status Code 2050 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2046
Message: Media is unmountable
Explanation: Media has been marked as unusable due to mount errors.
RecommendedAction: Clean the drives in the media’s robot. Determine whether
any of the media is bad.

NetBackup status code: 2047
Message: Media is write protected
Explanation: The media cannot be used for a write job because it is write protected.
Recommended Action: Make sure that media in the scratch pool is not write
protected.

NetBackup status code: 2048
Message: Media is in use by the ACS robotic library
Explanation: ACS media that is required by this job is in use on another system.
RecommendedAction: Make sure that the required media is not in use by another
application.

NetBackup status code: 2049
Message: Media not found in the ACS robotic library
Explanation: Media that is needed by this job is in not found in the ACS robotic
library.
RecommendedAction: Make sure that the required media is available in the ACS
robot.
For more information, refer to the section on configuring ACSLS robots in the
NetBackup Device Configuration Guide.

NetBackup status code: 2050
Message: ACS media has an unreadable external label
Explanation: This job needs ACS media that cannot be used because its external
label or barcode is unreadable.
Recommended Action: Correct the barcode label problem for this media.
For more information, refer to the section on configuring ACSLS robots in the
NetBackup Device Configuration Guide.

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.

 

Symantec NetBackup status code 2041 to status code 2045

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 2041 to Status Code 2045 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2041
Message: Storage unit is down
Explanation: A disk storage unit has been designated as down and cannot be
used.
Recommended Action: Run the bperror -disk command to indicate why the
disk is considered down.

NetBackup status code: 2042
Message: Density mismatch detected
Explanation: This error is an internal NetBackup error.Ajob has requested media
with the wrong density. A mismatch may exist between the image catalog and the
media database.
RecommendedAction: Restore the jobs request tape media by media ID density.
If the requested density does not match the configured density for the media, it
cannot be allocated.

NetBackup status code: 2043
Message: Requested slot is empty
Explanation: Media is not found in the expected slot in the robot.
Recommended Action: The robot may need to be inventoried.

NetBackup status code: 2044
Message: Media is assigned to another application
Explanation: Requested media cannot be allocated because it is assigned to an
application other than NetBackup.
Recommended Action: Verify that media that is required for the job is assigned
to NetBackup.

NetBackup status code: 2045
Message: Storage unit is disabled since max job count is less than 1
Explanation: Storage unit cannot be used because its maximum job count is set
to 0.
RecommendedAction: Increase themaximumjob count (ormaximumconcurrent
drive count) to a value greater than 0.

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.

 

Symantec NetBackup status code 2036 to status code 2040

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 2036 to Status Code 2040 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2036
Message: Drive is in a robotic library that is up
Explanation: Operator has attempted to assign a pending tape mount request to
a drive that is in a robot that is up.
Recommended Action: A request for non-robotic media may have caused a
pending request in the device monitor, and the operator has assigned the request
to a drive that is not a standalone drive. This error is not fatal. The request will
pend again in the NetBackup device monitor. Assign the pending mount to a
standalone drive or to a drive that is in AVR mode (non-robotic).

NetBackup status code: 2037
Message: Drive is not ready
Explanation: The required tape is in a drive, but the drive is not in a ready state.
Recommended Action: This error may occur when a request for non-robotic
media had caused a pending request in the device monitor, and the operator has
assigned the request to a drive that is not in a ready state. This is not a fatal error.
The request will pend again in the NetBackup device monitor. Verify that required
tape is in the drive it is being assigned to, and that the drive ready light has come
on. It may take some time for the drive to become ready after the tape has been
inserted. If the drive never goes to a ready state after a tape has been inserted,
there may be a problem with the drive.

NetBackup status code: 2038
Message: Media loaded in drive is not write-enabled
Explanation: This error may occur when a storage unit request for non-robotic
media had caused a pending request in the device monitor, and the operator has
inserted media that is not write enabled into the drive.
Recommended Action: This is not a fatal error. The request will pend again in
the NetBackup device monitor. If you are sure that it is OK to write on this tape,
verify that the required tape has its write enable switch set to allow write.

NetBackup status code: 2039
Message: SCSI reservation conflict detected
Explanation: The NetBackup bptm component was unable to read or write a tape
drive because another job unexpectedly holds a SCSI reservation for the drive.
Recommended Action: This error should never occur at job resource allocation
time, but may occur during i/o for a tape job. The verbose bptm logs on the media
server may be useful in understanding the problem.

NetBackup status code: 2040
Message: Maximum job count has been reached for the storage unit
Explanation: Storage cannot be allocated because it would exceed maximum job
count. The maximum job count is configurable for each storage unit. Multiple
copy jobs may cause this same error, if more copies are targeted for a storage unit
than the storage unit is configured for.
Recommended Action: Target a different storage unit with one of the copies, or
increase the maximum job count for the storage unit.

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.

 

Symantec NetBackup status code 2031 to status code 2035

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 2031 to Status Code 2035 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2031
Message: Media is not defined in EMM
Explanation: The media that is required for this job is not defined in the EMM
database.
RecommendedAction: Amedia volume that is required for a restore job has been
deleted from the EMM database. If the media is available, use bpimport to import
it.

NetBackup status code: 2032
Message: Media is in use according to EMM
Explanation: The NetBackup database indicates that the media is in use but is
not allocated to another 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: 2033
Message: Media has been misplaced
Explanation: Job requires media that is not in the expected robotic slot.
Recommended Action: Verify that the media that is required by the job is in the
proper robotic slot as shown by vmquery.
If the error persists, the following logsmaybe useful in understanding 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.
¦ The verbose bptm logs on the media server(s) that access this media.

NetBackup status code: 2034
Message: Retry the allocation request later
Explanation: Resources that are required for a job are currently in use.
Recommended Action: This error should never appear as a job return status. In
the mds and nbrb vxul logs, it indicates that a job should queue because resources
are busy.

NetBackup status code: 2035
Message: Request needs to pend
Explanation: A job requires operator intervention before it can continue.
Recommended Action: This error should never appear as a job return status. In
the mds and nbrb vxul logs, it indicates that a job should post a request for
operator intervention to the NetBackup device monitor.

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.

 

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.

 

Symantec NetBackup status code 2021 to status code 2025

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 2021 to Status Code 2025 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2021
Message: Allocation record insert failed
Explanation: The NetBackup mds component was unable to update the database
for a device allocation.
Recommended Action: This error is internal. Check the following logs:
¦ 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: 2022
Message: Allocation status record insert failed
Explanation: The NetBackup mds component was unable to update the database
with device allocation status information.
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: 2023
Message: Allocation identifier is not known to EMM
Explanation: The NetBackup mds component cannot find the device allocation
record that is needed to allocate the device 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: 2024
Message: Allocation request update failed
Explanation: The NetBackup mds component was unable to update the database
for a device allocation.
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: 2025
Message: Allocation request delete failed
Explanation: The NetBackup mds component was unable to delete a device
allocation from the database.
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.

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.

 

Symantec NetBackup status code 2016 to status code 2020

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 2016 to Status Code 2020 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2016
Message: Media is assigned to another server
Explanation: Ajob cannot use the media on the storage server, because the media
is assigned to another storage server.
Recommended Action: Check the following logs:
¦ 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: 2017
Message: Media needs to be unmounted from a drive
Explanation: The requested media needs to be unmounted from the drive it is in
before it can be used for another job.
RecommendedAction: Identify the media that is requested by the job that returns
this error. If it is used by another job, wait for that job to complete.

NetBackup status code: 2018
Message: Number of cleanings is invalid
Explanation: A cleaning media has an invalid number of cleanings that remain.
RecommendedAction: On the ChangeMedia screen, set the number of cleanings
remaining for the cleaning media to a number greater than or equal to zero (0).

NetBackup status code: 2019
Message: Media is in a drive that is not configured on local system
Explanation: A job is configured to use a media volume that has no drive path
configured to an eligible media server for the job. A media volume is misplaced
or all drive paths are down for the media server accessible by the storage unit
that is configured for a job.
Recommended Action: If drive paths are down, identify the media server that is
configured for use by the storage unit, and bring up the drive path to that media
server.

NetBackup status code: 2020
Message: Robotic library is down on server
Explanation: NetBackup has marked the robot as down for the required media
server.
Recommended Action: Verify that the media server that is required for this
allocation is running, and verify that ltid is up on that media server.

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.

 

Symantec NetBackup status code 2011 to status code 2015

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 2011 to Status Code 2015 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2011
Message: The media server reported a system error.
Explanation: An allocation for the media server is in an inconsistent state.
RecommendedAction: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
¦ 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: 2012
Message: Media has conflicts in EMM
Explanation: Requested media for job cannot be used because it is marked as
having conflicts in the nbemm database.
Recommended Action: The media is marked as having conflicts. The upgrade
from NetBackup 5.x has found multiple volume databases where two tapes in
different volume databases have the same media ID. Call technical support to
resolve this situation.

NetBackup status code: 2013
Message: Error record insert failed
Explanation: A database record insert has failed.
RecommendedAction: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
¦ 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: 2014
Message: Media is not assigned
Explanation: A job requires assigned media, but the requested media is not
assigned.
Recommended Action: Verify that the job requested the desired media. For
example, if you ask to list contents of the media, make sure that you have specified
the correct media ID.
Check the following logs:
¦ 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: 2015
Message: Media is expired
Explanation: A job is trying to write to media that has already expired.
Recommended Action: Make sure that non-expired media is available for the
job.
Check the following logs:
¦ 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.

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.

 

Symantec NetBackup status code 2006 to status code 2010

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 2006 to Status Code 2010 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2006
Message: NDMP credentials are not defined in EMM.
Explanation: No eligible media server is configured with NDMP credentials to
access the NDMP storage unit. Or, NetBackup tried to restore an NDMP image
from a disk storage unit when the media server is not at NetBackup Release 6.5.2
or later.
Recommended Action: If the job uses an NDMP device, verify that the media
server being used has NDMP credentials configured for the filer.

NetBackup status code: 2007
Message: Storage unit is not compatible with requesting job
Explanation: A job has asked for a storage unit that cannot be used for the job.
Recommended Action: This error can occur when a job tries to run on a media
server that is not at a recent enough NetBackup revision level.. The job may require
a feature that is not available on the media server being requested. Verify that
the storage unit type and media server that the policy and storage unit call out
support the feature that the job is trying to use.
This error can occur when the policy being run is not compatible with the storage
units requested by the policy:
¦ SnapVault storage units are requested for multiple copy jobs.
¦ Catalog backups are directed to shared disk storage units.
¦ Multiplexed jobs are directed to storage units that do not have the multiplex
feature configured.
¦ NDMP backup policies are directed to non-NDMP storage units.

NetBackup status code: 2008
Message: All compatible drive paths are down
Explanation: All configured drive that can be used for this job are down.
RecommendedAction: Verify that ltid is running on the required media server,
and the media server is active for tape. Using device monitor, bring up the drive
paths if they are down. If drives are downed again, clean the drives.

NetBackup status code: 2009
Message: All compatible drive paths are down but media is available
Explanation: All configured drives that can be used for this job are down.
RecommendedAction: Verify that ltid is running on the required media server,
and the media server is active for tape. Using device monitor, bring up the drive
paths if they are down. If drives are downed again, clean the drives.

NetBackup status code: 2010
Message: Job type is invalid
Explanation: The job type that is specified in an allocation request to the Resource
Broker is not valid for the operation requested.
RecommendedAction: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
¦ 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.

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.

 

Symantec NetBackup status code 2002 to status code 2005

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 2002 to Status Code 2005 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2002
Message: Invalid STU identifier type
Explanation: Ajob has asked for allocation using an invalid Storage Unit identifier
type. The only valid Storage Unit identifier types are 0 (specific STU), 1 (group)
or 2 (ANY).
Recommended Action: This error is internal. Call NetBackup support for
resolution.
Check the following logs:
¦ 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: 2003
Message: Drive is not allocated.
Explanation: MDS has been asked to deallocate a drive that is not allocated.
RecommendedAction: This error is internal to theMDScomponent of NetBackup.
Check the following logs:
¦ The mds unified logging files (OID 143) from the master server at debug level2.
¡ The nbrb unified logging files (OID 118) from the master server at debug level 3.

NetBackup status code: 2004
Message: Drive is already allocated
Explanation: MDS has been erroneously asked to allocate a drive that is already
allocated.
Recommended Action: A drive may have been reset while it was allocated for a
job. Wait for the jobs that use the drive to complete.

NetBackup status code: 2005
Message: MDS has received an invalid message from a media server.
Explanation: bptm or bpdm on a media server has sent an improperly formatted
message to MDS.
RecommendedAction: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
¦ 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.
¦ The bptm legacy log from the media server, with VERBOSE=5.

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.

 
1 2