Symantec NetBackup Device configuration status code 97 to status code 101

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 97 to status code 101 which may be received while using the Symantec NetBackup tool.

Device configuration status code 97
Message: No valid license key for Disk Array configuration
Explanation: Disk array snapshot support is a licensed featured. You must install
the Snapshot Client license key before NetBackup can configure disk array
credentials.
Recommended Action: Install the Snapshot Client license key.

Device configuration status code 98
Message: Open Storage feature is not licensed
Explanation: Credentials for OpenStorage servers cannot be added without the
NetBackup OpenStorage license key.
Recommended Action: Install the OpenStorage license key.

Device configuration status code 99
Message: Credentials already exist
Explanation: Credentials already exist for the host you are trying to add.
RecommendedAction: Delete the existing credentials and then add the new ones.

Device configuration status code 100
Message: NetBackup Snapshot client not licensed
Explanation: Credentials for this type of host cannot be added without the
NetBackup Snapshot Client license key. Host types that require this license are
disk array manager servers and virtual machine servers.
Recommended Action: Install the NetBackup Snapshot Client license key.

Device configuration status code 101
Message: authorization error, verify username/password
Explanation: Authorization failed with the given set of username and password
values.
Recommended Action: Verify the values provided and check for typographical
errors.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 91 to status code 96

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 91 to status code 96 which may be received while using the Symantec NetBackup tool.

Device configuration status code 91
Message: The drive serial number already exists in the device database.
Explanation: An attempt was made to add a drive with a duplicate serial number.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the added drive has a unique serial number.

Device configuration status code 92
Message: VxSS access denied
Explanation: A user attempts an operation without adequate permissions
¦ Verify that the user has the correct permissions to perform this operation.
¦ Verify that the authentication and authorization security settings are correct,
under Host Properties in the NetBackup Administration Console.
See the NetBackup Security and Encryption Guide for information on how to
use the Symantec Product Authentication and Authorization Service.

Device configuration status code 93
Message: Database Server is down
Explanation: Arequest was made to theEMMServer, but the underlying database
server does not respond.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ This error can occur if a cold catalog backup is in progress. Retry the request
after this operation has completed.

Device configuration status code 95
Message: The requested operation is not valid for the specified Disk Type
Explanation: The storage device you configured is not a disk storage device.
Recommended Action: Select an appropriate storage device.

Device configuration status code 96
Message: The specified Disk Array Host is not configured in NetBackup
Explanation: You must first add this disk array host to the NetBackup host
configuration before this operation can be performed. To view hosts, see nbemmcmd
-listhosts in the NetBackup Commands Reference Guide.
¦ If you try to update an existing host’s credentials, this host no longer exists
in NetBackup. It must be added again by using the tpconfig or the nbemmcmd
command.
¦ The name you entered for the disk array host does not match any of the
computer aliases in the NetBackup computer configuration. Use the nbemmcmd
command to add the fully qualified array host name (or the name entered) to
the computer alias list for your disk array.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 86 to status code 90

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 86 to status code 90 which may be received while using the Symantec NetBackup tool.

Device configuration status code 86
Message: Invalid Drive Name Rule
Explanation: A drive name rule was not specified, or contained an invalid
character.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Observe the rules for drive names:
¦ Cannot begin with a dash.
¦ Cannot exceed 48 characters.
¦ A literal field can only contain alphanumeric characters and plus (+), dash
(-), period (.), or underscore (_).
¦ An invalid field name was specified; check command usage.

Device configuration status code 87
Message: System Error
Explanation: An operating system error occurred.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that adequate memory is available.
¦ Verify that Windows networking is properly installed.

Device configuration status code 88
Message: Invalid host
Explanation: Anattempt was made to add a device to a host that theEMMdatabase
does not recognize.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use nbemmcmd -addhost to add the host to the EMM database.

Device configuration status code 89
Message: Drive name rule has exceeded its maximum length of 48 characters
Explanation: The specified drive name rule is too long.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Choose a shorter rule.

Device configuration status code 90
Message: Another device configuration is already in progress
Explanation: An instance of the Device Configuration Wizard or tpautoconf is
already running.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation after the current instance is done.
¦ A lock on the device configuration cache may have been orphaned. Use the
nbemmcmd command to clear the lock, then retry the operation.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 81 to status code 85

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 81 to status code 85 which may be received while using the Symantec NetBackup tool.

Device configuration status code 81
Message: This is a drive path operation, use the -drpath option
Explanation: Apath operation was specified with the tpconfig command without
the -drpath option. This error can occur when you try to change a drive’s path
using tpconfig -update -drive.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Check tpconfig usage to ensure that the command is used properly and use
tpconfig -update -drpath instead.

Device configuration status code 82
Message: Add Drive Name Rule request failed
Explanation: A request to add a drive name rule failed.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ The rule being added already exists.
¦ The specified host does not exist in the EMM database. Use the nbemmcmd
-addhost command to add the host to the EMM database.

Device configuration status code 83
Message: Update Drive Name Rule request failed
Explanation: An update to a drive name rule failed.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ The rule being updated does not exist. Ensure that the drive name rule is
entered correctly.
¦ The specified host does not have a local drive name rule configured. Configure
a drive name rule.

Device configuration status code 84
Message: Delete Drive Name Rule request failed
Explanation: Arequest to delete a drive name rule failed. You cannot add or delete
a global drive name rule.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
¦ A local drive name rule does not exist on the hosts specified.

Device configuration status code 85
Message: List Drive Name Rule request failed
Explanation: Could not list the drive name rules for a given host or set of hosts.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the hosts are known in the EMM database.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 76 to status code 79

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 76 to status code 79 which may be received while using the Symantec NetBackup tool.

Device configuration status code 76
Message: NDMP config_get_connection_type failed
Explanation: The NAS host fails to successfully process the
config_get_connection_type protocol request.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 77
Message: Unable to connect to the EMM server
Explanation: A request was made to the EMM server, but it either did not reach
the EMM server or resulted from a communication failure.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that pbx_exchange and nbemm are running.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

Device configuration status code 78
Message: The EMM server failed to process the request
Explanation: A request was made to the EMM server, but it either did not reach
the EMM server or resulted from a communication failure.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that pbx_exchange and nbemm are running.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

Device configuration status code 79
Message: Unable to allocate memory for this process
Explanation: A memory allocation request failed.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that adequate memory is available.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 71 to status code 75

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 71 to status code 75 which may be received while using the Symantec NetBackup tool.

Device configuration status code 71
Message: NDMP get_host_info failed
Explanation: The NAS host fails to correctly process the ndmp_get_host_info
protocol request.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 72
Message: NDMP get_server_info failed
Explanation: The NAS host fails to successfully process the get_server_info
protocol request.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 73
Message: Unsupported NDMP version
Explanation: NetBackup supports tape devices on NDMP protocol versions V2,
V3, and V4. For automatic device configuration, only V3 and V4 are supported.
¦ Examine debug logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ See your NAS vendor documentation for instructions on how to switch NDMP
versions.

Device configuration status code 74
Message: NDMP authorization error, verify username/password
Explanation: NetBackup fails to authenticate the username or password on the
NAS host.
Recommended Action: Use the tpautoconf -verify command to verify the
username and password.

Device configuration status code 75
Message: NDMP config_get_mover_type failed
Explanation: TheNAShost fails to successfully process the config_get_mover_type
protocol request.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 66 to status code 70

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 66 to status code 70 which may be received while using the Symantec NetBackup tool.

Device configuration status code 66
Message: NDMP robot does not exist
Explanation: An update request was issued for a non-existent robot.
Recommended Action: Use the NetBackup Administration Console, or the
tpconfig -update -robot command, to add the correct robot.

Device configuration status code 67
Message: Unable to connect to NDMP host verify hostname
Explanation: A network connection to the NAS host failed.
¦ Use the tpautoconf -verify command to verify the hostname, username,
and password.
¦ Use the ping command to verify network access.

Device configuration status code 68
Message: Unable to process NDMP message
Explanation: An unexpected error occurs while an NDMP message processed.
Recommended Action: Examine debug logs and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 69
Message: NDMP host not connected
Explanation: Unable to process NDMP messages with the NDMP host.
Recommended Action: Examine debug logs for more information on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 70
Message: Unable to create NDMP session
Explanation: An error occurs while opening an NDMP connection to a NAS filer.
¦ Examine debug logs for more information on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use the tpautoconf -verify command to verify the hostname, username,
and password.
¦ Use the ping command to verify network access.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 61 to status code 65

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 61 to status code 65 which may be received while using the Symantec NetBackup tool.

Device configuration status code 61
Message: NDMP host exists, use change option
Explanation: An attempt to add a filer fails because the filer already exists in the
EMM database.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use the -update option of tpconfig instead of -add.

Device configuration status code 62
Message: NDMP host does not exist
Explanation: The NDMP host does not exist in the EMM database.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use the -add -nh option on the tpconfig command to add the NDMP host.

Device configuration status code 63
Message: NDMP request failed
Explanation: An attempt to create an NDMP session failed, or an attempt to send
an NDMP message failed.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify NAS filer licenses, supported operating system levels, and network
connectivity.

Device configuration status code 64
Message: Invalid NDMP device
Explanation: An invalid NDMP device was specified.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 65
Message: NDMP robot exists, use change option
Explanation: The robot currently exists in the EMM database.
Recommended Action: Use the NetBackup Administration Console, or the
tpconfig -update -robot command, to change the robot configuration.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 56 to status code 60

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 56 to status code 60 which may be received while using the Symantec NetBackup tool.

Device configuration status code 56
Message: Invalid NDMP username
Explanation: An invalid username or no username was specified.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use tpconfig -dnh to verify that the host has been configured.

Device configuration status code 57
Message: Internal NDMP error
Explanation: An error occurs on the NDMP device.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Check the usage of the set_ndmp_attr -probe or tpautoconf -probe
commands.
¦ An error occurs while trying to get the serial number and inquiry string for a
device connected to an NDMP filer. Verify that the device is properly attached
to the filer.

Device configuration status code 58
Message: NDMP failed to verify host
Explanation: An error occurs while using the NDMP verify functionality.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Check the usage of the tpautoconf -verify commands.
¦ Verify that the device is properly attached to the filer.

Device configuration status code 59
Message: NDMP is not installed on platform
Explanation: The NDMP option is not installed on this server.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the NDMP option is properly installed and licensed.
¦ Verify that NDMP is supported on the platform in question.

Device configuration status code 60
Message: Invalid NDMP password
Explanation: An invalid NDMP password or no password was provided.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the password is appropriate for the media server and filer pair.
¦ Verify that the password was provided correctly on the command or in the
NDMPHost dialog box.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 48 to status code 55

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 48 to status code 55 which may be received while using the Symantec NetBackup tool.

Device configuration status code 48
Message: RSM is not supported.
Explanation: On a request to make a device configuration change, the RSM
(Microsoft Removable Storage Manager) robot type was specified, but it is no
longer supported.
Recommended Action: Use a supported Media Manager robot type.

Device configuration status code 49
Message: global device database host name is invalid.
Explanation: On a device configuration request, the EMM server name cannot
be obtained.
TheEMMserver name is obtained through an internal request to read the bp.conf
file (or Windows registry). This request is likely to fail if the EMMSERVER entry
is not set.
RecommendedAction: Use tpautoconf -get_gdbhost on a device host to obtain
itsEMMserver name. Use tpautoconf -set_gdbhost to set theEMMserver name,
as needed.

Device configuration status code 51
Message: No compatible device is registered at these SCSI coordinates.
Explanation: On a request to add or change robot or drive information in the
device configuration, the following occurred: the specified SCSI coordinates did
not correspond to a device in the system registry. This status code applies to
Windows systems only.
RecommendedAction: To avoid manually specifying SCSI coordinates (port, bus,
target, and LUN), use the Device Configuration Wizard. The wizard fully automates
(on supported device discovery platforms) device configuration requests. Or use
the Media and Device Management interface to browse for devices in the system
registry. Check the operating system registry to ensure that devices are present
at the specified coordinates when SCSI coordinates are manually configured.

Device configuration status code 52
Message: The device name is not valid, no device responded.
Explanation: On a request to add or change robot or drive information in the
device configuration, the following occurred: no device was found in the system
registry with the specified device name. This error code applies to Windows
systems only.
Recommended Action: To avoid manually specifying the device name, use the
Device Configuration Wizard. The wizard fully automates (on supported device
discovery platforms) device configuration requests. Or use the Media And Device
Management interface to browse for devices in the system registry. Check the
operating system registry to ensure that devices are present at the specified
coordinates when devices are manually configured.

Device configuration status code 53
Message: Shared Storage Option (SSO) is not licensed
Explanation: An attempt to add a path to a drive failed. It failed because the SSO
license was not installed.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that an active SSO license is installed on all servers that have a path
configured to this drive and the server where this operation is performed.

Device configuration status code 55
Message: Invalid NDMP hostname
Explanation: An invalid hostname or no hostname was specified.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Use tpconfig -dnh to verify that the host has been configured.
¦ Check the usage of the tpautoconf -list_snapvault_volumes command.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 
1 2 3 4