Scribd
Upload
95 views

Code 213

The document describes an error occurring when trying to communicate with a media server for a basic disk storage unit. It indicates the storage unit is using the master server instead of the configured media server due to an alias set between the two servers. The suggested resolution is to delete the storage unit, alias, and recreate the storage unit to resolve the communication issue.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
95 views

Code 213

The document describes an error occurring when trying to communicate with a media server for a basic disk storage unit. It indicates the storage unit is using the master server instead of the configured media server due to an alias set between the two servers. The suggested resolution is to delete the storage unit, alias, and recreate the storage unit to resolve the communication issue.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Problem

GENERAL ERROR: Status Code 213 - No storage units available for use.

Error
MPXProvider returned Not Enough Valid Resources for request ID [set_host_and_dg_info_in_stu_list] could not get any media servers for storage unit

Solution

Error Code(s)/Message(s): Error message in VxUL (OID 118 NBRB):


V-118-146 [ProviderManager::allocate] MPXProvider returned Not Enough Valid Resources for request ID [set_host_and_dg_info_in_stu_list] could not get any media servers for storage unit

Overview: The Status 213 is generated when the master fails to communicate with the media server. The UNC path to the remote server was not a factor. Troubleshooting: The configuration for the basic disk storage unit indicates the media server and the remote server share.
\install_path\netbackup\bin\admincmd\bpstulist -L Label: Storage Unit Type: Media Subtype: Host Connection: Concurrent Jobs: On Demand Only: Path: Robot Type: Max Fragment Size: Max MPX: Stage data: Block Sharing: File System Export: High Water Mark: Low Water Mark: Ok On Root: Disk_Storage Disk Basic (1) media_server 1 yes "\\remote_server\share" (not robotic) 524288 1 no no no 98 80 no

Verify the status of the basic disk storage unit with nbdevquery.
\install_path\netbackup\bin\admincmd\nbdevquery -listdp -stype BasicDisk -U Disk Pool Name Disk Pool Id Disk Type Status Flag Flag Flag Flag Flag Flag Flag Flag Flag Flag Flag Raw Size (GB) Usable Size (GB) Num Volumes High Watermark Low Watermark Comment Storage Server : : : : : : : : : : : : : : : : : : : : : : Disk_Storage INValid BasicDisk UP Patchwork SingleStorageServer AdminUp InternalUp SpanImages BasicStaging FragmentImages CatalogBackup Cpr RandomWrites FT-Transfer 0.00 0.00 1 98 80 Generic disk group master_server

Note: The Storage Server is listed as the master_server and not the media_server.
\install_path\netbackup\bin\admincmd\nbdevquery -listdv -stype BasicDisk -U Disk Pool Name Disk Type Disk Volume Name Disk Media ID Total Capacity (GB) Free Space (GB) Use% Status Flag Flag Flag Num Read Mounts Num Write Mounts : : : : : : : : : : : : : Disk_Storage BasicDisk Internal_16 @aaaan 0.00 0.00 100 DOWN ReadOnWrite AdminUp InternalUp 0 1

This Storage unit is DOWN because of the Storage Server mismatch. Check aliases:
\install_path\netbackup\bin\admincmd\nbemmcmd -machinealias -getalias machinename media_server -machinetype media

Note: This command listed the master_server as an alias for the media_server.

Resolution: 1. Delete the media_server disk storage unit. 2. Delete the alias.
\install_path\netbackup\bin\admincmd\nbemmcmd -machinealias -deletealias alias master_server -machinetype media

3. Create a new disk storage unit.

You might also like