STATUS CODE: 254 - Occurs when adding a storage unit via the command line bpadm or bpstuadd commands

STATUS CODE: 254 - Occurs when adding a storage unit via the command line bpadm or bpstuadd commands

Article: 100017212
Last Published: 2008-01-31
Ratings: 1 0
Product(s): NetBackup

Problem

STATUS CODE: 254 - Occurs when adding a storage unit via the command line bpadm or bpstuadd commands

Error Message

Failure adding storage unit '' (254 - server name not found in the NetBackup configuration)

Solution

Overview:

Trying to manually add a storage unit will fail with a "server name not found in the NetBackup configuration" error when a media server is not yet registered with the EMM server.  Starting with VERITAS NetBackup (tm) 6.0, a media server must be listed in the EMM server configuration in addition to being in the bp.conf file. This is a new step and allows NetBackup to know what media servers are in a given NetBackup environment.  

Troubleshooting:

This error will occur when running bpstuadd manually or when trying to add storage units from the command line bpadm administration command.

To duplicate the problem:

1. Launch the bpadm command:
# /usr/openv/netbackup/bin/bpadm
2. Select s) Storage Unit Management from the menu
3. Select a) Add Storage Unit from the menu
4. Fill out the storage unit information and enter the specific hostname for the media server
5. When prompted, add the storage unit:
Add storage unit? (y/n): y
Adding storage unit 'tape-dlt2'...
 
Failure adding storage unit 'tape-dlt2' (254 - server name not found in the NetBackup configuration)
Press any key to continue

The Status 254 will occur when the media server hostname has not been added to the EMM server configuration.

Master Server Log Files:

The /usr/openv/netbackup/logs/admin/log.<date> file will show the following errors when adding the storage unit attached to a media server that is not configured on the EMM server:
<16> emmlib_AddStorageUnit: (0) ADD_STORAGE_UNIT failed, emmError = 2000047, nbError = 0
<16> db_addSTUNIT: (-) Translating EMM_ERROR_MediaServerNotExist(2000047) to 254 in the NetBackup context
<2> db_addSTUNIT: skip db_sendNotify stunit=empty
<2> bpstuadd: server name not found in the NetBackup configuration
<2> bpstuadd: EXIT status = 254

Unified logging will show the corresponding errors when verifying the hostname with the EMM server.  Use the vxlogview command to search for messages that appeared when the Status 254 occurred.
# vxlogview -b '09/21/2005 10:35:00 AM' -e '09/21/2005 10:36:00 AM'
09/21/05 10:35:41.014 V-111-1049 [StorageUnitImpl::helperCreateStorageUnit] EMMServer generic error = MediaServer < media1 > does not exist - retval = < 2000000 >
09/21/05 10:35:41.015 [StorageUnitImpl::CreateStorageUnit] retval = < 2000047 >


Resolution:

Verify the media server is present in the EMM server configuration by running:
# cd /usr/openv/netbackup/bin/admincmd
# ./nbemmcmd -listhosts
The following hosts were found:
master      starfury
server      starfury
Command completed successfully.

This example lists a master server with no configured media servers.

This output should list the media server where the storage unit will reside. If the Media server is not in this listing,  the nbemmcmd -addhost command must be run.  This is required to add the media server to the EMM server configuration.  Refer to article 279049 in the Related Documents section below for instructions and examples on adding a media server to the EMM server configuration.  Once the nbemmcmd -addhost command has been run,  the storage unit can be added successfully.

 
 

 

References

Etrack : 254 UMI : V-111-1049

Was this content helpful?