NetBackup status code: 213

Article:HOWTO50974  |  Created: 2011-05-04  |  Updated: 2012-11-19  |  Article URL
Article Type
How To



NetBackup status code: 213

Message: no storage units available for use

Explanation: The NetBackup resource broker (nbrb) did not find any storage units available for use. Either all storage units are unavailable or all storage units are configured for On demand only. In addition, the policy and schedule does not require a specific storage unit.

Recommended Action: Do the following, as appropriate:

  • Examine the Backup Status and All Log Entries report for the appropriate time period to determine the policy or schedule that received the error.

  • Verify that the media server has not been deactivated for the storage unit or units that are unavailable.

  • Verify that the storage unit's drives are not down.

  • Verify the following attribute settings for all storage units:

    • For disk storage units, the Maximum concurrent jobs is not set to 0

    • For Media Manager storage units, the Maximum concurrent write drives is not set to 0

  • Verify that the robot number and host name in the storage unit configuration matches the Media and Device Management device configuration.

  • Determine if all storage units are set to On demand only for a combined policy and schedule that does not require a specific storage unit. In this case, either specify a storage unit for the policy and the schedule combination or turn off On demand only for a storage unit.

  • If the storage unit is on a UNIX or Linux NetBackup media server, it may indicate a problem with bpcd. Check /etc/inetd.conf on the media server to verify that the bpcd entry is correct.

    If the storage unit is on a Windows NetBackup media server, verify that the NetBackup Client service was started on the Windows NetBackup media server.

  • For detailed troubleshooting information, increase the logging levels of nbrb and mds on the master server.

    Use the vxlogcfg command as explained in the following topic:

    See "About unified logging" in the Troubleshooting Guide.

    Retry the operation and check the resulting debug logs.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices