Symantec NetBackup Media Manager status code 196 to status code 199

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 196 to status code 199 which may be received while using the Symantec NetBackup tool.

Media Manager status code 196
Message: EMM database error
Explanation: The calling program does not recognize the error the EMM server
returned.
¦ 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 EMM server processes new requests.

Media Manager status code 198
Message: pool not defined as a catalog backup pool
Explanation: An attempt was made to remove the Catalog Backup attribute from
a pool in which it was not set.
Recommended Action: Verify that the appropriate pool name was used in this
operation.

Media Manager status code 199
Message: the media is allocated for use
Explanation: A request was made to modify a media that was in use.
¦ 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 once the media is no longer in use.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 191 to status code 195

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 191 to status code 195 which may be received while using the Symantec NetBackup tool.

Media Manager status code 191
Message: invalid EMM argument
Explanation: An invalid argument was provided on a call to the EMM server.
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.

Media Manager status code 192
Message: unknown EMM error code
Explanation: An unknown error was returned from the EMM server.
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.

Media Manager status code 193
Message: generic EMM SQL error
Explanation: The EMM server received an error from the underlying database.
Recommended Action:
Examinecommandoutput, 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.

Media Manager status code 194
Message: EMM DB record not found
Explanation: During a NetBackup upgrade a pre-requisite host was not upgraded
in the correct order.
¦ 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 proper upgrade order is followed as described in the NetBackup
Installation Guide.

Media Manager status code 195
Message: CORBA communication error
Explanation: While trying to communicate with the EMM server, a problem
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 Symantec Private Branch Exchange (VxPBX) processesnewrequests.
¦ Verify that the EMM server processes new requests.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 188 to status code 190

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 188 to status code 190 which may be received while using the Symantec NetBackup tool.

Media Manager status code 188
Message: VxSS Access Denied
Explanation: The user identity that is used to attempt an operation does not have
the permissions needed to perform the action.
¦ If you use the default groups, make certain that the user attempts to perform
an operation appropriate for that group. For example, a member of
NBU_Operators is unable to modify policy information, a permission reserved
for administrator roles.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/username
¦ /user/openv/netbackup/logs
¦ /tmp
¦ If you use your own defined groups and permissions, first determine the object
with which the operation is associated. Then add the permissions relative to
the action. For example, a user is required to up and down drives but does not
currently have permission to do so. Verify that the user belongs to the correct
authorization group.
If necessary, verify that the group has Up and Down permissions on the Drive
object within the Group Permission tab. If necessary, you can increase the
verbosity level of NetBackup to locate what object and what permissions are
required for the failing request. The pertinent lines in the debug logs look
similar to the following:
17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.
Name: JMIZZLE
Expiry: Sep 24 21:45:32 2003 GMT
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
AuthType: 1
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:
Function: VssAzAuthorize. Object
NBU_RES_Drives
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:
Function: VssAzAuthorize. Permissions Up
17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:
Function: VssAzAuthorize. 20 Permission denied.
In the example, the user JMIZZLE attempts to perform an operation that
requires the Up permission on the Drives object. To diagnose the problem,
examine the group(s) to which the user belongs to ensure that the appropriate
group includes the Up permission. (Up is a member of the Operate permission
set for Drives.)

Media Manager status code 189
Message: failed to initialize a connection to the Enterprise Media Manager
Explanation: A request to initialize a connection with the EMM server failed or
was already initialized.
¦ Verify that pbx_exchange and nbemm are 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.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

Media Manager status code 190
Message: the request sent to the Device Allocator has failed
Explanation: A request to reserve or release a drive with the DA (EMM server)
failed.
¦ Verify that pbx_exchange and nbemm are 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.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.
¦ For a DA reserve drive request, verify that another host had not already
reserved the drive.
¦ For a DA release drive request, verify the following: that the drive is DA
reserved by the host requesting the DA release and has not already been
released.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 182 to status code 187

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 182 to status code 187 which may be received while using the Symantec NetBackup tool.

Media Manager status code 182
Message: device test state file does not exist
Explanation: The state file does not exist. The reason may be because no tests
have been run yet.
RecommendedAction: If the state file is lost, any previous test runs are also lost.
The recommended action is to start again.

Media Manager status code 185
Message: the robotic library is full and may still have media in its map
Explanation: During a robot inventory update, the user attempted to use the
empty_map option. The MAP contained more media than the library had space
for. In this case, the inventory update was successful, the empty_map part was
only partially successful. Those media still in the MAP are not changed or added
in the EMM database.
Recommended Action: No action is necessary on the user’s part except to be
aware that not all of the media was removed from the MAP and placed into the
library.

Media Manager status code 186
Message: invalid container id
Explanation: ANetBackup Vault container ID was used with 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.
¦ Retry the operation with a container ID that does not contain invalid characters.

Media Manager status code 187
Message: VxSS authentication failed
Explanation: The parties on either end of a socket connection cannot mutually
authenticate each other.
¦ Ensure that the Symantec Product Authentication Service is installed and
configured.
For complete installation instructions, see the NetBackup Security and
Encryption Guide.
¦ Check that both parties have a valid certificate by examining the listed expiry
date from a bpnbat -WhoAmI. For example:
bpnbat -WhoAmI
Name: JDOG
Domain: MYCOMPANY
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
Expiry Date: Sep 19 12:51:55 2009 GMT
Authentication method: Microsoft Windows
Operation completed successfully.
¦ Shows an expiry date of September 19th, 2009. After 12:51:55 GMT this
credential is no longer valid and a new credential is required.
¦ If you are running from the NetBackup Administration console, close and
reopen the console. The console automatically obtains a credential for the
currently logged in identity, if possible. By default these certificates are valid
for 24 hours. To set a longer default time, consult the following:
See the NetBackup Security and Encryption Guide.
¦ Ensure that the certificates for both sides either use the same broker, are
children of the same root broker, or have trusts established between them.
More information is available on broker hierarchies and how to establish trust
relationships between brokers.
See the NetBackup Security and Encryption Guide.
¦ Ensure that connectivity is possible between the physical systems in question.
If general sockets cannot connect between the machines (such as ping and
telnet), network issues unrelated to NetBackup may be the cause of this
problem.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/username
¦ /user/openv/netbackup/logs
¦ /tmp

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 176 to status code 181

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 176 to status code 181 which may be received while using the Symantec NetBackup tool.

Media Manager status code 176
Message: unable to find any records in the device test database
Explanation: The state file exists, but it is empty. This error indicates that no
previous test runs have occurred.
Recommended Action: None required.

Media Manager status code 177
Message: request can only be performed on the Media and Device Management
Domain Server
Explanation: The host this request was performed on is blocked from being a
database host. An administrator blocked the host to restrict which hosts are
allowed to be EMM servers.
¦ Verify that you specified the correct EMM server (the -h option on the
command line). If you did not specify the database host, the command line
defaults to the local host, while the console uses the currently administered
host.
¦ Contact the administrator in charge of this configuration and verify that the
host was intentionally blocked from being a database host. If not, remove the
NOT_DATABASE_HOST flag in the host’s vm.conf file. To do so without having
to stop and restart the daemons, use:
vmquery -h <hoostname> -remove_not_db_host.
To add this entry to a host without having to stop and restart the daemons,
use: vmquery -h <hostname> -add_not_db_host.

Media Manager status code 181
Message: not authorized to connect to robotic daemon
Explanation: A caller requesting services from a robotic daemon is not
authenticated or authorized. Or when two systems try to authenticate one another,
a problem occurs.
¦ See the NetBackup Security and Encryption Guide for information on Media
Manager security.
Media Manager security is based on NetBackup authentication and
authorization, but has extensions for handling SERVER entries in the Media
Manager configuration file.
¦ Examine the debug log files for a more detailed message on the authentication
and authorization problem.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Determine whether authorization fails on vmd. Examine the debug log files for
Media Manager status code 126 occurrences (not authorized to connect to
vmd).
¦ Correct the Media Manager security configuration by adjusting the
authentication configuration, the AUTHORIZATION_REQUIRED entry, the
ENABLE_ROBOT_AUTH entry, and the SERVER entries.
¦ If an authentication problem (rather than a configuration issue) is suspected,
do the following:
¦ Ensure that the authentication libraries exist:
Windows:
install_path\NetBackup\lib\libvopie.dll
install_path\NetBackup\lib\libvnoauth.dll
UNIX and Linux (except HP-UX):
/usr/openv/lib/libvopie.so
/usr/openv/lib/libvnoauth.so
UNIX and Linux (HP-UX only):
/usr/openv/lib/libvopie.sl
/usr/openv/lib/libvnoauth.sl
¦ Check the methods_allow.txt files on the systems that have problems to
ensure that authentication is enabled. The files are in the following
locations:
Windows: install_path\NetBackup\var\auth
UNIX and Linux: /usr/openv/var/auth
¦ On the systems that have the authentication problem, remove the remote
host that is not authenticated from the methods_allow.txt file and retry
the operation.
For example, if Host A and Host B have the problem, remove Host A from
the file on Host B, and vice versa.
If the problem still exists, the error is caused by connection problems not
related to authentication.
If connections are successful after you remove the host, run bpauthsync
-vopie on the master server to synchronize the key files on the systems
again.
On Windows:
install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers
On UNIX and Linux:
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers
Add the removed names and retry the operation.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 171 to status code 175

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 171 to status code 175 which may be received while using the Symantec NetBackup tool.

Media Manager status code 171
Message: a scratch pool is already defined
Explanation: A new scratch pool cannot be defined because another scratch pool
already exists.
Recommended Action:
Use the scratch pool already defined, or delete the current scratch pool and create
a new scratch pool.

Media Manager status code 172
Message: pool not defined as a scratch pool
Explanation: You or a NetBackup media management interface have tried to
delete (unset) a scratch pool that is not defined as a scratch pool.
Recommended Action: To delete the scratch pool, use the vmpool command.
Make sure that the name of the pool that is specified with the unset_scratch
option is the correct name of the scratch pool.

Media Manager status code 173
Message: invalid scratch pool name
Explanation: You, or a NetBackup media management interface have tried to
specify the NetBackup, DataStore, or None pool as a scratch pool. The NetBackup,
DataStore, and None pools cannot be specified as scratch pools.
Recommended Action: Create a scratch pool with a different name.

Media Manager status code 175
Message: unable to open the device test state file
Explanation: The process is not able to open the state file, mostly likely because
another process locked it.
Recommended Action:
Try again to open the state file. If you cannot open the state file, you may have to
remove the file, which would result in a loss of previous test runs.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 166 to status code 169

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 166 to status code 169 which may be received while using the Symantec NetBackup tool.

Media Manager status code 166
Message: media access port not available
Explanation: A request was made to physically move a volume into or out of a
robotic library, but the media access port was unavailable.
¦ 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.
¦ Ensure that the move request was not sent to a robotic control daemon or
process on a system that runs an older, incompatible software version.
¦ Ensure that the targeted robotic control daemon or process operates normally.

Media Manager status code 167
Message: ADAMM GUID is not unique in the database
Explanation: A volume entry that was added to or changed in the EMM database
had a specifiedADAMMGUID. It was a duplicate of theADAMMGUID for another
volume already in theEMMdatabase. All volumes in theEMMdatabase must have
an ADAMM GUID that is either unique or null. (ADAMM is Advanced Device and
Media Management, and a GUID is a Global Unique Identifier.)
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ From the daemon debug log file, determine the volume that has an ADAMM
GUID conflict with the volume entry that is added or changed.

Media Manager status code 168
Message: ADAMM GUID does not exist in database
Explanation: The EMM database was queried for a specified ADAMM (Advanced
Device and Media Management) GUID, and no volumes were found matching the
specified criteria. (The GUID is a Global Unique Identifier.)
Recommended Action:
Run vmphyinv for the media whose ADAMM GUID does not exist in the database.

Media Manager status code 169
Message: internal database access failure
Explanation: During an update of a drive status from a pre-6.0 NetBackup server
in EMM, a problem 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.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 162 to status code 165

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 162 to status code 165 which may be received while using the Symantec NetBackup tool.

Media Manager status code 162
Message: the global device database device name is invalid
Explanation: An invalid or a missing device name was encountered in a request
to modify the device configuration.
¦ 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.
¦ Identify the targeted host. Verify that all Media Manager binaries on that host
are at a compatible version level with other hosts that are part of the
configuration. Update the software version as needed.

Media Manager status code 163
Message: the operation requested has failed
Explanation: The requested operation failed. The reason was not specified.
Recommended Action: This error code may appear for a number of reasons.
Examinecommandoutput, 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.

Media Manager status code 164
Message: the robotic daemon returned an invalid volume GUID
Explanation: An invalid RSM GUID was returned from the RSM API. (RSM is the
Microsoft Removable Storage Manager. GUID is a Global Unique Identifier.)
¦ Examine the system’s application log, the Removable Storage system interface,
and the daemon and reqlib debug logs for a more detailed message on the
error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation and examine the logs. From the daemon debug log file,
determine the media ID that has the invalid RSM GUID.
¦ Make sure that the software components are compatible.

Media Manager status code 165
Message: Evaluation period expired. Go to www.symantec.com to order this
product.
Explanation: The NetBackup evaluation software has expired.
See the address in the message or www.symantec.com/enterprise/ for ordering
information.
Recommended Action: Obtain a licensed copy of NetBackup.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 152 to status code 160

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 152 to status code 160 which may be received while using the Symantec NetBackup tool.

Media Manager status code 152
Message: global device database record not found
Explanation: A request was made to update a global device database record, and
the record specified was not found in the global device database. This condition
can occur when a device configuration change is made after the global device
database host has changed.
RecommendedAction: If the request to update the record fails because the record
does not exist, a request is made to add the missing record. No action is required.

Media Manager status code 153
Message: device entry is not unique in global device database
Explanation: A request was made to add a global device database record, and the
record specified was a duplicate of an existing record. This condition can occur
if two processes update simultaneously the device configuration on the same host.
¦ Coordinate changes to the device configuration so that changes come from a
single source.
¦ Investigate the global device database changes on the server (database) side
by examining the daemon debug log file for a more detailed error message.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Media Manager status code 155
Message: global device database append operation failed
Explanation: Arequest was made to change the device configuration, and a global
device database record cannot be written to the global device database file.
Recommended Action:
Examine the daemon debug log for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Media Manager status code 160
Message: the global device database device type is invalid
Explanation: An invalid device type appears in a request to modify the device
configuration.
¦ 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.
¦ Identify the targeted host. Verify that all Media Manager binaries on that host
are at a compatible version level with other hosts that are part of the
configuration. Update the software version as needed.

Hope this was helpful.

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

 

Symantec NetBackup Media Manager status code 146 to status code 150

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 146 to status code 150 which may be received while using the Symantec NetBackup tool.

Media Manager status code 146
Message: incompatible database version
Explanation: Arequesting process orvmdencountered an invalid or an unknown
database or communications protocol. The possible data stores that an error
affects are volume, volume pool, bar code rule, global device database, and shared
drive information.
¦ 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.
¦ Identify the target components (for example, vmd and daemons or services,
or user interfaces on local or remote hosts). Verify that all Media Manager
binaries are at a compatible version level. Depending on which requests
encountered the invalid version, determine whether or not the database is
corrupt. Use an appropriate interface to query for the type of information that
is involved in the error condition.

Media Manager status code 147
Message: invalid offsite slot
Explanation: Arequest was made to change the off-site slot location for a volume,
and the value specified was not within the acceptable range.
¦ 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.
¦ Specify an off-site slot value within the range of 0 to 2,147,483,647.

Media Manager status code 148
Message: invalid offsite session id
Explanation: A request was made to change the off-site session ID for a volume,
and the value specified was not within the acceptable range.
¦ 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.
¦ Specify an off-site session ID within the range of 0 to 2,147,483,647.

Media Manager status code 149
Message: current version does not support this configuration
Explanation: A request cannot be performed because it attempted to reference
unlicensed functionality. An example request: the attempt to add a volume with
a media type that is not valid for the licensed product.
¦ 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.
¦ List the license keys that were installed and verify that the referenced
functionality is supported with the currently installed license keys. Check to
see that the databases that define externalized object types are in place and
not corrupted. These database files are the following, in the
/usr/openv/var/global directory (UNIX and Linux) or
install_path\NetBackup\var\global folder (Windows):
¦ external_densities.txt
¦ external_drivetypes.txt
¦ external_mediatypes.txt
¦ external_robotics .txt

Media Manager status code 150
Message: registering this host would exceed the maximum allowed
Explanation: The EMM/DA received a request to register shared drives from a
host that was not currently registered. The maximum number of hosts that are
registered with this EMM/DA were already reached. The current limit for the
number of hosts that can register with the EMM/DA is 255.
¦ Restrict the size of the SSO configuration to no more than 255 hosts.
¦ Break up the media and the device management domain into multiple domains,
with all domains having 255 or fewer hosts that register shared drives.

Hope this was helpful.

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

 
1 2 3 4