Troubleshooting - Data Protector PDF

1/10/2019 https://cgrfiles.cgr.go.cr/publico/ver9/hpux/DP_DEPOT/DATA-PROTECTOR/OMNI-DOCS/opt/omni/help/C/Trouble.
txt
*********************************************
* *
* Data Protector Troubleshooting *
* *
*********************************************
MESSAGE:
[12:5] Internal error in ("p":num) => process aborted

This is an unexpected condition and is likely due to a
corrupted media or combination of circumstances
involving both this product and the operating system.
Please report this error to your post-sales
Data Protector Support Representative.
DESCRIPTION:
An internal error occurred. The process was not able to recover and
aborted ungracefully immediately after reporting this condition.
ACTION:
Please verify the Data Protector medium format.

If the media is not corrupted than please do following before
contacting your post-sales Data Protector Support Representative,
please gather as much information as possible:
* Write down product version and build number.
* Make a note of the circumstances that cause this error.
* Save session output to a file (e.g. session.txt).
* Collect all log files (*.log) in <Data_Protector_home>/log directories
on all hosts involved in the situation when this error occurred
(e.g. host running VBDA, host running BMA and host running BSM).
MESSAGE:
[12:1000] Table allocation error. (No more free entries!).
DESCRIPTION:
Table allocation error.
ACTION:
Internal program static tables are used due to several error recovery
procedures. Restart the GUI.
MESSAGE:
[12:1010] Error in protocol.
DESCRIPTION:
The internal Data Protector message received is not in the recognizable format.
Most probably the peer has an old (or invalid) version of Data Protector installed.
ACTION:
https://cgrfiles.cgr.go.cr/publico/ver9/hpux/DP_DEPOT/DATA-PROTECTOR/OMNI-DOCS/opt/omni/help/C/Trouble.txt 1/462
1/10/2019 https://cgrfiles.cgr.go.cr/publico/ver9/hpux/DP_DEPOT/DATA-PROTECTOR/OMNI-DOCS/opt/omni/help/C/Trouble.txt
Install the newest version of Data Protector.
MESSAGE:
[12:1012] Cannot access the file.
DESCRIPTION:
Configuration file cannot be accessed. This message means that the Cell
Manager daemon cannot read or write from a certain configuration file.
ACTION:
Check if the appropriate files exist in the Data Protector directory.
MESSAGE:
[12:1015] The number of configured clients is greater than the number of

available client (host) licenses. Possibly the license has expired.
Run command omnicc -query to see the licensing summary report.
DESCRIPTION:
Not enough licenses.
ACTION:
Add new licenses or change the configuration.
MESSAGE:
[12:1020] Cannot transfer file to the client host or from the client host.
DESCRIPTION:
Configuration file which resides on the client host cannot be accessed.
ACTION:
* Check debug.log located on the CM and client host in <Data_Protector_home>\log\ on NT

or in /var/opt/omni/log/debug.log on UNIX machines to see the detailed
reason for that error.
* Check if Data Protector is installed on the client host.
* If installed, then check:
* For Oracle Integration on NT clients:
- If dir <Data_Protector_home>\config\oracle\ccs exists. If the dir doesn't exist the
Oracle integration is not correctly installed.(Re-install the Oracle
integration).
* For Oracle Integration on UNIX clients:
- If dir /var/opt/omni/oracle/ccs exists. If the dir doesn't exist the Oracle
integration is not correctly installed. (Re-install the Oracle integration).

* For SAP Integration on NT clients:
- If dir <Data_Protector_home>\config\sap exists. If the dir doesn't exist the SAP
integration is not correctly installed.(Re-install the SAP integration).
* For SAP Integration on UNIX clients:
- If dir /var/opt/omni/sap/ exists. If the dir doesn't exist the SAP
integration is not correctly installed.(Re-install the SAP integration).
MESSAGE:
[12:1031] Unrecognized option "p" !
DESCRIPTION:
The program did not recognize the command line input as a valid keyword:
* The option might not be valid for this program, or
* User misspelled an option, or
* A parameter for an option was specified with a leading dash ('-').
ACTION:
* If options were specified by the user, check the syntax of command line parameters.
* If error was reported by an agent, invoked by session manager, verify that the
version of agent corresponds to the version of session manager.
MESSAGE:
[12:1032] Invalid parameter "p" for option "p" !
DESCRIPTION:
The supplied parameters are not valid for the specified option:
* Too few or too many parameters for this option, or
* The parameter might be out of range, or
* An option was specified without a leading dash ('-').
ACTION:
MESSAGE:
[12:1033] param1
Cannot open option file: (param2)
DESCRIPTION:
The program received a -read option or an input redirection operator

(-trees <file) and the input file could not be accessed
ACTION:
* Verify that the input file exists on the appropriate host and
can be read by the program.
MESSAGE:
[12:1034] Maxiumum number of connections to CRS reached!
DESCRIPTION:
Maxiumum number of connections to CRS reached!
ACTION:
Close idle connections.
MESSAGE:
[12:1035] Maxiumum number of session manager startup retries exceeded!
DESCRIPTION:
Maxiumum number of session manager startup retries exceeded!
ACTION:
MESSAGE:
[12:1036] Interprocess communication problem.
DESCRIPTION:
Server error: The cell_format file on the Cell Manager cannot be accessed.
ACTION:
Ensure that the Data Protector services/processes are properly configured and running on the Cell
Manager.
MESSAGE:
[12:1040] Agent failed to obtain home directory from registry.
DESCRIPTION:
An agent that was started to fulfill the request (possibly remotely on

another client) failed to initialize.
This indicates that Data Protector client software is not
installed or configured properly on the client or that some executables
are not compatible with the version currently installed.
ACTION:
* Check the version of the agent on the client.

* Re-install Data Protector software on the client.
MESSAGE:
[12:1041] Agent failed to open the message catalog.
DESCRIPTION:
An agent that was started to fulfill the request (possibly remotely on

another client) failed to initialize.
This indicates that Data Protector client software is not
installed or configured properly on the client or that some executables
are not compatible with the version currently installed.
ACTION:
* Check the version of the agent on the client.

* Re-install Data Protector software on the client.
MESSAGE:
[12:1049] Service/daemon failed to write to configuration files and/or registry.
DESCRIPTION:
Service/daemon failed to write to configuration files and/or registry.
ACTION:
* Verify that the service account has administrative privileges.

* Verify that the service account is allowed to access the Data Protector
configuration files and registry.
MESSAGE:
[12:1051] Client security violation. Access denied.
DESCRIPTION:
The target host is secured and has been accessed by a host that is not
on its list of cell authorities.
ACTION:
* Check and update the client's list of cell authorities.

* In case your client has been locked out, edit the allow_hosts file manually.
MESSAGE:
[12:1115] Internal Database is probably corrupt.

Please run omnidbcheck!
DESCRIPTION:
The Data Protector Internal Database is probably corrupt.
ACTION:
Terminate all running sessions and GUIs so that no process is accessing the
database. Next, login to the Cell Manager as root and run the omnidbcheck
-keybuild command. If this fails then the Internal Database is unfixable
and you must recover it from a backup.
MESSAGE:
[12:1117] Cannot lock Internal Database - currently unavailable.
DESCRIPTION:
You have a lot of parallel jobs and they want to access the same part of
the Internal Database.
ACTION:
Check to be sure that no other Data Protector processes are running on the
Cell Manager (especially Session Managers bsm/rsm/msm/dbsm/asm and
the omnidbcheck command.) Stop the Cell Manager (using the omnisv
-stop command) and then restart the Cell Manager (using the omnisv
-start command).
Try rescheduling some backups to run them in sequence (instead of parallel).
If daily purge is running you can configure it in the

global options file to run when no backups are running.
MESSAGE:
[12:1118] Cannot open database/file.
DESCRIPTION:
Data Protector was unable to open the Internal Database. The database files are
either not available or the Unix file permissions to access the database files
are incorrect.
ACTION:
On a UNIX Cell Manager:

Check the database files ( *.dat, *.ext, *.key) in the
/var/opt/omni/db/cdb and /var/opt/omni/db/mmdb directories on
the Cell Manager. The permissions of these files should be 600 and user root.
If there are no files, database has not been initialized yet. In this case, use the
omnidbinit command to initialize the database.
Also check for /var/opt/omni/db/catalog/extfiles.txt for extension files and check they are
in place - they might be missing.
On a Windows Cell Manager:

Check that database files ( *.dat, *.ext, *.key) in the <Data_Protector_home>\db\cdb
and <Data_Protector_home>\db\mmdb directories on the Cell Manager don't have the read only
attribute
set. If there are no files, database has not been initialized yet. In this case, use the
omnidbinit command to initialize the database.
Also check for <Data_Protector_home>\db\catalog for extension files and check they are
in place - they might be missing.
MESSAGE:
[12:1121] Cannot open database.

Somebody is running omnidbcheck or omnidbutil command!
DESCRIPTION:
You tried to run a process that opens the database. However, Data Protector
was unable to open the database because other user was running
omnidbcheck or an omnidbutil command.
ACTION:
Wait for the omnidbcheck or omnidbutil command, then restart the

operation.
MESSAGE:
[12:1122] Cannot open Internal Database in exclusive mode.

Check that no Session Managers are running.
DESCRIPTION:
Message is usual at merging mmdb database to central mmdb database. It

means that there are session managers running on central host. It might seem
that no Session Manager is running, but the message appears. Reason is that
there is a lock for cca 30 min after Session Manager is down. In that case
restarting CRS solves a problem.
ACTION:
Wait for the Session Managers to complete, then restart the operation. Check
that no Session Managers are running.
MESSAGE:
[12:1130] Object details in this object version are corrupted.
DESCRIPTION:
Object details needed for restore of this object version are corrupted. This object version will
be skipped.
ACTION:
Select another object version for restore, or

Try to re-import the related medium.
MESSAGE:
[12:1162] Not enough disk space for Internal Database.
DESCRIPTION:
Data Protector does not have enough disk space to use the Internal Database.
ACTION:

Delete or move files from the disk where the Data Protector Internal Database is
located (/var/opt/omni/db) and then restart the operation.
All disks where Data Protector files reside (/opt/omni, /var/opt/omni)
must have at least 2 MB free disk space.

Delete or move files from the disk where the Data Protector Internal Database is
located (<Data_Protector_home>\db) and then restart the operation. You can also
move the location of the Internal Database to another location
(check in the Data Protector documentation how to move the Internal Database to
another location).
The disk where Data Protector is installed must have at least 2 MB of free disk space.
MESSAGE:
[12:1163] Internal Database record limit per file has been reached.
DESCRIPTION:
The limit for Data Protector Internal Database records has been reached.
ACTION:
Stop all Session Managers and terminate all GUIs, then use the
omnidbutil -purge -filenames command to delete obsolete data from

the Internal Database. Restart the operation.
MESSAGE:
[12:1164] Internal Database key files have been corrupted.

Please run omnidbcheck -keybuild!
DESCRIPTION:
The Data Protector Internal Database index file has been corrupted.
ACTION:
Use the omnidbcheck -keybuild command to fix the index file.
MESSAGE:
[12:1165] Internal Database network communication error.
DESCRIPTION:
The Data Protector Internal Database has problems communicating with the Velocis
Daemon (RDS).
It is very likely that RDS was restarted, and GUI was not.
ACTION:
On a Unix Cell Manager:

Check to be sure that the Velocis Daemon (RDS) is running. Stop the Cell
Manager (using the omnisv -stop command) and restart the Cell Manager
(using the omnisv -start command). Start the GUI.

Check to be sure that the Velocis Daemon (RDS.exe) is running. Use the Service
Control Manager to restart the Data Protector RDS and Data Protector CRS services.
MESSAGE:
[12:1166] Internal Database error. The IDB services are most probably not running.
DESCRIPTION:
The Internal Database services are not running.
ACTION:
Check whether the Internal Database services are running (using the command omnisv -status).
Stop the Cell Manager services (using the command omnisv -stop) and restart them
(using the command omnisv -start command).
MESSAGE:
[12:1167] There is no more space in the Internal Database for file versions.
DESCRIPTION:
File versions part of the Internal Database is full. Data Protector is unable to write
information about files into the database.
ACTION:
Check the database usage and extension files configuration for file
versions part of database. You should either configure additional
extension module files or cleanup the database.
It is possible that your database has some obsolete data, which can
be removed. You should run database purge and see if you get some
space back. You should schedule database purge to run regularly.
For example, in order to configure additional module files size

run the following command:
/opt/omni/sbin/omnidbutil -extend pathname -maxsize size_MD
MESSAGE:
[12:1168] There is no more space in the Internal Database for filenames.

DESCRIPTION:
Filenames part of the Internal Database is full. Data Protector is unable to write
information about files into the database.
ACTION:
Check the database usage and extension files configuration for filenames
part of database. You should either configure additional
extension module files or cleanup the database.
It is possible that your database has some obsolete data, which can
be removed. You should run filename purge and see if you get some
space back.
MESSAGE:
[12:1171] Too many objects match specified filters.

DESCRIPTION:
Copy Session Manager can copy only a certain number (default 500)
of objects in one copy session. If more objects match specified
filters then remainder of them will not be copied.
ACTION:
* Tighten criteria in filters so that fewer objects are selected.

* Increase the global variable CopyAutomatedMaxObjects.
MESSAGE:
[12:1172] Too many objects match specified filters.

DESCRIPTION:
Copy Session Manager can consolidate only a certain number (default 500)
of objects in one consolidation session. If more objects match specified
filters then remainder of them will not be copied.
ACTION:
* Tighten criteria in filters so that fewer objects are selected.

* Increase the global variable ConsolidateAutomatedMaxObjects.
MESSAGE:
[12:1176] Data Protector is in maintenance mode! No BACKUP, RESTORE, COPY or other writable
sessions are allowed. Only READONLY queries to internal database are permitted.
DESCRIPTION:
Data Protector is in maintenance mode - all writable operations are rejected!
ACTION:
* To stop the maintenance mode run: "omnisv -maintenance -stop" from CLI.
MESSAGE:
[12:1223] Cannot remove pool.

Pool is used as default pool for device(s).
DESCRIPTION:
You cannot remove a pool that is used as the default pool for logical
devices.
ACTION:
Move logical devices to another pool.
MESSAGE:
[12:1235] Cannot group specified medium in magazine.
DESCRIPTION:
One of specified media cannot be used as part of magazine.
Possible causes:
* Specified medium is already part of magazine
* Specified medium is not Data Protector medium
* Specified medium does not belong to specified

magazine pool
* Specified medium not currently in library
* Specified medium is in library which
does not support magazine media
* All specified media are not in same library
ACTION:
Specify only media with following requirements:

* all media are in same library which supports
magazine media
* all media have to be Data Protector media
* no media should be part of existing magazine
MESSAGE:
[12:1236] Cannot move/modify single medium of magazine.
DESCRIPTION:
Data Protector does not allow move/modify operation

on single magazine medium. Magazine media are
treated as single entity.
ACTION:
You should perform move/modify operation on

complete magazine instead of single magazine
media.
MESSAGE:
[12:1243] Device not found.
DESCRIPTION:
BACKUP:
When adding/modifying an object to the backup specification, you tried to specify a
logical device that does not exist. Also, you may have renamed or deleted that
device.
RESTORE:
The restore requires a device which does not exist in the cell.
ACTION:
Specify a device that is configured in the cell.
MESSAGE:
[12:1256] Current object browsing not possible anymore.

Some information about object was removed from Internal Database.
Start browsing again from object level.
DESCRIPTION:
Object you are browsing was removed from Data Protector Internal Database.
These can be caused by media of object being overwritten or exported from
Data Protector cell.
ACTION:
You should try browsing again. You should refresh your restore view and
start browsing object from object level again.
MESSAGE:
[12:1259] The Catalog Database not in sync with the Media Management Database.
DESCRIPTION:
Data Protector detected objects in the Catalog Database which are not in sync with
Media Management database.
This can be caused due to different reasons:
* import of media was ungracefully stopped
* CDB or MMDB was loaded from text files (omnidbutil -readascii)
and were not synchronized
ACTION:
You should stop all actions in Data Protector (restore, backup) and run
omnidbutil -cdbsync <cell_manager> on the Cell Manager.
If you have centralized Media Management database you have to
run the command on the Cell Manager where cMMDB is located.
MESSAGE:
[12:1264] Medium currently in use by another process.
DESCRIPTION:
You tried to use a medium that is locked by either an executing process or a

process that terminated unsuccessfully.
ACTION:
If other Session Managers are running, you cannot use this medium until the
other Session Managers finish (or are terminated).
MESSAGE:
[12:1273] Magazine pool cannot use free pool.
DESCRIPTION:
You tried to configure/modify magazine pool to use free pool.
ACTION:
Data Protector does not support use of magazine pool and free pool feature at the same time. You
have to decide which feature is more important for you and choose only one of them.
MESSAGE:
[12:1274] Cannot remove free pool that is still in use.
DESCRIPTION:
You tried to remove a free pool that is still in use by other pools.
ACTION:
You should find out which pools of particular medium type are still using free pool (configuration
option of pool). You will be able to remove free pool only when you will disable this option for
all pools of particular media type.
MESSAGE:
[12:1275] Cannot move protected medium to free pool.
DESCRIPTION:
You tried to move protected medium to free pool.
ACTION:
Free pool can contain only free (unprotected) media. If you really want to move that medium to
free pool you will have to remove medium protection first (recycle medium).
MESSAGE:
[12:1276] Cannot move free medium to pool that uses free pool.
DESCRIPTION:
You tried to move free (unprotected) medium to pool that uses free pool.
ACTION:
You cannot move free medium to medium pool that uses free pool and has configured option to
automatically move free media to free pool. You can disable that pool option if you do not really
need it.
MESSAGE:
[12:1277] Cannot use Free pool as device default pool.
DESCRIPTION:
You have specified Free pool as device default pool. Free pool cannot be used for backup and
therefore cannot be used as device default pool.
ACTION:
You should specify regular pool as device default pool
MESSAGE:
[12:1304] The mountpoint/filesystem cannot be backed up. Unrecognized configuration.
DESCRIPTION:
The mountpoint/filesystem is not recognized. It needs to be configured

explicitly in the backup specification using "Manual Add".
ACTION:
Use the GUI to redefine this mountpoint/filesystem selection in the

backup specification with "Manual Add".
MESSAGE:
[12:1405] Device detection not possible for selected client.
DESCRIPTION:
Device detection is not possible for selected client.

This can be caused by several reasons:
* device detection is not supported for platform
(it is only supported for HP-UX 11.x and Windows systems)
* client systems is protected with access security and does not
allow agents to be started from your Cell Manager
ACTION:
* Check if your client system supports device detection.

* Check if client system has access limited to particular Cell Managers.
MESSAGE:
[12:1512] You do not have permission to abort a session.
DESCRIPTION:
Data Protector security has reported that you have no permission to abort the
session. If user belongs to a Data Protector class that has the Abort ACL
disabled, he will not be able to abort sessions belonging to other users.
ACTION:
Set the Abort ACL in the appropriate class.
MESSAGE:
[12:1583] Host is not in this cell.
DESCRIPTION:
When adding/modifying an object to the Backup Specification, you tried to get list of
available mountpoints for a host that is not configured in the cell.
ACTION:
Use the ... button to get the list of configured hosts.
Check if the Disk Agent software is installed on the host.
MESSAGE:
[12:1601] Handshaking error. Versions of the client and the Cell Manager do not match.
DESCRIPTION:
Internal compatibility check reported that the running GUI or command is

not compatible with the Cell Manager daemon.
ACTION:
Check the Data Protector release on the hosts and update the software.
MESSAGE:
[12:1602] Cannot access the Cell Manager system. (inet is not responding)
The Cell Manager host is not reachable or is not up and running
or has no Data Protector software installed and configured on it.
DESCRIPTION:
One of the Data Protector clients tried to connect to the Cell Manager but the connection failed.
ACTION:
Check if the Cell Manager host is up and running. Check if it is accessible on

the network (use ping command). If not, check the configuration of
network services and routing (use nslookup command).
Check if the Data Protector software is properly installed on the host. You can
use the command: telnet hostname 5555 . After 10 seconds the
Data Protector should respond with the version information to confirm that it
is ready.
MESSAGE:
[12:1604] Cannot reach the CRS on the Cell Manager system.

CRS on the Cell Manager host is not reachable or is not up and running.
DESCRIPTION:
One of the Data Protector clients tried to connect to the CRS of the Cell Manager but the
connection failed.
ACTION:
Check if the CRS on the Cell Manager host is up and running. Use the command
omnisv -status on HP-UX, Solaris or Linux Cell Manager or
omnisv.exe -status on Windows Cell Manager.
To start the Data Protector daemons on the Cell Manager host use the command
omnisv -start on HP-UX, Solaris or Linux Cell Manager or
omnisv.exe -start on Windows Cell Manager.
MESSAGE:
[12:1610] Parameter string is too long.
DESCRIPTION:
Action response is too long (exceeds the internal limits)
ACTION:
This message means that the output of low level query is bigger than the
limit. Split the command into several commands in order to use less
resources.
MESSAGE:
[12:1618] Maximum number of Session Managers allowed is currently running.
DESCRIPTION:
Too many concurrent sessions running.
ACTION:
Use the monitor GUI or the omnistat command to check the number of
currently executing sessions. Abort any unnecessary sessions. Stop the Cell
Manager (using the omnisv -stop command) and restart the Cell Manager
(using the omnisv -start command). This will terminate all active
GUIs and command-line interfaces.
MESSAGE:
[12:1625] Import host failed.
DESCRIPTION:
The host information cannot be added/updated in the Cell Manager configuration file.
ACTION:
* Please check that the Data Protector services on the Cell Manager computer are running.
* Also check that Data Protector Inet service on the remote computer is running
(use: telnet <remote computer> 5555 to see if the service responds).
* Make sure that the remote client is not already part of another cell.
Afterwards use Data Protector GUI or omnicc -import_host command to manually import
the client to the selected Cell Manager.
MESSAGE:
[12:1629] Host is unavailable.

Cannot change config files.
DESCRIPTION:
When exporting a host from a cell, it was not reachable. The host was
properly exported only on the Cell Manager side.
ACTION:
Check if the host is connected to the network and reachable.
Problem will occur when you will try to import this host to another cell. You
must delete the cell_server file on the host (on HP-UX or Solaris this is in
/etc/opt/omni/client/).
On Windows systems, delete the string in HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-
Packard\OpenView\OmniBackII\Site\CellManager.
MESSAGE:
[12:1639] Error contacting the cluster target system.

Cluster information cannot be retrieved.
DESCRIPTION:
For successful import of a cluster, cluster node or cluster virtual server,

Data Protector should be installed on all nodes as cluster aware and all nodes
should be up and running.
ACTION:
Check if all nodes of the cluster are running and that Data Protector is configured
on all of them as cluster aware.
You can check if the cluster is properly defined and running by opening the Cluster
Administrator:
"Start" -> "Programs" -> "Administrative Tools" -> "Cluster Administrator"
Check if all nodes are running and that Data Protector resources are up and running. Also
check the integrity of the cluster.
You can check if Data Protector is configured as cluster aware by opening the registry
editor (regedt32.exe) and check the entry under:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\OmniBackII\Common.
There should be a REG_DWORD value:
ClusteringEnabled
set to 1.
If this is not the case, Data Protector is not configured in cluster aware mode. In this case
upgrade or reinstall Data Protector according to the documentation.
MESSAGE:
[12:1640] The cluster target system was contacted, but no information was returned.
DESCRIPTION:
The cluster structure could not be read.

ACTION:
Administrator:
ClusteringEnabled
set to 1.
MESSAGE:
[12:1641] The cluster target system was contacted, the information was returned, but it has an
unsupported format.
DESCRIPTION:
There was an error in protocol or some other system error.

ACTION:
This problem most probably occurred because of a system failure. First try the import action
again. If the problem persist, perform the following actions.
Administrator:
ClusteringEnabled
set to 1.
MESSAGE:
[12:1642] The cluster target system was contacted, the information was returned, but one or more
nodes does not have Data Protector installed.
DESCRIPTION:

ACTION:
Administrator:
ClusteringEnabled
set to 1.
MESSAGE:
[12:1643] The cluster target system was contacted, the information was returned, but one or more
nodes does not have Data Protector configured as cluster aware.
DESCRIPTION:

ACTION:
Administrator:
ClusteringEnabled
set to 1.
MESSAGE:
[12:1644] The cluster target system was contacted, the information was returned, but the system
specified to be imported was not found as part of the cluster.
DESCRIPTION:
To import a specific target system in the Data Protector cluster client view, the target
system should be part of the cluster. The system specified is apparently not part
of the cluster upon which the import function was called.

ACTION:
Check if the target system specified is spelled correctly.
Check if the target system is a part of the cluster you are importing from. You can
do this by opening the Cluster Administrator:
and check whether the system specified appears to be up and running within the cluster.
MESSAGE:
[12:1645] Format of RMAN channel names is not correct.
DESCRIPTION:
You have entered wrong format for RMAN channel names.

It has to be in following format ORACLE8LIST<SID_p:%t>.dbf
where ORACLE8LIST is the name of Oracle Backup Specification.
Example:
If name of your Oracle Backup Specification is TEST and

ORACLE_SID name is STRUNA then it has to be TEST<STRUNA_p:%t>.dbf.
ACTION:
Rewrite RMAN channel name.
MESSAGE:
[12:1652] Connect to Cell Manager failed.
DESCRIPTION:
Version of the Cell Manager is not compatible with this version of User Interface.
ACTION:
On your local host, install a User Interface version which is compatible with the
version of the installed Cell Manager. Typically these versions have to be identical.
MESSAGE:
[12:1653] Import of some cluster nodes/virtual servers failed.
DESCRIPTION:

Data Protector should be installed on all nodes as cluster aware and
all nodes and virtual servers should be up and running.
ACTION:
on all of them as cluster aware. Also check that all cluster virtual servers are online.
Administrator:
ClusteringEnabled
set to 1.
MESSAGE:
[12:1655] Connection to storage appliance failed.
DESCRIPTION:
Cell Manager could not connect to the storage appliance using the information you provided.
ACTION:
Check that your storage appliance is running and online and that it is properly attached to you
LAN.
Also check if your firewall configuration blocks connections from the Cell Manager to your storage
appliance.
Note that while it was not possible to establish a connection from Cell Manager to storage
appliance
it could still be possible that the Data Protector disk/media agent can connect to the storage
appliance. The connection information you provided will be saved. You can check them for errors
and then try to go on with the configuration process.
MESSAGE:
[12:1656] Automigration support missing on Cell Manager.
DESCRIPTION:
The connection information you entered for the VLS device could not be checked because the Cell
Manager
does not have the VLS Automigration feature installed.
ACTION:
You can choose to ignore this problem. In this case you need to make sure that the VLS device
connection
information you entered is correct before proceeding.
To enable the Cell Manager to check VLS device connection information install the VLS
Automigration
package on the Cell Manager.
MESSAGE:
[12:1660] Import Installation Server failed.
DESCRIPTION:
The Installation Server information cannot be added/updated in the Cell Manager configuration
file.
ACTION:
* Please check that the Data Protector services on the Cell Manager computer are running.
* Also check that Data Protector Inet service on the remote computer is running
* Install that host as Data Protector Installation Server.
MESSAGE:
[12:1664] Connection to the IAP could not be established.
DESCRIPTION:
The check of the connection to the IAP failed.
ACTION:
The IAP will be imported anyhow. Make sure you check the following settings before you use the
IAP.
- Servername (Is the entered servername correct?)

- User (Does the user is an Application user on the IAP?)
- Port (Does your firewall allow connection through this port?)
- Password (Check if you typed the password correct.)
- Certificate (Did you use the right certificate?)
MESSAGE:
[12:1665] Import of the Hyper-V server could not be performed.
DESCRIPTION:
The check of the connection to the Hyper-V server failed.
ACTION:
The Hyper-V server could not be imported. Make sure you check the following settings before you
try again.

- User (Is the user a user on the Hyper-V server?)
- Password (Check if you typed the password correctly.)
- Is the MS Volume Shadow Copy Integration agent installed on the server?
- Is the Virtual Enviroment Integration agent installed on the server?
MESSAGE:
[12:1666] Connection to the VMware server could not be established.
DESCRIPTION:
The check of the connection to the VMware Server failed.
ACTION:
The Server will be imported anyhow. Make sure you check the following settings before you use the
server.

- User (Is the user a valid user of the ESX(i)/vCenter Server?)
- Password (Check if you typed the password correctly.)
- Certificate (Did you use the right certificate?)
MESSAGE:
[12:2001] The client is not a member of any cell.
DESCRIPTION:
The client is not able to determine its Cell Manager. Either the client was
exported from the cell or client's configuration is corrupted.
ACTION:
Import the client to a cell. If the client already appears on the client list
of the cell, export it first (delete the client without uninstalling the
Data Protector software).
If you need to use GUI or CLI from this client to complete the procedure,
you need to specify the Cell Manager with the -server command line option.
MESSAGE:
[12:2024] No clients with Media Agent available
DESCRIPTION:
The cell manager cannot find any client systems equipped for communcation with backup devices.
ACTION:
* Make sure that client hosts connected to backup devices in your current cell do have media agent
software installed.
* In a Manager-of-Managers environment, check that your Manager GUI is connected to the cell
hosting your media agent clients.
MESSAGE:
[12:2025] No clients with NDMP Media Agent available
DESCRIPTION:
The cell manager cannot find any client systems equipped for communcation with NDMP backup
devices.
ACTION:
* Make sure that client hosts connected to NDMP backup devices in your current cell do have media
agent software installed.
* In a Manager-of-Managers environment, check that your Manager GUI is connected to the cell
hosting your media agent clients.
MESSAGE:
[12:3038] IPC No more available ports in the range specified by OB2PORTRANGESPEC or OB2PORTRANGE
DESCRIPTION:
The process failed to allocate the listen port. This typically happens
when using port ranges via the OB2PORTRANGESPEC omnirc variable.
It is also possible that the process was not allowed to create a listen
port due to restrictions imposed by firewall software on the system.
ACTION:
* If there is a firewall on the system, verify that the process

is allowed to accept incoming connections.
* When using port ranges, make sure that the port range for the
service/daemon process is at least 5 ports wide. For other processes
the number of ports in the range that must be available depends on
how many processes will run at the same time.
Also, make sure that there are no well-known ports in a port range
for any process.
MESSAGE:
[12:3184] Licensing system corrupted
DESCRIPTION:
Licensing system corrupted
ACTION:
Use omnicc -query to reload license info
MESSAGE:
[12:5000] ___________________________________________________________
The number of configured clients (num) is greater
than the number of client host licenses (num).
The licenses may have expired have expired.
Run the command omnicc -query to view the licensing

summary report.
___________________________________________________________
DESCRIPTION:
The runtime check for the number of configured clients failed.
ACTION:
If the configuration is not confirmed, run omnicc. Check with the

omnicc -query if the license(s) are expired, or too many hosts are
configured. If so, buy additional licenses or deinstall/exclude some
hosts.
DESCRIPTION:
The runtime check for the number of configured clients failed.
ACTION:
If the configuration is not confirmed, run omnicc. Check with the

omnicc -query if the license(s) are expired, or too many hosts are
configured. If so, buy additional licenses or deinstall/exclude some
hosts.
MESSAGE:
[12:5107] Error sending e-mail: MAPILogon failed.
DESCRIPTION:
Data Protector was unable to send e-mail because MAPILogon call returned error.
Data Protector needs a MAPI profile named OmniBack
in order to send e-mail notification.
ACTION:
Check if OmniBack profile exists on the Cell Manager that

tried to send e-mail. The profile should be configured for the user
under which account the CRS service is running.
MESSAGE:
[12:8010] Internal error.
DESCRIPTION:
An internal error inside Data Protector has happened.

In case of MS SQL backup or configuration it is possible that internal error
is caused by MS SQL Server or because the MS SQL Server is not installed on the
client system.
ACTION:
In case of MS SQL backup or configuration, see if the MS SQL Server is properly

installed and configured on the client system.
Otherwise:
1. Check debug.log file.
2. Restart OmniInet service on client with debug option and see the debug
file for details.
MESSAGE:
[12:8150] Security violation: Host not in local cell.
DESCRIPTION:
Host is not a member of this Cell Manager.
ACTION:
Import host to be a part of this Cell Manager.
MESSAGE:
[12:8151] Script not found on host.
DESCRIPTION:
The script that OmniInet has to execute on the local host is not found.
ACTION:
Check the Data Protector installation on the selected host.

Maybe not all integration modules are installed properly.
MESSAGE:
[12:8200] The path name of the Sybase isql command specified in the configuration does not exist.
DESCRIPTION:
Data Protector cannot find the Sybase isql command.

It could be that Sybase Server Home directory is wrong.
ACTION:
1. Check existence and permissions of the Sybase Server home directory

on the client.
2. Check if there is enough space on the Cell Manager in /etc/opt/omni/server/integ/config/Sybase
(<Data_Protector_home>\Config\Server\Integ\Config\Sybase on Windows).
If there is enough space, check if the parameter ISQL_path exist in file
hostname.domain%INSTANCE_NAME and
if it is containing the correct path for isql command.
3. Contact your database administrator in order to get information about
configuration of the Sybase Server.
MESSAGE:
[12:8201] Home directory of the Sybase database is not set.
DESCRIPTION:
Home directory of the Sybase database is not set. The home directory can found in
SYBASE shell environment variable.
ACTION:
Check if there is enough space on the Cell Manager in /etc/opt/omni/server/integ/config/Sybase

If there is enough space, check if the parameter Home_Dir in file hostname.domain%INSTANCE_NAME
exist and
if it is containing the correct path to the Sybase home directory.
MESSAGE:
[12:8202] SA_PASSWORD not set.
DESCRIPTION:
Password for sybase administrator is not set.
ACTION:
Check if there is enough space on the Cell Manager in /etc/opt/omni/server/integ/config/Sybase .

If there is enough space, check if the parameter SA_password in file hostname.domain%INSTANCE_NAME
exist and
if it is containing the correct password.
MESSAGE:
[12:8203] The Data Protector Sybase configuration files cannot be created.
DESCRIPTION:
The configuration parameters:

- Sybase Server Home directory,
- Sybase ISQL command full path name,
- Password for the Sybase SA user.
cannot be written to the Data Protector configuration directory on the Cell Manager.
It is possible the /etc/opt/omni/server/integ/config/Sybase directory on the Cell Manager

(<Data_Protector_home>\Config\Server\Integ\Config\Sybase on Windows) is deleted or has wrong
permissions.
ACTION:

1. Check permissions of the /etc/opt/omni/server/integ/config/Sybase directory.
The directory should be owned by root and have 755 permissions.
2. Check if the Sybase Integration Module is correctly installed.
3. Check if there is enough space on client disks.
4. Start the configuration once more.

1. Check if directory <Data_Protector_home>\Config\Integ\Config\Sybase exists.
2. Check if the Sybase Integration Module is correctly installed.
MESSAGE:
[12:8204] The configuration directory cannot be updated or created.
DESCRIPTION:
The Data Protector repository with configuration of your Sybase database

instances cannot be updated or created.
ACTION:
Start the configuration. Check if the configuration was done successful.
If you got this error once more, then take the following actions:
1. Check permissions, existence and contents of Data Protector repository with

configuration of your Sybase Server.
The repository is on the Data Protector Cell Manager.
For HP-UX 10.x/11.x and Solaris Cell Managers, the repository is in directory:
/etc/opt/omni/server/integ/config/Sybase.
On Windows Cell Managers, the repository is in directory:
<Data_Protector_home>\Config\Integ\Config\Sybase.
2. Re-install Data Protector Sybase Integration Module to the client.
MESSAGE:
[12:8205] The selected Sybase Server has never been configured.
DESCRIPTION:
The Data Protector repository with list of Sybase Servers does

not exist.
ACTION:

list of Sybase Servers.
For HP-UX 10.x/11.x and Solaris Cell Manager, the repository is in directory:
/etc/opt/omni/server/integ/config/Sybase
On Windows Cell Manager, the repository is in directory:
<Data_Protector_home>\Config\Server\Integ\Config\Sybase
MESSAGE:
[12:8206] The selected Sybase Server has never been configured.
DESCRIPTION:
The Data Protector repository with list of Sybase Servers does

not contain the name of the selected Sybase Server.
ACTION:

list of Sybase Servers.
For HP-UX 10.x/11.x and Solaris Cell Manager, the repository is in directory:
/etc/opt/omni/server/integ/config/Sybase
<Data_Protector_home>\Config\Server\Integ\Config\Sybase
MESSAGE:
[12:8207] On HP-UX or Solaris hosts:

The soft link for libob2syb.sl from Sybase Library Directory to Data Protector does not exist.
DESCRIPTION:
Data Protector found out that there is no link to Data Protector libob2syb.sl
shared library with backup interface in the lib subdirectory of the Sybase Home
directory. The link could be deleted.
ACTION:
1. Check if there is a libob2syb.sl library in /opt/omni/lib

(/usr/omni/lib on non-HP-UX 10.x/11.x or Solaris).
If there is no such file, check if device that contains /opt/omni/lib is
full (or almost full) and in case there is enough space, try to push the
Sybase Integration Module to the client.
2. Check if there is a soft link from <SYBHOME>/lib/libob2syb.sl to

/opt/omni/lib/libob2syb.sl (/usr/omni/lib on non HP-UX 10.x/11.x or Solaris).
3. If there is no such link, create it with command:

ln -s /opt/omni/lib/libob2syb.sl <SYBHOME>/lib/libob2syb.sl
For non HP-UX 10.x/11.x or Solaris clients the command is:

ln -s /usr/omni/lib/libob2syb.sl <SYBHOME>/lib/libob2syb.sl
Where <SYBHOME> is the Sybase Home directory
On Windows host:
The libob2syb.dll does not exist in the Sybase Library directory.
DESCRIPTION:
Data Protector found out that there is no Data Protector libob2syb.dll

in the lib subdirectory of the Sybase Home directory. The file could be deleted.
ACTION:
1. Check if there is a libob2syb.dll in <Data_Protector_home>\bin directory. If there is no

file, check if device that contains <Data_Protector_home>\bin is full (or almost full).
2. If there is a file libob2syb.dll, copy it to the Sybase Library directory.
MESSAGE:
[12:8208] The password for the Sybase SA user is wrong or the Sybase Server is not running.
DESCRIPTION:
Data Protector failed to connect to the Sybase Server. It could be that

either the password for the Sybase SA user is wrong or the Sybase Server is
not running.
ACTION:
Check if the Sybase Server is running.
Check if the processes dataserver and backupserver are running.

If the Sybase Server is not running, start it.
Check also if the specified password for the Sybase administrator is correct.
MESSAGE:
[12:8209] Sybase Server home directory specified in the configuration does not exist.
DESCRIPTION:
Data Protector cannot find the Sybase Server home directory.

The Sybase Server home directory can be read from $SYBASE environment
variable on the client where the Sybase Server is located.
ACTION:
1. Check existence and permissions of the Sybase Server home directory

on the client node.
configuration of the Sybase Server.
MESSAGE:
[12:8210] Some files from the Data Protector Sybase Module are missing.
DESCRIPTION:
The /opt/omni/lib/libob2syb.sl (/usr/omni/lib/libob2syb.sl on non HP-UX 10.x/11.x or Solaris ) or

/opt/omni/lbin/sybackup.sh.temp (/usr/omni/lbin/sybackup.sh.temp on non HP-UX 10.x/11.x or
Solaris)
is missing
(The libob2syb.sl is shared library and sybackup.sh.temp is a template script)
ACTION:
On HP-UX 10.x/11.x or Solaris clients:
Check if there is a file libob2syb.sl in directory /opt/omni/lib .
If it is missing, push the Sybase Integration Module to the host.
On other clients:
Check if there is a file libob2syb.sl in directory /usr/omni/lib .
If it is missing, push the Sybase Integration Module to the host.
MESSAGE:
[12:8211] The Sybase Backup Server is not running.
DESCRIPTION:
Data Protector failed to find the Sybase Backup Server. It could be that
it is not running.
ACTION:
Check if the Sybase Backup Server is running with command:

ps -ef|grep sybase
Check if the processes dataserver and backupserver are running.

If the Sybase Backup Server is not running, start it.
MESSAGE:
[12:8212] Sybase Server system table 'sysdatabases' does not exist.
DESCRIPTION:
Data Protector cannot find the 'sysdatabases' table in the Sybase Server.
ACTION:
Check if the Sybase Server has sysdatabases system table.

In order to check this do the following:
a) Login to the Sybase client as the Sybase user
b) Start the following isql command:
1> select * from sysdatabase;
2> go
c) Follow Sybase instructions on how to recreate the sysdatabases
table.
MESSAGE:
[12:8213] The Sybase Server is not running.
DESCRIPTION:
Data Protector failed to find the Sybase Server. It could be that

it is not running.
ACTION:
Check if the Sybase Server is running with command:

ps -ef|grep sybase
Check if there is a dataserver process running.

If the Sybase Backup Server is not running, start it.
MESSAGE:
[12:8214] No permissions to touch file in Data Protector tmp directory.
DESCRIPTION:
User Sybase does not have permissions to create file in Data Protector
temporary directory (/var/opt/omni/tmp on HP-UX or Solaris, and /usr/omni/tmp on
other OS).
ACTION:
Change the permissions on Data Protector temporary directory to drwxrwxrwx (777).
MESSAGE:
[12:8215] Sybase home directory does not exist.
DESCRIPTION:
Data Protector could not find the Sybase home directory.
ACTION:
Reconfigure the Sybase integration with full Sybase home directory.
MESSAGE:
[12:8216] Sybase isql path is not correct.
DESCRIPTION:
Data Protector could not find the isql.exe binary.
ACTION:
Reconfigure the Sybase integration with the full isql.exe path.
MESSAGE:
[12:8217] Sybase user is not set.
DESCRIPTION:
Sybase user that will be used to start backup is not set.
ACTION:
Reconfigure the Sybase integration with the correct Sybase user name.
MESSAGE:
[12:8218] Unable to copy libob2syb.dll to the Sybase library directory.
DESCRIPTION:
Data Protector is not able to copy libob2syb.dll library to

%SYBASE%\lib\ directory.
ACTION:
Copy <Data_Protector_home>\bin\libob2sybase.dll library to

%SYBASE%\bin\libob2sybase.dll.
MESSAGE:
[12:8219] Unable to start isql
DESCRIPTION:
Data Protector is not able to start $SYBASE/bin/isql.

Either the Sybase user or its password is incorrect.
ACTION:
Reconfigure the Sybase integration with the correct Sybase user name and its password.
Check if the Sybase Server is running.
MESSAGE:
[12:8220] Cannot find sybase binaries in Sybase home directory
DESCRIPTION:
Data Protector is not able to find Sybase binaries in Sybase home directory.
ACTION:
Check if the sybase home directory is set correctly.
MESSAGE:
[12:8300] The Oracle SQL*Net login information to the database instance is not correct or database
is not running.
DESCRIPTION:
One of the Oracle SQL*Net login information to the target or to recovery catalog database
in the configuration are not correct or databases are not running.
The Data Protector cannot connect target or Oracle RMAN Recovery database
with login information specified in the configuration.
ACTION:
1. Check if Oracle RMAN Recovery database and Oracle Target database

instances are running.
2. Check if Oracle SQL*Net listeners are running and they are correctly
configured. See Oracle documentation how to configure Oracle listeners.
3. Check if Oracle SQL*Net tnsnames.ora file is in
<ORACLE_HOME>/network/admin directory and it is correctly configured.
See Oracle documentation how to configure Oracle tnsnames file.
4. Check if your Oracle installation uses TNS_ADMIN variable for
Oracle networking admin directory. If your Oracle installation uses
that variable the export that variable in
/etc/opt/omni/oracle8/$ORACLE_SID/.profile file.
5. Login as root user to the client machine, export ORACLE_HOME and ORACLE_SID,
and start the Oracle SQL*Plus.
Try to connect to Oracle databases with login information specified in
the configuration.
The login information must be in the following format:
<user>/<password>@<ORACLE_TNS_SERVICE_NAME>
EXAMPLE:
# export ORACLE_HOME=/oracle
# export ORACLE_SID=SID
# $ORACLE_HOME/bin/sqlplus
. . .
. . .
SQL> connect rman/rman@ORACLE
MESSAGE:
[12:8301] Oracle Server home directory not found.
DESCRIPTION:
Data Protector cannot find the Oracle Server home directory.

The specified or configured Oracle Server home directory doesn't exist on
the client host.
ACTION:
1. Check existence and permissions of Oracle Server home directory

(<ORACLE_HOME>) on the client node.
configuration of Oracle Server.
3. Update the existing configuration or configure the integration with the
correct information about Oracle Server home directory (<ORACLE_HOME>).
MESSAGE:
[12:8302] It is not possible to connect to Oracle Database Server.
DESCRIPTION:
It is possible that Oracle Database Server is not running or command "sqlplus"

doesn't exist in the <ORACLE_HOME>/bin directory on the Oracle host.
ACTION:
Start the Oracle Server processes and check <ORACLE_HOME>/bin/sqlplus command.
MESSAGE:
[12:8303] Oracle RMAN register command was failed. Oracle RMAN process which register the target
database into the Oracle RMAN Recovery database failed.
DESCRIPTION:
Oracle RMAN process which register the target database to the Oracle RMAN
Recovery database failed. This is an Oracle process.
ACTION:
1. Check if database instances of target and RMAN Recovery database are
running.
2. Check if database name of target database is correct. It has to be same
as name specified in the Oracle init file.
4. Check if login information for RMAN Recovery database is correct.
See Oracle documentation how to configure Oracle user in RMAN
Recovery database.
5. Check if login information for target database is correct. The user in
the connection has to have at least 'sysoper' permissions.
See Oracle documentation how to configure Oracle backup owner in
target database.
6. Check if Oracle RMAN Recovery database is correctly created.

See Oracle documentation how to create Oracle RMAN Recovery database.
MESSAGE:
[12:8304] Data Protector cannot find the Oracle SQL*Net login information for Oracle RMAN Recovery
database or Oracle target database.
DESCRIPTION:
The Data Protector repository with configuration of your Oracle database

instances does not contain Oracle SQL*Net connections strings for
Oracle RMAN Recovery database or Oracle target database.
The repository was probably deleted.
ACTION:

configuration of your Oracle database instances.
For UNIX Cell Manager, the repository is in directory:
/etc/opt/omni/server/integ/config/Oracle8.
<Data_Protector_home>\Config\Server\Integ\Config\Oracle8.
2. Re-install Data Protector Oracle Integration Module to the client.
MESSAGE:
[12:8305] No Oracle Recovery Manager (RMAN) executable found in bin directory of Oracle Server
home directory.
DESCRIPTION:
Data Protector cannot find the Oracle Recovery Manager (rman or rman80.exe)
executable in bin directory of Oracle Server home directory.
The Oracle Recovery Manager executable (rman or rman80.exe) is needed to
successfully complete the configuration process.
The Oracle Server home directory can be read from <ORACLE_HOME>
ACTION:
1. Check the "Oracle Server home directory" (<ORACLE_HOME>) parameter in the

configuration.
2. Login to the client machine and check for <ORACLE_HOME>/bin/rman on
UNIX clients or check for <ORACLE_HOME>\bin\rman.exe on NT clients.
MESSAGE:
[12:8306] The configuration on the Cell Manager cannot be created.
DESCRIPTION:

instances cannot be created.
ACTION:

MESSAGE:
[12:8307] The configuration on the Cell Manager cannot be updated.
DESCRIPTION:

instances cannot be updated.
ACTION:

MESSAGE:
[12:8308] Oracle RMAN resync command was failed. Oracle RMAN process which resync the target
database with the Oracle RMAN Recovery database failed.
DESCRIPTION:
Oracle RMAN process which resync the target database with the Oracle RMAN
Recovery database failed. This is an Oracle process.
ACTION:
1. Check if database instances of target and RMAN Recovery database are
running.
2. Check if database name of target database is correct. It has to be same as
name specified in the Oracle init file.
3. Check if the current incarnation is registered in the recovery catalog.
4. Check if login information for RMAN Recovery database is correct.
See Oracle documentation how to configure Oracle user in RMAN Recovery
database.
5. Check if login information for target database is correct. The user
in the connection has to have at least 'sysoper' permissions.
See Oracle documentation how to configure Oracle backup owner in target
database.
6. Check if Oracle RMAN Recovery database is correctly created.
See Oracle documentation how to create Oracle RMAN Recovery database.
MESSAGE:
[12:8309] Oracle shared server process connection was specified.

Oracle requires a dedicated server process connection.
DESCRIPTION:
The service specified in the connection string is configured to use Oracle shared server process.
The connection for backup/restore purposes must be using Oracle dedicated server process.
ACTION:
Specify a net service name that is configured to use a dedicated server.

Specifically, the net service name value should include the SERVER=DEDICATED clause in the
connect descriptor.
For a complete description of the net service name, see the Oracle Net Services Administrator’s
Guide.
MESSAGE:
[12:8310] Oracle is not linked with the Data Protector library for backup.
In case of 32-bit executables the name is /opt/omni/lib/libob2oracle8.sl.
In case of 64-bit executables the name is /opt/omni/lib/libob2oracle8_64bit.sl.
DESCRIPTION:
ACTION:
Shutdown the Oracle Server and link it with the Data Protector library
as described in "Linking Oracle with the Data Protector Database Library"

of the "HP Data Protector Integration Guide for Oracle and SAP".
MESSAGE:
[12:8311] ORACLE configuration error.
DESCRIPTION:
ORACLE executable returned an error that cannot be handled inside Data Protector.
ACTION:
Try and find out what might be the problem from the output of the ORACLE
executable which was presented in the configuration.
MESSAGE:
[12:8312] Bad Oracle database name.
DESCRIPTION:
The Oracle database name, which you are trying to configure, does not match the
Oracle database name pointed to by the connection string.
ACTION:
Repeat the configuration using the correct instance name for the given Oracle service name.
MESSAGE:
[12:8314] The selected Oracle database instance has never been configured.
DESCRIPTION:
The selected Oracle database instance has never been configured.

The Data Protector repository with list of Oracle databases does
not contain the name of selected Oracle database (<DB_NAME | INSTANCE_NAME>).
ACTION:
MESSAGE:
[12:8315] Listener for the selected Oracle database is not running.
DESCRIPTION:
The Data Protector cannot connect to the selected Oracle database.
ACTION:
- Start the listener

- Try to ping the selected Oracle database with the command 'tnsping <SID>'
MESSAGE:
[12:8316] Listener for the selected Oracle database is not correctly configured.
DESCRIPTION:
The Data Protector cannot connect to the selected Oracle database.
ACTION:
- Edit listener config files

- Restart listener
- Try to ping the selected Oracle database with the command 'tnsping <SID>'
MESSAGE:
[12:8324] This Oracle Server instance is not configured.
DESCRIPTION:

instances is empty.
ACTION:

3. In case of a cluster environment and trying to run a util_cmd in the console,

please be sure OB2BARHOSTNAME is correctly defined as the virtual hostname of the cluster.
MESSAGE:
[12:8325] Cannot connect to the database "as sysdba" with target login.
DESCRIPTION:
SQL*Plus command "connect <login>/<password> as sysdba" failed.
ACTION:

2. Check if you run "grant sysdba to <login>" on the target database.
3. Check if you run "grant sysoper to <login>" on the target database.
4. Check if ora<SID>.ini file has "remote_password_file = exclusive".
5. Check if password specified in configuration is the same as specified
for "orapwd file=... password=..." command.
6. Check if user <login> has the same password as password specified
for "orapwd file=... password=..." command.
MESSAGE:
[12:8326] The location of the backup control file specified in the configuration does not exist.
DESCRIPTION:
Data Protector cannot find the location directory of the backup control file.
ACTION:

MESSAGE:
[12:8328] Unable to update Oracle's configuration files.
DESCRIPTION:
The Data Protector configuration process is unable to update the configuration

files that reside on the Cell Manager.
ACTION:
Please take following actions:

a list of Oracle configuration files.
/etc/opt/omni/server/integ/config/Oracle8/.
2. Delete the configuration files of a given Oracle installation and try to

configure Oracle client again.
MESSAGE:
[12:8345] Binary util_orarest is missing. Cannot get information from the remote host.
DESCRIPTION:
Check if Oracle integration is installed on the target host.

This error most likely occurs if you are trying to restore a ZDB made with OmniBack 4.x.
ACTION:
Set the environment variable OB2_ORARESTHOSTNAME=<target_host> to specify different target

hostname,
where you want to restore your database. In the ZDB case this must be the application host.
After setting the variable, restart Data Protector GUI.
Refer to the Data Protector Oracle integration troubleshooting section
for details.
MESSAGE:
[12:8347] IPC Connection to host failed.
DESCRIPTION:
This error most likely occurs in two situations:
1. Data Protector Inet is not running.
2. The target host is not online.
ACTION:
Take the following actions:

1. Check Data Protector installation.
2. In case of disaster recovery, set the environment variable OB2_ORARESTHOSTNAME=<target_host>
to specify different target hostname, where you want to restore your database.
After setting the variable, restart Data Protector GUI.
Refer to the Data Protector Oracle integration troubleshooting section
for details.
MESSAGE:
[12:8400] Data Protector cannot find home directory of Oracle EBU component (<OBK_HOME> or
<EBU_HOME>).
DESCRIPTION:

instances does not contain home directory of Oracle EBU component.
ACTION:

MESSAGE:
[12:8401] No Oracle EBU executable found in bin directory of Oracle EBU home directory.
DESCRIPTION:
Data Protector cannot find the Oracle EBU executable (ebu/obackup on UNIX or
ebu.exe on NT) in bin directory of Oracle EBU home directory.
The Oracle EBU executable is needed to successfully complete the configuration
process. The Oracle EBU home directory can be read from <EBU_HOME> (for EBU
version 2.2) or <OBK_HOME> (for EBU version 2.1 and 2.0) environment
variable on the client where EBU is installed.
ACTION:
1. Check the "Oracle EBU home directory" parameter in the configuration.

2. Login to the client machine as oracle user and check for:
2.1 <OBK_HOME>/bin/obackup for UNIX clients running EBU 2.0 or EBU 2.1
2.2 <EBU_HOME>/bin/ebu for UNIX clients running EBU 2.2
2.2 <EBU_HOME>\bin\ebu.exe for NT clients running EBU 2.2
MESSAGE:
[12:8402] The Oracle EBU executable has disabled SHLIB_PATH.
DESCRIPTION:
The obackup command cannot load the Data Protector shared library.
ACTION:
Run "chatr +s enable ${OBK_HOME}/bin/*".
MESSAGE:
[12:8403] The Oracle SQL*Net login information to the database instance is not correct or database
is not running.
DESCRIPTION:
The Oracle SQL*Net login information to target or to Oracle EBU

catalog database specified in the configuration are not correct or
databases are not running. The Data Protector cannot connect target or
Oracle EBU catalog database with login information specified in the
configuration.
ACTION:
1. Check if database instances are running.

configured.
See Oracle documentation how to configure Oracle listeners.
<ORACLE_HOME>/network/admin directory and
it is correctly configured.
/etc/opt/omni/oracle/$ORACLE_SID/.profile file.
5. Login as root user to the client machine, export ORACLE_HOME and ORACLE_SID,
Try to connect to Oracle databases with login information specified
in the configuration.
EXAMPLE:
. . .
. . .
SQL> connect obk/obk@CATALOG_DB
SQL> select * from obk_database;
SQL> connect sys/manager@TARGET_DB
SQL> select * from dba_tablespaces;
MESSAGE:
[12:8404] Oracle Server home directory specified in the configuration does not exist.
DESCRIPTION:

The Oracle Server home directory can be read from <ORACLE_HOME> environment
variable on the client where Oracle Server is installed.
ACTION:

2. Contact you database administrator in order to get information about
MESSAGE:
[12:8405] Unable to connect to Oracle Database Server.
DESCRIPTION:
It is possible that Oracle is not running or the command "sqlplus" doesn't

exist in the <ORACLE_HOME/bin directory on the SAP Client host.
ACTION:
Start the Oracle processes.
MESSAGE:
[12:8406] Oracle Configuration Command Script is not found.
DESCRIPTION:
ACTION:
Check the OCCS file.
MESSAGE:
[12:8407] Data Protector cannot find the Oracle SQL*Net login information for Oracle EBU catalog
database.
DESCRIPTION:

instances does not contain Oracle SQL*Net connections strings for Oracle
EBU catalog database.
ACTION:

MESSAGE:
[12:8408] Data Protector cannot find the Oracle SQL*Net login information for Oracle target
database.
DESCRIPTION:

instances does not contain Oracle SQL*Net connections strings for Oracle
target database.
ACTION:

MESSAGE:
[12:8409] Oracle EBU process of registration target database to the Oracle EBU Catalog database
failed.
DESCRIPTION:
Oracle EBU process of registration target database to the Oracle EBU

Catalog database failed.
This is an Oracle process.
ACTION:
1. Check if database instances of target and EBU Catalog database
are running.
2. Check if database name of target database is correct. It has to be same
as name specified in the Oracle init file.
4. Check if login information for EBU Catalog database is correct.
See Oracle documentation how to configure Oracle Catalog owner in the
EBU Catalog database.
5. Check if login information for target database is correct. The user in
the connection has to have at least 'sysoper' permissions.
See Oracle documentation how to configure Oracle backup owner in
target database.
6. If Oracle EBU Catalog database is not created then you have select
"Create Catalog Database" check-box and to specify password of Oracle
sys user for EBU Catalog Database in the configuration and to
restart the configuration.
MESSAGE:
[12:8410] The configuration directory cannot be created.
DESCRIPTION:
ACTION:
Try to create the configuration directory. Check the permission.
Start the configuration once more.
MESSAGE:
[12:8411] The configuration files cannot be created.
DESCRIPTION:
The options ORACLE_HOME, ConnectionString, Path of the SAP backup utilities

cannot be written to configuration directory.
ACTION:
Check the configuration directory. Try to create a file. Check the permission.
MESSAGE:
[12:8412] Oracle Parameter File (alias Oracle init file) specified in the configuration does not
exist.
DESCRIPTION:
Data Protector cannot find the Oracle Parameter File (alias Oracle init file)
specified in the configuration or there was no file entered at all.
ACTION:
By default, the Oracle Parameter file is located in dbs subdirectory of

Oracle Server home directory (<ORACLE_HOME>/dbs). The name of file is
"init<ORACLE_SID>.ora".

2. Check existence and permissions of Oracle Parameter file specified
3. Contact you database administrator in order to get information about
MESSAGE:
[12:8413] There is no dbname.
DESCRIPTION:
The configuration file with dbname doesn't exist.
ACTION:
Check in the configuration directory the file "dbname".
MESSAGE:
[12:8414] The selected Oracle database instance has never been configured.
DESCRIPTION:
The selected Oracle database instance has never been configured.

The Data Protector repository with list of Oracle database instances does not
contain the name of selected Oracle database instance (<ORACLE_SID>).
ACTION:

MESSAGE:
[12:8415] Data Protector cannot find the Oracle SQL*Net login information for Oracle EBU catalog
database or Oracle target database.
DESCRIPTION:

instances does not contain Oracle SQL*Net connections strings for Oracle EBU
catalog database or Oracle target database.
ACTION:

MESSAGE:
[12:8416] NOTE: This message is obsolete. Please add DDTS bug record if you get this error.
DESCRIPTION:
NOTE: This message is obsolete. Please add DDTS bug record if you get this error.
ACTION:
MESSAGE:
[12:8417] No ORACLE executable found in <ORACLE_HOME>\bin
DESCRIPTION:
ACTION:
Check the <ORACLE_HOME> parameter in the configuration. Executable

sqlplus not found in the <ORACLE_HOME>\bin directory.
MESSAGE:
[12:8418] <EBU_HOME>\bin\catalog.ebu file not deleted.
DESCRIPTION:
ACTION:
<EBU_HOME>\bin\catalog.ebu on the client host exists, but cannot be deleted.
Delete it and try to configure integration again.
MESSAGE:
[12:8419] Cannot open Oracle configuration file on client host

<Data_Protector_home>\config\oracle\ccs\<ORACLE_SID>
DESCRIPTION:
ACTION:
Check if the file exists on the client host.

Try to delete it and start again with the configuration process.
MESSAGE:
DESCRIPTION:
ACTION:
MESSAGE:
DESCRIPTION:
ACTION:
MESSAGE:
DESCRIPTION:
ACTION:
Internal error inside util_oracle.exe has happened. Restart OmniInet service

on client with debug option and see the debug file for details.
MESSAGE:
[12:8423] Data Protector cannot find home directory of Oracle Server (<ORACLE_HOME>).
DESCRIPTION:

instances does not contain home directory of Oracle Server.
ACTION:

MESSAGE:
[12:8424] This Oracle Server instance is not configured.
DESCRIPTION:

instances is empty.
ACTION:

3. In case of a cluster environment and trying to run a util_cmd in the console,

please be sure OB2BARHOSTNAME is correctly defined as the virtual hostname of the cluster.
MESSAGE:
[12:8426] Copy of the file failed.
DESCRIPTION:
Check for error code in the log file /etc/opt/omni/oracle/oracle.log.
ACTION:
MESSAGE:
[12:8427] Failed to load OCI client library.
DESCRIPTION:
For more information check Data Protector debug.log.
ACTION:
MESSAGE:
[12:8489] Oracle ASM instance version could not be retrieved.
DESCRIPTION:
Error occured while retreiving ASM instance version.
ACTION:
Please make sure ASM instance is started and is properly configured. If ASM instance does not
have a default name or ASM home directory is not the same as Oracle home directory,
please use util_oracle8.pl utility to configure the integration from CLI providing
also additional ASM options.
MESSAGE:
[12:8496] The ZDB_ORA_INCLUDE_CF_OLF omnirc variable was set. Online redo log files and current
control files will be part of the replica.
DESCRIPTION:
The replica created during this ZDB session is tracked for Instant Recovery.
If this replica is used for Instant Recovery, the most recent online redo log files
and control files of the target database will be overwritten with the copies on the
replica.
If database recovery beyond the replica creation time is needed, a control file will
have to be restored after the Instant Recovery and before recovering the database.
Automatic Instant Recovery followed by the database recovery is not supported in this
configuration.
ACTION:
Make a detailed recovery plan before using this replica for Instant Recovery.
If you need the automatic Instant Recovery reconfigure the database according to
the requirements from the HP Data Protector Zero Downtime Backup Integration Guide
and turn off the ZDB_ORA_INCLUDE_CF_OLF variable.
MESSAGE:
[12:8499] Not all ASM disks could be mapped to their physical devices.
DESCRIPTION:
Error occured while retreiving physical device for ASM diskgroup on which only
SPFILE resides. Agent could not start util_oracle8.pl utility on the application
client or it could not connect to ASM instance and get the ASM paths from
v$ASM_DISK view.
ACTION:
Please make sure ASM instance is properly configured. If ASM instance does not
have a default name +ASM, please use util_oracle8.pl utility to configure the
integration providing also the connection data for ASM instance.
MESSAGE:
[12:8500] Unknown internal error.
DESCRIPTION:
Something unpredictable has happened inside the Data Protector agent.
ACTION:
Contact your administrator.
MESSAGE:
[12:8501] Invalid command line arguments.
DESCRIPTION:
Invalid command line option specified.
ACTION:
See documentation about valid command line parameters.

If this situation happens while using the Data Protector Manager then contact HP
Support Representative.
MESSAGE:
[12:8510] Cannot connect to the Cell Manager.
DESCRIPTION:
Connection to the Cell Manager is lost.
ACTION:
Check the network connection to the Cell Manager host.

Maybe the Cell Manager host went down unpredictably.
MESSAGE:
[12:8520] Cannot login to SQL server, cause unknown.
DESCRIPTION:
Cannot login to SQL server, cause unknown.
ACTION:
* Check login/password configuration.

* If needed reconfigure the integration.
* Check whether MSSQL Server service is running on the host running MSSQL
server.
* If the MSSQL Server service is stopped, start it.
* Check Data Protector debug.log and MS SQL Server's errorlog files for errors.
MESSAGE:
[12:8521] SQL server not available, service may be stopped.
DESCRIPTION:
Data Protector agent cannot connect to the desired MSSQL server.
ACTION:
Check whether MSSQL Server service is running on the host running MSSQL server.
If the MSSQL Server service is stopped, start it.
MESSAGE:
[12:8522] Service is paused, login denied
DESCRIPTION:
Data Protector agent cannot connect to the desired MSSQL server.
ACTION:
Check whether MSSQL Server service is running on the host running MSSQL server.
If the MSSQL Server service is stopped, start it.
MESSAGE:
[12:8523] Login incorrect.
DESCRIPTION:
Cannot login to MSSQL server.
ACTION:
* Check login/password configuration.

* If needed reconfigure the integration.
* Check whether MSSQL Server service is running on the host running MSSQL
server.
* If the MSSQL Server service is stopped, start it.
* Check Data Protector debug.log and MS SQL Server's errorlog files for errors.
MESSAGE:
[12:8524] Out of memory.
DESCRIPTION:
Agent has run out of memory.
ACTION:
Check if some process on the SQL Server host uses a lot of memory.
MESSAGE:
[12:8525] COM initialization or COM object creation failed.
DESCRIPTION:
Data Protector Agent for MS SQL 7 uses COM objects to connect to the SQL Server.
It has failed create an instance of SQL Server 7 object. This usually means
that SQL Server 7 is not installed or is corrupted.
ACTION:
Check if SQL Server 7 or later is installed on the system.
MESSAGE:
[12:8526] Wrong SQL Server version.
DESCRIPTION:
Data Protector Agent for MS SQL Server 7 has tried to connect to SQL Server
version older than 7.0 on the specified system. Is SQL Server version 7.0 or
later installed?
ACTION:
Check if the appropriate version of Data Protector Agent for SQL Server is installed on
the system. Agent 6.5 has to be installed for SQL Servers 6.5 or older and
agent 7.0 for SQL Server 7.0.
MESSAGE:
[12:8550] Correct disk array options can not be displayed.
DESCRIPTION:
The replicas for this session have different instant recovery disk array options. They can not be
restored in single session.
ACTION:
1. Perform restore of different objects in session from command line one by one.
2. If you wish to perform restore from the GUI in the future, check that all disks backed up
reside on same disk array and have same replication settings in VSS hardware providers.
MESSAGE:
[12:8561] The selected Data Protector Single Mailbox integration is not configured.
DESCRIPTION:
Data Protector Single Mailbox integration has to be configured before first creation of backup
specification.
ACTION:
1. Create Single Mailbox Configuration from "Configure Single Mailbox" dialog.

2. See Data Protector documentation on configuring MS Single Mailbox integration.
MESSAGE:
[12:8562] The Data Protector Single Mailbox integration cannot be configured.
DESCRIPTION:
The MAPI Profile cannot be created for configuration parameters specified in "Configure Single
Mailbox" dialog.
ACTION:
1. Check MS Exchange Administrator login/password.

2. Check if "act as part of the operating system" user right is given to MS Exchange
Administrator.
3. Check that mailbox for MS Exchange Administrator exists on MS Exchange Server.
4. Check whether MS Exchange Server service is running on the host running MS Exchange Server.
5. If the MS Exchange Server service is stopped, start it.
6. Examine Data Protector debug.log file for errors.
8. Create MAPI Profile manually (see Data Protector MS Single Mailbox troubleshooting section for
details).
MESSAGE:
[12:8563] Cannot login to MS Exchange Server.
DESCRIPTION:
The Data Protector Single Mailbox configuration is invalid or MS Exchange Server doesn't appear to
be running.
ACTION:
1. Check MS Exchange Administrator login/password.

2. Check if "act as part of the operating system" user right is given to MS Exchange
Administrator.
3. Check that mailbox for MS Exchange Administrator exists on MS Exchange Server.
4. Check whether MS Exchange Server service is running on the host running MS Exchange Server.
5. If the MS Exchange Server service is stopped, start it.
6. Examine Data Protector debug.log file for errors.
7. Start the configuration.
8. See Data Protector documentation on configuring Data Protector Single Mailbox integration.
MESSAGE:
[12:8564] The Microsoft Exchange MAPI interface can not be intialized.
DESCRIPTION:
Microsoft Exchange Single Mailbox Integration requires that Microsoft Exchange MAPI is installed
on the system.
ACTION:
Please, download the ExchangeMapiCdo package from the web site http://www.microsoft.com/downloads
and install it on your system.
MESSAGE:
[12:8651] Path to notes.ini does not exist.
DESCRIPTION:
Path to notes.ini does not exist.
ACTION:
Check if the path to notes.ini exists.
MESSAGE:
[12:8652] Domino Server name cannot be obtained through a Lotus C API call
DESCRIPTION:
Domino Server name cannot be obtained through a Lotus C API call.
ACTION:
Please specify it manually with -server:<SVR> option.
MESSAGE:
[12:8654] Basic Lotus C API initialization failed.
DESCRIPTION:
Before any Lotus C API call the initialization of the API must be performed. This initialization
failed.
ACTION:
Check the path to the specified notes.ini file.

UNIX specifics: Also check the specified LOTUS_HOME, LOTUS_DATA and LOTUS_EXEC paths.
Abnormal state of the Notes/Domino Server could also cause the initialization failure.
Try to restart the Notes/Domino Server.
MESSAGE:
[12:8655] Cannot get the Domino Data directory.
DESCRIPTION:
Cannot get the Domino Data directory.
ACTION:
Check the path to the specified notes.ini file.
Check if the "Directory=" environment variable is properly defined in the notes.ini file.
MESSAGE:
[12:8656] Domino Server name cannot be obtained through the Lotus C API call.
DESCRIPTION:
Domino Server name cannot be obtained through the Lotus C API call.
ACTION:
Notes/Domino Server must be up and running.
MESSAGE:
[12:8657] No Domino Server found on the system.
DESCRIPTION:
No Domino Server found on the system.
ACTION:
Notes/Domino Server must be up and running.
MESSAGE:
[12:8658] While browsing Notes data on the Domino Server system an error occurred.
DESCRIPTION:
While browsing Notes data on the Domino Server system an error occurred.
ACTION:
Lotus C API call might fail. Check Data Protector debug.log for details.
Try to restart Notes/Domino Server.
MESSAGE:
[12:8659] Data Protector Lotus Integration is not configured.
DESCRIPTION:
Data Protector Lotus Integration is not configured.
ACTION:
Check the configuration and the path to the notes.ini file.

You can manually delete Lotus configuration files and reconfigure the integration.
MESSAGE:
[12:8660] Data Protector Lotus Integration is not configured.
DESCRIPTION:
Data Protector Lotus Integration is not configured or Lotus

configuration files are corrupted.
ACTION:
Check the configuration and path to the notes.ini file.

You can manually delete Lotus configuration files and reconfigure the integration.
MESSAGE:
[12:8661] Check the path to the "LOTUS HOME" directory.
DESCRIPTION:
Check the path to the "LOTUS HOME" directory you specified.
ACTION:
You need to reconfigure the Lotus Integration and specify a proper path to the Lotus home
directory.
(Example: '/opt/lotus/')
MESSAGE:
[12:8662] Check the path to the "LOTUS DATA" directory.
DESCRIPTION:
Check the path to the specified "LOTUS DATA" directory.
ACTION:
You need to reconfigure the Lotus Integration and specify the proper path to the Lotus data
directory.
(Example: '/local/notesdata/')
MESSAGE:
[12:8663] Check the path to the "LOTUS EXEC" directory.
DESCRIPTION:
Check the path to the specified "LOTUS EXEC" directory.
ACTION:
You need to reconfigure the Lotus Integration and specify the proper path to the Domino executable
directory.
(Example: '/opt/lotus/notes/latest/hppa/' for HP-UX systems)
MESSAGE:
[12:8664] No Domino Server found on the system or path is not set correctly.
DESCRIPTION:
No Domino Server found on the system or path to nNOTES.dll/libnotes.sl/libnotes_r.a is not set

correctly.
ACTION:
Notes/Domino Server must be up and running. Please refer to the troubleshooting section of the HP
Data Protector Integration Guide for IBM Applications: Informix, DB2, and Lotus Notes/Domino.
MESSAGE:
[12:8700] The oratab file doesn't exist. (OBSOLETE MESSAGE)
DESCRIPTION:
The /etc/oratab file is not find on the SAP Client host.
ACTION:
Create the /etc/oratab file and add "<ORACLE_SID>:<ORACLE_HOME>:Y".
MESSAGE:
[12:8701] Cannot find Oracle SQL*Plus.
DESCRIPTION:
The Oracle SQL*Plus cannot be found in ORACLE_HOME/bin directory.

It is not possible to connect to Oracle Database Server.
ACTION:
1. Check if ORACLE_HOME directory is the right one.

2. Login as root user to the client machine, set ORACLE_SID and ORACLE_HOME,
EXAMPLE:
. . .
. . .
SQL> connect sys/manager@ORACLE
Connected.
MESSAGE:
[12:8702] The SAP backup utilities are not found.
DESCRIPTION:
The SAP backup utilities (brbackup, brrestore etc.) do not exist in

the specified directory (BRTOOLS directory).
ACTION:
1. Check if the SAP backup utilities exist on the SAP Client host.
2. Check permissions of the directory. The directory should be owned
by ora<SID> and have 755 permissions.
3. Check the Data Protector SAP configuration file on the Cell Manager:
/etc/opt/omni/server/integ/config/SAP/hostname.domain%INSTANCE_NAME.
The Data Protector SAP configuration parameter "conf" is in the following format:
PATH /usr/sap/<SID>/SYS/exe/run
MESSAGE:
[12:8703] There is no soft link to Data Protector "backint" interface in the directory where are
SAP backup utilities.
DESCRIPTION:
Data Protector found out that there is no link to Data Protector "backint"
interface in the directory where are SAP backup utilities.
The link could be deleted.
ACTION:
2. Check permissions of the directory. The directory should be owned
by ora<SID> and have 755 permissions.
MESSAGE:
[12:8704] The Data Protector SAP configuration files cannot be created.
DESCRIPTION:

- Oracle Server Home directory (ORACLE_HOME),
- Oracle Login information to Target Database,
- Path of the SAP backup utilities
cannot be written to the Data Protector configuration directory on the Cell Manager.
It is possible the /etc/opt/omni/server/integ/config/SAP directory is deleted or has wrong
permissions.
ACTION:
1. Check permissions of the /etc/opt/omni/server/integ/config/SAP directory.

2. Check if SAP Integration Module is correctly installed.
MESSAGE:
[12:8705] Data Protector cannot find the Oracle SQL*Net Login Information to Oracle Target
Database.
DESCRIPTION:
The Data Protector repository with configuration of your Oracle SAP database
instances does not contain Oracle SQL*Net Login Information to Oracle Target
Database.
ACTION:

/etc/opt/omni/server/integ/config/SAP.
On Windows Cell Manager, the repository is directory:
<Data_Protector_home>\Config\Server\Integ\Config\SAP.
2. Re-install Data Protector SAP Integration Module to the client.
MESSAGE:
[12:8706] The Oracle SQL*Net Login Information to the database instance is not correct or database
is not running. It is not possible to connect to Oracle Database Server.
DESCRIPTION:
The Oracle SQL*Net Login Information to the Oracle database instance

specified in the configuration is not correct or database is not running.
It could be possible that Oracle SQL*Net Listener is not running or
SQL*Net configuration is not correctly configured.
ACTION:
1. Check if database instances are running.

configured.
See Oracle documentation how to configure Oracle listeners.
<ORACLE_HOME>/network/admin directory and
it is correctly configured.
/etc/opt/omni/oracle/$ORACLE_SID/.profile file.
5. Login as root user to the client machine, set ORACLE_SID and ORACLE_HOME,
EXAMPLE:
. . .
. . .
SQL> connect system/manager@SID
Connected.
MESSAGE:
[12:8707] INTERNAL ERROR: Invalid Arguments. Tablespace name is not specified.
DESCRIPTION:
Tablespace name is not specified.
ACTION:
Check that the command was started as
util_sap.exe -OBJS1 <ORACLE_SID> <TABLESPACE_NAME>
MESSAGE:
[12:8708] Oracle Server home directory specified in the configuration does not exist or have wrong
permissions.
DESCRIPTION:

The Oracle Server home directory can be read from <ORACLE_HOME> environment
variable on the client where Oracle Server is installed.
ACTION:

3. The permission of Oracle Server home directory has to be 755.
MESSAGE:
[12:8709] The selected SAP Oracle database instance has never been configured.
DESCRIPTION:
The selected SAP Oracle database instance has never been configured.
The Data Protector repository with list of SAP Oracle database instances does
not contain the name of selected Oracle database instance (<ORACLE_SID>).
ACTION:
MESSAGE:
[12:8710] Cannot copy/link BRtools interface file(s) to the SAP directory.
DESCRIPTION:
ACTION:
Cannot copy/link file from <Data_Protector_home>\BIN to the BRtools direcotry entered in the
configuration.
Check if file exists in <Data_Protector_home>\BIN directory.
On Windows check if share named sapmnt exists on your SAP/R3 client.
If nothing else, copy/link the file by yourself.
MESSAGE:
[12:8711] The SAP backup utilities are not found.
DESCRIPTION:
The SAP backup utilities (brbackup, brrestore etc.) do not exist in

the specified directory (BRTOOLS directory).
ACTION:
The default directory path where SAP/R3 utilities reside is

\\<host>\sapmnt\<sid>\sys\exe\run.
2. Check permissions of the directory.
MESSAGE:
[12:8712] Oracle is not linked with the Data Protector library for backup.
In case of 32-bit executables the name is /opt/omni/lib/libob2oracle8.sl.
In case of 64-bit executables the name is /opt/omni/lib/libob2oracle8_64bit.sl.
DESCRIPTION:
ACTION:
Shutdown the Oracle Server and link it with the Data Protector library using
the following commands:
$ cd ${ORACLE_HOME}/rdbms/lib
for 32-bit executables:
$ make -f ins_rdbms.mk ioracle "LLIBOBK=/opt/omni/lib/libob2oracle8.sl"
for 64-bit executables:
$ make -f ins_rdbms.mk ioracle "LLIBOBK=/opt/omni/lib/libob2oracle8_64bit.sl"
MESSAGE:
[12:8713] Cannot put configuration on the Cell Manager.
DESCRIPTION:
Data Protector / SAP R/3 integration configuration utility was unable to update
configuration on the Cell Manager.
ACTION:
Make sure you have the latest version of Data Protector.

Check that appropriate directory structure under Data Protector installation
directory exists.
Restart Data Protector server processes on your Cell Manager.
MESSAGE:
[12:8714] Specified SAPDATA_HOME directory is invalid.
DESCRIPTION:
Specified SAPDATA_HOME directory is invalid.
ACTION:
Make sure that the directory you specify as SAPDATA_HOME exists, has correct
permissions set and contains correct data.
MESSAGE:
[12:8715] Backup ID incorrect.
DESCRIPTION:
Backup ID that was either specified by user, or saved in the

Data Protector Internal Database is incorrect.
ACTION:
If the supplied backup ID was specified by you, make sure it is correct.

If it was read from the Internal Database, check if the Internal Database contains
correct information about file versions.
MESSAGE:
[12:8716] File sizes do not match.
DESCRIPTION:
The file size you specified doesn't match the file size that is
reported by the OS.
ACTION:
Make sure you specify the correct size.

If the size reported by the OS is incorrect, make sure you have
the latest patches for your OS.
MESSAGE:
[12:8717] Load balancing procedure failed.
DESCRIPTION:
Load balancing procedure failed.
ACTION:
See the message output and check if all filenames are correct,
all the files and directories are accessible and
that you have enough space in Data Protector temporary directory.
MESSAGE:
[12:8718] Time balancing procedure failed.
DESCRIPTION:
Time balancing procedure failed.
ACTION:
MESSAGE:
[12:8719] Manual balancing procedure failed.
DESCRIPTION:
Manual balancing procedure failed.
ACTION:
MESSAGE:
[12:8720] Disk balancing procedure failed.
DESCRIPTION:
Disk balancing procedure failed.
ACTION:
MESSAGE:
[12:8721] Not enough space in temporary directory.
DESCRIPTION:
There is not enough free space in Data Protector temporary directory.
ACTION:
Make sure that the directory used by Data Protector as temporary is accessible for
read-write access and it's located on disk that has enough space for a file
containing a list of files to back up.
MESSAGE:
[12:8722] Cannot open file.
DESCRIPTION:
SAP R/3 integration agent could not open a file.

Please see debug.log for details.
ACTION:
Make sure that the file in question is accessible for the user which is
specified as the owner of this backup specification.
MESSAGE:
[12:8723] Cannot get file size.
DESCRIPTION:
SAP R/3 integration agent could not get file size.

ACTION:
Make sure that the file in question is accessible for the user which is
MESSAGE:
[12:8724] Cannot get disk free space.
DESCRIPTION:
SAP R/3 integration agent could not get the amount of free space on disk.
ACTION:
Make sure that the disk in question is accessible for the user which is
MESSAGE:
[12:8725] Can not open configuration file.
DESCRIPTION:
SAP R/3 integration agent could not read configuration file.

ACTION:
Check configuration file manually or reconfigure.
MESSAGE:
[12:8740] Database replica is not suitable for recovery after instant recovery.
DESCRIPTION:
Selected ONLINE replica includes current control file copies which are not to be
used for recovery.
ACTION:
For database recovery execute the following steps before starting instant recovery:
1. Copy current control files and online redo logs to a safe location.
2. Perform instant recovery.
3. Copy current control files and online redo logs back to their original location.
4. Mount target database.
5. Restore missing archived redo logs required for database recovery.
Exaple:
# sqlplus <user>/<password>@<net service name>

SQL> select SEQUENCE#, NAME from V$ARCHIVED_LOG
where (NEXT_TIME>to_date('<selected ir session (e.g. 2007/10/03)>','YYYY/MM/DD'))
and (FIRST_CHANGE#<='<until SCN>');
# brrestore -a <log_no>,... -d util_file -c force -u <user>/<password>
6. Recover target database.
Example:
rman target <user>/<password>@<net service name>

RMAN> run{
2> allocate channel dbrec type disk;
3> recover database until scn <until SCN>;
4> release channel dbrec;
5> }
MESSAGE:
[12:8741] Database replica is not suitable for recovery after instant recovery.
DESCRIPTION:
Selected OFFLINE replica includes current control file and online redo log copies. This
replica is suitable for version recovery.
ACTION:
Exaple:

Example:

RMAN> run{
5> }
MESSAGE:
[12:8743] Database replica was not created using Data Protector GUI. It might
not be suitable for recovery after instant recovery.
DESCRIPTION:
Selected replica could include current control file copies which are not to be
used for recovery.
ACTION:
Exaple:

Example:

RMAN> run{
5> }
MESSAGE:
[12:8800] Cannot start Informix "dbaccess" utility.
DESCRIPTION:
Data Protector starts Informix command "$INFORMIXDIR/bin/dbaccess sysmaster -" which

fails. The possible cause could be that the name of Informix Server is not the
right one.
ACTION:
1. Check if the name of Informix Server is correct.

2. Login as root(Unix) or informix(NT) user to the client machine, export INFORMIXDIR, ONCONFIG,
INFORMIXSQLHOST and INFORMIXSERVER and start the dbaccess.
EXAMPLE:
Unix:
# export INFORMIXDIR=/informix
# export ONCONFIG=onconfig
# export INFORMIXSQLHOST=/informix/etc/sqlhosts
# export INFORMIXSERVER=SERV
# $INFORMIXDIR/bin/dbaccess sysmaster -
. . .
. . .
NT:
set INFORMIXDIR=d:\informix
set ONCONFIG=onconfig
set INFORMIXSQLHOST=sqlhosts
set INFORMIXSERVER=SERV
%INFORMIXDIR%\bin\dbaccess sysmaster -
. . .
. . .
3. If you have different language setting then you have to put them in
Environment section in file host.domain%$INFORMIXSERVER, located on the Cell Manager
in /etc/opt/omni/server/integ/config/Informix
(<Data_Protector_home>\Config\Server\Integ\Config\Informix on Windows)
EXAMPLE:
Environment={
DB_LOCALE='sl_SI.iso2';
CLIENT_LOCALE='sl_SI.iso2';
LC_COLLATE='sl_SI.iso88592';
}
MESSAGE:
[12:8801] The Informix command "dbaccess" does not exist in Informix Server Home directory.
DESCRIPTION:
Data Protector cannot find the Informix "dbaccess" command. It should be

in bin subdirectory of Informix Server Home directory.
It is possible that Informix Server Home directory is not correct.
ACTION:
1. Check if Informix Server Home directory is correct.

2. Check if there is a dbaccess command in the Informix Server Home directory.
3. Check permission of dbaccess command in the Informix Server Home directory.
EXAMPLE:
Unix
# $INFORMIXDIR/bin/dbaccess sysmaster -
. . .
. . .
NT:
%INFORMIXDIR%\bin\dbaccess sysmaster -
. . .
. . .
MESSAGE:
[12:8802] The Informix Server Home directory is not found.
DESCRIPTION:
Informix directory is not set or it doesn't exist.
ACTION:
Check if Informix directory hasn't been mistyped in the configuration window.
MESSAGE:
[12:8804] The Informix command "onstat" does not exist in Informix Server Home directory.
DESCRIPTION:
Data Protector cannot find the Informix "onstat" command. It should be

ACTION:

2. Check if there is a onstat command in the Informix Server Home directory.
3. Check permission of onstat command in the Informix Server Home directory.
EXAMPLE:
Unix
# $INFORMIXDIR/bin/onstat -d
. . .
. . .
NT:
%INFORMIXDIR%\bin\onstat -d
. . .
. . .
MESSAGE:
[12:8805] Informix Server is not running.
DESCRIPTION:
Informix server is not running.
ACTION:
Start the server with the following procedure:

Login as informix user to the client machine, export INFORMIXDIR, ONCONFIG,
INFORMIXSQLHOST and INFORMIXSERVER and start the oninit command.
EXAMPLE:
Unix:
# $INFORMIXDIR/bin/oninit
. . .
. . .
NT:
%INFORMIXDIR%\bin\oninit
. . .
. . .
On NT also check if Data Protector Inet service is running

by the same account as Informix server.
MESSAGE:
[12:8807] The Informix Server ONCONFIG parameter file cannot be found.
DESCRIPTION:
The ONCONFIG parameter file is not set or the file couldn't be found.
The ONCONFIG parameter file resides in etc subdirectory of Informix Server
Home Directory.
ACTION:
Check if ONCONFIG parameter file exists and if its name wasn't mistyped
in the configuration window.
MESSAGE:
[12:8808] The Informix sqlhosts file is not set or the file does not exist.
DESCRIPTION:
The sqlhosts file resides in etc subdirectory (Unix) of Informix Server

Home Directory.
Note that you have to specify full path name for Informix sqlhosts file.
ACTION:
Check if the path to sqlhosts file wasn't mistyped in the configuration window.
If it was mistyped, please start the configuration again with correct path.
MESSAGE:
[12:8809] The Data Protector Informix configuration files cannot be created.
DESCRIPTION:

- Informix Server Home directory,
- Informix ONCONFIG configuration file,
- Full Path name of Informix Server sqlhosts file.
cannot be written to the Data Protector configuration on the Cell Manager
It is possible the /etc/opt/omni/server/integ/config/Informix directory on the Cell Manager
does not exist or has wrong permissions.
(<Data_Protector_home>\Config\Server\Integ\Config\Informix on Windows)
ACTION:
1. Check permissions of the /etc/opt/omni/server/integ/config/Informix

(/usr/omni/config/integ/config/Informix for non HP-UX 10.x or Solaris
and <Data_Protector_home>\Config\Server\Integ\Config\Informix on Windows) directory on the Cell
Manager.
2. Check if Informix Integration Module is correctly installed.
MESSAGE:
[12:8810] The Data Protector configuration directory cannot be created.
DESCRIPTION:
The Data Protector repository with configuration of your Informix Server

instances cannot be created.
ACTION:

configuration of your Informix Server instances.
For HP-UX 10.x/11.x or Solaris Cell Manager, the repository is in directory:
/etc/opt/omni/server/integ/config/Informix.
On Windows Cell Manager the repository is in directory:
<Data_Protector_home>\Config\Server\Integ\Config\Informix
2. Re-install Data Protector Informix Integration Module to the client.
MESSAGE:
[12:8811] The selected Informix Server instance has never been configured.
DESCRIPTION:
The selected Informix Server instance has never been configured.

The Data Protector repository with list of Informix Server instances does
not contain the name of selected Informix Server (<INFORMXISERVER>).
ACTION:

MESSAGE:
[12:8812] The selected Informix Server instance has never been configured.
DESCRIPTION:
The selected Informix Server instance has never been configured.

The Data Protector repository with list of Informix Server instances does
not contain the name of selected Informix Server (<INFORMXISERVER>).
ACTION:

MESSAGE:
[12:8813] The Informix command "onbar" does not exist in Informix Server Home directory or does
not have (only Unix) s bit (sticky bit) set.
DESCRIPTION:
Data Protector cannot find the Informix "onbar" command. It should be

ACTION:

2. Check if there is a onbar command in the Informix Server Home directory.
3. Check permission of onbar command in the Informix Server Home directory.
(the Unix permissions should be: -rwsr-sr-x).
4. Check owner of onbar command in the Informix Server Home directory.
(the owner should be root user in informix group).
INFORMIXSQLHOST and INFORMIXSERVER and start the onbar.
EXAMPLE:
# $INFORMIXDIR/bin/onbar -b
. . .
. . .
NT:
%INFORMIXDIR%\bin\onbar -b
. . .
. . .
MESSAGE:
[12:8814] The Informix command "oninit" does not exist in Informix Server Home directory.
DESCRIPTION:
Data Protector cannot find the Informix "oninit" command. It should be

ACTION:

2. Check if there is a oninit command in the Informix Server Home directory.
3. Check permission of oninit command in the Informix Server Home directory.
INFORMIXSQLHOST and INFORMIXSERVER and start the oninit.
EXAMPLE:
# $INFORMIXDIR/bin/oninit
. . .
. . .
NT:
%INFORMIXDIR%\bin\oninit
. . .
. . .
MESSAGE:
[12:8815] Data Protector shared library ob2informix.sl(Unix) or ob2informix.dll(NT) not found.
DESCRIPTION:
Unix:
Data Protector shared library ob2informix.sl not found.
NT:
Data Protector dynamic library ob2informix.dll not found.
ACTION:
Unix:
Check if shared library ob2informix.sl exists in directory /opt/omni/lib.
If it doesn't, please push Data Protector Informix Integration Module to the client.
NT:
Check if dynamic library ob2informix.dll exists in directory <Data_Protector_home>\bin.
If it doesn't, please push Data Protector Informix Integration Module to the client.
MESSAGE:
[12:8816] Informix Server is On-Line.
DESCRIPTION:
Informix Server is On-Line.
ACTION:
When running whole restore Informix Server has to be Off-Line.

Please shutdown Informix Server.
MESSAGE:
[12:8817] The Informix command "onbar_d" does not exist in Informix Server Home directory or does
not have (Unix) s bit set (sticky bit).
DESCRIPTION:
Data Protector cannot find the Informix "onbar_d" command. It should be in bin subdirectory of
Informix Server Home directory.
ACTION:

2. Check if there is a onbar_d command in the Informix Server Home directory.
3. Check permission of onbar command in the Informix Server Home directory.
(the Unix permissions should be: -rwsr-sr-x).
4. Check owner of onbar command in the Informix Server Home directory.
(the owner should be root user in informix group).
INFORMIXSQLHOST and INFORMIXSERVER and start the onbar.
EXAMPLE:
# $INFORMIXDIR/bin/onbar -b
. . .
. . .
NT:
%INFORMIXDIR%\bin\onbar -b
. . .
. . .
MESSAGE:
[12:9301] Store does not exist or you don't have permissions.

DESCRIPTION:
The issue can appear if the store was deleted on the B2D device or if the permissions for this
store were modified.
ACTION:
- Check if the store exists or if any of the permissions were modified for this store.
- If the store is set up correctly, check the device settings in Data Protector. Right-click the
device, select Properties and in the Devices - Store and Gateways page check the Client ID.
MESSAGE:
[12:9499] You are running out of disk space on StoreOnceSoftware Store root directory on server
"p".
DESCRIPTION:
The StoreOnceSotware free disk space threshold was reached.

Please see the event log on Windows or system log on Linux for details.
Once the minimum free disk space (omnirc variable OB2_STOREONCESOFTWARE_MINIMUM_DISK_SPACE) is
reached further backups will fail.
ACTION:
* Free up disk space or add more disks to the target store root directory.
* Relocate the store to a larger disk and reconfigure the store root path.
* Adjust the omnirc variable OB2_STOREONCESOFTWARE_DISK_SPACE_THRESHOLD.
MESSAGE:
[12:10110] Cannot use local library access.
DESCRIPTION:
The use of local library access is not possible. Invalid library specified.
ACTION:
libtab file is probably misconfigured. Check that you have created

libtab file on a host where library robotics is connected and
that you have put it in Data Protector install directory. File should be
named ".libtab" on UNIX clients and "libtab" on WIN32 and NETWARE
clients.
the format of the file is following (all fields mandatory):
<hostname> <control device file> <logical device name>
MESSAGE:
[12:10900] Detail Catalog Database Internal Error.
DESCRIPTION:
An unexpected condition has occurred while accessing the DCBF part of the
Data Protector Internal Database.
ACTION:
* Check the debug.log if it contains some more details on the reported failure.
* Check the Internal Database and then recover it if required. See the
online Help topic "IDB Consistency Check" or chapter "Managing the Data Protector
Internal Database" in the HP Data Protector Administrator's Guide.
MESSAGE:
[12:10904] Open of detail catalog binary file failed.
DESCRIPTION:
Detail catalog binary file that contains (some of) the data needed to browse the
backup history could not be opened. You will be able to browse further but you
will not see those versions of backed up files that were stored in that specific
binary file. Debug.log file (<Data_Protector_home>\log\debug.log) contains more details
on which specific detail catalog binary file could not be opened and for what
reason.
ACTION:
* Check for possible reasons why those files can be missing and try to fix the
issue. For example if the file is on the filesystem that is for some reason
not mounted, mount it ...
* If file is really missing, you can get the contents of the file back by
executing the following procedure:
1) Stop all sessions and close all GUIs
2) Run: omnidbutil -fixmpos
3) Find the correct medium and run "Import catalog" for that medium. Note
that the debug.log contains the medium ID of the file and that you can
use: omnimm -media_info <mediumID>
* You may want to further check the Internal Database and then recover it if
required. See the chapter "Managing the Data Protector Internal Database" in
Data Protector Admin Guide
MESSAGE:
[12:10905] Read of detail catalog binary file failed.
DESCRIPTION:
DC binary file that contains the data needed to browse the backup history could
not be read. You can browse the backup history but you will not able to see
those versions of backed up files that were stored in that specific DC binary
file. Typically this error indicates that the CDB part of the Internal Database
and the DCBF part of the Internal Database are not consistent. The debug.log
file contains more details on which specific DC binary file could not be read.
ACTION:
* Check the Internal Database and then recover it if required. See the online
Help topic "IDB Consistency Check" or chapter "Managing the Data Protector
Internal Database" in the HP Data Protector Administrator's Guide.
MESSAGE:
[12:10907] Invalid format of detail catalog binary file.
DESCRIPTION:
DC binary file that contains the data needed to browse the backup history is not
in the expected format. You can browse the backup history but you will not see
those versions of backed up files that were stored in that specific DC binary
file. Typically this error indicates that the CDB part of the Internal Database
and the DCBF part of the Internal Database are not consistent or that the binary
file is corrupted. The debug.log file contains more details on which specific DC
binary file in not in correct format.
ACTION:
* Recover the corrupted DC binary file by executing the following procedure:

1) Stop all sessions and close all GUIs.
2) Remove the corrupted binary file.
3) Run omnidbutil -fixmpos command from the CLI.
4) Find and run "Import catalog" for the correct medium. Note that the
debug.log contains the medium ID of the file and that you can use omnimm
-media_info <mediumID> command. See the online Help topic "Overview of IDB
Recovery Methods" or chapter "Recovering the Data Protector Internal Database"
in the HP Data Protector Administrator's Guide for more information on the
recovery procedure of the Internal Database.
MESSAGE:
[12:15923] Backup method mismatch.
DESCRIPTION:
Barlist does not correspond to the currently configured backup method for the
selected database instance.
ACTION:
* If you wish to use this barlist selected database instance must be reconfigured,
else remove it from the current location.
MESSAGE:
[12:15924] Backup method not configured.
DESCRIPTION:
Backup method for selected database instance has not been configured.
ACTION:
* Configure the database instance backup method using util_oracle8 configuration

utility as described in HP Data Protector Zero Downtime Backup Integration Guide.
MESSAGE:
[12:16100] Unable to get VLS Smart Copy slots.
DESCRIPTION:
It was not possible to retrieve a list of the Smart Copy slots of the VLS. A
failure has been reported from UMA.
ACTION:
* Check the VLS connection settings for this device in the clients context.
* Make sure that Media Agent is still installed properly on the client machine.
MESSAGE:
[12:16107] Duplicate barcodes detected.
DESCRIPTION:
Two or more tapes in the Smart Copy slots associated with this library share
the same barcode. Duplicate barcodes are not supported in Automigration and
can lead to loss of data.
ACTION:
* Use CommandView VLS of your Virtual Library System to identify the tapes that
share a barcode and eject all except for one so that there is only one tape
with each barcode left.
* You can also attach a new barcode label to those physical tapes to have only
unique barcodes and reinsert them into your library.
* Note that having more than one tape without a barcode is also considered a
duplicate barcode.
MESSAGE:
[12:16119] Cell Manager 'p' is not yet configured as a Manager-of-Managers Server.
DESCRIPTION:
One of the Data Protector clients tried to connect to the Manager-of-Managers but the connection
failed.
CRS is not running in Manager-of-Managers Server mode.
ACTION:
Open Data Protector Manager (not Data Protector Manager-of-Managers),

connect to the CM who you want to configure as a MoM, set 'Clients' context
and click on the 'Configure CM as Manager-of-Managers Server' option from Actions menu.
Or manually the empty file cell/mom_info must be created

and Data Protector server processes must be restarted on the Manager-of-Managers server host.
MESSAGE:
[12:17112] Smart Cache host crendentials Encryption/Decryption Failed.
DESCRIPTION:
Smart Cache host crendentials Encryption/Decryption Failed.
ACTION:
Check KMS server status.
MESSAGE:
[30:6] You do not have permission to reply to a mount request.
DESCRIPTION:
Data Protector security has reported that you have no permission to respond to
the specified mount request. This occurs when you try to respond to mount a
request from a session that you did not initiate and you belong to a
group that has the ACL Mount Request disabled.
ACTION:
Set the Mount Request ACL in the appropriate class.
MESSAGE:
[30:8] No Session Manager with that session ID is currently running.
DESCRIPTION:
There is no session with that session ID currently running.
ACTION:
Use omnistat to display all currently running sessions.
MESSAGE:
[31:20] You have no permission to start a backup.
DESCRIPTION:
You have no permission to start a backup.
ACTION:
Either add the start backup user right to this user group or move this
user to a user group that has the start backup user right.
MESSAGE:
[31:21] You have no permission to start a backup specification.
DESCRIPTION:
You have no permission to start a backup specification.
ACTION:
Either add the start backup specification user right to this user group or
transfer this user to a user group that has the start backup specification
user right.
MESSAGE:
[31:22] You have no permission to start a backup specification.
DESCRIPTION:
You have no permission to start a backup specification.
ACTION:
Either add the backup specification user right to this user group or
transfer this user to a user group that has the backup specification
user right.
MESSAGE:
[32:21] You do not have permission to start a restore.
DESCRIPTION:
You do not have permission to perform a restore.
ACTION:
Either add the start restore access right to your Data Protector user group or
transfer your Data Protector user name to a Data Protector user group that has
the start restore access right.
MESSAGE:
[32:22] You do not have permission to start full restore.
DESCRIPTION:
You do not have permission to perform a full restore.
ACTION:
Either add the start restore access right to your Data Protector user group or
transfer your Data Protector user name to a user group that has
the start restore access right.
MESSAGE:
[32:23] You do not have permission to restore to other hosts.
DESCRIPTION:
You have no permission to restore to other hosts.
ACTION:
Either add the restore to other hosts access right to your Data Protector user
group or transfer your Data Protector user name to a Data Protector user group
that has the restore to other hosts access right.
MESSAGE:
[32:61] You do not have permission to perform an Informix restore.
DESCRIPTION:
You have no permission to perform an Informix restore.

To start an Informix restore your Data Protector user name has to be in the
Operator or Administrator user group.
ACTION:
Move your Data Protector user to the Operator user group, which has start restore
of integrations access right
MESSAGE:
[33:4] File containing Cell Manager host not found.
DESCRIPTION:
The client is not able to determine its Cell Manager. Either the client was
exported from the cell or client's configuration is corrupted.
ACTION:
Import the client to a cell.
MESSAGE:
[33:50] Cannot connect to session with sessionID p.
DESCRIPTION:
You tried to monitor a session that cannot be monitored,

or the session has already ended.
ACTION:
Restart the monitor, specifying a valid session.
MESSAGE:
[33:131] No details for this session type.
DESCRIPTION:
You tried to view status information for a session, which is neither a backup nor
restore session. You can only view status information for backup and restore
sessions.
ACTION:
Retry the operation, specifying a backup or restore session.
MESSAGE:
[33:132] Monitoring is not supported for this session type.
DESCRIPTION:
You tried to monitor a session that is not a backup or restore session. You
can only monitor backup and restore sessions.
ACTION:
Restart the monitor, specifying a backup or restore session.
MESSAGE:
[35:6] You have no permission to initialize a medium.
DESCRIPTION:
You tried to initialize medium, but you lack the Media configuration
access right.
ACTION:
Either add the Media configuration access right to this user class or
transfer this user to a user class that has the Media configuration access
right.
MESSAGE:
[42:4] Cannot connect to required session p.
DESCRIPTION:
You specified the wrong session ID when trying to abort a session.
ACTION:
Use the omnistat command to get the correct session ID, then try the command.
MESSAGE:
[42:7] You cannot abort session of this type.
DESCRIPTION:
You tried to abort a session that is not a backup or restore session. You can
only abort backup and restore sessions.
ACTION:
Wait for the session to end or abort the session in GUI where you started it.
MESSAGE:
[43:7] You do not have permission to start an omniupload.
DESCRIPTION:
You tried to start omniupload command but you have no permission to start it.
ACTION:
Either add the Device Configuration access right to this user group or transfer this
user to a user group that has the Device Configuration access right.
MESSAGE:
[47:2] You do not have permission to start the omnidev.
DESCRIPTION:
You tried to start omnidev but you have no permission to start it.
ACTION:
Either add the Device Configuration and Media Configuration access rights
to your Data Protector user group or transfer your Data Protector user to
a Data Protector user group that has Device Configuration and Media
Configuration access rights.
MESSAGE:
[60:1000] No reply from param1 on host param2.

Agent identification is "param3".
The connection to the agent will be closed.
DESCRIPTION:
Session Manager was waiting for reply from disk or Media Agent.
The reply did not arrive before the timeout.
ACTION:
Make sure that the client on the problematic host is installed correctly.
Also check the connection to the INET process on the client host
(telnet <client_hostname> 5555). Check that the client host is visible on the network
from the server (nslookup <client_hostname)). Repeat the same command also on client to
check that the server host is accessible and visible. Make sure that the client host
is included in the Cell Manager configuration.
MESSAGE:
[60:1001] Connection to the param1 on host param2 is inactive

for over than the timeout period and will therefore be closed.
DESCRIPTION:
Trouble communicating with one of the agents. Agent does not

update its status periodically and it most probably hanged or died
ungracefully.
ACTION:
Restart the same operation again. If it is reproducible, start the session in the debug mode
and notify the support.
MESSAGE:
[60:1002] Session Manager received close from the param1 on host param2
The agent did not respond in time. Connection will be closed.
DESCRIPTION:
The connection to disk, Media Agent or monitor was closed

unexpectedly. This is probably due to abnormal agent termination or
agent host shutdown.
ACTION:
* Make sure that the network between the server and problematic client is up and running.
* Restart the same operation again. If it is reproducible, start the session in the debug mode
MESSAGE:
[60:1005] Agent param1, version param2, is not compatible

with current version of Session Manager. Connection will be closed.
DESCRIPTION:
The agent is not compatible with the current version

of the Session Manager.
ACTION:
Install the new version of the agent on the problematic host.
MESSAGE:
[60:1006] The param1 on host param2 did not identify itself on startup.
Connection will be closed.
DESCRIPTION:
Agent must first identify itself to Session Manager in order

to check compatibility. The problem is probably due to inet process
on the target host being unable to execute the proper agent.
ACTION:
Check the availability of Data Protector executables on the target host,

their permissions and the availability of shared libraries.
MESSAGE:
[60:1008] Script param2 for the off line

mount request notification dispatching not found.
System error reported is "param1".
DESCRIPTION:
Cannot find the script for the off line mount request notification.
ACTION:
* Create the off line mount request notification executable.
On Unix computer:
Script must be owned by root. No one else must have write permission
for the script in order for the script to be executed.
MESSAGE:
[60:1012] Interprocess communication error on a Session Manager connection.

The connection was to param2 on host param3.
Ipc library reports "param1".
DESCRIPTION:
Unexpected interprocess communication error on a connection to

an agent or monitor. The connection is closed. If the connection was
to a monitor you can ignore this message.
ACTION:
* Make sure that the network between the server and problematic client is up and running.
* Restart the same operation again. If it is reproducible, start the session in the debug mode
MESSAGE:
[60:1014] Could not open log and media database.

Internal Database layer reports:
"param1".
Aborting.
DESCRIPTION:
Session Manager could not open the log and media database.
This could be result of lockmgr process not running or someone running
omnidbcheck command.
ACTION:
Check if there is anyone running omnidbcheck, and restart the

session after the check has finished. If there is no lockmgr process named
omni running (lockmgr -a omni) restart it. You can check the presence of the
lockmgr with omnisv -status command.
MESSAGE:
[60:1016] Unknown event on Session Manager from param1 on host param2.

DESCRIPTION:
Unknown event received from one of the agents.
ACTION:
* The client and server versions may be incompatible:

install the new version of the agent on the problematic host.
* Run the same session with the '-debug 1-99 <suffix>' option and
report this message to support service. Support service might request
the debug files that were written by the Data Protector.
MESSAGE:
[60:1017] Invalid format of the message from param1 on host param2.

DESCRIPTION:
Invalid format of the known message received from one

of the agents.
ACTION:
* The client and server versions may be incompatible:

install the new version of the agent on the problematic host.
* Run the same session with the '-debug 1-99 <suffix>' option and
report this message to support service. Support service might request

the debug files that were written by the Data Protector.
MESSAGE:
[60:1018] Error when starting agents on host param1.

Please check the inetd settings, security and availability of
Data Protector executables.
DESCRIPTION:
Error when starting the agent on target host.
ACTION:
Check the settings for the inetd daemon in /etc/inetd.conf

and /etc/services for the inet entry. Then check if the /opt/omni/lbin/inet
exists, is owned by root and has the setuid flag set.
Then check for other Data Protector executables in /usr/omni/bin.
The Media Agents are bma, rma, mma, uma, and the Disk Agents are vbda, vrda, rbda, rrda.
MESSAGE:
[60:1022] An old format of internal Data Protector message received

from param1 on host param2:
param3
Most probably the client does not have the latest version of Data Protector installed.
DESCRIPTION:
OmniBack II changed its internal message protocol for version A.03.10.
ACTION:
Make sure that the client you want to back up has the latest Data Protector version installed.
MESSAGE:
[60:1023] Medium "param1" labeled "param2"

of data format param3 - param4 is not compatible with
device "param5" of dataformat param6 - param7.
DESCRIPTION:
Specified medium was initialized and used on a device

that has different data format that the one currently used.
ACTION:
Use appropriate device according to dataformat of this medium.

Check that device uses media pool compatible with media dataformat.
MESSAGE:
[60:1025] The device is still in use by a media management operation.
DESCRIPTION:
Media management operations were allowed on this device in order to satisfy the mount request.
Mount request was confirmed but the operation is still in progress and the session cannot reclaim
the device.
ACTION:
- Wait for the media management operation to finish.

- Confirm mount request.
MESSAGE:
[60:1027] Blank medium with duplicate barcode found.

Conflicting medium : "p [p]"
DESCRIPTION:
You tried to use blank medium with barcode already used.

Since barcode is unique identifier it is strong possibility that
read of medium header failed and this blank medium is actually
a dp medium with corrupted header data.
ACTION:
* if medium is really blank you can use it by exporting conflicting medium

* if medium is actually a dp medium and is corrupted use some other medium
MESSAGE:
[60:1028] Medium "param1" labeled "param2"

is of data format param3 - param4 while datafromat of
device "param5" is configured to param6 - param7.
DESCRIPTION:
Specified medium was initialized and used on a device

that has different data format that the one currently used.
ACTION:
Data Protector tracks the NDMP server type to prevent backup and restore
between incompatible NDMP implementations. If you have modified your NDMP
configuration and switched the NDMP server type from NetApp to BlueArc/Hitachi/HP-X9000
consider setting the global option "CheckNdmpDataFormatType".
MESSAGE:
[60:1061] KMS reports storeid:keyid p:p not found. Aborting session.
DESCRIPTION:
The key required for encryption/decryption of data is missing. This can

happen if the medium is imported into the Cell Server without the associated
encryption keys being imported or if the keystore is corrupted.
ACTION:
* If the medium is imported, ensure that the associated keys are imported.
* If there is no medium to be imported or the problem persists even after
medium import, check the consistency of the keystore database by executing
the command "omnidbcheck -keystore".
* If there is an inconsistency reported, then the keystore should be restored
from the latest backup.
MESSAGE:
[61:1001] Invalid version of the param1 named "param2"

on host param3.
Reported version is param4.
DESCRIPTION:
The peer that communicates with the backup or restore session

manager reported invalid or unsupported version. The peer process is not
allowed to work with backup or restore Session Manager.
ACTION:
* Install the correct (new) version of the agents or commands on

the host you are having trouble with.
* It is possible that you have an invalid version of the Session Manager installed.
In that case install the correct (new) version of the Cell Manager.
MESSAGE:
[61:1002] The param1 named "param2" on host param3

reached its inactivity timeout of param4 seconds.
The agent on host will be shutdown.
DESCRIPTION:
The agent that works with the Session Manager has been inactive
for over than the global Session Manager timeout period. The Session Manager
shut the agent down.
ACTION:
* Incase of DB2 restore session please check whether table space container
re-creation is in progres and wait for the re-creation to complete then
restart the restore session or please increase the 'SmDaIdleTimeout'
to a suitable value and restart the restore session.
* Report the problem to the support.
MESSAGE:
[61:1003] The param1 did not identify itself in time of param3 seconds.
The agent on host param2 will be shutdown.
DESCRIPTION:
Every agent must identify first to the Session Manager. If the

agent fails to do so in about five minutes (configurable), the connection
to the agent is closed.
ACTION:
If several attempts to connect to the

Disk Agent fail, and the time exceeds the identification timeout, then
another agent is shut down because of the timeout. If this is the case,
report the problem to the support. Else check if everything is OK with
the host on which the agent should run, if it is not overloaded, if the
network connections are OK, ...
MESSAGE:
[61:1004] Error starting param1 on param2.
DESCRIPTION:
This error shows, when the inet process on the host where
the agent should run, cannot start the agent. The message from the
omniinet process may also be displayed and states the error. It is also
possible, that there is no omniinet configured in the /etc/services file,
or /usr/adm/inetd.sec prohibits its execution from the Cell Manager host.
ACTION:
* See the message from the inet process for the reason of the
error and then either set the permissions or install the binaries. If it
is not possible to run the omniinet process on the agent host (no omniinet
message),
then you should check your inetd daemon and its configuration files
(/etc/services, /etc/inetd.conf, /usr/adm/inetd.sec) for the omniinet entry.
* The access from the Cell Manager machine to the omniinet must be allowed
on every host, where the agents run.
MESSAGE:
[61:1005] Got unexpected close from param1 on param2.
DESCRIPTION:
The agent or monitor did not properly terminate. There are

several probable causes. First is, that the process was killed by user
or administrator of the machine, second, that there was not enough memory
for the agent to complete the backup.
ACTION:
Unknown.
MESSAGE:
[61:1006] Could not start param1 on param2.
DESCRIPTION:
Unknown error when starting an agent. Most probable, because

there is not enough memory on the agent to run. There could be other
possible causes.
ACTION:
Check for free memory on the agent computer. Contact

the support if there is enough memory. They should instruct you how
to produce the debug information necessary to identify the
cause of the problem.
MESSAGE:
[61:1011] Received reconnect request from param1@param3 "param2".
DESCRIPTION:
It is not possible to start Media Agent on specified host.

There might be a problem with your network setup or Data Protector inet
process is not properly configured on the target host.
ACTION:
Check your network setup and check if the configuration

of the /etc/services and /etc/inetd.conf on the target host is correct
for the inet entry."
MESSAGE:
[61:2001] No specification in the Session Manager command line options

or no such specification exists.
DESCRIPTION:
The specification specified by user does not exist on the Cell Manager host.
Or the Session Manager has no access to the file.
ACTION:
Check the spelling of the name of the specification.
MESSAGE:
[61:2012] Session pre-exec script p failed. Exit code = num

The session will not start.
DESCRIPTION:
Session pre-exec script must return 0 value in order to start

the session. If the pre-exec script returns anything but 0, the backup
or restore session will not start.
ACTION:
Check the pre-exec script and what it returns to the Session Manager.
MESSAGE:
[61:2013] Some of the backup devices are occupied. Session is waiting

for all the devices to get free.
DESCRIPTION:
Session Manager tries to lock all the devices it will use

before the session is started. If the devices are in use, the session
waits until the devices get free or the timeout (configurable) expires.
ACTION:
You can wait for other sessions to complete, abort other sessions,
to start the current, or abort the current session.
MESSAGE:
[61:2014] Someone is using the Data Protector Internal Database at this time.
Backup is waiting for the database to get free.
DESCRIPTION:
When performing the backup of the Data Protector Internal Database, the
Session Manager tries to get the exclusive access to the database. If this
is not possible, the backup of the database starts waiting for all other
processes to close the database.
ACTION:
Close all other sessions and all GUIs and omnidbcheck, if you
want the database backup to start immediately.
MESSAGE:
[61:2015] Timeout waiting for the devices to get free.

The session will terminate.
DESCRIPTION:
The session reached the timeout when waiting for all the devices
in a session to get free.
ACTION:
* You can configure the timeout with Data Protector global option.
If the default does not suit you, you can change it
in file $OMNICONFIG/options/global set the parameter
SmWaitForDevice to new value (in minutes).
* You can also schedule your backups in a way that they
don't have to wait for device.
MESSAGE:
[61:2016] Timeout waiting for the database to get free.

DESCRIPTION:
The session reached the timeout when waiting to get the exclusive
access to the database.
ACTION:
You can configure the timeout with Data Protector global option.
[in file $OMNICONFIG/options/global set the parameter SmWaitForDB
to new value (in minutes)] if the default does not suit you.
MESSAGE:
[61:2017] There are not enough licenses for all concurrent devices.
Session is waiting for some of the licenses to get free.
DESCRIPTION:
You have not enough licenses in order to run this session. The
session is waiting for some other session to complete and free some licenses.
ACTION:
Buy more licenses to increase the number of devices you can run
in parallel.
MESSAGE:
[61:2018] Timeout waiting for the licenses to get free.

DESCRIPTION:
The Session Manager reached the timeout waiting for some session
to complete and free the licenses needed for the session to run.
The session was aborted.
ACTION:
If the default timeout parameter is not OK, you can change it.
Set the SmWaitForDevice global option to new value (in minutes)
in file $OMNICONFIG/options/global.
Or buy more licenses to increase the number of devices
you can run in parallel.
MESSAGE:
[61:2021] Host p is not in this cell.

Object will not be backed up.
DESCRIPTION:
This message is displayed if you have exported or uninstalled a host, but the
same host is still configured in the backup specification.
ACTION:
* Modify the backup specification.

* Install the host or import it.
MESSAGE:
[61:2050] Too many backup sessions are running in parallel.

Session is waiting for some other session to complete.
DESCRIPTION:
Maximum number of running sessions per Cell Manager are limited.
ACTION:
Change MAXBSESSIONS option in global options file in order to increase

the number of maximum backup sessions running in parallel.
MESSAGE:
[61:2051] All mountpoints on host "p" are excluded.

Nothing will be backed up.
DESCRIPTION:
All mountpoints/drives that were retrieved from the specified

host are in the exclude list. No backup of this host will be performed.
ACTION:
Use the Data Protector GUI to remove some exclude items for the host backup.
MESSAGE:
[61:2052] Bar backup session was started but no client connected

in num seconds.
Aborting session!
DESCRIPTION:
Backup Session Manager did not receive a connection from

a bar client and it therefore aborted the session.
ACTION:
* Change the SmWaitForFirstBackupClient global variable to set a bigger timeout.

* Also make sure the system that the BAR client is started on is included
in the current Cell Manager (check the Cell Manager clients configuration,
and on the client /etc/opt/omni/client/cell_server (on UNIX) or the
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\OmniBackII\Site\CellManager
value (on Windows systems).
* Also make sure that the user on the client which is configured to perform the
BAR backup has an appropriate user rights in the current Cell Manager
users configuration.
MESSAGE:
[61:2053] While trying to get the mountpoints for host backup on host param1
an old format of Data Protector message was detected.
Most probably the client does not have the latest version of Data Protector installed.
DESCRIPTION:
Data Protector changed its internal message protocol for version 3.1.
ACTION:
Make sure that the client you want to back up has the latest Data Protector version installed.
MESSAGE:
[61:2060] KMS failed to automatically create a key for entity "p".
DESCRIPTION:
Key Management Server reported that it was not able to create a key.
ACTION:
Please check the audit log of the Key Management Server for errors.
Try to create an active key for this entity using omnikeytool command.
Check if the keystore is corrupted by running 'omnidbcheck -keystore'.
MESSAGE:
[61:2062] Failed to export encryption keys for medium "p".
DESCRIPTION:
Key Management Server reported that it was not able to export the requested key.
ACTION:
Please check the audit log of the Key Management Server for errors.
MESSAGE:
[61:3001] Unknown message (code param1) received from param2@param3.
DESCRIPTION:
Invalid message used in internal communication between session

manager, agent or monitor received by the Session Manager. This could be the
result of some protocol error, or version mismatch.
ACTION:
Please report the problem to the support.
MESSAGE:
[61:3002] Invalid format of the message "param1", received from param2

on host param3.
DESCRIPTION:
Invalid message format used in internal communication between

the Session Manager, agent or monitor received by the Session Manager.
This could be the result of some version mismatch or protocol error.
ACTION:
Please report the problem to the support.
MESSAGE:
[61:3003] Lost connection to param1 named "param2"

on host param3.
Ipc subsystem reports: "param4"
DESCRIPTION:
The mechanism used

in Data Protector for the communication is TCP. The error describes, that there
are some problems with the network/networking system software or with the
remote host.
ACTION:
* Check your network operation and the remote host operation. Also check that the
agent on the client did not die ungracefully due to a lack of system resources.
* If the problem persists, reproduce it with the debug option and contact support.
MESSAGE:
[61:3004] Internal SM connection error on connection to p

on host p.
DESCRIPTION:
Internal error.
ACTION:
Please report this error to the support.
MESSAGE:
[61:3005] Cannot perform stat() on script "param2",

system reports: "param1"
DESCRIPTION:
There has been a check to see if the executable file exists. This has failed because this
script cannot be found. This may be because of an incorrect spelling or because the script
is in an incorrect directory.
ACTION:
Check the spelling of the filename of the script and then check if this script exists in the
specified directory.
MESSAGE:
[61:3006] Script "param1" on the Cell Manager

has invalid permissions and will not be executed by Session Manager.
DESCRIPTION:
The mount request notification script must be owned by root,

and nobody except the owner of the script must have the write permissions
for the script.
ACTION:
Change the owner and/or permissions of the mount request notification

script.
MESSAGE:
[61:4001] Error accessing the database, in line param2, file param3.

Database subsystem reports:
"param1"
DESCRIPTION:
There is a problem with the Data Protector Internal Database.
ACTION:
If the cause of the problem cannot be found and eliminated by the information
described after "Database subsystem reports:", please report this error
to the support.
MESSAGE:
[61:4002] Could not initialize the database subsystem. Subsystem reports:

"p"
DESCRIPTION:
The Session Manager could not open the database. The database
was probably checked with omnidbcheck at the time or it was just backed up.
Or the Session Manager could not find all the necessary files on the
disk, to start the database.
ACTION:
Check if someone is running omnidbcheck, then check if the

backup of the Data Protector Internal Database is not running at this time. Else
check if all the database files exist in /usr/omni/config/db.
MESSAGE:
[61:4006] Could not connect to inet in order to start param3@param2 "param1".
DESCRIPTION:
Session Manager could not start the agent, because it

could not connect to omniinet process on that host that then starts the
agent.
ACTION:
* You should check your inetd daemon and its configuration files
MESSAGE:
[61:4007] Could not connect to inet in order to start param3@param2 "param1".
DESCRIPTION:
Session Manager could not start the Disk Agent, because it

could not connect to the omniinet process on that host which then starts the
Disk Agent.
ACTION:
* You should check your inetd daemon and its configuration files
MESSAGE:
[61:4008] Logical device "param1" not found in the database.
DESCRIPTION:
The logical device should be configured, before you can

start the backup.
ACTION:
Check the spelling of the logical device name. If it is correct,
then configure logical device with that name, because Data Protector does
not know anything about that device.
MESSAGE:
[61:4009] Pool "param1" contains different type of media that device

"param2" can use.
DESCRIPTION:
Pool you have selected for the backup contains media of a

different type than the configured device can use. Device default pool
will be used instead.
ACTION:
Change the name of the pool to a pool that contains the correct
media.
MESSAGE:
[61:4010] Pool "param1" not found in the database.
DESCRIPTION:
The pool you have specified for the backup is not found in the
database.
ACTION:
* Check the spelling of the pool name. If it is correct, then you have
deleted or not event configured yet the media pool with the specified name.
* Configure new pool with the name. Please specify the correct media type
for the pool.
MESSAGE:
[61:4011] No valid pool defined for use with the device "param1"
DESCRIPTION:
No or invalid pool was specified for the backup, and the device
default pool is also not configured or contains invalid media.
ACTION:
Configure or change the default pool of the logical device. You

can also specify which pool you want to use for the backup session.
MESSAGE:
[61:4012] Cannot switch session user, because the following error occurred
"p"
Aborting session.
DESCRIPTION:
The specified user was not found in the Data Protector user list
or an error occurred while parsing the Data Protector user data.
ACTION:
Please make sure that the user specified as the session owner exists in the
Data Protector user list. Also make sure that the user is properly configured on
the system.
MESSAGE:
[61:4014] Could not allocate media for the backup.

Media management subsystem reports:
"param1"
DESCRIPTION:
Session Manager tries to allocate a medium for the backup. There

are several reasons why this operation could fail. Most probably,
there are no media with any free space on it configured for the pool.
Other causes could be some errors accessing the database.
ACTION:
Check if you have any free media in the target pool. If not, then
add some. Else report the problem to the support. If you have a loose allocation
policy for the pool, then you could insert a blank medium, that would be
initialized during backup.
MESSAGE:
[61:4019] Could not allocate medium from pool "param1" with

strict allocation policy. Aborting Media Agent param2.
DESCRIPTION:
The pool media allocation policy for the pool you use for the
backup is strict. That means, that you have to use the medium Data Protector
determines it should be used. If the medium cannot be allocated, then
the backup to that device is aborted.
ACTION:
Add more media to the pool. If there are problems with

the database, report the problem to the support.
MESSAGE:
[61:4038] Pool "param1" used on device "param2" is Free pool and

Cannot be used for backup.
DESCRIPTION:
Your backup is configured to use Free pool for backup.
ACTION:
You should change you backup configuration for particular device in order to use regular pool
instead of free pool.
MESSAGE:
[61:4039] Following error occurred while storing detail catalog

information for device "param1"
with loaded medium "param2" [param3]
to Data Protector Internal Database:
param4
From this point on, all objects on this medium

will have logging switched to "No Log".
DESCRIPTION:
Data Protector could not store a part of the detail catalog during the backup or
import. All files that are backed up on the same device after this message are
not marked as backed up in the Data Protector Internal Database. Backup is still valid and
restore of complete objects is possible.
ACTION:
* Check the additional error message for the cause of the problem and fix the
problem. Most often the problem will occur when the disk runs out of space
or when the maximum size limit of the DC directories is reached.
* If you want to browse files in that particular backup import the catalog for the
medium that was in use when the error occurred and all media that were written
after the error in the same device
* Make sure that file system where DC directories reside supports large files.
MESSAGE:
[61:4051] The specified session owner was not found in the user list.
DESCRIPTION:
The user specified as session owner was not found in the Data Protector user list.
The backup may succeed anyway, but the user you have specified may not be able to
restore the data. Even in that case, another user with sufficient user rights
(or an Administrator) will be able to restore the data.
ACTION:
* Verify the user you have specified.

* Verify that the specified user is configured in the Data Protector user list.
MESSAGE:
[61:5004] There are not enough media in the exchanger to complete the backup.
Inserting new media during backup session will be necessary.
DESCRIPTION:
There are not enough media in the repository of the autochanger

in order for your backup to complete. You will probably get a mount
request during the backup.
ACTION:
You could perform the rescan of the autochanger (if repository is

not too large), and then restart the backup preview. If you still get
this message, you should replace some media in the autochanger (and
update the Data Protector picture of the device repository of course),
and run preview again, until preview runs without this message.
MESSAGE:
[61:5007] There are not enough media in the pool to complete the backup.
DESCRIPTION:
There are not enough media in the target pool used with
the device, to complete the backup.
ACTION:
You can use blank media, that will be initialized during the
backup, or you can initialize and add new media to the target pool.
MESSAGE:
[61:6001] No memory to receive the catalogs from the backup Media Agent
named "p". Malloc reports: "p"
DESCRIPTION:
There is not enough memory, so the Session Manager will not

write the backup detail catalogs to the database. The only effect of
this error will be, that the user will not be able to browse the
on-line file catalogs of the backup.
ACTION:
Remove the memory hogs from the system or add more swap space.
MESSAGE:
[61:6002] Error receiving catalog data from the BMA@"param3" "param1".

Ipc subsystem reports:
"param2"
DESCRIPTION:
An error occurred when receiving the backup detail catalog

from the Media Agent. The only effect of
this error will be that the user will not be able to browse the
on-line file catalogs of the backup.
ACTION:
Please report this problem to the support.
MESSAGE:
[61:6003] Size limit of the database reached. Catalogs will not be written to
the database for the rest of this session.
Running omnidbutil -purge could help prevent this error to occur.
DESCRIPTION:
The database has a limit on the size to which it is allowed

to grow (it never returns the disk space back to the system). When
the size limit is reached, the detail catalogs are no longer written to
the database, and the user is no longer able to browse the contents of the
backup.
ACTION:
Run omnidbutil -purge to reclaim some of the now used database

space. You can change the database size limit in file
$OMNICONFIG/options/global - parameter DBLIMIT specify MBytes.
MESSAGE:
[61:7001] Medium of type param1 discovered in device "param2".

The medium will not be used for the backup.
DESCRIPTION:
Media Agent checks for several media types, like tar, cpio,
fbackup, OmniStorage, ... If such a medium is discovered, it is not
initialized during the backup, as blank media are.
ACTION:
If you want to force the initialization of such a medium,

you should initialize the medium manually, by using -force option
for the initialization.
MESSAGE:
[61:7002] Medium with id param1 not found in the media database.

The medium will not be used for backup.
DESCRIPTION:
Medium that is checked if it can be used for the backup, was

not found in the database. This could mean, that the medium belongs to
some other cell, or that the database was reinitialized.
ACTION:
You could either import the medium, with all its data into the
database, or you could reinitialize the medium (with the -force option)."
MESSAGE:
[61:7003] Medium param1 in device "param3" does not belong to pool "param2".
The medium will not be used for backup.
DESCRIPTION:
Medium that is checked if it can be used for the backup, belongs

to a different pool than the backup target pool. The medium is not used
for the backup.
ACTION:
If you want to use that specific medium, you should move it to the
target pool, or you should specify a different pool for the backup.
MESSAGE:
[61:7004] Medium param1 in device "param3" cannot be used for backup.

Media management subsystem reports:
"param2".
DESCRIPTION:
Medium cannot be used for the backup. There are several possible
reasons. If the allocation policy does not allow appending to the medium,
and the medium contains some protected data, the medium is not allowed
to be used in the backup. The same goes when the allocation policy
allows appending, but the medium is full, and the data are still under
protection. Also, media which have copies cannot be appended.
ACTION:
You can remove the protection from all the sessions on the
medium. Do not do this, unless you are sure you do not need any data
contained on the medium.
MESSAGE:
[61:7006] Error checking medium "param1" in device "param2".

(param3).
DESCRIPTION:
An error occurred when checking the medium for the use in the
backup. The medium is not written to.
ACTION:
MESSAGE:
[61:7007] Could not add medium param1 to pool "param2".

Aborting backup to device "param3".
(param4).
DESCRIPTION:
An error occurred when adding a medium that was initialized

during the backup to the target backup pool. The backup to the
device was aborted.
ACTION:
MESSAGE:
[61:7008] Invalid medium param1 in the prealloc list

of the device "param2".
DESCRIPTION:
Invalid medium discovered in the prealloc list for the device.

The medium is deleted from the prealloc list.
ACTION:
Remove the medium from the device prealloc list in the backup specification.
MESSAGE:
[61:7009] Medium param1 in the prealloc list of the device "param3"

belongs to a different pool than "param2".
DESCRIPTION:
Medium in the prealloc list belongs to different pool than the

target pool for the backup. The medium will not be used in the backup.
ACTION:
Remove the medium from the device prealloc list in the backup specification
or change the target pool for the backup.
MESSAGE:
[61:7010] Medium param1 in prealloc list of the device "param2"

is protected and full or have copies.
DESCRIPTION:
Medium in the device prealloc list is full and contains

protected data. Such a medium is not used in the backup.
It is possible that medium has copies and cannot be
appended because of this.
ACTION:
If you want to use the medium, you can remove the protection
from all the data contained on the medium ('recycle medium'). Or you
can remove the medium from the device preallocation list. Or you
can ignore this message.
MESSAGE:
[61:7011] _________________________________________________________
Mount request:
MediumId : p
Label : p
Location : p
Host : p
Device : p
PD/slot : p
_________________________________________________________
DESCRIPTION:
All media available in the device is used up

for writing (backup) or reading (restore).
ACTION:
To confirm a mount request:
1. Insert a medium (put the device online if necessary):
2. Use the omnimnt command or the Data Protector GUI to confirm the mount .
MESSAGE:
[61:7101] Medium "param1" in device "param3"

in the pool "param2" with strict allocation policy
Cannot be used for backup.
Medium label is: "param4"
DESCRIPTION:
Library repository was not correct or if you are using pool which has
strict Media Allocation Policy, you must mount the exact medium
specified by the mount request.
ACTION:
Mount the medium specified by the mount request or use rescan library
before backup if you often manually replace media in a library.
MESSAGE:
[61:7109] Medium in device "param1" cannot be initialized.
DESCRIPTION:
Auto-initialization of blank media is not allowed even though media pool policy is set to loose.
This prevents accidental overwriting of valid media in case of a device malfunction.
ACTION:
* Format all new media before using them for backups.

* Alternatively, set InitOnLoosePolicy=1 in the global options file to disable this safety
feature.
MESSAGE:
[61:7300] MREQ 7300

param1
param2
param3
DESCRIPTION:
ACTION:
MESSAGE:
[61:7301] MREQ 7301

param1
param2
param3
DESCRIPTION:
ACTION:
MESSAGE:
[61:7302] MREQ 7302

param1
param2
param3
param4
DESCRIPTION:
There is no more media in pool with strict allocation policy.
ACTION:
Please add new media to pool.
MESSAGE:
[61:7303] MREQ 7303

param1
param2
param3
param4
param5
param6
DESCRIPTION:
ACTION:
MESSAGE:
[61:7310] MREQ 7310

param1
param2
DESCRIPTION:
ACTION:
MESSAGE:
[61:7311] MREQ 7311

param1
param2
param3
DESCRIPTION:
ACTION:
MESSAGE:
[61:7312] MREQ 7312

param1
param2
param3
param4
DESCRIPTION:
There is no more media in pool with strict allocation policy.
ACTION:
Please add new media to pool.
MESSAGE:
[61:7313] MREQ 7313

param1
param2
param3
param4
param5
param6
DESCRIPTION:
ACTION:
MESSAGE:
[61:7321] MREQ 7321

param1
param2
DESCRIPTION:
ACTION:
MESSAGE:
[61:7322] MREQ 7322

param1
param2
param3
param4
param5
DESCRIPTION:
Medium not resident.
ACTION:
Please enter medium into device.
MESSAGE:
[61:7330] MREQ 7330

param1
param2
param3
param4
param5
DESCRIPTION:
ACTION:
MESSAGE:
[61:7331] MREQ 7331

param1
param2
DESCRIPTION:
ACTION:
MESSAGE:
[61:7340] MREQ 7340

param1
param2
DESCRIPTION:
ACTION:
MESSAGE:
[61:8000] Client named "param1" not configured in the backup specification.
DESCRIPTION:
The client statement with the specified name must exist in the
backup specification used by the OB2BAR client. The backup is aborted if the client
statement is not found in the backup specification.
ACTION:
See the OB2BAR troubleshooting list.
MESSAGE:
[61:8001] No device configured for the client param1 in the backup specification.
DESCRIPTION:
For every client in the backup specification, there should be one or more
devices configured. The devices tell the Session Manager, where to
send the backup data. If there is no device specified for the client in
the backup specification, the backup is aborted.
ACTION:
*Edit the backup specification and add at least one DEVICE statement before
the CLIENT statement in the desired backup specification. The syntax of the DEVICE
statement is the same for the work list and the backup specification. See also
OB2BAR troubleshooting list.
MESSAGE:
[61:8002] Media used by the device "param1" is not the same as used by
the backup device "param2". Switching to backup device.
DESCRIPTION:
The restore device, specified by the user uses different kind

of media than the device on which the backup was performed. Thus the
backup device is also used to restore the data from the media.
ACTION:
Specify the logical device, that uses the same type of media
as the device on which the backup was performed.
MESSAGE:
[61:9000] Error getting positions of the object param1:param2

named "param3". Database error reported is:
"param4"
DESCRIPTION:
The restore will probably not work due to the database

corruption or system error.
ACTION:
You can try and restore the data directly from media. Call
the support.
MESSAGE:
[61:9001] Could not find the object param1:param2 named "param3"

in the database. Database error reported is:
"param4"
DESCRIPTION:
The object user is trying to restore is not found in the database.

This could be result of incorrect object specification or database corruption
or system error.
ACTION:
Check the object name and type first. If you are having problems
with the database, call the support."
MESSAGE:
[61:9002] Error reading positions of trees of object param1:param2

named "param3". Database error reported is:
"param4"
DESCRIPTION:
There was an error finding the positions of the data to be

restored. The data will be restored, but the restore could last a bit
longer then normal, since it is searching all the object data on media for
the files to be restored.
ACTION:
Run omnidbcheck.
MESSAGE:
[61:10001] param1
Cannot open() script: (param2)
DESCRIPTION:
An error occurred when trying to start the session pre-exec or

post-exec script.
ACTION:
Check if the script exists on the disk and if it has the execute
permissions.
MESSAGE:
[61:10002] param1
Script execution timed out => aborted by the Session Manager
DESCRIPTION:
The pre-exec or post-exec script should output at least one

character every couple of minutes. If not, the Session Manager terminates
the script. If this is a pre-exec script, the backup is not started.
ACTION:
Modify your script, to produce some output.
MESSAGE:
[61:10003] param1
Error reading script output (param2)
DESCRIPTION:
An error occurred reading output of the session pre-exec or

post-exec script.
ACTION:
None.
MESSAGE:
[61:11018] Could not find related full backup of the object

param1:param2 named "param3".
Backup mode is changed to full.
DESCRIPTION:
Full backup must exist before performing incremental backup.
ACTION:
Related full backup session is not yet in the internal database in the following cases:
* you are starting a backup of the object for the first time
* a full backup of the object already exists but with different trees specified
- trees of already backed up backup specification have changed
- multiple backup specifications with the same object and different trees exist
MESSAGE:
[61:12500] Cannot connect to inet for getting filesystem list

on host"param1".
DESCRIPTION:
In order to start host object backup, Backup Session Manager tries to

get the list of filesystems (mountpoints or disks) from host to be backed up.
This operation failed.
ACTION:
* Check that inet on the problematic host responds (telnet <host> 5555).
* Also check that there is Data Protector software installed on the client.
MESSAGE:
[61:17102] Not enough licenses "param1".

Session is waiting for some of devices to get free.
DESCRIPTION:
Session Manager does not get enough licenses for the devices you are using
ACTION:
Check if you have enough single drive licenses for the devices you are using.
If you are using Multidrive Server License instead of Single Drive , check if
"Client is Device server" option is set in Client/Install context in the GUI.
MESSAGE:
[61:17112] Medium header verification failed on drive p.

All objects on this medium will be marked as failed.
DESCRIPTION:
Medium header sanity check detected header consistency errors on the medium.
Medium will be marked as poor and all objects on this medium as failed.
ACTION:
* Replace the medium with a new medium.

* Back up all failed objects.
MESSAGE:
[61:17115] No licenses "param1".

Session will abort.
DESCRIPTION:
Session Manager does not find any licenses for the devices you are using
ACTION:
You do not have any single drive licenses for the devices you are using.
If you are using Multidrive Server License instead of Single Drive , check if
"Client is Device server" option is set in Client/Install context in the GUI.
MESSAGE:
[61:20005] Hard link detection is not supported with enhanced backups.

Hard links for object 'p:p' will be backed up as files.
DESCRIPTION:
Backup specification contains options for hard link detection that are not
supported with enhanced backups.
ACTION:
To suppress this warning in the future, modify the backup specification so

that it will not contain hard link detection options.
- For Windows Filesystem objects, unselect the "Detect NTFS hardlinks" option.
- For other Filesystem objects, select the "Backup POSIX hard links as files" option.
MESSAGE:
[62:1001] Specified device for the object not found.
DESCRIPTION:
Data Protector cannot find the specified device.
ACTION:
Check the device name spelling or the device configuration."
MESSAGE:
[62:1004] Object version not found or access denied.

Internal Database layer reports:
"param1".
DESCRIPTION:
Cannot find the desired data in the database.
ACTION:
Perform the media list operation first"
MESSAGE:
[62:1009] No objects to restore. Session will be aborted!
DESCRIPTION:
There are no objects and/or media available in the Data Protector Internal Database
for this restore session.
Most probably the media for this session were exported.
ACTION:
Check that this session and media still exist in the database.
MESSAGE:
[62:1017] Multiple devices with the same lockname detected.

Detected conflict: "p" "p" ("p")
DESCRIPTION:
Some devices are using the same lockname.

To avoid an infinite device lock, the session is aborted.
ACTION:
* Choose non-conflicting devices manually.
MESSAGE:
[62:1018] Medium '[p] p' might be

currently in use by another Data Protector process and cannot be loaded.
DESCRIPTION:
You tried to use a medium that is locked by either an executing process or a

process that terminated unsuccessfully. It is also possible that the medium
has been ejected from the library.
ACTION:
* If other Session Managers are running, wait until they finish (or are terminated)
and confirm the mount request.
* Check that the library repository is up to date. Rescan the library, if necessary.
MESSAGE:
[62:1021] Bar restore session was started but no client connected

in num seconds.
Aborting session!
DESCRIPTION:
Restore Session Manager did not receive a connection from

a bar client and it therefore aborted the session.
ACTION:
* Change the SmWaitForFirstRestoreClient global variable to set a bigger timeout.

* Also make sure the system that the BAR client is started on is included
in the current Cell Manager (check the Cell Manager clients configuration,
and on the client /etc/opt/omni/client/cell_server (on UNIX) or the
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\OmniBackII\Site\CellManager
value (on Windows systems).
* Also make sure that the user on the client which is configured to perform the
BAR restore has an appropriate user rights in the current Cell Manager
users configuration.
MESSAGE:
[62:1028] Filtering unrequired object versions.
DESCRIPTION:
Filtering unrequired object versions. This minimizes the number of media

that will be used for the restore. This operation may take some time,
depending on the restore selection and the size of database catalog.
ACTION:
* To cancel this operation, abort the session using the GUI or the omniabort CLI.
The session will use the information that has already been obtained.
MESSAGE:
[62:1057] Object "p" is not resumable and will be skipped.
DESCRIPTION:
Different restore chain is selected while resuming restore of the object.

Most probably some media available at the moment of original restore is not available now.
ACTION:
Check the availability of the media(s) or perform complete restore.
MESSAGE:
[62:1073] The library "p" that the media has been moved to does not contain
devices that can perform the requested operation.
Original Library: "p"
DESCRIPTION:
The medium was moved from the original to another library where no compatible
devices can be found. The restore or object copy cannot be performed.
ACTION:
* Check whether the medium is in the correct library.* Devices in the library must be enabled for
restore or object copy.* Check if the original backup device is tagged. If so, devices in the
library must also have this tag.* This may also happen if the original backup device was deleted
and new device with the same name was created in another library. This situation should be
avoided.
MESSAGE:
[62:1102] There were unsuccessful verifications!
DESCRIPTION:
The objects that are listed above were not successfully verified. Verification was either aborted
or errors were detected.
ACTION:
* Check the session output to find the reason for the failure.
MESSAGE:
[64:18] Some of the devices are occupied. Session is waiting

for all the devices to get free.
DESCRIPTION:
Session Manager tries to lock all the devices it will use

before the session is started. If the devices are in use, the session
waits until the devices are free or the timeout (configurable) expires.
ACTION:
You can wait for other sessions to complete; abort other sessions; or
start or abort the current session.
MESSAGE:
[64:19] Timeout waiting for the devices to get free.

DESCRIPTION:
The session reached the timeout when waiting for all the devices
in a session to be free.
ACTION:
* You can configure the timeout with the Data Protector global option.
You can change the default value
in $OMNICONFIG/options/global by setting the SmWaitForDevice parameter
to a new value (in minutes).
* You can also schedule your backups such that they
don't have to wait for devices.
MESSAGE:
[64:24] Device "p" cannot be used as source and destination device at the same time.
Device will be used as source device.
DESCRIPTION:
Same device cannot be used as source and destination device at the same time.
ACTION:
* Specify alternative source devices that will read media using "Source Devices"
page in GUI or -sourcedevice option in omniobjcopy command.
* Make sure that alternative source devices do not overlap with configured
destination devices.
MESSAGE:
[64:25] Cannot perform copy operation due to minimum number of devices not large enough.
Minimum number of devices is num, required num.
DESCRIPTION:
Certain applications generate dependant streams during backups. Copy

has to preserve stream layout and requires same number of devices that
were originally used for backup.
ACTION:
* Add at least required number of devices to copy.
MESSAGE:
[64:102] Object p from session p is not consolidatable.
DESCRIPTION:
The specified object may not be consolidatable for any of the following reasons:
* The object type does not support consolidation (for example, rawdisk backup, application backup,
and so on).
* All required backups were not performed with the Enhanced incremental backup option enabled.
* All required incrementals are not located in a single file library.
* All required backups do not have the status "Completed" or "Completed/Errors".
* A required backup is missing.
* A required backup is software encrypted.
* The selected object version is of type Full.
ACTION:
Determine why the object is not consolidatable and remove the cause before performing new backups
or consolidations.
MESSAGE:
[64:114] Aborting session. Recursive loop detected in the following post-copy specifications:
DESCRIPTION:
This copy specification includes another post-copy specification that triggers this copy
specification again, which results in a recursive loop. This would produce a never-ending loop of
copy sessions and therefore the session must be aborted.
ACTION:
Revise your chaining strategy and remove the recursive loop from the copy specifications used in
this session.
MESSAGE:
[64:120] Replacement device not found for 'p'.

DESCRIPTION:
The selected read device for selected object is Source-side gateway

and none explicit gateway of corresponding device were taget for copy.
ACTION:
Tag the explicit gateway for copy of corresponding device.

The other option is, that the original Source-side gateway is replaced with explicit gateway.
MESSAGE:
[64:151] Object p from session p could not be restarted.
The source object does not exist or does not match the filter criteria.
DESCRIPTION:
The source object cannot be found for one of the following reasons:
- The object does not exist anymore (for example, object was removed from database because
protection has expired).
- At the time of the restarted copying, the object does not match the selection criteria specified
in the object copy specification.
ACTION:
No action.
MESSAGE:
[64:155] Some object versions will not be copied, as they were filtered out
due to ownership settings.
DESCRIPTION:
You have selected to filter out objects owned by other users. This may
narrow the initial object selection in interactive object copy sessions,
and may even result in no object copies created.
ACTION:
To suppress this warning either select only objects that belong to the specified owner, or omit
filtering as follows:
* If starting the session from the GUI, clear the "Filter source objects by owner" option.
* If starting the session from the CLI, do not specify the -filter_by_owner option.
MESSAGE:
[64:156] Some object versions will not be consolidated, as they were filtered out
due to ownership settings.
DESCRIPTION:
You have selected to filter out objects owned by other users. This may
narrow the initial object selection in interactive object consolidation
sessions, and may even result in no objects consolidated.
ACTION:
To suppress this warning either select only objects that belong to the specified owner, or omit
filtering as follows:
* If starting the session from the GUI, clear the "Filter source objects by owner" option.
* If starting the session from the CLI, do not specify the -filter_by_owner option.
MESSAGE:
[65:2] Could not connect to Data Protector inet process on host p.
DESCRIPTION:
Media Management Session Manager cannot connect to Data Protector Inet

process on the reported host.
Possible causes:
* Data Protector is not installed on that host
* Windows: Data Protector Inet service is not running
* UX: operating system inetd is not running
* UX: inetd configuration is not correct
ACTION:
* Check if Data Protector is properly installed on the host.

* You can use "telnet <host> 5555" to check if Data Protector
Inet is up and running.
* Windows: Check if Data Protector Inet service is running.
* UX: Check if operating system inetd is running.
* UX: Check /usr/adm/inetd.sec if Data Protector Inet port
have strict security.
* UX: Check /etc/services and /etc/inetd.conf for.
Data Protector specific lines.
* UX: Tell /etc/inetd daemon to re-read the configuration
(/etc/inetd -c).
MESSAGE:
[65:3] Could not start Media Agent. Session is aborted.
DESCRIPTION:
Could not start Media Agent. Media Agent did not identify
itself to the Session Manager.
For details, see message from Data Protector Inet process.
ACTION:
* Check if Media Agent software is installed on the device host.
MESSAGE:
[65:4] Media Agent failed! Session is aborted.
DESCRIPTION:
Session Manager lost connection to the Media Agent.
Possible causes:
* Media Agent host went down
* Network between the Cell Manager and Media Agent host
went down or disconnected.
* Media Agent was killed/terminated

* Media Agent died ungracefully
ACTION:
* Check if the Media Agent host went down.

* Check the network connection between the Cell Manager and the Media Agent host.
* Check if the user on the Media Agent host killed the xMA process.
MESSAGE:
[65:5] Invalid version of peer "p", version "p".
DESCRIPTION:
Reported agent (Media Agent or command/GUI) is not

compatible with this version of the Session Manager.
ACTION:
* Check versions of installed software in your cell

and update all clients to the same version of software.
MESSAGE:
[65:6] Internal Database layer reports:

"p"
DESCRIPTION:
Data Protector Internal Database layer reports error.

See detailed error message for details.
ACTION:
* See detailed error message for troubleshooting.

* If you cannot resolve problem with information
you got in the error message, then you should
contact HP Support
MESSAGE:
[65:8] p on host p did not identify itself in

timeout of num seconds. Connection will be closed.
DESCRIPTION:
Reported agent did not identify itself in the required

timeout period.
ACTION:
* Check if Media Agent software is properly installed

on the Media Agent client.
MESSAGE:
[65:9] p on host p is inactive

for num seconds. Connection will be closed.
DESCRIPTION:
Reported agent was inactive for reported timeout

and is therefore probably hanging.
ACTION:
* Check the status of Data Protector

processes on the host.
MESSAGE:
[65:10] Invalid device "p" specified.
DESCRIPTION:
Specified device is not configured in this cell.
ACTION:
* Check spelling of device name.
MESSAGE:
[65:11] No slot ID for exchanger device specified.
DESCRIPTION:
Specified device is exchanger and needs a slot ID

to proceed.
ACTION:
* Specify exchanger slot(s) for operation.
MESSAGE:
[65:13] Invalid slot p specified.
DESCRIPTION:
Specified slot is not configured for the device.
ACTION:
* Check the library configuration and specify a configured slot.
MESSAGE:
[65:15] Default pool "p" of specified device is invalid.
DESCRIPTION:
Device's default pool is invalid (should not happen).
ACTION:
* Change device's default pool.
MESSAGE:
[65:16] Specified pool "p" is invalid.
DESCRIPTION:
Specified pool is not configured (does not exist).
ACTION:
* Specify configured pool.
MESSAGE:
[65:17] Device "p" and pool "p" do not match.
DESCRIPTION:
Device's media type is different than that of the specified pool.
ACTION:
* Specify pool with the same media type as that of the device.
MESSAGE:
[65:18] Communication error to p on host p

Error reported: "p".
Session is aborted.
DESCRIPTION:
Communication error to reported agent.
Possible causes:
* Media Agent host went down.
* Network between the Cell Manager and Media Agent host
went down or disconnected.
* Media Agent was killed/terminated.
ACTION:
* Check if the host went down.

* Check the network connection between the Cell Manager and the Media Agent host.
MESSAGE:
[65:19] Interprocess communication error:

"p"
DESCRIPTION:
Internal error of interprocess communication layer.
Possible causes:
* Network went down or disconnected.
* TCP/IP networking returned internal error.
ACTION:
* Check the network connection.

* If you cannot resolve the problem, then you should contact your HP Support representative.
MESSAGE:
[65:29] Pool "p" does not support magazine operations.
DESCRIPTION:
Magazine operation requested on pool which does not

support magazine operations.
ACTION:
* Configure your pool to have magazine support.
MESSAGE:
[65:31] Medium already in the database. No need to import.
DESCRIPTION:
Found medium is already in the Data Protector Internal Database.

There is no need to import it.
ACTION:
* Import Data Protector Foreign media only.

* If you are trying to import a magazine and would
like this medium to be part of the imported magazine
then you should export the medium and retry importing the magazine.
MESSAGE:
[65:32] Wrong medium loaded.
DESCRIPTION:
Non-Data Protector medium found in drive - cannot import or copy.
ACTION:
* Import Data Protector Foreign media only.

* Copy Data Protector media only.
MESSAGE:
[65:33] Original and copy mismatch.

Skipping medium.
DESCRIPTION:
The copy of the medium being imported does not match the original medium which is already in the
Data Protector Internal Database.
Possible causes:
* Original medium was overwritten.
* Original medium was appended in a new session.
ACTION:
* You can import the copy as a new original.
MESSAGE:
[65:35] Session already exists in the database.

Skipping medium.
DESCRIPTION:
Reported session already in the database.
Possible causes:
* You have tried to import an original medium which
already has a valid copy in the Data Protector Internal Database.
* You have tried to import a medium from a different cell
that has a session with the same sessionID already in the Data Protector Internal Database.
ACTION:
* Export copies, then import the original medium before the copies.
* If you just want to restore from that medium, you can
use the List from Media option. Otherwise, you should
first export the media that hold the duplicate session.
MESSAGE:
[65:45] You cannot copy media into a free pool "p".
DESCRIPTION:
Medium copy operation is not allowed for free pools, because the copied medium can be protected.
ACTION:
You should copy the medium into a regular pool.
MESSAGE:
[65:46] You cannot import media into a free pool "p".
DESCRIPTION:
You cannot import media into a free pool, because the imported medium can be protected (can have
valid protection).
ACTION:
You should import the medium into a regular pool.
MESSAGE:
[65:47] Magazine "p" already has a valid medium in slot p.

Try with the force option.
DESCRIPTION:
Specified magazine already has a valid medium

in the reported slot.
You cannot initialize a single medium in a magazine
if the old medium still exists.
ACTION:
* Check if you specified the correct slot.

* Export the magazine medium first.
MESSAGE:
[65:48] Cleaning tape requested by device "p".

Please clean the drive.
DESCRIPTION:
Reported device claims that the drive is dirty.
Possible causes:
* Drive is actually dirty.
* Drive does not support dirty drive detection.
* Drive makes false alarms about dirty drive.
ACTION:
* Clean the drive and retry the operation.

* Check the device documentation if the device
supports dirty drive detection. If not, you should
turn this off (in the Advanced options for the device).
* If the drive makes false alarms, it is possible that
old/worn media are causing the drive to become "dirty".
MESSAGE:
[65:49] Operation supported only on SCSI libraries.
DESCRIPTION:
Barcode scan, Enter and Eject operations are

supported only for SCSI libraries.
ACTION:
* You should run the operation on SCSI libraries.
MESSAGE:
[65:56] Number of media for the target device (num).

is different than number of media for the source device (num).
DESCRIPTION:
You have specified a different number of slots for the source device than for the target device.
ACTION:
* Specify an equal number of slots for source and target devices.
MESSAGE:
[65:57] Magazine with description "p" doesn't exist.

Cannot initialize a single medium.
DESCRIPTION:
You have specified a wrong magazine (does not exist).
ACTION:
* Check the magazine name and retry the operation.
MESSAGE:
[65:58] Magazine with description "p" already exist.

Cannot initialize a magazine medium.
DESCRIPTION:
You have specified a magazine name which already exists.

Cannot initialize magazines with duplicate names.
ACTION:
* Check that the magazine name does not exist and

retry the operation.
MESSAGE:
[65:59] Source medium has a larger capacity than the target medium.
Copy on medium "p" failed.
DESCRIPTION:
Target medium is too small to copy.
ACTION:
* Use target medium which is big enough and retry the operation.
MESSAGE:
[65:61] Medium is still under protection => recycle medium.
DESCRIPTION:
Data on medium is still under protection.
ACTION:
* to init/erase this medium, recycle it first.

Note: this will unprotect all objects on the medium.
* Retry the operation with the force option.
MESSAGE:
[65:62] This medium can be initialized only with the force option specified.
DESCRIPTION:
This medium cannot be initialized without the force option specified.
ACTION:
* to initialize this medium, specify the force option
MESSAGE:
[65:64] Initialization denied.
DESCRIPTION:
You cannot initialize this medium.

You should check above messages for details.
ACTION:
* Check detailed messages and retry the operation with the force option.
MESSAGE:
[65:65] Cannot lock the medium in the database. Probably in use.
DESCRIPTION:
Medium is locked by some other Data Protector process.
Possible causes:
* Medium is used in some other session which is still running.
* Medium is requested for mount request during backup.
* Medium was locked by some other session and the session died ungracefully.
ACTION:
* Retry the operation later when medium will be free.
MESSAGE:
[65:67] Erase denied.
DESCRIPTION:
Erase was denied.
Possible causes:
* Medium is not a Data Protector medium or not in the Data Protector Internal Database (Foreign).
* Medium data is still protected.
ACTION:
* Erase the Data Protector medium or recycle it first.
MESSAGE:
[65:68] Duplicate barcode [p]. Ignored.
DESCRIPTION:
Data Protector detected a barcode on a medium which is already

used by some other medium in the Data Protector Internal Database.
Data Protector ignored the barcode found and did not label
the medium with barcode.
ACTION:
Ensure that you don't have duplicate barcodes in your Data Protector environment. Then scan media
with wrong or changed barcodes.
MESSAGE:
[65:72] Cannot abort the ACS/DAS operation.
DESCRIPTION:
Data Protector cannot abort the ACS or DAS operation.
ACTION:
* You have to wait for the operation to finish.
MESSAGE:
[65:73] Media Management daemon reports:

"p"
DESCRIPTION:
Media Management daemon/service call failed.

See detailed error message for details.
ACTION:
* See detailed error message for troubleshooting.

* If you cannot resolve problem with information
you got in the detailed error message, then you should
contact your HP Support representative
MESSAGE:
[65:74] Slots are not configured.
DESCRIPTION:
Specified device is an exchanger, but does not have

any slots configured.
ACTION:
* Configure exchanger slots and retry the operation.
MESSAGE:
[65:77] Read from media denied.
DESCRIPTION:
Data Protector is unable to copy detected media.

You probably specified invalid medium to copy.
ACTION:
* You should specify a correct Data Protector medium and retry the operation.
MESSAGE:
[65:78] Same device p specified as source and target.
DESCRIPTION:
You have specified same device for source and target

device.
ACTION:
* You should specify different devices as the source

and target. They should be of the same media type.
MESSAGE:
[65:79] This medium is a copy.
DESCRIPTION:
Data Protector cannot copy a media copy.

You can only create media copies out of original media.
ACTION:
* You should create a media copy from an original medium.
MESSAGE:
[65:82] Slot p in use by some other Data Protector process.

Skipping slot.
DESCRIPTION:
Reported slot is currently in use by some other Data Protector session.
ACTION:
* Wait for other sessions to finish and retry the

operation later.
MESSAGE:
[65:85] Device "p" is not a part of a library and thus cannot

label a medium as barcode.
DESCRIPTION:
Cannot label the medium as barcode on the specified device,

because the device is not a part of a library.
ACTION:
* Use a device in a library to use barcode as medium label.
MESSAGE:
[65:86] Library "p" does not have a barcode reader or

barcode reader support not enabled.
DESCRIPTION:
Cannot label the medium as barcode on the specified device.

The specified device does not have a barcode reader
or barcode reader support is not enabled.
ACTION:
* If device has barcode reader, you should enable

barcode reader support in the library configuration.
MESSAGE:
[65:87] Operation supported only on ACS and DAS libraries.
DESCRIPTION:
Silo Query, Enter and Eject operations are supported only for ACS and DAS libraries.
ACTION:
* You should run the operation on ACS or DAS libraries.
MESSAGE:
[65:88] Library p does not have a barcode reader or

barcode reader support not enabled.
DESCRIPTION:
Cannot run a barcode scan on the specified device.

The specified device does not have a barcode reader
or barcode reader support is not enabled.
ACTION:
* If device has barcode reader, you should enable

barcode reader support in the library configuration.
MESSAGE:
[65:93] Slot p configured as cleaning slot ==> skipped.
DESCRIPTION:
Reported slot is configured as a cleaning slot the

in library configuration.
Data Protector does not load cleaning
tapes unless it's needed.
ACTION:
* If the slot does not hold a cleaning tape, you should

change your library configuration.
MESSAGE:
[65:94] Original medium with medium ID = "p"

belongs to Cell Manager p.
Only import as original can be done.
DESCRIPTION:
You want to import a medium copy, but the original medium

does not belong to this cell.
ACTION:
* You should import medium in the same cell as the original

or import a copy as original (which will create a new
original in this cell).
MESSAGE:
[65:95] Original medium with medium ID = "p"

doesn't exist in database.
Only import as original can be done.
DESCRIPTION:
You want to import a medium copy, but the original medium

is not in the Data Protector Internal Database.
ACTION:
* You should import the original before a copy

or import a copy as original (which will import the copy
as a new original, but you will not be able to
import the original later).
MESSAGE:
[65:96] Data on copy and original don't match.

Import failed.
DESCRIPTION:
You want to import a medium copy, but the copy holds

different data than that on the original.
ACTION:
* You can import a medium using the force option,

(which will import a copy as a new original).
MESSAGE:
[65:97] Slot p already updated with magazine medium ==> skipped.
DESCRIPTION:
Data Protector has detected a magazine in the exchanger and

automatically updated the device's repository.
There is no need to scan the updated slot.
ACTION:
None.
MESSAGE:
[65:98] Duplicate session ID found in the database.

New session was created by p.p@p.
New sessionID: p
DESCRIPTION:
Session ID already exists in the database, but the medium

was generated on a different Cell Manager.
Data Protector has allocated a new sessionID.
ACTION:
* You will have to use the new Session ID to access the

import data from the command line.
MESSAGE:
[65:99] Import failed with possible cause:

this media already has valid copy in DB.
DESCRIPTION:
Import of the medium failed because Data Protector information

about objects on the medium are already in the database.
This is because you already have a copy of the medium in the database.
ACTION:
* You cannot import an original medium if you already
have a valid copy in the database.

* You should export all copies of a particular medium, then import the original medium, and then
all
copies of the medium.
MESSAGE:
[65:120] Device is already locked by someone else.
DESCRIPTION:
Specified device is already in use by some

other Data Protector session.
ACTION:
* You should wait for other sessions to finish

and retry the operation.
MESSAGE:
[65:124] Medium is write-protected.
DESCRIPTION:
This medium cannot be used for write operations.
ACTION:
* to use this medium for write operations, remove write-protection.
MESSAGE:
[65:125] Data Protector medium "p" is write-protected.
DESCRIPTION:
This medium cannot be used for write operations.
ACTION:
* to use this medium for write operations, remove write-protection.
MESSAGE:
[65:139] Could not allocate any medium/device

for source medium 'p'.
DESCRIPTION:
Automated Media Copy found no source device or destination

medium/device that could be allocated.
Possible causes:
* No suitable source device could be used.
* No suitable destination device could be used.
* No medium could be allocated for any destination device.
ACTION:
* Check that there are enough source and destination devices configured for same media type.
* Check that source and destination devices are not disabled.
* Check that no backup sessions are using same devices as configured for AMC.
* Check that there are enough free/usable media of same type as source medium.
* Restart the session.
MESSAGE:
[65:140] No media matching the AMO specification parameters found.

Session will terminate.
DESCRIPTION:
Automated Media Copy found no media in the IDB

that need to be copied.
Possible causes:
* Backup sessions that should contain source media have failed.
* Inappropriate timeframe was specified in AMO specification.
* Backup specification(s) contained only media types unsupported by Automated Media Copy (NDMP,
Fastrax)
ACTION:
* Check that the AMO specification contains correct parameters.

* Verify this information using "Sessions In Timeframe" reports with same parameters.
MESSAGE:
[65:144] No media were copied in this session.

Session has failed.
DESCRIPTION:
Automated Media Copy could not copy any media in this session.
Possible causes:
* Backup sessions that should contain source media have failed.
* Inappropriate timeframe was specified in AMO specification.
* Backup specification(s) contained only media types unsupported by Automated Media Copy (NDMP,
Fastrax)
* No devices could be used.
* No destination media could be allocated.
ACTION:
* Check that the AMO specification contains correct parameters.

* Verify this information using "Sessions In Timeframe" reports with same parameters.
* Verify that devices used by Automated Media Copy are not used by other sessions.
* Verify that you have enough unused media to perform an Automated Media Copy operation.
MESSAGE:
[70:1] Protocol error: cannot parse options => aborting
DESCRIPTION:
Internal Error: The startup handshake protocol between the Data Protector
INET agent and the invoking session manager failed.
ACTION:
Verify that the INET executable on the client computer and Session Manager
versions are compatible.
MESSAGE:
[70:2] User "param1" non-existent on this host => aborting
DESCRIPTION:
Data Protector does not permit a user 'user:group' to start an agent

on a system where he does not possess a valid account. The INET
agent enforcing this security verification has detected such a
situation.
ACTION:
Create an account for the user on the system or run agents in root
mode.
MESSAGE:
[70:3] Group "param1" non-existent on this host => aborting
DESCRIPTION:

on a system where his group does not exist. The INET agent
enforcing this security verification has detected such a situation.
ACTION:
Create a group for the user on the system or change the group
membership of the user.
MESSAGE:
[70:4] User "param1" is not a member of the group "param2" => aborting
DESCRIPTION:

on a system where he is not a member of the specified group. The
INET agent enforcing this security verification has detected such a
situation.
ACTION:
Create a group for the user on the system or change the group
membership of the user.
MESSAGE:
[70:5] Cannot execute 'param1' (param2) => aborting
DESCRIPTION:
The INET agent is unable to execute the requested agent. The error
message indicates the reason as reported by the OS.
ACTION:
* Verify that the Data Protector product is installed correctly on

the problematic host.
* Verify that the specified agent binary can be accessed and
executed on the problematic host.
MESSAGE:
[70:6] Invalid exec code (param1) => aborting
DESCRIPTION:
Internal Error: The Session Manager requested the execution of an

invalid or non-existent agent.
ACTION:
Verify that the INET executable on the client computer and Session
Manager versions are compatible.
MESSAGE:
[70:7] Security violation: Cannot switch to uid=0 in user mode
DESCRIPTION:
Data Protector does not permit user 'root:sys' to be a member of a

non-privileged user class, since this could lead to network
security problems. The INET agent enforcing this security
verification has detected such a situation.
ACTION:
Verify that user 'root:sys' is not member of a non-privileged

user class running agents in 'user' mode.
MESSAGE:
[70:13] System limit exceeded when starting program 'param1' (param2) => aborting
DESCRIPTION:
The INET agent is unable to execute the requested agent. System error
indicates that the most likely cause is that the total size of arguments
exceeded the system limit for the total environment size.
ACTION:
* Verify the ARG_MAX (or equivalent) setting on the client system.

Increase the value to 102400 (or other suitable value).
* Alternatively, try reducing the number of -tree parameters in a
filesystem backup/restore, for example by breaking the restore into
smaller jobs.
MESSAGE:
[70:15] Cannot start program 'param1' (param2) => aborting
DESCRIPTION:
The INET agent is unable to execute the requested agent. The error
message indicates the reason as reported by the OS. The program exists but
it cannot be executed.
ACTION:
* Verify that the Data Protector product is installed correctly on

the problematic host.
* Verify that the specified agent binary can be accessed and
executed on the problematic host.
MESSAGE:
[70:22] Timeout period passed for the executed script.
DESCRIPTION:
The executed script did not return in the specific timeframe as expected.
ACTION:
Check the script for possible unresolved loops or unhandled situations.

Also, check if all processes needed by the script are valid targets and
that they are running. Try to run the script manually and check the results.
MESSAGE:
[70:23] Invalid parameters for the script to execute.
DESCRIPTION:
Parameters passed to the calling script are invalid.
ACTION:
Check the parameters that are sent to the script and see
if they match the parameters the script needs.
MESSAGE:
[70:24] A system error occurred when starting the target script or an agent module. The system
error code reported is num and the message resolves to 'p'.
DESCRIPTION:
The script or an agent module did not start because of a system error.
ACTION:
Check the reported system error message.
* Verify that the script exists.

* Verify that the specified agent is installed on the host, and that the agent's binary can be
accessed and executed on that host.
* If error code is "[128] There are no child processes to wait for.", Contact Microsoft for more
details and resolution.
MESSAGE:
[70:101] Inet process: Client process "p" did not connect !
DESCRIPTION:
Spawned child process failed to connect to Inet process.
ACTION:
* AS400: Check TCP/IP configuration. Test the

configuration issuing ping 'localhost' from
the console.
MESSAGE:
DESCRIPTION:
Disk Agent (xDA) was given an invalid option by the invoking

session manager. Could be that the user specified a
tree (or similar parameter) with a leading dash '-'.
ACTION:
Probably user error - check that there are no leading dashes.

Also, check that the agent version corresponds
to the session manager.
MESSAGE:
[80:1003] Cannot allocate/attach shared memory (param1) => aborting.
DESCRIPTION:
Disk Agent (xDA) or Application Agent cannot allocate/attach shared

memory for data transfer.
ACTION:
* In case that the error is reported in the following conditions:

- NT client
- Restore/Backup is started directly from Application Agent (Oracle EBU.EXE or
SAP BRRESTORE/BRBACKUP)
- Media Agent is running on the same host as Application Agent
then possible cause could be that Application Agent does not have
permissions to access shared memory created by Media Agent.
To resolve the problem one of the following solutions can be used:
- Add the user starting backup/restore to the local Administrator
or Backup Operator group.
- Set OB2SHMEM_IPCGLOBAL environment variable to 1 to allow all system
authenticated users to connect to Media Agent shared memory.
- Restart Inet service to run under the same account as user who
starts backup/restore
* On the other hand, the problem could be that there is not enough memory space
on the client. You can modify OS shared memory parameters in order to increase
shared memory space. Also, you can decrease block size of Media Agent which
results in slower backup but less space is allocated in shared memory.
* On NetWare client, the problem could be bad memory optimization or lack of
physical memory (RAM) (Article 'Optimizing IntranetWare Server memory' from
Novell's Application Notes, March 1997, discusses memory optimization
issues on NetWare server).
MESSAGE:
[80:1005] Agent requested a record of size num bytes,
maximum allowed for current block size is num bytes.
DESCRIPTION:
The most probable cause is that an internal limitation has been

exceeded. If this happens in SAP agent, read the instructions below
for possible workarounds.
ACTION:
Workarounds for SAP agent:

* Reduce the number of files that are backed up in a single session, or
* Increase the block size of the device.
MESSAGE:
[80:1010] Cannot initialize pipe connection (param1) => aborting.
DESCRIPTION:
The xBDA parent process is not able to open a pipe connection and
fork its NETIO process. This is possibly due to insufficient system
resources on the system running the xBDA agent. The error message
indicates the reason as reported by the OS.
ACTION:
o Verify that the system running the xBDA agent has sufficient
resources to open a pipe and establish an IPC connection.
MESSAGE:
[80:1011] Cannot fork NETIO process (param1) => aborting.
DESCRIPTION:
The xBDA main process is not able to fork its NETIO subprocess.
This is possibly due to insufficient system resources on the system
running the xBDA agent. The error message indicates the reason as
reported by the OS.
ACTION:
o Verify that the system running the xBDA agent has sufficient
resources to fork and execute another process. The most probable
cause is 'insufficient memory' or 'process table full'.
MESSAGE:
[80:1031] Received ABORT request from NET => aborting.
DESCRIPTION:
The NETIO process has requested an immediate abort. This is most

probably caused by an unexpected disconnect event on the connection
to the Media Agent, indicating an ungraceful termination of the
Media Agent.
ACTION:
o The backup will not be completed successfully. You should restart

the backup session.
MESSAGE:
[80:1200] param1
DESCRIPTION:
The xxDA received a -read option or an input redirection operator

ACTION:
o Verify that the input file exists on the appropriate system and
can be read by the xxDA.
MESSAGE:
[80:1552] Cannot load the specified Change Log Provider library "p".
Error: p
Will be using normal tree walk traversing as fallback.
DESCRIPTION:
The speciified Change Log Provider library could not be load because of:
+ the library could not be found on the system

+ the path given in the OMNIRC was not correct
ACTION:
o Please check if the library is put in the right place and the path in OMNIRC is correct.
MESSAGE:
[81:1] Invalid option "p" => ignored
DESCRIPTION:
The xBDA received an invalid option from the session manager. It is

possible that the user specified an option argument starting with a
dash character '-'.
ACTION:
* Check that option arguments do not have a leading dash.

* Verify that the xBDA and BSM versions are compatible.
MESSAGE:
[81:2] param1
DESCRIPTION:
The xBDA received a -read option or an input redirection operator
ACTION:
Verify that the input file exists on the appropriate host and
can be read by the xBDA.
MESSAGE:
[81:11] param1
Cannot open() script: (param2).
DESCRIPTION:
The xBDA cannot invoke a pre-/post-exec script using the open()

system call. The error message indicates the reason as reported by
the OS.
ACTION:
* Verify that the shell command line is syntactically correct and

does not contain inaccessible or non-executable command
invocations.
* Verify that the computer running the xBDA agent has sufficient
resources to spawn another process.
MESSAGE:
[81:16] param1
Error reading script output (param2).
DESCRIPTION:
The xBDA process detected an error while reading from the pipe
through which it is connected with its pre-/post-exec process. The
error is probably cause by an ungraceful termination of the script.
The error message indicates the reason as reported by the OS.
ACTION:

invocations.
* Verify that the executed programs behave as expected and do not
produce unexpected results. Test the shell command line manually
for possible bugs.
MESSAGE:
[81:42] Final BMA acknowledgment missing => backup INCOMPLETE
DESCRIPTION:
The xBDA was disconnected from the media agent before the last
pending data block was acknowledged. This indicates that the backup
record stream is not complete and the backup cannot be regarded as
successful.
ACTION:
The backup will not be completed successfully. You should restart

the backup session.
MESSAGE:
[81:49] The LOFS mountpoint has been skipped for backup.
DESCRIPTION:
The LOFS mountpoint has been skipped for backup. This indicates that the
disk agent has been configured to skip LOFS mountpoints to avoid duplication
of data by setting the Disk Agent variable OB2BACKUPLOFS to 0.
ACTION:
If the LOFS mountpoint needs to be backed up, the Disk Agent variable OB2BACKUPLOFS
has to be set to 1 and the backup needs to be restarted. By default, this variable
is set to 1.
MESSAGE:
[81:52] param1
Not a valid mount point => aborting.
DESCRIPTION:
The filesystem mount point specified by the user is not a real mount
point on the system running the VBDA agent.
ACTION:
Verify the configuration of the backup object and the table of

mounted filesystems on the host running the VBDA agent.
MESSAGE:
[81:53] param1
Not in hard link catalog => backed up regularly.
DESCRIPTION:
A hard link reference was created after the xBDA completed its 1st
treewalk building its internal hard link catalog. The object will
be backed up as a regular file and cannot be restored as a hard link
reference, but as a separate file only.
ACTION:
If you are concerned about the consistence of your backup data,

restart the backup session.
MESSAGE:
[81:54] param1
Object does not reside in current filesystem => not backed up.
DESCRIPTION:
The specified object (file/directory) does not belong to the

physical filesystem being backed up.
ACTION:
No actions are necessary. If you find this message annoying, you

may exclude the specified object from the backup fileset using the
-exclude option.
MESSAGE:
[81:55] param1
Unknown object type => not backed up.
DESCRIPTION:
The stat() system call identifies a filesystem object not

recognized/supported by Data Protector.
ACTION:
* No actions are necessary. If you find this message annoying, you

may exclude the specified object from the backup fileset using the
-exclude option.
* Please document the nature of the specified filesystem object and
notify Data Protector Support about the problem encountered.
MESSAGE:
[81:62] param1
Object is not a character device => not backed up
DESCRIPTION:
You have specified a rawdisk section pathname which does not refer
to a character device file.
ACTION:
Verify the configuration of the backup object and the rawdisk

section files on the host running the RBDA agent.
MESSAGE:
[81:63] param1
Object is not a disk device => not backed up
DESCRIPTION:
You have specified a rawdisk section pathname which does not refer
to a disk device.
ACTION:
Verify the configuration of the backup object and the

relevant device files on the host running the RBDA agent.
MESSAGE:
[81:64] param1
Object is a mounted filesystem
DESCRIPTION:
You have specified a rawdisk section pathname which refers to a disk

device containing a filesystem currently mounted.
ACTION:
No actions are necessary. If you are concerned about the

consistence of your backup data, you should use the pre/post-exec
feature to unmount the filesystem before the backup and re-mount
if after the backup has completed.
MESSAGE:
[81:65] param1
Cannot compute disk capacity (param2) => not backed up
DESCRIPTION:
Data Protector is unable to determine the capacity of the specified

rawdisk section. The list of possible reasons would be too long and
too technical. The section cannot be backed up.
ACTION:
Your disk is probably not supported by Data Protector. Determine

the disk drive model & notify Data Protector Support.
MESSAGE:
[81:71] Cannot open mount table: (param1)
DESCRIPTION:
Data Protector is unable to access the register of mounted

filesystems on the system running the VBDA agent. The error message
ACTION:
* Verify that the mount table (file /etc/mnttab on HP-UX and Solaris
systems) exists on the system running the VBDA agent and can be accessed.
* Consult you local system administrator about possible reasons for
this failure.
MESSAGE:
[81:72] param1
Cannot verify filesystem mount point: (param2).
DESCRIPTION:
Data Protector is unable to locate the specified mount point in the

register of mounted filesystems.
ACTION:
For Windows client systems:

* Verify that the drive exists on the client system and that the
files can be accessed (i.e. by Windows Explorer).
* If you have added the mount point manually, verify that it exists
on the client system. If the drive has removable media, verify
that the drive is not empty.
* If the drive was removed or reconfigured since the backup
specification was created, remove it from the backup specification
or correct the problem by reconfiguring the drive.
* If you are backing up a shared disk, make sure that you have
configured the Data Protector Inet account on the client system and
that this account can access the share of the remote system.
Also, make sure that you have specified a complete UNC path and
not a drive letter of a mapped network drive.
For UNIX client systems:

* Verify that the specified mount point exists on the system running
the VBDA agent and can be accessed.
* Is the specified filesystem mounted at backup time?
MESSAGE:
[81:74] Filesystem too deep: (param1) levels.
DESCRIPTION:
The Filesystem Backup Disk Agent has reached the maximum depth of
its recursive filesystem traversal. This indicates that your
directory structure is too deep to be processed by most UNIX
commands and should be re-structured to have less directory levels.
ACTION:
* Try to reconfigure the filesystem backup object to contain several

trees starting at a lower level in the directory hierarchy.
* Decrease the depth of the directory structure to less than 50
levels.
MESSAGE:
[81:75] param1
Cannot traverse: (param2) => not backed up.
DESCRIPTION:
The specified directory could not be traversed (probably due to

insufficient access rights) and will not be backed up. The error
ACTION:
* Eliminate the problem cause described by the error message and

* If you find this message annoying, you may exclude the specified
directory from the backup fileset using the -exclude option.
MESSAGE:
[81:76] param1
Cannot perform stat(): (param2) => not backed up.
DESCRIPTION:
The specified object could not be examined and will not be backed
up. The error message indicates the reason as reported by the OS.
ACTION:

object from the backup fileset using the -exclude option.
MESSAGE:
[81:77] param1
Cannot open: (param2) => not backed up.
DESCRIPTION:
The specified object could not be opened and will not be backed up.
ACTION:

object from the backup specification using the exclude option
(in backup specification editor or -exclude in the command line)
* On Windows, if the reported file is in the directory
%SystemRoot%\system32\config\ or an NTUSER.DAT file in
Documents and Settings, then it is a system specific file and can
not be backed up with a filesystem backup. Such files should be
excluded from the filesystem backup definition because they are
backed up through the Data Protector CONFIGURATION backup.
The following are some examples of such system specific files:
%SystemRoot%\system32\config\default
%SystemRoot%\system32\config\DEFAULT.LOG
%SystemRoot%\system32\config\SAM
%SystemRoot%\system32\config\SAM.LOG
%SystemRoot%\system32\config\SECURITY
%SystemRoot%\system32\config\SECURITY.LOG
%SystemRoot%\system32\config\software
%SystemRoot%\system32\config\SOFTWARE.LOG
%SystemRoot%\system32\config\system
%SystemRoot%\system32\config\SYSTEM.ALT
%SystemRoot%\system32\Perflib_Perfdata_001.dat
C:\Documents and Settings\administrator\NTUSER.DAT
MESSAGE:
[81:78] param1
Cannot read param2 bytes at offset param3: (param4).
DESCRIPTION:
The specified object could not be read and will not be backed up.
ACTION:

MESSAGE:
[81:79] param1
Cannot close: (param2).
DESCRIPTION:
The specified object could not be closed after it has been backed up
and its backup status will not be successful. The error message
ACTION:

MESSAGE:
[81:80] param1
Cannot preserve time attributes: (param2).
DESCRIPTION:
The VBDA is not able to preserve the time attributes of the

specified object. The error message indicates the reason as
reported by the OS.
ACTION:
* No actions are necessary. The VBDA attempts to reset the DTA

(date/time accessed) attribute of each file as it is backed up.
* If the VBDA generates many messages of this type (caused
by insufficient access rights), you should set the 'Do not
preserve access time attributes' option in the configuration
of the backup object.
MESSAGE:
[81:81] param1
Cannot unlock (param2).
DESCRIPTION:
The specified object could not be unlocked after backup and its
backup status will not be successful. The error message indicates
the reason as reported by the OS.
ACTION:
No actions are necessary. The specified object will be unlocked

automatically as the VBDA process terminates.
MESSAGE:
[81:82] param1
Cannot apply lock: (param2).
DESCRIPTION:
The specified object could not be locked before backup. The error
ACTION:
* Eliminate the problem cause described by the error message.

* If the VBDA generates many message of this type (caused by
insufficient access rights), you should unset the 'lock files
during backup' option in the configuration of the backup object.
MESSAGE:
[81:83] param1
Cannot force lock: chmod(param2) failed! (param3).
DESCRIPTION:
The specified object could not be locked before backup. The error
ACTION:
* Eliminate the problem cause described by the error message.

* If the VBDA generates many message of this type (caused by
insufficient access rights), you should unset the 'lock files
during backup' option in the configuration of the backup object.
MESSAGE:
[81:84] param1
Cannot read ACLs: (param2).
DESCRIPTION:
The extended ACL attributes belonging to this object cannot be read

and will not be backed up. The error message indicates the reason
as reported by the OS.
ACTION:
Eliminate the problem cause described by the error message and

restart the backup session to complete a successful backup.
MESSAGE:
[81:85] param1
Cannot read link: (param2) => not backed up.
DESCRIPTION:
The specified symbolic link cannot be resolved and will not be

backed up. The error message indicates the reason as reported by
the OS.
ACTION:

restart the backup session to complete a successful backup.
MESSAGE:
[81:86] param1
Filesystem is mounted read-only => locking disabled.
DESCRIPTION:
The filesystem being backed up is mounted read-only or is read-only

by nature (CD-ROM) and does not support mandatory locking. The VBDA
will disable the locking feature automatically to prevent spurious
error messages.
ACTION:
No actions are necessary. If you find this message annoying,
unset the 'lock files during backup' option in the configuration

of this backup object.
MESSAGE:
[81:91] param1
Cannot unlock: chmod(param2) failed! (param3).
DESCRIPTION:
The specified object could not be unlocked after backup and its
backup status will not be successful. The error message indicates
ACTION:
No actions are necessary. The specified object will be unlocked

automatically as the VBDA process terminates.
MESSAGE:
[81:92] param1
File is longer than it was when it was opened.
(was param2 bytes, now param3 bytes)
DESCRIPTION:
File size has changed while the file was being backed up. Backup
image is incomplete and the data may also be in an inconsistent
state.
Backup image will be marked as invalid and will produce a warning
at restore time.
ACTION:
When restoring, be careful not to overwrite the files on the disk

with potentially corrupted files from backup. Restore to alternate
location or make sure that you have a consistent backup of the
current state.
If consistency of data is more important than the possibility that
backup processes will obstruct other processes when accessing the
files, you should consider using the 'Lock files during backup'
option.
MESSAGE:
[81:93] param1
File is shorter than it was when it was opened.
(was param2 bytes, now param3 bytes)
DESCRIPTION:
File size has changed while the file was being backed up. It is
very likely that the backup image contains inconsistent data.
Backup image will be marked as invalid and will produce a warning
at restore time.
ACTION:
When restoring, be careful not to overwrite the files on the disk

with potentially corrupted files from backup. Restore to alternate
location or make sure that you have a consistent backup of the
current state.
If consistency of data is more important than the possibility that
backup processes will obstruct other processes when accessing the
files, you should consider using the 'Lock files during backup'
option.
MESSAGE:
[81:141] param1
Cannot export configuration object: (param2) => backup incomplete.
DESCRIPTION:
The specified configuration object could not be exported for backup.

ACTION:
Special system configuration objects are exported to a temporary

directory prior to the backup.
The most common cause of export failure is insufficient disk space
on the drive where Data Protector is installed. If this is the case, then
try one or more of the following:
* Free some disk space.
* Delete any unneeded user profiles from Control Panel (System).
* Reduce the size of user profiles (i.e. by keeping user data in
another directory).
MESSAGE:
[81:145]
Automatic DR information could not be collected.
Aborting the collecting of system recovery data.
DESCRIPTION:
A fatal error was encountered during execution of the Automatic Disaster Recovery module.
As a result the System Recovery Data was not collected.
This backup cannot be used for Disaster Recovery purposes.
ACTION:
Review the Automatic DR log file (AutoDR.log) in the Data Protector temporary directory.
The cause for the fatal error is usually stated near the end of the log file.
Try to identify the cause of the error. Repeat the backup after the error has been corrected.
If the error cannot be corrected, uninstall the Automatic DR module and repeat the backup
procedure
to allow for Assisted Manual and Disk Delivery Disaster Recovery.
The following conditions have been reported to result in a fatal error:

1. Insufficient registry size
- Symptoms (i.e. log file entries):
ERROR registry 'Exception while saving registry'
...
WindowsError: [Errno 1450] Insufficient system resources exist to complete the requested
service.
- Action: Increase the registry size limit.
2. Improperly configured storage devices

INFO safeboot 'add services for class:' u'{CE5939AE-EBDE-11D0-B181-0000F8753EC4}'
[dev_get_service_keys] Class GUID = {CE5939AE-EBDE-11D0-B181-0000F8753EC4}
[get_device_string] DRIM_WIN_ERROR 13 SetupDiGetDeviceRegistryProperty
- Action: Identify the misconfigured devices and configure them.
Notes:
a) Such device appears as "Unknown device" in the Windows Device Manager.
b) Such error indicates that some drivers are most likely improperly installed/configured.
c) The GUID {CE5939AE-EBDE-11D0-B181-0000F8753EC4} is an example of "Medium Changers". The
actual GUID may differ.
MESSAGE:
[81:157]
Some non-critical errors were detected during the collecting of Automatic DR
data. Please review the Automatic DR log file.
DESCRIPTION:
A non-critical error was encountered during execution of the Automatic Disaster Recovery module.
This backup can most likely be used for Disaster Recovery purposes.
ACTION:
To identify the errors search for string " ERROR ".

Ignore all entries containing " WARN ".
Possible reasons:
1. Services/drivers outside of <SystemRoot> folder (e.g. virus scanners):
ERROR safeboot 'unsupported location' 'intercheck support 06' 2 u'\??\D:\Program
Files\Sophos SWEEP for NT\icntst06.sys'
- Action: None. This message may be ignored.
2. A disk larger than 7.8 Gb on Windows NT 4.0

INFO storage 'check_system_partition' 'boot' u'C:'
ERROR storage 'boot' 'volume' u'C:' 'last_cyl' 1105 ' >= 1024.' 'System may not boot after
disaster recovery.'
- Action: Check the boot/system volume size and physical location on the disk. If both of them
are physically located
below 7.8 Gb, the message may be ignored.
MESSAGE:
[81:160] p file/directory detected on the system.

This file/directory will not be backed up.
DESCRIPTION:
Manually created file/directory exists on the system.

This file/directory will not be backed up.
ACTION:
Create a hardlink to some other location.
MESSAGE:
[81:180] param1
Cannot clear archive flag: (param2).
DESCRIPTION:
The VBDA is not able to clear the archive flag of the

specified object. The error message indicates the reason as
reported by the OS.
ACTION:
The VBDA attempts to clear the archive flag for each successfully
backed up file. Failure to do so will affect future incremental
backups of this object.
If you receive this warning for many files and cannot remove
the cause, you should set the 'Do not clear archive flag' option
in the configuration of the backup object.
MESSAGE:
[81:181] param1
Duplicate filename => not backed up.
DESCRIPTION:
VBDA detected that a directory contains two files whose names differ
only in the capitalization. By default, the Windows Disk Agent
does not operate in the case sensitive (posix compatible) mode and
fails to back up some of the files.
ACTION:
It is recommended that you rename the conflicting files, using

the same utilities that you used to create them.
If you cannot avoid using duplicate filenames, you can set the
environment variable OB2NTCASESENSITIVE (see documentation for
how to use the omnirc file). However, you must be aware that
there are some limitations:
* Tree specifications become case sensitive. Certain objects may
fail if they were not properly capitalized (typically those that
were added manually).
All trees as well as the drive letter must be properly
capitalized.
* Case sensitivity is not consistent. Exclude, skip and only
specifications are NOT case sensitive. Also, tree specifications
cannot be used to guarantee that only the file that is specified
will be backed up or restored (usually, all files that differ
only in capitalization will be processed).
* Only files will be processed correctly. Duplicate directory names
will not be processed correctly even with OB2NTCASESENSITIVE set.
Furthermore, failures in backup with duplicate directory names
will NOT be reported (unlike when OB2NTCASESENSITIVE is not set).
If directory contents are similar, backup may finish without
errors, but will be incomplete or incorrect. It is therefore
still required that you avoid duplicate directory names.
* When restoring directories that contain duplicate filenames,
the restore will only operate properly if you use the
'Keep most recent' (MERGE) option.
If you need to restore only specific files, it is better to
restore the directory to a new location (using into or as
options) and then use POSIX utilities to manually copy the
files that you want to overwrite.
MESSAGE:
[81:202] param1
Not a valid VBFS mount point => aborting.
DESCRIPTION:
Backup session fails. The backup mount point is not the mountpoint of
the VBFS.
ACTION:
Check backup specification. Also, run the OmniStorage zdf command on

the Data Protector client host to find the VBFS mountpoint.
MESSAGE:
[81:230] Cannot read VBFS file (p).

VBFS API error code (num).
DESCRIPTION:
Either of the two NVB Disk Agents are running in parallel and the
mounting of the optical platter timed-out.
Something is wrong with the jukebox drives or optical platters.
ACTION:
* Use the -lock_file option in the backup specification for each NVB
Disk Agent. Also, check your jukebox and specify or modify
OB2OSTTIMEOUT value to 200 or more seconds in the .omnirc file.
* Use the fsckp command to check the platter where the file is.
MESSAGE:
[81:234] Cannot read VBFS file (p),

mounting a nearline volume failed.
DESCRIPTION:
Error number 203 (mounting a nearline volume failed) can be the result
of one of the following scenarios:
* The VBFS optical platter targeted for backup is dirty or damaged and
cannot be mounted in the jukebox.
* The latest VBFS optical platter that has been mounted cannot be
unmounted and remains in the jukebox drive, so the VBFS optical
platter targeted for backup cannot be mounted.
* Drive in the optical jukebox is being used by someone else and the
OmniStorage Library Manager cannot mount the VBFS optical
platter targeted for backup.
* Some other process has locked a VBFS optical platter targeted for
backup.
ACTION:
* Check to see if files on the VBFS optical platter are accessible by

"cat" or "more" commands.
Try to mount the VBFS optical platter manually with the
mountp OmniStorage command (you must find out the VBFS optical
platter volume ID with the zls file OmniStorage command).
* Try to mount and unmount all VBFS optical platters manually with
the mountp OmniStorage command.
* Use -lock_file option for backup.
Stop migration during backup. Migration is stopped by a command
issued before the backup process starts, the pre_exec command:
/usr/omnistorage/bin/qqr -s /vbfs_mount_point
If migration is stopped, you must start migration again with the
post_exec command :
/usr/omnistorage/bin/qqr -u /vbfs_mount_point
* Use the -lock_file option for backup. That will prevent other
processes from using the VBFS optical platters targeted for backup.
Stop migration during backup and restart it after the backup.
MESSAGE:
[81:239] Cannot read VBFS file (p),

read of nearline data failed.
DESCRIPTION:
Error number 10 (error reading file) can be the result of one of the
following scenarios:
* The VBFS optical platter targeted for backup is dirty or damaged and
cannot be mounted in the jukebox.
* Some other process has locked the VBFS optical platter targeted for
backup.
ACTION:
* Check to see if files on the VBFS optical platter are accessible by cat
or more.
* Specify or modify the OB2OSTTIMEOUT value to 200 or more seconds
in the .omnirc file. Also, try backup with the -lock_file option
specified.
MESSAGE:
[81:250] Cannot establish connection with Library Manager host => aborting.
DESCRIPTION:
Backup session fails.

The backup Data Protector client does not have a VBFS manager running,
or the backup Data Protector client is an improperly configured
OmniStorage VBFS client.
ACTION:
=======
* Check all OmniStorage daemons on the OmniStorage VBFS client host.
* If all is well, shut down and restart OmniStorage.
* If you are backing up the OmniStorage VBFS client, set the
OB2OSTSERVER environment variable to the full domain name of the
OmniStorage VBFS server host.
* Ensure that the full domain name of the OmniStorage VBFS server host
is configured in the /etc/hosts file on the OmniStorage VBFS client
host.
MESSAGE:
[81:302] param1
Object is not a character device => not backed up.
DESCRIPTION:
You have specified a rawdisk section pathname which does not refer to
character device file.
ACTION:
Verify the configuration of the backup object and the rawdisk section files on
the host running the Disk Agent (RBDA).
MESSAGE:
[81:304] param1
Object is a mounted filesystem.
DESCRIPTION:
You have specified a rawdisk section pathname that refers to a disk device
containing a filesystem currently mounted.
ACTION:
No action is necessary. If you are concerned about the consistency of your

backup data, you must use the pre/post-exec feature to unmount the
filesystem before the backup and remount it after the backup has completed.
MESSAGE:
[81:305] param1
Cannot compute disk capacity (param2) => not backed up.
DESCRIPTION:
Data Protector is unable to determine the capacity of the specified rawdisk

section. The section cannot be backed up.
ACTION:
The disk is not supported by Data Protector.
MESSAGE:
[81:316] param1
Object is not mounted foreign.
DESCRIPTION:
You have specified a rawdisk section pathname that refers to a disk device
currently not mounted foreign.
ACTION:
* Mount the disk device using the following command

mount /foreign devicename .
MESSAGE:
[81:518] Media Management Database corrupted ==> backup aborted!

Please run omnidbcheck to check database.
DESCRIPTION:
The IDB is not in a consistent state, so it will not be
backed up.
ACTION:
Run the omnidbcheck command to check the consistency of the

database. If this does not solve the problem, you must
restore the database from the latest backup.
MESSAGE:
[81:519] Catalog Database corrupted ==> backup aborted!

DESCRIPTION:
The IDB is not in a consistent state, so it will not be

backed up.
ACTION:

MESSAGE:
[81:522] Cannot back up internal database because another database check in progress.
DESCRIPTION:
The IDB cannot be backed up because another consistency

check of database is running. This can be done be either omnidbcheck command
or another backup of database in the same time.
ACTION:
You should back up your database in the time when you are sure that omnidbcheck
will not run. You should also take care that you don't have more than one
backup of internal database at the same time.
MESSAGE:
[81:523] Cannot step into a critical section.

The system reports: "p".
DESCRIPTION:
There is a problem stepping into a critical section, which may be due to the lack of semaphores.
ACTION:
Change the value of maximum number of semaphores on the system or stop some of the programs, which
are using semaphores.
MESSAGE:
[81:525] Failed to login into KMS server.
DESCRIPTION:
There is a problem logging in into the KMS server.
ACTION:
Check if the KMS server is running.
MESSAGE:
[81:526] Cannot lock the keystore.
DESCRIPTION:
There is a problem locking all the key stores, which may be due to the stores already locked.
ACTION:
The KMS may be already locked in another backup session.
MESSAGE:
[81:528] Key Store Database corrupted ==> backup aborted!

DESCRIPTION:
The Keystore is not in a consistent state, so it will not be

backed up.
ACTION:

MESSAGE:
[81:700] Cannot create a snapshot for "p" volume of size num MB.
DESCRIPTION:
Data Protector tried to create a snapshot for the particular HP NAS volume,
but failed to do so.
ACTION:
You should check if there is enough free space available to create

the specific snapshot. If not, either increase the free space
or set a smaller size for the snapshot volume.
Another option is also to disable snapshots on the particular client.
The size for the snapshot volume and the option to disable it
are specified in the .omnirc file. Refer to HP NAS documentation on how to
proceed.
MESSAGE:
[81:702] Cannot create snapshot "p" - snapshot already exists.
DESCRIPTION:
Data Protector tried to create a snapshot for the particular HP NAS volume,
but failed to do so because a snapshot with the same name already exists.
ACTION:
The following reasons are the most likely causes of the problem:
* Previous Data Protector session failed to remove the snapshot after backup
completed. If this is the case, remove the snapshot manually.
* Another Data Protector Disk Agent is backing up the same volume at the same
time. Modify the schedule for backup specifications so that only
one Disk Agent is running for a particular volume at one time.
If this does not help, you still have the option to disable the snapshot for
the particular client in the .omnirc file. Refer to the HP NAS documentation
on how to proceed.
MESSAGE:
[81:703] Snapshot "p" is not valid - object will be aborted.
DESCRIPTION:
Data Protector by default uses snapshots to back up HP NAS volumes. If the snapshot
becomes invalid, the data is no more consistent. Therefore, backup of the object
is aborted.
ACTION:
The most common reason for this is that the snapshot volume is full. The default
size is 10% of the volume size, but you can modify this in the .omnirc file.
If this does not help, you still have the option to disable the snapshot for
the particular client in the .omnirc file. Refer to the HP NAS documentation
on how to do this as well as on how to set the size for the snapshot.
MESSAGE:
[81:1009] It was not possible to create volume snapshot for 'p'. System error: 'p'.
DESCRIPTION:
Microsoft VSS Snapshot of the volume to be backed up could not be created due to a VSS system
error.
This could have occured due to lack of storage space or high disk activity.
ACTION:
Check the System and Application event logs for more information.
Retry the backup.
Provide a different dedicated volume for shadow copy creation.
Check the Data Protector Troubleshooting guide for more detals.
MESSAGE:
[81:1400] Cannot open the enhanced incremental repository, file p

(p)
DESCRIPTION:
The location where the enhanced incremental database is stored either does
not exist or is not accessible.
ACTION:
The system error may indicate the nature of the problem.

Verify that the directory exists and has appropriate permissions.
The permissions should allow both read and write access for all users.
MESSAGE:
[81:1402] Multiple serious errors while processing the enhanced incremental database (num times)
=> disabling further attempts.
DESCRIPTION:
Multiple errors related to the enhanced incremental database indicate

a serious problem with the repository. In this case Disk Agent switches
to conventional incremental backup to prevent the error messages from
clogging the session output and to decrease media space consumption.
From this point on Data Protector acts as if the enhanced
incremental repository was inaccessible.
Resulting actions and consequences (if any) are indicated by a message
at the end of the backup object.
ACTION:
The system error reported in previous errors may indicate the nature of the problem.
Verify that the directories and files exist and have appropriate permissions.
MESSAGE:
[81:1403] Multiple recoverable errors while processing the enhanced incremental database. Disk
Agent will continue with the same actions but will not report or log them anymore.
DESCRIPTION:
Multiple errors related to processing of enhanced incremental data occurred.

Disk Agent stops reporting them to prevent the error messages from clogging
the session output, but continues with the same actions.
Resulting actions and consequences (if any) are indicated by a message
at the end of the backup object.
ACTION:
Check for actions recommended for previous errors or warnings.
MESSAGE:
[81:1404] Due to errors in processing, this backup will not be suitable for object
consolidation.
DESCRIPTION:
Due to errors in processing, the Disk Agent was not able to use reliable
detection of changes for all files. Some or all files were backed up using
standard incremental criteria. Object consolidation of such backups is
not possible.
ACTION:

Since object consolidation of this object is not possible until the problem
is resolved, continue performing full backups on a regular basis.
MESSAGE:
[81:1405] Enhanced incremental detection was only performed where possible.
DESCRIPTION:
Due to errors or other conditions in processing, the Disk Agent was not able
to use reliable detection of changes for all files. Some or all files were
backed up using standard incremental criteria.
ACTION:
Enhanced incremental mode can be set to perform a full backup of problematic

directories and therefore guarantee that no changed files are missed.
Note that if there are many directories that cause this condition, changing
the enhanced incremental mode can result in a considerable increase of
media usage.
MESSAGE:
[81:1406] One or more directories were backed up in full mode to prevent potential data loss.
DESCRIPTION:
Due to errors or other conditions in processing, the Disk Agent backed up

files in some directories in full mode to prevent potential data loss.
This message indicates that Data Protector successfully
recovered from encountered conditions and that therefore this backup object
version can also be used for object consolidation.
ACTION:
This message itself does not indicate a problem. However, if there are
many directories that cause this condition, media space consumption may
increase significantly.
MESSAGE:
[81:1407] Due to a change of the backup space, num files were backed up in full mode.
DESCRIPTION:
When the backup space is extended (for example trees are added or excludes
are removed) all files that become part of the backup space are backed up,
regardless of whether they have changed or not. When the backup space
is modified, this message is informative and does not indicate a problem.
However, if this message is not a result of changes of the backup
specification, it may indicate that two or more backup specifications are
backing up different sets of files within the same backup object.
ACTION:
* Verify that this message is a consequence of changes of the backup

specification.
* If the message is caused by an interference between unrelated backup
chains, use the backup object description to separate them or disable
enhanced incremental option for all but one of them.
MESSAGE:
[81:1408] Enhanced incremental is not supported on this platform.
DESCRIPTION:
Disk Agent on this platform does not support the enhanced incremental option.
The option is ignored and a conventional full or incremental backup is performed.
As a consequence, object consolidation cannot be performed for backup
objects on this platform.
ACTION:
This message is informational.
MESSAGE:
[81:1421] Enhanced incremental database information is out of date for directory p.
DESCRIPTION:
This warning can be a result of the following situations:

* A directory that once existed has been created again. A single message
per such directory will be issued and the message will not recur in
future backups.
* The enhanced incremental database (or the entire system) was restored.
The condition will apply to all directories being backed up and will not
recur in future backups.
* There was a problem with updating the enhanced incremental database.
This will in most cases be indicated by an earlier error message. The
messages are likely to repeat in subsequent backups as long as the
underlying problem exists.
ACTION:
* In situations where this warning appears only once and does not persist
in future backups, typically no action is required. The actions taken by
Data Protector (if any) are indicated by a message at the
end of the backup object.
* If the problem persists, check the log files enhincr.log and debug.log
for details and resolve the problem that causes failures of updates of
enhanced incremental database files.
MESSAGE:
[81:1423] Enhanced incremental database update time mismatch for directory p.
DESCRIPTION:
Update time for information in the enhanced incremental database appears

to be in the future. This can happen in the following situations:
* Date/time on the Cell Manager system has been adjusted.
* Some sessions are taking a very long time to complete.
Note that differences smaller than approximately 1 day are handled internally.
ACTION:
Data Protector fixes the mismatch automatically. How files are

treated depends on enhanced incremental settings. Resulting actions and
consequences (if any) are indicated by a message at the end of the backup object.
When Data Protector fixes the mismatch, this and/or any other
session running on the same data may back up more than is necessary to
prevent a potential data loss (undetected changes).
If the problem persists, it is recommended that you determine the cause.
MESSAGE:
[81:1424] Cannot create a directory in the enhanced incremental repository, directory path p
(p)
DESCRIPTION:
The location where the enhanced incremental database is stored either does
not exist or is not accessible.
ACTION:
The system error may indicate the nature of the problem.

Verify that the parent directory exists and has appropriate permissions.
MESSAGE:
[81:1426] No free space available to write to the enhanced incremental database. Incremental
for-ever will not run until the problem is resolved.
DESCRIPTION:
This error condition can occur either when the disk is full
or when the database has reached its maximum storage limit.
ACTION:
If disk is full, free-up some disk space and re-run the backup.
* If the database has reached its size limit (~1 Terabyte), then
the error indicates the user has reached the supported limit of
40 billion of files per volume.
MESSAGE:
[81:1427] Timeout occurred when accessing the Enhanced incremental database. Backup continues in
normal full/incremental mode.
DESCRIPTION:
This error condition may occur when a disk agent timed-out while
waiting to access the enhanced incremental database file.
* This situation may occur when at the same instance of time,
multiple disk agents are running on the same mount point waiting
to access the enhanced incremental database file.
ACTION:
In situations where this warning appears only once and does not persist in
future backups, typically no action is required.
Data Protector will perform reliable detection of changes for all the files
in the next enhanced incremental backup.
* If the problem persists, then please increase the time-out period for that
particular backup through environment variables and re-run the backup.
MESSAGE:
[81:1428] Enhanced incremental information not found in Enhanced incremental database.
DESCRIPTION:
This message appears when there was missing information for a directory in the
enhanced incremental database due to errors or other conditions in processing.
* The Disk Agent will not able to use reliable detection of changes for all files
in such directories and files will be backed-up using standard incremental criteria.
ACTION:
In situations where this warning appears only once and does not persist
in future backups, typically no action is required.
* Data Protector will use reliable detection of changes for all files in the
next enhanced incremental backup. The actions taken by Data Protector (if any)
are indicated by a message at the end of the backup object.
* If the problem persists, check the log files enhincr.log and debug.log
for details and resolve the problem that causes failures of updates of
Enhanced incremental database files.
MESSAGE:
[81:1429] Access denied. Incremental for-ever will not run until the problem is resolved.
DESCRIPTION:
The warning indicates that the enhanced incremental database does not
have appropriate access permissions for the user.
ACTION:
Make sure that both the enhanced incremental database directory and
the database file have appropriate access permissions.
* The permissions should allow both read and write permissions for
users who can run backups.
MESSAGE:
[81:1430] Attempt to write a read-only Enhanced incremental database. Incremental for-ever will
not run until the problem is resolved.
DESCRIPTION:
The warning indicates that the enhanced incremental database does not
have WRITE permissions for the user.
ACTION:
Make sure that both the enhanced incremental database directory

and the database file have read and write permissions for users
who can run backups.
MESSAGE:
[81:1431] Disk I/O error occurred. Incremental for-ever will not run until the problem is
resolved.
DESCRIPTION:
This error condition occurs when the disk in use has issues.
On some platforms, this error could also be caused by a disk-full condition.
This error can also occur due to errors in processing the enhanced incremental database.
ACTION:
Please check if there are any problems in accessing your filesystem disk.
* If Disk is full, then free-up some disk space and re-run the backups.
* If there are no problems with the disk, and if the problem still persists,
then there could be issues in accessing the enhanced incremental database file.
* Please delete the enhanced incremental database file and run a full enhanced incremental backup.
MESSAGE:
[81:1432] The enhanced incremental database file is corrupted. Incremental for-ever will not run
until the problem is resolved.
DESCRIPTION:
The enhanced incremental database file in use is corrupted and hence

it is not possible to continue reliable detection of changed files.
ACTION:
Please delete the enhanced incremental database file and

run a full enhanced incremental backup.
MESSAGE:
[81:1433] Enhanced Incremental database file is invalid. Incremental for-ever will not run until
the problem is resolved.
DESCRIPTION:
The enhanced incremental database file that exists on disk is not a valid
database file and hence it is not possible to continue reliable detection of changed files.
* On some platforms, this message could also be caused by a corrupted
enhanced incremental database file.
ACTION:
Please delete the enhanced incremental database file and

run a full enhanced incremental backup.
MESSAGE:
[81:1505] Cannot register host p on IAP server p. The session will be aborted.
DESCRIPTION:
The IAP host and the IAP Deduplication Agent host have to be registered in the IAP to do backup.
The registration of host may fail because no registration rules apply to client, or IAP domain
is invalid or does not exist.
ACTION:
To fix this please go on the PCC machine of the IAP and check registration rules using the
"fglist regrules" to check for appropriate rules and check IAP domain configuration.
After that use "fglist hosts" to get a list of available hosts.
MESSAGE:
[81:1551] Change Log Provider API does not support hard-link search.
DESCRIPTION:
The Change Log Provider API does not support hard-link search. It will automatically back up hard-
links as normal files.
ACTION:
To avoid this warning, explicitly specify in the backup specification to back up hard-links as
normal files. You can do this by either applying an IAP-specific template to the backup
specification or by activating "Backup POSIX hard links as files" in "Object Properties"->"Other"
manually.
MESSAGE:
[84:5] Filesystem too deep: (param1) levels .
DESCRIPTION:
The Filesystem Backup Disk Agent has reached the maximum depth of
its recursive filesystem traversal. This indicates that your
directory structure is too deep.
ACTION:
* Try to reconfigure the filesystem backup object to contain several trees

starting at lower level in the directory hierarchy.
* Decrease the depth of the directory structure to less than 100 levels.
MESSAGE:
[84:6] Cannot open mount table: (param1).
DESCRIPTION:

filesystems. Probably invalid access rights.
ACTION:
Verify the cause of this problem described in the error

message and notify your system administrator.
MESSAGE:
[84:12] param1
Cannot force lock: (param2).
DESCRIPTION:
The specified object could not be locked before restore.

ACTION:
None.
MESSAGE:
[84:15] param1
Cannot close: (param2).
DESCRIPTION:
If the specified object cannot be closed after it is backed up,

the backup status of this object is unsuccessful.
The error message indicates the reason as reported by the operating system.
ACTION:
* Eliminate the problem described by the error message and restart the
backup session.
* Exclude the specified object from the backup fileset by using the
-exclude option.
MESSAGE:
[84:16] param1
Cannot unlock: (param2).
DESCRIPTION:
The specified object could not be unlocked after restore and

its restore status will not be successful.
ACTION:
None.
MESSAGE:
[84:20] param1
Cannot preserve time attributes: (param2).
DESCRIPTION:
The xRDA is not able to preserve the time attributes of the

specified object. The reason is most probably insufficient
access permissions.
ACTION:
* If the xRDA generated plenty of messages of this type, then

the -touch option should be used to disable time attribute
preservation.
MESSAGE:
[84:51] Filesystem (p) is READ ONLY !
DESCRIPTION:
FileSystem on which we wanted to restore data is mounted
read only.
ACTION:
* Unmount the filesystem

* Mount the filesystem back as read/write filesystem
* try again with restore of data
MESSAGE:
[84:67] param1
Failed to resolve short file name conflict => not restored.
DESCRIPTION:
This file cannot be restored because another file on the disk

already occupies the name with its short name (8.3) and the
Disk Agent failed to temporarily rename it.
ACTION:
Rename the file(s) that is (are) causing the conflict or

restore the problematic files to another location.
MESSAGE:
[84:68] p
File on the disk is newer than file on the tape => not restored.
DESCRIPTION:
Restore Disk Agent does not overwrite newer files by default.

To change the behavior, specify Overwrite in restore options.
ACTION:
This message is informational.
MESSAGE:
[84:71] param1
Cannot mknod: (param2).
DESCRIPTION:
You cannot restore special files, if you have no Access

Rights for 'restore as root'.
ACTION:
* get the Access Right for 'restore as root'

* try again with restore of data
MESSAGE:
[84:109] Incorrect type of backup - backup must be done with: p.
DESCRIPTION:
You wanted to restore file from session, which type is

RAW_DISK.
ACTION:
For restoration of file from rawdisk use Restore Single

File from Raw Disk.
MESSAGE:
[84:114] Unknown type of compression: num.
DESCRIPTION:
There is an error in the shared library 'libdc.sl' (on HP-UX) or

'libdc.so' (on Solaris). There is a difference between unique data
compression type of backup and shared library at restore.
Restored file is compressed.
ACTION:
Make or get the new shared library with right unique data
compression type and try to restore again or decompress
compressed file with your own program for decompression.
MESSAGE:
[84:119] Unknown type of encoding !
DESCRIPTION:
There is an error in the shared library 'libde.sl' (on HP-UX) or

'libde.so' (on Solaris). There is a difference between unique data
encoding type of backup and shared library at restore.
Restored file is encoded.
ACTION:
Make or get the new shared library with right unique data
encoding type and try to restore again or decode
encoded file with your own program for decoding.
MESSAGE:
[84:125] Disk full => restore aborted!
DESCRIPTION:
There is not enough space on the disk to complete the restore. When the
agent fails in the middle of a file, the file is left on the disk, but
the file is incomplete.
ACTION:
* Delete the partially restored file to prevent inadvertent use and to

prevent a conflict if you retry the restore session.
* Free up enough disk space and retry the restore session or restore
the data to another location.
MESSAGE:
[84:208] param1
Configuration object not recognized by the system => not restored.
DESCRIPTION:
The system does not have a corresponding configuration

object. This can happen if you reconfigure the system
between backup and restore or if you attempt to restore
configuration objects to another system that has a
different set of configuration objects.
ACTION:
This message will typically occur when you try to

restore a user profile that was deleted from Control
Panel. To restore a deleted profile, first recreate it
by logging on as that user. Then log off and run restore.
You can always restore any configuration object by
specifying a location using the Restore As option.
Configuration object will be restored as plain file(s).
You can then manually merge the files with existing
user profiles or reconfigure your system to recognize
the files as part of its configuration.
MESSAGE:
[84:209] param1
Cannot touch the file (param2).
DESCRIPTION:
When restoring user profiles, the file that contains

user's registry is touched (last modification time is
set to current time).
This prevents the system from overwriting the restored
profile by the roaming profile.
ACTION:
If the user profile you were restoring is not configured

as a roaming profile, this error can be ignored.
MESSAGE:
[84:210] param1
Object is not restorable.
DESCRIPTION:
This CONFIGURATION object can only be restored within

disaster recovery procedure.
ACTION:
None.
MESSAGE:
[84:304] Volume Shadowcopy Service encountered invalid state during restore.Aborting restore
DESCRIPTION:
Possibly some of the configuration object's services are not running.

It is possible that Active Directory/Certificate Server restore was
tried while Active Directory Domain Services/Active Directory Certificate
services were not started.
ACTION:
If Active Directory restore failed/Aborted, it may have to be done after boot in DSRM mode.
MESSAGE:
[84:500] Cannot migrate file (p) to the nearline storage.

DESCRIPTION:
The Data Protector restore to the VBFS works, but automatic migration of
restored files does not work.
ACTION:
Check all OmniStorage daemons on the Data Protector client host. Also,
check to see if the destination mountpoint is a VBFS mountpoint. If
everything looks fine, shutdown and restart OmniStorage.
MESSAGE:
[84:600] Cannot establish connection with Library Manager host.

DESCRIPTION:
The Data Protector restore reports an error, but the data is restored and
the files are not migrated to the nearline storage. The Data Protector
restore client host does not have the VBFS manager running.
ACTION:
Check all OmniStorage daemons on the Data Protector client host. If

everything looks fine, shutdown and restart OmniStorage.
MESSAGE:
[84:1400] Cannot resume restore of tree p in object p.

Error loading checkpoint information on the client.
DESCRIPTION:
Resume of a failed restore was not possible on the client.

Because checkpoint information cannot be loaded Disk Agent does not know from where to continue
the restore.
ACTION:
=======
To restore this object you need to start a new restore from the beginning, not a resume.
MESSAGE:
[84:1402] Resumed restore is not possible as some files would not be restored.
DESCRIPTION:
Resume of a failed restore was not possible on the client because not all hard linked files
would have been correctly restored.
ACTION:
=======
To restore this object you need to start a new restore from the beginning, not a resume.
MESSAGE:
[84:1403] If restore of this object version fails it will not be possible to resume it.
DESCRIPTION:
An error has occured while saving checkpoint information.

Checkpointing for this object will be aborted, and if restore of the object fails it will not be
possible to resume it.
ACTION:
=======
Verify that location where Disk Agent saves checkpoint information is writable and there is enough
diskspace available.
MESSAGE:
[84:2399] param1
Disk quota information was restored as plain text file:
param2
DESCRIPTION:
This version of Data Protector Disk Agent does not support

restore of disk quota information. The information was
restored to a plain text file located in <Data_Protector_home>\ mp
directory.
ACTION:
If disk quotas are used on the system in question, examine

the restored file and manually apply disk quotas.
If you do not intend to use disk quotas or if you do not
want to change current disk quota settings, ignore this
message.
MESSAGE:
[84:2400] GroupWise files cannot be restored to the original location.
DESCRIPTION:
====
GroupWise objects will have to be restored to a NSS or a native Linux volume.
ACTION:
Please use "as/into" options.
MESSAGE:
[85:23] param1
Not Super-User => cannot restore raw.
DESCRIPTION:
You cannot restore a disk image (rawdisk) or files from a disk image, if
you have no access rights for 'restore as root'.
ACTION:
o get the access right for 'restore as root'

o try again to restore
MESSAGE:
[85:109] Incorrect type of backup - backup must be done with: p
DESCRIPTION:
You wanted to restore a file from session, which type is

different than RAWDISK
ACTION:
For restoration of a disk image (rawdisk) the object must be backed up

as RAWDISK
MESSAGE:
[85:155] param1
Cannot write: (param2) => not restored.
DESCRIPTION:
Unable to write to raw volume or a raw physical drive.
ACTION:
If a formatted physical drive is being restored then it is possible

that this drive does not have a drive letter assigned.
Please assign a drive letter and retry the operation.
MESSAGE:
[85:300] p
Object is a mounted filesystem => not restored.
DESCRIPTION:
Disk image (rawdisk) has a mounted filesystem.
ACTION:
* Unmount the filesystem and try again to restore the disk image (rawdisk).
* If the filesystem is not mounted, this error indicates that the rawdisk's
superblock is corrupt. Run a filesystem check procedure to prepare the
rawdisk for restore.
MESSAGE:
[85:303] p
Object is not a disk => not restored.
DESCRIPTION:
The specified filename is not a character device file.
ACTION:
Check the restore object configuration.
MESSAGE:
[85:304] p
Object is not mounted foreign => not restored.
DESCRIPTION:
Disk device(rawdisk) is not mounted foreign.
ACTION:
* Mount the disk device using the following command

mount /foreign devicename and try again to restore the disk image (rawdisk).
* If the disk device is mounted foreign, this error indicates that the rawdisk's
superblock is corrupt. Run a filesystem check procedure to prepare the
rawdisk for restore.
MESSAGE:
[90:10] Invalid option combination (p)
DESCRIPTION:
The xMA received an invalid option combination

from the session manager.
ACTION:
Verify that all settings are correct and in

a supported configuration.
MESSAGE:
[90:11] Unrecognized option "p" => ignored
DESCRIPTION:
The xMA received an invalid option from the

session manager. It is possible that the
user specified an option argument starting
with a dash character '-'.
ACTION:
Check that option arguments do not have a

leading dash. Verify that the xMA and xSM
versions are compatible.
MESSAGE:
[90:12] param1
DESCRIPTION:
The xMA received a -read option or an input

redirection operator (-dev <file) and the input
file could not be accessed.
ACTION:
Verify that the input file exists on the

appropriate host and can be read by the xMA.
MESSAGE:
[90:16] Cannot initialize connection (param1)

=> aborting
DESCRIPTION:
The xMA parent process is not able to open

connection and start its NETIO process. This
is possibly due to insufficient system resources
on the system running the xMA agent. The error
ACTION:
Verify that the system running the xMA agent

has sufficient resources to establish an IPC connection.
MESSAGE:
[90:17] Cannot param1 NETIO process (param2) => aborting
DESCRIPTION:
The xMA main process is not able to start its NETIO subprocess.
This is possibly due to insufficient system resources on the
system running the xMA agent. The error message indicates the
reason as reported by the OS.
ACTION:
Verify that the system running the xMA agent has sufficient
resources to fork and execute another process. The most probable
cause is 'insufficient memory' or 'process table full'.
MESSAGE:
[90:23] IPC failure reading NETIO message (param1) => aborting
DESCRIPTION:
The xMA main process detected an IPC error reading an incoming NETIO
message. The error message indicates the reason as reported by the OS.
ACTION:
The session will not be completed successfully. You should

restart the session.
MESSAGE:
[90:24] Unexpected close reading NETIO message (param1) => aborting
DESCRIPTION:
The xMA main process detected a connection loss reading an incoming

NETIO message. The error message indicates the reason as reported
by the OS.
ACTION:

MESSAGE:
[90:25] Unexpected error parsing NETIO message (param1) => aborting
DESCRIPTION:
The xMA main process detected a parse error reading an incoming

NETIO message. This indicates that the received message was
incorrectly formatted.
ACTION:

MESSAGE:
[90:26] MA/NETIO protocol error => aborting
DESCRIPTION:
The xMA main process received an unexpected message type on its

NETIO IPC channel.
ACTION:

MESSAGE:
[90:27] IPC failure reading SM message (param1) => aborting
DESCRIPTION:
The xMA main process detected an IPC error reading an incoming

session manager (SM) message. The error message indicates the
ACTION:

MESSAGE:
[90:28] Unexpected close reading SM message (param1) => aborting
DESCRIPTION:
The xMA main process detected a connection loss reading an incoming

session manager (SM) message. The error message indicates the
ACTION:

MESSAGE:
[90:29] Unexpected error parsing SM message (param1) => aborting
DESCRIPTION:
The xMA main process detected a parse error reading an incoming

session manager (SM) message. This indicates that the received
message was incorrectly formatted.
ACTION:

MESSAGE:
[90:30] SM/MA protocol error => aborting
DESCRIPTION:
The xMA main process received an unexpected message type on its
session manager (SM) IPC channel.
ACTION:
Verify that the xMA and xSM versions are compatible.

MESSAGE:
[90:31] NETIO process have problem communicating with Media Agent => aborting
DESCRIPTION:
The NETIO process have problem sending or receiving data over IPC channel.
ACTION:
Check if main Media Agent process have some problems. You should restart
the session again.
MESSAGE:
[90:41] Invalid device type specified (param1) => aborting
DESCRIPTION:
The device type configured for this logical device is invalid.
ACTION:
Verify the configuration of the logical device.
MESSAGE:
[90:42] Invalid device policy specified (param1) => aborting
DESCRIPTION:
The policy configured for this logical device is invalid.

In case of ACS/DAS policy it is possible that ACS/DAS
packet is not installed.
ACTION:
Verify the configuration of the logical device. In case of

ACS/DAS policy verify if ACS/DAS packet is correctly
installed.
MESSAGE:
[90:43] param1
Invalid physical device type => aborting
DESCRIPTION:
The type of the physical device examined does not correspond to the
device type of the logical device as configured.
ACTION:
Verify the device type of the physical device and the logical
device configuration.
MESSAGE:
[90:44] No physical device(s) specified => aborting
DESCRIPTION:
No physical device pathnames have been specified for the indicated

logical device. Each logical device must be configured to contain
at least one physical device.
ACTION:
MESSAGE:
[90:45] No exchanger control device specified => aborting
DESCRIPTION:
No SCSI-II exchanger control device pathname has been specified for

the indicated logical device. A SCSI-II exchanger must have a
control device through which medium move commands etc. are issued.
ACTION:
MESSAGE:
[90:46] Invalid data format specified => aborting
DESCRIPTION:
The data format configured for physical device is invalid.

In case of NDMP data format it is possible that NDMP
MA package is not installed.
ACTION:
Verify the data format of the physical device. In case of

NDMP data format verify if NDMP MA package is correctly
installed.
MESSAGE:
[90:47] Invalid device block size for HP-UX, supports only <= (num) KB => aborting
DESCRIPTION:
The block size configured for the physical device is invalid.

The maximum device block size that HP-UX 11i v2 supports is 256 KB.
The maximum device block size that HP-UX 11i v3 supports is 1024 KB.
ACTION:
Verify the block size and format the media with appropriate block
size for HP-UX platforms.
To support large block size, set the "st_large_recs" the kernel parameter
to '1' by using the "kctune st_large_recs=1" command on HP-UX 11i v2 server.
MESSAGE:
[90:48] Medium is corrupted, trying to reconstruct.
DESCRIPTION:
This medium was found to be corrupted. This could happen if agents were
killed during a session or if a connection to backup device was cut during
backup.
ACTION:
Operation will be continued on this medium, but due to corruption

some recalculation of medium index may happen.
This operation usualy takes longer on deduplication storage and for larger media.
MESSAGE:
[90:51] param1
Cannot write to device (param2)
DESCRIPTION:
The xMA has detected an error while writing to the device. The
error message indicates the reason as reported by the OS. In addition,
you can check if debug log file contains more information.
In case of StoreOnceSoftware device, please check if StoreOnceSoftware service is running
and if the target store is accessible.
ACTION:

restart the session. If the error occurred on NT system and the
error reports incorrect parameter, the most probable cause is
the invalid block size used to configure the backup device.
You should check the device's block size and set it to the
appropriate value.
If the error reports "File too large", you should enable large
file support (if possible on system indicating message).
If you are using StoreOnceSoftware, try to reset the StoreOnceSoftware service
and then rerun the session again.
If you are using Smart Cache device retry the backup after adding more storage to Smart Cache.
MESSAGE:
[90:52] param1
Cannot read from device (param2)
DESCRIPTION:
The xMA has detected an error while reading from the device. The
error message indicates the reason as reported by the OS.
If error message indicates "Invalid medium data format" this medium
is probably unusable for appending backup, but may be still usable
for restore.
ACTION:

If the error reported is "Invalid medium data format" change the medium
since this medium is marked as poor.
In case of StoreOnceSoftware, try to restart the StoreOnceSoftware service
and check if the target store is accessible.
MESSAGE:
[90:53] param1
Cannot seek to requested position (param2)
DESCRIPTION:
The xMA has detected an error while attempting to position the

read/write head to a certain position. The error message indicates
ACTION:
A possible cause for this error is a corrupted tape format. Verify

the tape format using the Data Protector medium verification utility.
MESSAGE:
[90:54] param1
Cannot open device (param2)
DESCRIPTION:
The xMA has detected an error trying to open the device. The error
message indicates the reason as reported by the OS. Frequently, a
'No such device or address' message from a tape device indicates
that no medium is loaded or that a wrong device file is specified for this
device. This error can also be reported if the medium is bad or damaged.
It could also happen that the device is currently in use by
another process. A cleaning tape could be present preventing an
open procedure and a retry process could be in progress.
In the SAN environment the reason for this message can be a changed SCSI
address of a device. This could happen if a
reset in the SAN environment occurred through a reboot or power failure.
A 'Device driver is loaded' message means that you tried
to access this device through a SCSI driver while the device is locked by some
other driver. Try using the other driver instead (drive letter
or tapeX class on Windows NT).
In case of StoreOnceSoftware device, please check if StoreOnceSoftware service is running
and if the target store is accessible.
If you get the 'Operation timeout' message, the opening of the
device exceeded the available time defined by the OB2DEVTIMEOUT environment variable.
In case of a 'The medium is Write Protected' message, it is possible that the
medium is not write protected, but the tape drive supports only read operations
on this medium. This typically happens if you use previous generation media in a new
generation tape drive.
ACTION:
Verify that the medium is loaded and ready. Unset write protection on the
medium cartridge. Check that the medium is not damaged. Respond to a mount
request possibly pending. Check if the device file in the device configuration
is correct. If the device is in use by another process, wait till that process
finishes using the device.
If you are using StoreOnceSoftware, try to reset the StoreOnceSoftware service
and then rerun the session again.
MESSAGE:
[90:55] param1
FATAL error opening device (param2)
DESCRIPTION:
The xMA has detected a fatal error trying to open the device. The
ACTION:
MESSAGE:
[90:56] param1
Cannot close device (param2)
DESCRIPTION:
The xMA has detected an error while closing the device. The error
NOTE: An incorrectly closed Data Protector medium might result in
unrecoverable tape format inconsistencies !!
ACTION:
Verify the tape format using the Data Protector medium verification
utility. Restart the session as it might have completed unsuccessfully.
MESSAGE:
[90:57] param1
Cannot lock exchanger control device (param2)
DESCRIPTION:
The xMA could not reserve the exchanger control device for its
exclusive use. Exclusive locking is necessary for multi-drive
exchangers to prevent mechanical damage. You're likely to see this
problem if you're running several Media Agents that share the same
autochanger concurrently. The error message indicates the reason as
reported by the OS.
ACTION:
Restart the session as it might have completed unsuccessfully.
MESSAGE:
[90:58] param1
Cannot unlock exchanger control device (param2)
DESCRIPTION:
The xMA could not release the exchanger control device. The error
ACTION:
No actions are necessary. The exchanger control device will be

released automatically as soon as the xMA process terminates.
MESSAGE:
[90:59] param1 param2

Cannot open exchanger control device (param3)
DESCRIPTION:
The xMA could not open the specified exchanger control device. The
Frequently, a 'No such device or address' message from an exchanger
control device indicates that a wrong device file is specified for this
device. In the SAN environment the reason for this message can be a
changed SCSI address of the device that occurred in SAN. This could
happen if a reset in the SAN occurred through a reboot or power
failure.
ACTION:
Verify that the control device file exists on the appropriate host
and can be accessed by the xMA process. Check if device file in
device configuration is correct.
MESSAGE:
[90:63] param1 Cannot load exchanger medium (param2)
DESCRIPTION:
The exchanger failed to complete the SCSI move command. An operating

system error or a SCSI error has been encountered. The error message
indicates the reason as reported by the operating system or the
exchanger robotics.
ACTION:
Verify that the autochanger device is online and ready. If

necessary, perform a H/W reset of the autochanger or cycle power.
Then restart the failed Data Protector session.
Check that the drive is properly configured. The drive index may be
incorrect.
Also this message appears in when we try to load an STK medium
into a drive that is configured on a host where an MA-ACS Media
Agent is not installed.
MESSAGE:
[90:64] param1 Cannot unload exchanger medium (param2)
DESCRIPTION:
The exchanger failed to complete the SCSI move command. An operating

system error or a SCSI error has been encountered. The error message
indicates the reason as reported by the operating system or the
exchanger robotics.
ACTION:

Then restart the failed Data Protector session.
MESSAGE:
[90:65] param1
Cannot append to medium (param2)
DESCRIPTION:
The BMA process was unable to append to existing data on the medium
in use.
ACTION:
No actions are necessary. Data Protector will attempt to use another

medium as this one has no empty space available. Simply respond
to a possible pending mount request. If your medium is using
different block size than specified for your device you might
adjust it in device properties and be able to use this medium.
MESSAGE:
[90:71] param1
Cannot popen() script: (param2)
DESCRIPTION:
The xMA could not invoke a subshell script using the popen() system
call. The error message indicates the reason as reported by the OS.
ACTION:
Verify that the shell command line is syntactically correct and

invocations.
Verify that the computer running the xBDA agent has sufficient
MESSAGE:
[90:73] param1
Error reading script output (param2)
DESCRIPTION:
The xMA process detected an error while reading from the pipe
through which it is connected with its subshell process. The error
is probably cause by an ungraceful termination of the subshell. The
ACTION:
Verify that the shell command line is syntactically correct and

invocations.
Verify that the executed programs behave as expected and do not
for possible bugs.
MESSAGE:
[90:83] param1
Medium not in Data Protector format => aborting
DESCRIPTION:
The medium examined is not in Data Protector format and cannot be

verified by Data Protector.
ACTION:
Mount a valid Data Protector medium and restart the verification.
MESSAGE:
[90:87] param1
Cannot pre-erase (invalid physical device type) => aborting
DESCRIPTION:
The attempted optical pre-erase operation is not applicable to the

physical device type.
ACTION:
Attempt a pre-erase operation on raw magnetic disks only. Note that only some optical drives are
capable of
pre-erasing an optical platter.
MESSAGE:
[90:88] param1
Cannot pre-erase (unknown medium capacity) => aborting
DESCRIPTION:
The attempted optical pre-erase operation cannot be completed as the

capacity of the medium could not be determined.
ACTION:
Do not use the pre-erase feature on this optical disk. Data Protector
generally requires that the capacity of a rawdisk is known in
order to use and handle it properly.
NOTE: If only some of the optical disks within your autochanger
cannot be pre-erased, that might be an indication that
their surfaces are not impeccable. You should replace such
disks with fresh media.
MESSAGE:
[90:89] param1
Cannot determine disk characteristics (param2) => aborting
DESCRIPTION:
The attempted optical pre-erase operation cannot be completed as the

characteristics of the disk could not be obtained.
ACTION:
Verify that the disk drive model is supported by Data Protector.

Verify that the disk is not corrupted in any way.
Do not attempt to use such a disk again. This might be an
indication that its surface is not impeccable.
MESSAGE:
[90:90] param1
Cannot erase disk surface (param2) => aborting
DESCRIPTION:
The pre-erase operation failed due to a system error. The error

ACTION:

restart the session. If the disk refuses to complete the
pre-erase operation, you should not use it for backup/restore
purposes.
(Usually, a bad quality medium will cause this error!)
MESSAGE:
[90:101] [num:num] Invalid record header => block corrupted
DESCRIPTION:
The MA block at the specified position contains an invalid record

header which suggests that the block might be corrupted.
ACTION:
No recovery actions are possible. Document the problem and notify

Data Protector Support.
MESSAGE:
[90:102] [num:num] Invalid block header => not in Data Protector format
DESCRIPTION:
The block at the specified position is not in Data Protector format.

This is likely if an existing Data Protector tape has been partly
overwritten by another application.
ACTION:
Discard the invalid medium and export it from the Data Protector
Internal Database. You can re-initialize it and continue using it for your
backup.
MESSAGE:
[90:103] [num:num] Stored/Computed CRC mismatch => block corrupted
DESCRIPTION:
The CRC checksum computed at backup time does not match the newly
computed CRC at verify time. The block at the specified position is
probably corrupted.
ACTION:
Random bit errors which could produce this message are very
unlikely but still possible. Export this medium from the Data Protector
Internal Database and do not use it for backup anymore. It is probably
a good idea to retire such a medium ...
MESSAGE:
[90:113] Cannot unload medium, source drive (num) appears to be empty
DESCRIPTION:
The exchanger status indicates that the source drive of an attempted

unload operation is empty. An empty drive cannot be unloaded.
ACTION:
If this message does not reflect the real physical condition

inside the exchanger, then the internal exchanger status is
somehow corrupted and needs to be reset. Shut down the Data Protector
session, reset the exchanger (hit the reset button on the front
panel or cycle power) and perform a rescan from within Data Protector
MESSAGE:
[90:114] p Cannot unload medium, target slot (num) appears to be occupied
DESCRIPTION:
The exchanger status indicates that the target slot in the exchanger
repository already contains a medium. The unload operation cannot
be completed and the xMA must terminate.
ACTION:
If this message does not reflect the real physical condition

inside the exchanger, then the internal exchanger status is
somehow corrupted and needs to be reset. Shut down the Data Protector
session, reset the exchanger (hit the reset button on the front
panel or cycle power) and perform a rescan from within Data Protector
MESSAGE:
[90:115] p Cannot dismount busy drive, no empty slots available.
DESCRIPTION:
Data Protector tried to dismount a medium from a drive

back to a slot where it was mounted from. This slot and all other
slots are full. Thus Data Protector could not dismount
the busy drive.
ACTION:
Manually remove the medium from the drive or free up some slots/mailslots
MESSAGE:
[90:116] There are no available connections on the StoreOnce device. Retrying...
DESCRIPTION:
Media Agent couldn't establish connection to the StoreOnce device due to all
available connections being busy. Media Agent will keep retrying.
ACTION:
Please ensure that the device has enough free connections, and eventually
retry the operation at a later point in time.
MESSAGE:
[90:120] param1
Cannot get device file status (param2) => aborting
DESCRIPTION:
Cannot get the status of the device file. The device file name is specified at a
location where no file can be created.
ACTION:
Change the specified device file.
MESSAGE:
[90:121] param1
Not a character device nor regular file => aborting
DESCRIPTION:
You tried to work with a device that is a block device or the file name
specified is not a regular file.
ACTION:
Change the device file name into a character (raw) device or into a regular
file.
MESSAGE:
[90:122] param1
No access permission for device file => aborting
DESCRIPTION:
You have no permission to access the logical device.
ACTION:
Check your permissions and change them appropriately.
MESSAGE:
[90:123] param1
Unknown device, please check device support matrix
DESCRIPTION:
The type of the physical device examined does not correspond to the
device type of the logical device as configured. You may be using
a device that was not yet supported with this release or you are
using an unsupported device.
ACTION:
Verify that the device is supported in device support matrix.

If the device was in a list of supported devices with this
release check if the device type is set correctly in the
logical device configuration.
MESSAGE:
[90:124] Not a BSD device => aborting
DESCRIPTION:
You have used a device that is not defined as a Berkley Style Device.
ACTION:
In the Logical Device Editor change the logical device file name to
a BSD device. For more information on creating device file names, see
also the Operating System Manual.
MESSAGE:
[90:125] Limited block size of 64K => aborting
DESCRIPTION:
You have used a device that has a limited block size of 64K.
ACTION:
In the Logical Device Editor, change a logical device file name into
a device filename with unlimited block size.
MESSAGE:
[90:126] Not a variable block size => aborting
DESCRIPTION:
You have used a device that has a non-variable block size.
ACTION:
In the Logical Device editor, change the device file name appropriately
to a device file name with a defined variable block size.
MESSAGE:
[90:127] Cannot access blocks after early warning EOT (param1) => aborting
DESCRIPTION:
The medium is at a position after early warning End Of Tape, but blocks
are not accessible. It is possible that medium is damaged.
ACTION:
The following actions are possible:

* Check the error string and the Tape Alert Flag (if the device supports
the tape Alert diagnostics) and respond accordingly.
* The medium can be damaged, so replace it with a new one and restart the
operation.
MESSAGE:
[90:128] Cannot switch to exclusive access.
DESCRIPTION:
Operating system cannot switch to access for just one process. Probably
access is already excluded with some other process.
ACTION:
Wait for other process to finish, and then restart the operation.
MESSAGE:
[90:129] Medium has no capacity.
DESCRIPTION:
You tried to back up to a medium with no capacity.
ACTION:
Replace the medium with a medium that has enough capacity.
MESSAGE:
[90:130] Cannot open. Device is busy.
DESCRIPTION:
Device is busy (occupied by another process).
ACTION:
Wait until the other process is finished on the specified device.
MESSAGE:
[90:135] Cannot eject medium. (param1)
DESCRIPTION:
For some reason a medium cannot be ejected from a drive.
ACTION:
Eject the medium manually.
MESSAGE:
[90:136] Cannot get current medium position. (param1)
DESCRIPTION:
For some reason, the medium position cannot be determined.
ACTION:
Check the disk or magnet-optical device you are using.
MESSAGE:
[90:140] Unexpected status of medium. (devFlags=0xnum)
DESCRIPTION:
Medium is in position that is not expected for Data Protector.
ACTION:
Check the exchanger (library device).
MESSAGE:
[90:141] Partial read of a block.
DESCRIPTION:
From the medium just a part of that block was read instead of the whole
block.
ACTION:
You can still use this medium for restore but the data will be successfully
read only up to the point where the warning occurred.
MESSAGE:
[90:142] Attempted read after logical EOD. (param1)
DESCRIPTION:
Medium was positioned after the End Of Data where no data

block resides. Possibly the medium format is not in the Data Protector valid
format or Data Protector data is not written properly because of the hardware
failure.
ACTION:
You can use the medium only for restore because backup information can
not be appended to the medium.
MESSAGE:
[90:150] Skipping write. (Apparently SCSI bus reset).
DESCRIPTION:
A SCSI bus reset has been detected and the medium can be repositioned to
any position of data on tape. In order to protect data from being overwritten,
Data Protector stops writing data to the medium.
ACTION:
Media Agent will abort a current process.
MESSAGE:
[90:151] Apparently SCSI bus reset.
DESCRIPTION:
A SCSI bus reset has been detected.
ACTION:
Media Agent will abort current process.
MESSAGE:
[90:152] Cannot write to the device after early warning EOT. (param1)
DESCRIPTION:
Medium is positioned after early warning EOT and Data Protector is unable
to write on this part of medium.
ACTION:
Complete restore is still possible as long as the medium is not exported.
If you export the medium, a complete restore is not possible. Some data
written to the end of medium will be lost.
MESSAGE:
[90:153] Cannot write to the device. Position at physical EOT.
DESCRIPTION:
* This message occurs when copying a source medium to a target medium

with not enough space.
* Data Protector cannot write catalog data after the early warning end of
tape. The size of catalog data to be written between the early warning
end of tape and the physical end of tape is too large.
ACTION:
* Change the target medium with a medium, which has got enough space.
* The catalog data is written to the Data Protector Internal Database, and it can be
restored as long as the medium is not exported.
If you export the medium, full restore is impossible and some data
written to the end of tape will be lost.
MESSAGE:
[90:154] Partial write of a block.
DESCRIPTION:
For some reason there was just a part of block written to medium.
ACTION:
You can use this medium for restore only, but just up to the point where
the error occurred.
MESSAGE:
[90:155] Cannot close after write problem. (param1)
DESCRIPTION:
Data Protector was forced to close a current medium. However,

there was a problem closing the medium.
ACTION:
Check the device. If the device functions properly, there is probably a

problem with a medium. Try to perform the backup to another medium.
MESSAGE:
[90:156] Cannot open after write problem. (param1)
DESCRIPTION:
Data Protector was forced to close and re-open a medium.

But there was problem with re-opening.
ACTION:

MESSAGE:
[90:157] param1
Rewindable device.
DESCRIPTION:
Data Protector was forced to close and re-open a medium.

But the device was opened as a rewindable device.
ACTION:
Device must be opened as non-rewindable.
MESSAGE:
[90:158] Skipping write. (Apparently SCSI Unit Attention).
DESCRIPTION:
A SCSI Unit Attention has been detected and the medium can be repositioned to
ACTION:
Media Agent will abort a current process.
MESSAGE:
[90:159] Apparently SCSI Unit Attention.
DESCRIPTION:
A SCSI Unit Attention has been detected.
ACTION:
Media Agent will abort current process.
MESSAGE:
[90:160] Skipping write of filemark. (Apparently SCSI bus reset).
DESCRIPTION:
A SCSI bus reset has been detected and the medium can be repositioned to
ACTION:
Media Agent will terminate the current process.
MESSAGE:
[90:161] Cannot write filemark. (param1)
DESCRIPTION:
For some reason the filemark cannot be written.
ACTION:

MESSAGE:
[90:162] Skipping write of filemark. (Apparently SCSI Unit Attention).
DESCRIPTION:
A SCSI Unit Attention has been detected and the medium can be repositioned to
ACTION:
Media Agent will terminate the current process.
MESSAGE:
[90:172] INQUIRY call failed. (param1)
DESCRIPTION:
When the INQUIRY call fails, we are unable to find out what device we are
dealing with.
ACTION:
Check if the device is correctly connected to and recognized by the system.
MESSAGE:
[90:173] REQUEST SENSE call failed. Possible cleanme signal detection failure.
(param1)
DESCRIPTION:
When the REQUEST SENSE call fails we are unable to get special
information from a device such as the cleanme signal.
ACTION:
If this occurs at the beginning of a session, check if the device is correctly

connected to and recognized by the system. Otherwise, check if there is a
device error (needs cleaning).
MESSAGE:
[90:174] End-of-tape detection cannot be disabled. (param1)
DESCRIPTION:
End-of-tape detection cannot be disabled after receiving early

warning end-of-media.
ACTION:

problem with the medium. Try to perform the backup to another medium.
MESSAGE:
[90:175] End-of-tape detection cannot be enabled. (param1)
DESCRIPTION:
End-of-tape detection cannot be enabled before closing the medium.
ACTION:

problem with the medium. Try to perform the backup to another medium.
MESSAGE:
[90:180] Cannot rewind medium. (param1)
DESCRIPTION:
Device driver cannot rewind medium to the beginning of the medium.
ACTION:

problem with the medium. Try to perform backup to another medium.
MESSAGE:
[90:181] Cannot backspace segment. (param1)
DESCRIPTION:
Device driver cannot position medium back for specific number of

segments.
ACTION:

problem with a medium. Try to perform backup to another medium.
MESSAGE:
[90:182] Cannot forward segment. (param1)
DESCRIPTION:
Device driver cannot position medium forward for specific number

of segments.
ACTION:

MESSAGE:
[90:183] Cannot backspace block. (param1)
DESCRIPTION:
Device driver cannot position medium back for specific number of

blocks.
ACTION:

MESSAGE:
[90:184] Cannot forward block. (param1)
DESCRIPTION:
Device driver cannot position medium forward for specific number

of blocks.
ACTION:

MESSAGE:
[90:186] Lost position. (param1)
DESCRIPTION:
After positioning the medium, a real block position is different. Data Protector
detected that a block of data has been corrupted or not written to the
medium.
ACTION:
You can use the medium for restore up to the point where the error occurred.
MESSAGE:
[90:188] Medium full. Cannot append. (param1)
DESCRIPTION:
Cannot append to a full medium.
ACTION:
Use another medium that is not full.
MESSAGE:
[90:189] Cannot position to end of data. (param1)
DESCRIPTION:
For some reason device driver cannot position a medium to the end of data.
ACTION:

MESSAGE:
[90:190] Invalid format version of Data Protector medium.
DESCRIPTION:
Format version on the medium is not a valid Data Protector version.
ACTION:
Replace the medium with another one that has a valid Data Protector version.
MESSAGE:
[90:191] Invalid position specified. (param1)
DESCRIPTION:
Medium was positioned to the invalid position.
ACTION:
Try with segment and/or block specification that do not exceed a maximum
number of segments and/or blocks.
MESSAGE:
[90:192] Cannot position to the requested position. (param1)
DESCRIPTION:
For some reason medium cannot be positioned to the requested position.
ACTION:
Check whether medium is a valid Data Protector medium.
MESSAGE:
[90:193] Positioning to end of data failed. => retrying.
DESCRIPTION:
Positioning to end of data on the medium failed, possibly because of

device failure or media corruption. Data Protector tries to repeat the positioning
procedure several times, and if it succeeds, it continues the session.
ACTION:
Check if the device is working properly and if data on the medium is in

proper Data Protector format.
MESSAGE:
[90:194] Could not seek to the end of data. Please verify your tape. Since this
operation can take some time, please plan this activity.
DESCRIPTION:
Positioning to the end of data wasn't successful. This may happen when
the tape is poor or unusable, or when there is a problem with a drive
or when the data near the end of the tape is not correctly written on medium.
Please verify your tape using omnimver or verify the tape from the GUI.
ACTION:
Verify your tape with omnimver or GUI verify for possible data format
corruption. If tape is poor or unusable you cannot use it for backup
append anymore.
MESSAGE:
[90:195] Physical position of the last segment is not consistent with the
position information from the database. Instead of expected last
segment number num, last segment on the tape is num.
DESCRIPTION:
During positioning to the end-of-data there was noticed that

position on the last segment written on the tape is not the same as
the position that was expected by the Internal Database. When difference between
expected and actual segment number is two, it reflects that the last
backup didn't finish normally. Probably the BSM was killed or BMA
lost connection with BSM. The backup will proceed normally anyway.
ACTION:
You should check with omnimver or TapeAnalyser if tape is OK and verify

if the positions are written in correct ascending order. If there is
no problem with the tape it is probably the Internal Database that is not up to date
or corrupted.
MESSAGE:
[90:196] Invalid format version of Data Protector medium reported in Cartridge memory.
DESCRIPTION:
Format version stored in the medium's cartridge memory is not

a valid Data Protector version.
ACTION:
Cartridge memory will be automatically updated by Data Protector from

information on the medium.
MESSAGE:
[90:197] Could not read data (attribute ID=p) from cartridge memory (p).
DESCRIPTION:
Data Protector was trying to read data from medium's cartridge memory and
was not successful.
ACTION:
Check if device is working properly and is able to access medium's

cartridge memory. Check if cartridge memory is accessible at all.
MESSAGE:
[90:198] Could not write data (attribute ID=p) from cartridge memory (p).
DESCRIPTION:
Data Protector was trying to write data to medium's cartridge memory and
was not successful.
ACTION:
Check if device is working properly and is able to access medium's

cartridge memory. Check if cartridge memory is accessible at all.
MESSAGE:
[90:199] Contents of medium's cartridge memory and medium header on

the tape are inconsistent.
DESCRIPTION:
Data Protector read medium header from the tape but the information did
not match the one read from medium's cartridge memory.
ACTION:
Reformat or scratch media with Data Protector. This will either rewrite a new
media header at the beginning of the tape or clear cartridge memory of
Data Protector information.
MESSAGE:
[90:205] Cannot connect to Media Agent (param1) => aborting
DESCRIPTION:
CMA process cannot connect with BMA process.
ACTION:
Check if CMA is connecting to the BMA with a correct port number.
MESSAGE:
[90:206] Cannot handshake with Media Agent (param1) => aborting
DESCRIPTION:
Cannot get important data from BMA like number of buffers, block
size and medium header size.
ACTION:
Restart operation.
MESSAGE:
[90:208] Device formats are not equal => aborting
DESCRIPTION:
You tried to replicate medium BMA and CMA that have not the same
format. They are different in block size or number of blocks or size of
a medium header.
ACTION:
Configure both sides of devices for BMA and CMA that have the same
formats such as a block size or the number of buffers.
MESSAGE:
[90:210] p GRAU DAS error in "p": error code=p
DESCRIPTION:
The API call function_name() failed. Real cause is explained with error
codes:
Explanations of error codes:
1. RPC failure.
2. ACI parameter invalid.
3. Volume not found of this type.
4. Drive not in GRAU ATL.
5. The requested drive is in use.
6. The robot has a physical problem with the volume.
7. An internal error in the AMU.
8. The DAS was unable to communicate with the AMU.
9. The robotic system is not functioning.
10. The AMU was unable to communicate with the robot.
11. The DAS system is not active.
12. The drive did not contain an unloaded volume.
13. Invalid registration.
14. Invalid hostname or IP address.
15. The area name does not exist.
16. The client is not authorized to make this request.
17. The dynamic area became full, insertion stopped.
18. The drive is currently available to another client.
19. The client does not exist.
20. The dynamic area does not exist.
21. No request exists with this number.
22. Retry attempts exceeded.
23. Requested volser is not mounted.
24. Requested volser is in use.
25. No space available to add range.
26. The range or object was not found.
27. The request was canceled by aci_cancel().
ACTION:
According to the error code number check the condition of GRAU library and
restart operation.
MESSAGE:
[90:220] Cannot determine element addresses: (p)
DESCRIPTION:
Unable to get element addresses that are necessary to manipulate

with SCSI-II libraries.
ACTION:
Check the library. If the library still does not respond, try turning it
off and on. If this does not help, reboot the system.
MESSAGE:
[90:221] Cannot p repository element(s): (no mailslot(s) defined)
DESCRIPTION:
SCSI-II library cannot eject the specified medium because library has
no mailslots.
ACTION:
You cannot use the eject operation.
MESSAGE:
[90:222] Cannot EJECT repository element num into mailslot num: (mailslot is full)
DESCRIPTION:
SCSI-II library cannot eject the specified medium into mailslot because
it is full.
ACTION:
Mailslot(s) must be emptied manually.
MESSAGE:
[90:223] Cannot EJECT repository element num into mailslot num: (slot is empty)
DESCRIPTION:
SCSI-II library cannot eject the specified medium into mailslot because
slot is empty.
ACTION:
Enter the medium into slot first. Then you can perform the EJECT
operation.
MESSAGE:
[90:224] Cannot EJECT repository element num into mailslot num: (p)
DESCRIPTION:
For some reason SCSI-II library cannot eject medium.
ACTION:
If some library door is open, close it.

Check the library. If it still does not respond, try turning it off
and on. If this does not help, reboot the system.
MESSAGE:
[90:227] Cannot read mailslot status => aborting
DESCRIPTION:
SCSI-II library does not return any information about the specified mailslot.
ACTION:
Check the library. If the library still does not respond, try turning it off and
on. If this does not help, reboot the system.
MESSAGE:
[90:228] p aborted due to operator inactivity timeout (num secs)
DESCRIPTION:
Operator did not fill the specified mailslot with a medium.
ACTION:
Try the operation again and this time fill the specified mailslot with
a medium.
MESSAGE:
[90:229] Eject operation was not fully completed. Check the mail slot(s) for ejected media.
DESCRIPTION:
Operator did not take media out from the mail slot, so eject operation
could not be completed or eject operation was aborted by the user.
ACTION:
Remove the media from the mail slot(s).
MESSAGE:
[90:230] Cannot ENTER repository element num from mailslot num: (slot is full)
DESCRIPTION:
SCSI-II library cannot enter a specified medium from a mailslot

because all slots are full.
ACTION:
Eject some media from slots first and remove them from the library. Then
try with the ENTER operation again.
MESSAGE:
[90:231] Cannot ENTER repository element num from mailslot num: (mailslot is empty)
DESCRIPTION:
SCSI-II library cannot enter the specified medium from a mailslot because
the mailslot is empty.
ACTION:
Mailslot(s) must be filled manually.
MESSAGE:
[90:233] Eject from slot num into mailslot num was successful with some recovery
action taken by SCSI library.
DESCRIPTION:
SCSI command Move Medium completed successfully with some recovery action
performed by the SCSI library.
ACTION:
Check if the SCSI library is in good condition. This can be sign that
something will fail in the future.
MESSAGE:
[90:234] Enter into slot num from mailslot num was successful with some recovery
action taken by SCSI library.
DESCRIPTION:
SCSI command Move Medium completed successfully with some recovery action
performed by the SCSI library.
ACTION:
Check if the SCSI library is in good condition. This can be sign that
something will fail in the future.
MESSAGE:
[90:239] Eject operation was not fully completed. Check the cap for ejected media.
DESCRIPTION:
Operator did not take media out from the cap, so eject operation
could not be completed or eject operation was aborted by the user.
ACTION:
Remove all the remaining media from the cap and perform inventory.
MESSAGE:
[90:240] "p": ACS reply out of sequence: num (expected num)
DESCRIPTION:
When working with StorageTek library the API function

function_name() did not reply with a correct sequence number. This is a
problem in API protocol.
ACTION:
Check if StorageTek library and the Cell Manager system are configured correctly.
MESSAGE:
[90:249] No library server specified => aborting
DESCRIPTION:
No library server hostname has been specified for

the indicated logical device. A ACS/GRAU library device must have a
defined library server which controls the robotics of the library.
ACTION:
MESSAGE:
[90:250] OB2CLEANME setting is obsolete. You should configure dirty drive detection
in logical device configuration.
DESCRIPTION:
In file .omnirc the OB2CLEANME variable that is obsolete is defined.
ACTION:
For detection of a dirty drive you must configure the dirty drive in the logical
MESSAGE:
[90:251] OB2BARCODE setting is obsolete. You should configure barcode reader support
in library configuration.
DESCRIPTION:
In file .omnirc is defined variable OB2BARCODE that is obsolete.
ACTION:
To scan a library with barcodes you must configure a barcode reader

support in the logical device configuration.
MESSAGE:
[90:252] OB2BLKSIZE setting is obsolete. You should configure block size

in logical device configuration.
DESCRIPTION:
In file .omnirc the OB2BLKSIZE variable that is obsolete is defined.
ACTION:
For defining a block size you must configure the block size in the logical
MESSAGE:
[90:253] Block Size setting of numKB is too big. Maximum allowed block size for
this device type is numKB.
DESCRIPTION:
The block size you set in the device configuration is too big.
ACTION:
Change the device configuration with a smaller block size. A maximum

block size allowed is printed out.
MESSAGE:
[90:254] p Cannot dismount busy drive.
DESCRIPTION:
Data Protector tried to mount a medium into a drive that is already

mounted but Data Protector did not succeed to dismount the busy drive.
ACTION:
You must configure a drive busy handling to eject a medium or eject

medium to a mailslot in the logical device configuration. If that does not
succeed you must dismount a drive manually.
MESSAGE:
[90:255] p Successfully loaded and dismounted busy drive.
DESCRIPTION:
Data Protector mounted a medium into a drive that was already mounted
and successfully dismounted.
ACTION:
MESSAGE:
[90:258] Capacity setting of numMB is too big. Maximum allowed capacity for
regular files is numMB.
DESCRIPTION:
The capacity you set in the device configuration is too big.
ACTION:
Change the device configuration with a smaller capacity. A maximum

capacity allowed is printed out.
MESSAGE:
[90:259] Medium replication failed to write successfully all data after early
warning EOM.
DESCRIPTION:
During copying the medium the copied data exceeded over the virtual
end-of-medium. After verifying the data written after the virtual
end-of-medium error occurred. The copied medium will be scratched.
It is possible that tape driver has problem writing data blocks
after virtual EOM.
ACTION:
=======
Change the copied medium with a medium that has bigger capacity.
Or try to make original backup using the OB2BLKPADDING settings.
Check in documentation about this issue.
MESSAGE:
[90:273] p Slot num does not contain a cleaning tape.
DESCRIPTION:
The slot that is configured as cleaning slot does not contain

a cleaning tape.
ACTION:
Replace tape with a cleaning tape or specify a new cleaning slot.
MESSAGE:
[90:280] DAS client software not found => aborting.
DESCRIPTION:
UMA could not load the shared library needed for interaction with the ADIC/GRAU library.
ACTION:
Install DAS client software. Check if the DAS client software was properly installed.
MESSAGE:
[90:281] ACS client software not found => aborting.
DESCRIPTION:
UMA could not load the shared library needed for interaction with the StorageTek library.
ACTION:
Install ACS client software. Check if the ACS client software was properly installed.
MESSAGE:
[90:300] p Cannot unload drive "p"

p
DESCRIPTION:
ACS/DAS robotics failed to complete the dismount command. The error
message indicates the reason as reported by the OS or ACS/DAS
client software.
ACTION:
Check reported error message and consult the ACS/DAS manual.

MESSAGE:
[90:301] p Cannot load the medium into drive "p"

p
DESCRIPTION:
ACS/DAS robotics failed to complete the mount command. The error message
indicates the reason as reported by the OS or ACS/DAS client software.
ACTION:
Check reported error message and consult the ACS/DAS manual.

MESSAGE:
[90:390] Cannot delete the expired file depot "p"
DESCRIPTION:
The BMA process was not able to delete the expired file depot.
This indicates that the file depot was either not existing or the
BMA did not have sufficient rights to delete the file depot.
ACTION:
Check if the file depot is still existing and which permissions

it has. If the permissions of the file depot are not enough
change it so that the file depot can be deleted by the BMA
process.
MESSAGE:
[90:391] Cannot delete the expired file depot "p"
DESCRIPTION:
The BMA process was not able to delete the expired file depot.
This indicates that the BMA did not have sufficient rights
to delete the file depot.
ACTION:
Check the file permissions of the file depot.

If the permissions of the file depot are not enough
change it so that the file depot can be deleted by the BMA
process.
MESSAGE:
[90:392] param1
Cannot access the directory (param2)
DESCRIPTION:
The BMA has found an error trying to get status information

from the file library directory. The message indicates the
reason reported by the operating system.
The message 'No such file or directory' means the directory does
not exist on the filesystem. An 'Access is denied' message means
the BMA does not have sufficient permissions to access the
directory. This frequently happens when the directory is located
on a network drive.
ACTION:
Check the directory exists in the filesystem and the BMA has
sufficient rights to access it. If the directory is located on
a network drive, check the Data Protector Inet process on the
Media Agent client has sufficient permissions to access the network
drive.
If the network drive is mapped from a Samba server check the user
mapping on the Samba server.
MESSAGE:
[90:500] Could not autodiscover the WWN for tape device "p". Error code num.
DESCRIPTION:
Autodiscover of the World Wide Name was not successful. This could
be due to the device not being accessible or not supporting WWN
autodiscovery.
Error codes:
01. failure
02. openFailedRouter
03. openFailedTape
04. openFailedXP
05. ioctlFailedXP
06. ioctlFailedCap
07. rSenseFailed
08. tsInqFailed
09. inqFailedXP
10. inqFailedCap
11. getLunsFailed
ACTION:
Manually enter the WWN into the backup configuration.
MESSAGE:
[90:501] Could not autodiscover the WWN for disk device "p". Error code num.
DESCRIPTION:
Autodiscover of the World Wide Name was not successful. This could
be due to the device not being accessible or not supporting WWN
autodiscovery.
Error codes:
01. failure
02. openFailedRouter
03. openFailedTape
04. openFailedXP
05. ioctlFailedXP
06. ioctlFailedCap
07. rSenseFailed
08. tsInqFailed
09. inqFailedXP
10. inqFailedCap
11. getLunsFailed
ACTION:
Try to enter the WWN name for the device into the WWN configuration file.
MESSAGE:
[90:502] Could not find WWN for device "p", using default.
DESCRIPTION:
When the World Wide Name for a device cannot be determined, the default
(0x00000000) is used. It might work if the device is connected to
a bridge that is used as a third party data mover.
ACTION:
Manually enter the WWN into a backup specification or into a

WWN configuration file.
MESSAGE:
[90:512] Could not execute XCOPY command (p).
DESCRIPTION:
Executing COPY command has failed given the indicated reason.
ACTION:
Make sure the bridge supports the data movement XCOPY command.
MESSAGE:
[90:513] Could not get the XCOPY status (p).
DESCRIPTION:
Executing RECEIVE_COPY_RESULTS has failed given the indicated reason.
ACTION:
XCOPY Engine may not support asynchronous XCOPY commands.
MESSAGE:
[90:801] Active Removable Storage Manager (RSM) service found on local system.
DESCRIPTION:
An active Removable Storage Manager (RSM) service on MS Windows 2003

(or newer) might cause a significant drop in backup performance in
SAN environment.
ACTION:
It is recommended to stop the RSM service on this system and on all

MS Windows 2003 systems (or newer) attached to the SAN. Refer to the
product documentation in order to stop the RSM service.
This message can be turned off by setting environment variable

OB2RSMWARNINGCHECK=0
MESSAGE:
[90:1004] Device address not found.
DESCRIPTION:
The device address could not be found. Either the device is turned off or it is
disconnected from the host. Another reason for this message can also be the exchange of
an old faulty device with a new one, with a different serial number that is
not searched.
ACTION:
Check if the device is turned on and connected to the host. If the address is
correct and a new device is connected in place of an old one, use the "Reload" serial
number button in the Device Properties "Settings" page. This way a new serial
number will be stored in the database.
MESSAGE:
[90:4005] Cannot set specified block size (num kB).
DESCRIPTION:
Media agent was unable to set NDMP record size. Reason for this might be that NDMP server doesn't
support specified record size.
ACTION:
Please check the release notes in order to determine which record sizes are supported for your
NDMP server.
MESSAGE:
[90:4006] NDMP MA Cannot back up files with a pathname longer than 1024 characters.
DESCRIPTION:
Media agent has encountered a file or directory with a pathname that exceeds
1024 characters. The files will be backed up normally but you will not be
able to select such files for restore individually.
ACTION:
Reorganize your directory structure so that pathnames do not exceed 1024 characters.
MESSAGE:
[90:5100] p
File was not backed up completely in any backup session in the restore chain being consolidated.
The incomplete file was excluded from the consolidated object.
DESCRIPTION:
The file was not backed up completely in any backup session in the restore
chain being consolidated.
The incomplete file was omitted from the consolidated object.
Upon restore, the file will not be restored.
As long as the media of the original session are still protected, the
partial data can be recovered by restoring a particular version of the file.
ACTION:
Analyze the original backup sessions and try to avoid the cause that
prevents the files from being backed up completely.
MESSAGE:
[90:5101] p
An incomplete file version from p was included in the consolidated object as is.
DESCRIPTION:
An incomplete file version was included in the consolidated object as is.
Upon restore, the file will be restored only up to the point to which
it was backed up successfully.
ACTION:
When restoring from such an object, make sure incomplete files do not
overwrite possibly still valid files on the destination filesystem.
MESSAGE:
[90:5102] p
The latest version of the file was not backed up completely.
In the consolidated object, the incomplete version was replaced by
an older complete version from p.
DESCRIPTION:
The file was not backed up completely in the latest backup session of the
restore chain being consolidated.
One of the earlier sessions contains a complete version. The most recent
complete version was used as a replacement in the consolidated object.
Upon restore, such files will not be restored to the most recent state,
but to the best possible complete state.
As long as the media of the original session are still protected, the
partial data can be recovered by restoring a particular version of the file.
ACTION:
MESSAGE:
[90:5103] p
An incomplete file version from p was included in the consolidated object as is.
DESCRIPTION:
An incomplete file version was included in the consolidated object as is.
Upon restore, the file will be restored only up to the point to which
it was backed up successfully.
ACTION:
When restoring from such an object, make sure incomplete files do not
overwrite possibly still valid files on the destination filesystem.
MESSAGE:
[90:5104] p
File was not backed up in any backup session in the restore chain being consolidated.
The file was excluded from the consolidated object.
DESCRIPTION:
The file was not backed up in any backup session in the restore chain being
consolidated.
The file was omitted from the consolidated object. Upon restore,
the file will not be restored.
ACTION:
prevents the files from being backed up.
MESSAGE:
[90:5105] Block sizes of the source and destination devices do not match.
Switching from virtual full to synthetic full backup.
DESCRIPTION:
Although the distributed file medium format is selected in the library and
all devices taking part in the consolidation session reside in the same file
library, the block sizes of the source and destination devices differ.
Thus the consolidation will create a synthetic full backup and not a
virtual full backup.
ACTION:
Make sure that the source and destination devices have the same block
size set.
MESSAGE:
[90:6100] Drive unable to decrypt data: Invalid decryption key retrieved from key management
server.
DESCRIPTION:
Medium contains encrypted data.

Decryption on drive during read failed as a wrong decryption key was retrieved from key management
server.
ACTION:
Please execute omnidbcheck -keystore on the cell manager to check

the sanity of the keystore.
MESSAGE:
[90:6101] Drive unable to decrypt data: Decryption mode for the drive is not enabled.
DESCRIPTION:

Drive is unable to decrypt the data because decryption mode is not enabled.
This may happen if a third party application tries to disable encryption on purpose.
ACTION:
Please verify if a third party application is trying to access the tape drive from the current
media agent host.
MESSAGE:
[90:6102] Drive unable to decrypt data: Data validation failed while reading encrypted data.
DESCRIPTION:

The encrypted backed up data on the medium was tampered,
it is not possible to read this data block.
This is a serious security error, the session will be aborted.
ACTION:
MESSAGE:
[90:6103] Unable to continue operation: Encryption related parameters have been changed by
another host on the SAN, aborting session.
DESCRIPTION:

Drive encryption parameters have been changed by a different host on the SAN.
This is an unexpected event; hence this session will be aborted.
ACTION:
Please investigate/fix if a different host is trying to access this device and retry this
operation or use SCSI RESERVE/RELEASE.
MESSAGE:
[90:6104] Unable to continue operation: Either a medium was unloaded or a medium which does not
support encryption was loaded.
DESCRIPTION:
Either the medium was unloaded or a medium which does not support encryption was loaded.
Please check the medium status and retry the operation.
ACTION:
MESSAGE:
[90:6105] Unable to continue operation: Invalid decryption key used for 10 times.
DESCRIPTION:

Wrong decryption key was used for 10 times to read encrypted data on the medium.
This may be a brute force attack to read encrypted data from the tape medium.
ACTION:
Please investigate/fix if a third party application on the currnent media agent

host is trying to read data from the encrypted medium,
reload the medium and retry the operation.
MESSAGE:
[90:6106] Unexpected encryption related error was encountered.
DESCRIPTION:
An unexpected encryption related error was encountered,

session will be aborted.
ACTION:
MESSAGE:
[90:6107] Unable to continue operation: AES library initialization failed, aborting session!
DESCRIPTION:
Unable to initialize Data Protector encryption.
ACTION:
MESSAGE:
[90:6108] Medium does not support encryption. Unencrypted backup on this medium will continue.
DESCRIPTION:
This medium does not support hardware encryption.

The backup on this medium will not be encrypted.
This behavior can be changed by OB2_ENCRYPT_MEDIUM_STRICT omnirc flag.
ACTION:
MESSAGE:
[90:6109] Medium does not support encryption, please use encryption supported medium.
DESCRIPTION:
This medium does not support hardware encryption; this medium will not be used for backup.
Please insert a new medium which supports drive based encryption.
This behavior can be changed by OB2_ENCRYPT_MEDIUM_STRICT omnirc flag.
ACTION:
MESSAGE:
[90:6111] Error retrieving encryption key.
DESCRIPTION:
The encryption key required could not be retrieved from key management server, aborting session.
ACTION:
MESSAGE:
[90:6112] Encryption could not be enabled on the drive, session will be aborted.
DESCRIPTION:
Encryption could not be enabled on the drive, aborting session.

Possible reasons are
1. No Medium present.
2. Issue with drive connectivity.
ACTION:
MESSAGE:
[90:6113] Error while enabling Encryption on the drive: session will be aborted.
DESCRIPTION:
Medium does not support encryption, aborting session.
ACTION:
MESSAGE:
[90:6114] Device does not support encryption, aborting session.
DESCRIPTION:
The device specification mandates that hardware encryption should be

enabled during current operation; however the device does not support encryption.
Aborting session.
ACTION:
Recheck if the tape device connected supports encryption and retry the operation.
MESSAGE:
[90:6116] Decryption could not be enabled on the drive.
DESCRIPTION:
Encrypted data was found on the drive but decryption could not be
enabled to read the encrypted data.
Possible reasons are
1. No Medium present.
2. Issue with drive connectivity.
ACTION:
MESSAGE:
[90:6119] Encryption on device is being managed by an external encryption controller :

decryption/encryption key is not available.
DESCRIPTION:
This error is due to failure of an operation on an encrypted media in the case

where Data Protector cannot control the encryption configuration on the device.
This could occur due to either the decryption key not being available or
a temporary network failure between the drive and the entity controlling encryption on the drive.
ACTION:
Please check the network connectivity between drive and external encryption controller.
MESSAGE:
[90:7002] Share presentation failed due to Samba issues.
DESCRIPTION:
This error is due to an issue with the Samba service on the target Media Agent
server.
ACTION:
Please check if the Samba service is correctly installed and configured on the
Media Agent server. The service should also be running at the time of the
operation.
MESSAGE:
[110:1] Bad message format while receiving username/password.

Aborting.
DESCRIPTION:
Error occurred while transmitting username/password for client.
ACTION:
Restart the client installation session.
MESSAGE:
[110:3] You cannot uninstall the Cell Manager !

Host skipped.
DESCRIPTION:
Client that you tried to uninstall is the Data Protector Cell Manager.
You cannot uninstall the Cell Manager from its own cell.
ACTION:
Uninstall Data Protector software from the client manually, using swremove
(HP-UX) or pkgrm (Solaris).
MESSAGE:
[110:4] No Cell Manager defined for clients !

Aborting.
DESCRIPTION:
If an installation session is started from the command line, there is no Cell Manager
defined in the installation data file. This could also be an internal error, such as a
communication protocol change.
ACTION:
Check the format of the installation data file if installing from the command line,
or contact your HP Support representative.
MESSAGE:
[110:5] No packets selected for installation.

Aborting.
DESCRIPTION:
If an installation session is started from the command line, there is no Cell Manager
defined in the installation data file. This could also be an internal error, such as a
communication protocol change.
ACTION:
Check the format of the installation data file when installing from the command line,
or contact your HP Support representative.
MESSAGE:
[110:16] Cannot connect to Cell Manager p => aborting.
DESCRIPTION:
Connection to the Cell Manager could not be established.

Possible causes are: client down, network problem, name resolution
problem, Data Protector daemons not running, or an internal error in
the Data Protector Internal Database subsystem.
ACTION:
* Check if the Cell Manager is up

* Check the host name resolution (name service)
* Check if the Cell Manager is accessible through the network
* Check if Data Protector services are accessible on the Cell Manager,
using telnet 5555
* Restart Data Protector daemons
* Contact your HP Support representative
MESSAGE:
[110:20] Protocol/network problem

(p).
DESCRIPTION:
Client could not be contacted because of an unexpected network problem.

The probable cause is a socket creation error.
ACTION:
MESSAGE:
[110:23] param1: Unknown hostname.
DESCRIPTION:
Host name is not recognized as valid - name lookup failed.
ACTION:
Check the host name spelling and name lookup via DNS, NIS or /etc/hosts on the Installation
Server.
MESSAGE:
[110:24] Client param1 : client not responding.
DESCRIPTION:
Installation on the selected client failed because the client was not accessible.
ACTION:
Check if the client you want to install is accessible on the network.
MESSAGE:
[110:100] Client export failed!

param1
DESCRIPTION:
Uninstalled client could not be exported from its cell.

Possible Cell Manager malfunction.
ACTION:
* Check network accessibility of the Cell Manager.

* If necessary, restart Data Protector daemons.
* Export the client directly from the Cell Manager, using the GUI.
MESSAGE:
[110:101] Client import failed!

param1
DESCRIPTION:
The successfully installed client could not be imported to the cell.

Possible causes are: improper installation, network inaccessibility
of the client, or Cell Manager malfunction.
ACTION:
* Check if Data Protector software works locally on installed client.

* Try to contact the Data Protector client using the command, "telnet <client> <Data Protector
port>"
* Check network accessibility of the Cell Manager.
* If necessary, restart Data Protector daemons.
* Try to import the client again, using the GUI.
MESSAGE:
[110:103] Command execution on client failed!

p
DESCRIPTION:
During the installation process, the operation started on the client failed.
Remote output (diagnostics) is printed out.
ACTION:
MESSAGE:
[110:104] Cannot create directory param1

param2.
DESCRIPTION:
Installation process was unable to create a temporary directory on the client

for storing installation utilities and the packet itself.
ACTION:
Check the free space on the client filesystem where the /tmp directory resides.
MESSAGE:
[110:105] Series p: utilities packet missing.
DESCRIPTION:
Installation program cannot find the utility packet on the Installation Server.
ACTION:
* Check if the Installation Server is properly installed.

* Check the /opt/omni/databases/utils directory tree for the utility packets.
MESSAGE:
[110:106] Error copying utility scripts.

p
DESCRIPTION:
Copying of the utility packet on the client failed.
ACTION:
* Check if there is enough space in /tmp directory
MESSAGE:
[110:107] Cannot unpack tar package.

p
DESCRIPTION:
Unpacking utility packet (tar command) on client failed.
ACTION:
MESSAGE:
[110:117] The system param1 is already in another cell: param2.
DESCRIPTION:
The distribution of Data Protector subproducts to this system failed because

it is already part of another cell. A client system can belong to only one cell.
ACTION:
* Export the client system from the current cell.

* Then retry the installation, or import the client.
MESSAGE:
[110:121] Insufficient disk space on filesystem containing path param1

param2 KB required, only param3 KB available.
DESCRIPTION:
There is not enough disk space on volumes with /tmp/omni_tmp

and /opt/omni directories.
ACTION:
*Free up more disk space and restart the installation.
MESSAGE:
[110:134] Cannot uninstall Data Protector

using an Installation Server that is located on the same host!
DESCRIPTION:
Cannot uninstall Data Protector software using an Installation Server

that is located on the same host as the client.
ACTION:
To uninstall Data Protector, either:

* Select another Installation Server or
* Use a native uninstallation tool (swremove, pkgrm, ...) for local uninstallation
MESSAGE:
[110:137] Migration of encryption keys from client p failed.
DESCRIPTION:
Cannot finish automatic migration of encryption keys from this client.
ACTION:
To migrate the encryption keys and enable encryption in all backup specification(s) associated
with this client,
* Run "omnikeymigrate -client <client name>".
MESSAGE:
[110:200] This system already has Data Protector installed.
DESCRIPTION:
The distribution of Data Protector components to this system failed because

it already has Data Protector installed. Installation/upgrade from Data Protector is not
supported.
ACTION:
1. Uninstall Data Protector software from the client system.

2. Retry the installation.
MESSAGE:
[110:1008] Import client failed.
DESCRIPTION:
The client information cannot be added/updated in the Cell Manager configuration file.
ACTION:
* Please check that the Data Protector services on the Cell Manager system are running.
* Also check that the Data Protector Inet service on the remote computer is running
* Make sure that the remote client is not already part of another cell.
* Use the Data Protector GUI to manually import the client to the selected
Cell Manager.
MESSAGE:
[110:1009] Invalid message format received.
DESCRIPTION:
Client sent a message, which is not recognized by the Installation Server process.
ACTION:
This is an internal error. If the problem persists, start the installation

in the debug mode and send the debug files to the Support representative.
MESSAGE:
[110:1015] Data Protector on client responded, but it is not a supported Windows client for remote
installation/unistallation.
DESCRIPTION:
The client you've specified for the installation is not a supported Windows client for remote
installation/unistallation.
To remotely install UNIX clients set up the UNIX Installation Server.
Windows 98/Me and Windows XP Home clients have to be installed/uninstalled locally.
ACTION:
Select only supported Windows clients for remote installation

(Windows 98/Me and Windows XP Home platforms cannot be installed remotely!)
MESSAGE:
[110:1021] Already connected to the client.
DESCRIPTION:
Setup cannot connect to a remote client because there is already another connection
to this remote computer. The permissions of the existing
connection might be insufficient to finish the installation.
Most probably you are browsing the remote clients in Windows Explorer.
ACTION:
Close all the connections to the remote client.
MESSAGE:
[110:1022] Cannot connect to the SCM (Service Control Manager) on client param1:
param2
DESCRIPTION:
Cannot connect to SCM (Service Control Manager)
ACTION:
If you are using Windows Server 2008, try to use the omniinetpasswd command to configure your user
account
so that you can connect to the client. For more information, see the HP Data Protector
Installation Guide.
MESSAGE:
[110:1024] Cannot start the Data Protector bootstrap service on client param1:
param2
DESCRIPTION:
The Data Protector bootstrap service was successfully installed on the remote client
but it could not be started. The Windows NT system error should tell more about
the problem.
Most probable cause for this is that the Installation Server is not available
or that the OmniBack share on the Installation Server is not accessible or it does not exist.
Also make sure that the installservice.exe file exists on that share.
ACTION:
* Make sure that the Installation Server is available and visible on the network.
* If the OmniBack share on the Installation Server does not exist, reinstall the Installation
Server.
* If installservice.exe is not at the proper location on the Installation Server, reinstall the
Installation Server.
To check that the OmniBack share on the Installation Server exists, and that the appropriate
executable
can be accessed, go to the client system you want to install and run:
dir \\<IS_computer>\OmniBack\i386\installservice.exe
from the MS-DOS prompt.
MESSAGE:
[110:1025] Cannot connect the Data Protector bootstrap service on client param1:
param2
DESCRIPTION:
Data Protector bootstrap service has been successfully installed and started,
but it does not respond.
ACTION:
Perform one of the following actions:

* If the client is running behind a firewall, make sure to open an appropriate port.
* If the client is using Microsoft Firewall, you can instruct the Installation
server to ignore the firewall, by setting the OB2FWPASSTHRU omnirc variable.
See the Release Notes for details.
* Restart the installation process on the failed client. If the problem can be
reproduced, start the installation session in the debug mode and call your HP Support
representative.
* Try to install the client locally and import it into the Data Protector cell.
MESSAGE:
[110:1026] Lost connection to client param1:

param2
DESCRIPTION:
The connection to receive progress messages has been broken.

System error indicates the specific problem.
ACTION:
* Make sure that the client just being installed is visible on the network.
* Also make sure that the client is up and running. This condition can also
occur if Data Protector client processes were terminated ungracefully.
* Restart the installation process on the failed client. If the problem can be
reproduced start the installation session in the debug mode and call the HP Support
representative.
MESSAGE:
[110:1027] Error connecting to client:

p
DESCRIPTION:
The connection to the remote computer could not be established.
ACTION:
* Make sure that the client just being installed is visible on the network (ping)
* Make sure that the client you want to install is a supported Windows client
(Windows 98/Me and Windows XP Home clients are not supported for remote installation)
* Also make sure that the volume where Data Protector is about to be installed is available as an
administrative share.
Example:
When installing Data Protector client software on disk D: on a remote computer,
that particular client must have a D$ administrative share.
(Contact your network administrator for details on how to create an Administrative share)
MESSAGE:
[110:1042] Client did not respond to the request; timeout occurred.
DESCRIPTION:
When Data Protector was checking if the installation on the client exists the request was accepted
by Data Protector services on the client but the response was not received.
Most probably the Data Protector Inet service on the client hanged.
ACTION:
* Restart the Data Protector Inet service on the client and start this session.
MESSAGE:
[110:1043] Hostname reported by client (param1) does not

match with its name in the Cell Manager configuration files (param2).
DESCRIPTION:
Installation check was verifying the hostname that was reported by the client against the
information in Cell Manager configuration files. The two hostnames do not match.
ACTION:
* Check the DNS configuration on both, Cell Manager and client systems and make sure the
result from the NSLookup command on the Cell Manager and client systems will match for the
specified
hostname.
MESSAGE:
[112:72] You have no permission to get media management information.
DESCRIPTION:
You tried to view media management information, but you lack the Media
configuration or Reporting and Notifications access rights.
ACTION:
Either add the Media configuration or Reporting and Notifications access

rights to this user group or transfer this user to a user group that has
the Media configuration or Reporting and Notifications access rights.
MESSAGE:
[112:73] You have no permission to get logical device information.
DESCRIPTION:
You tried to view logical device information, but you lack

the Device configuration or Reporting and Notifications access rights.
ACTION:
Either add the Device configuration or Reporting and Notifications access

rights to this user group or transfer this user to a user group that has
the Device configuration or Reporting and Notifications access rights.
MESSAGE:
[119:200] Cannot register host p on IAP server p. The session will be aborted.
DESCRIPTION:
The IAP host and the IAP Deduplication Agent host have to be registered in the IAP to do backup.
The registration of host may fail because no registration rules apply to client, or IAP domain
is invalid or does not exist.
ACTION:
To fix this please go on the PCC machine of the IAP and check registration rules using the
"rimflist regrules" to check for appropriate rules and check IAP domain configuration.
After that use "rimflist hosts" to get a list of available hosts.
MESSAGE:
[119:210] Connection to the IAP (p) could no be established.
DESCRIPTION:
The connection to the IAP failed due to a TCP connection failure.
ACTION:
This indicates that the IP adress and/or port specified for the connection to the IAP is may be
wrong.
Check also the IAP availability and configuration.
MESSAGE:
[121:136] Cannot install trigger in cron

Cannot open crontab for writing.
DESCRIPTION:
You either have not configured the cron or do not have permission to access
the cron file.
ACTION:
Check, and if necessary correct, the cron file configuration and the
permission of its configuration files.
MESSAGE:
[121:137] Cannot execute the omnib command for backup specification 'p'.
DESCRIPTION:
The omnitrig command cannot execute the command omnib.
ACTION:

Check to be sure that the /opt/omni/bin/omnib command exists, and be
sure that the Unix file permissions are correctly set. If the omnib command
exists and the permissions are correct, the file may be corrupt. In this case,
reinstall/update the Cell Manager.

Check to be sure that <Data_Protector_home>\bin\omnib.exe command exists. If the
omnib.exe command exists, the file may be corrupt. In this case,
reinstall/update the Cell Manager.
MESSAGE:
[123:31] Could not fork process p.
DESCRIPTION:
The command you specified could not execute for one of several reasons:
* the command was not able to connect to the selected Cell Manager
* the command is not contained in the /opt/omni/bin directory
* there are too many processes are already running
ACTION:
* Use the omnisv -status command to be sure that the Cell Manager
is running.
* Check the /opt/omni/bin directory to be sure that the command is in
the directory.
* Use the ps -ef command to be sure that the process limit of the system
has not been reached.
MESSAGE:
[123:32] Cannot connect to host p.
DESCRIPTION:
Data Protector could not connect to the specified host.
ACTION:
Use the ping command to check the connection to this host and telnet
<HOSTNAME> 5555.
MESSAGE:
[123:33] Unknown event (p) received.
DESCRIPTION:
This problem is caused by an internal error.
ACTION:
Restart the operation.
MESSAGE:
[123:36] No valid host running a Cell Manager daemon located.
DESCRIPTION:
You selected a host that is not defined as a Cell Manager.
ACTION:
Define a host as a Cell Manager using the procedures described in the HP Data Protector
Administrator's Guide, Integrations with Other Applications.
MESSAGE:
[123:39] Cannot get value of the environment variable DISPLAY.
DESCRIPTION:
You tried to get the status of a specified cell, but Data Protector was unable to
display this information.
ACTION:
* Be sure that the DISPLAY environment variable is set

* Be sure that the ITO/OpC management station allows the Cell Manager host
to display an hpterm (you must allow access to the appropriate client). To
allow access to the client, use the xhost + clientname command.
MESSAGE:
[124:111] Failed to enable encryption for hosts:

p.
DESCRIPTION:
Encrypted control communication is available only on supported platforms

and on systems with Disk Agent version later than Data Protector A.06.20.
ACTION:
Upgrade Data Protector clients.
MESSAGE:
[130:155] Full resync of recovery catalog failed.
DESCRIPTION:
Errors were reported while executing rman resync catalog command.

If you have done some strucutral changes on the database (adding/deleting tablespace/datafile)
and have not performed full resync of recovery catalog, these changes will not be
known to the database replicated to the backup client. Because of this backup could fail or
some datafiles might not get backed up.
ACTION:
If no structural changes were done on the database you can safely ignore this warning.
Please look at additional errors to fix the problem.
MESSAGE:
[130:730] Oracle SID (p) was missing from RMAN format string.
The RMAN script was:
p
DESCRIPTION:
The format string of RMAN script is corrupted.
ACTION:
Open the backup specification in GUI and save it.

Note:
When GUI shows the RMAN script it already displays the proper SID.
Nevertheless you need to edit the script and press the "Apply" button to save it.
MESSAGE:
[131:51] User "p.p@p" is not a valid Data Protector user
DESCRIPTION:
Specified user is not in the Data Protector users list.
ACTION:
* Check if user is on the Data Protector users list. You can check this using Data Protector
(Manager) GUI.
* If this happens during the integrations backup you must enter the user to the Data Protector
admin group.
MESSAGE:
[131:52] User "p.p@p" is not allowed to perform a backup
DESCRIPTION:
The user is not allowed to start a backup. He/She has no permissions
to access data.
ACTION:
Check if this user is in the Data Protector operator class. Also check if this user is in the Data
Protector users list.
MESSAGE:
[131:53] User "p.p@p" is not allowed to perform a restore or to query the Data Protector Internal
Database.
DESCRIPTION:
The user is not allowed to start restore or to query the Data Protector Internal Database.
He/She has no permissions to access data.
ACTION:
Check if the user is in the Data Protector operator class.

Also check if the user is in the Data Protector users list.
MESSAGE:
[131:104] Script returned error. (Return value: num).
DESCRIPTION:
Specified script returned non zero value.
ACTION:
The script should always return zero (0) as the return value if
the script execution succeeds.
If some other value is returned, Data Protector assumes an error and

displays this message. Check if your script returns this value.
Check why the script (or executable) returned an error value.
MESSAGE:
[131:107] Specified script cannot be started. (Return value: num).
DESCRIPTION:
The script that you have specified cannot be started.
ACTION:
* Check if the specified script exists in the

<Data_Protector_home>/bin directory.
* Check for the script file security settings.
MESSAGE:
[131:108] The list of files specified for backup or restore is too long.
DESCRIPTION:
The list of objects you specified to be backed up or restored is too long.
ACTION:
Please do one of the following:

1. Split the list of objects you wanted backed up or restored and repeat the operation.
2. Increase the size of Ipc buffer size using OB2IPCBUFSIZE variable.
MESSAGE:
[131:200] Syntax error in configuration file: Unexpected symbol 'p'.")

p:p Line: num)
DESCRIPTION:
Configurations of the Data Protector integrations are located on the Cell Manager
<Data Protector config>/integ/<integration type>/<application name>.
There is a syntax error in the file. The parser cannot interpret the
information.
ACTION:
* File might be corrupted: Check if the configuration file can be opened by a text editor.
* If the file has been edited manually by an administrator, check the syntax of the file.
* Check the <Data_Protector_home>/log/debug.log file for more information.
MESSAGE:
[131:201] Syntax error in configuration file: expected token type num differs from num for 'p'.
p:p, Line: num
DESCRIPTION:
information.
ACTION:
* File might be corrupted: Check if the configuration file can be opened with a text editor.
MESSAGE:
[131:202] Syntax error in configuration file: expected token p differs from 'p'.
p:p, Line: num
DESCRIPTION:
information.
ACTION:
MESSAGE:
[131:203] Syntax error in configuration file: Unexpected end of file in string.

p:p, Line: num
DESCRIPTION:
information.
ACTION:
MESSAGE:
[131:204] Error reading or writing configuration file. p:p
DESCRIPTION:
Configurations of the Data Protector integrations are located on the Cell Manager.
An error has occurred while reading or writing the file over the network.
ACTION:
* Check if the file exists.

* Check for any network problems that might cause the read error.
MESSAGE:
[131:205] Error parsing configuration file. p:p
DESCRIPTION:
The parser cannot interpret the information in the configuration file.
ACTION:
MESSAGE:
[134:651] ob2sybase: Backup specification concurrency number is missing!
DESCRIPTION:
Invalid arguments passed to ob2sybase. Backup specification concurrency number is

missing.
Possible causes:
* Backup specification is in the wrong format.
ACTION:
Create another backup specification using the Data Protector GUI.
MESSAGE:
[134:652] ob2sybase: Backup specification concurrency is out of a valid range (from 1 to 75)!
DESCRIPTION:
Invalid arguments passed to ob2sybase. Backup specification concurrency number is

out of a valid range!
Possible causes:
* Backup specification is in the wrong format.
ACTION:
Create another backup specification using the Data Protector GUI.
MESSAGE:
[134:653] ob2sybase: util_sybase.exe failed.
DESCRIPTION:
Call to util_sybase.exe failed.

Possible causes:
* the system-imposed limit on the total number of processes under execution
would be exceeded
by a single user would be exceeded
* there is insufficient swap space and/or physical memory available in which
to create the new process.
ACTION:
If it couldn't start the process because of insufficient swap space and/or

physical memory, then add another swap file.
MESSAGE:
[134:654] ob2sybase: Sybase concurrency (num) is bigger than backup specification concurrency
(num) !
DESCRIPTION:
Sybase concurrency is bigger than backup specification concurrency!

Cause:
* Number of backup streams for sybase database(s) is greater than sum
of device concurrencies of devices on which backup is to be performed.
ACTION:
Lower number of streams so it is less or equal to backup specification concurrency.
MESSAGE:
[134:655] ob2sybase: Could not start another process.
DESCRIPTION:
ob2sybase couldn't start another process.

Possible causes:
would be exceeded
by a single user would be exceeded
* there is insufficient swap space and/or physical memory available in which
to create the new process.
ACTION:
If it couldn't start the process because of insufficient swap space and/or

physical memory, then add another swap file.
MESSAGE:
[134:657] ob2sybase: Not enough memory.
DESCRIPTION:
System doesn't have enough free memory.
ACTION:
Quit unnecessary programs to free some memory.
MESSAGE:
[134:658] ob2sybase: util_sybase.exe was unsuccessful (no database list returned)
DESCRIPTION:
Call to util_sybase.exe didn't retrieve a list of databases.

Possible cause:
* Sybase SQL Server is not properly installed/configured.
ACTION:
Connect to SQL Server as a system administrator using ISQL utility and

execute the following commands:
select name from sysdatabases
go
You should get a list of all databases on this Sybase Database Server, otherwise
it is not installed/configured properly.
MESSAGE:
[134:660] ob2sybase: Call to open was unsuccessful.
DESCRIPTION:
Call to script util_sybase.exe failed.

The session will not be started.
Possible causes:
* util_sybase.exe doesn't exist in /opt/omni/lbin
* util_sybase.exe doesn't have permissions to execute
* directory /tmp is full.
ACTION:
If util_sybase.exe doesn't exist, then push Sybase module on the client.

If util_sybase.exe doesn't have execute permissions, run the following command as root:
on HP-UX and Solaris: chmod 755 /opt/omni/lbin/util_sybase.exe
If the filesystem, on which resides a directory /tmp, is full, then delete unnecessary
files.
MESSAGE:
[134:661] ob2sybase: Couldn't empty sybase.current.log
DESCRIPTION:
File sybase.current.log in directory /var/opt/omni/log

couldn't be emptied.
Possible causes:
* Directory has no write permissions.
* File has no write permissions.
ACTION:
If directory has no write permissions, run the following command as root:

on HP-UX and Solaris: chmod 777 /var/opt/omni/log
If file has no write permissions, run the following command as root:
on HP-UX and Solaris: chmod 666 /var/opt/omni/log/sybase.current.log
MESSAGE:
[134:662] Backup session \'p\' used num concurrent stream(s) (dump stripes).
This is different than current num load stripe(s).
DESCRIPTION:
The dump of version specified was created with different number of stripes than
specified in current load command.
The load command must have same number of stripes as dump.
ACTION:
Change the number of the stripes for restore to match the number of stripes
used in backup.
MESSAGE:
[136:31] Internal Database corrupted!
DESCRIPTION:
Data Protector Internal Database is corrupted. See debug.log for details.
ACTION:
MESSAGE:
[136:32] Bad import file format in file "param1", line#: param2, field#: param3!
DESCRIPTION:
Import file is corrupted.
ACTION:
Check file specified at location specified.
MESSAGE:
[136:150] This Cell Manager uses remote MMDB (p) - nothing to do!
DESCRIPTION:
Free pool deallocation was started on Cell Manager that uses central MMDB on remote server.
ACTION:
Free pool deallocation process should be started on central MMDB server.
MESSAGE:
[138:700] Error on device "p" occurred.
DESCRIPTION:
Data Protector has detected a device error.
ACTION:
* Check the device status according to the reported error message.

* Check also debug.log file on the system where the Media Agent was running.
* Verify the availability of the device with some test/blank media and with some
simple command (such as tar).
* Refer to Appendix B of the HP Data Protector Installation and Licensing Guide for additional
information on
connecting devices.
MESSAGE:
[138:702] Mount request on device "p".
DESCRIPTION:
All media available on the device are used up for writing (backup) or reading (restore).
ACTION:
To confirm a mount request:
1. Insert a medium (put the device online if necessary):

2. Use the Data Protector GUI or the omnimnt command to confirm the mount.
MESSAGE:
[138:704] The Data Protector Internal Database is running out of disk space, p.
DESCRIPTION:
One or more parts of the Internal Database are running out of disk
space according to the thresholds for this notification.
ACTION:
Check the status of the Internal Database using the:

* Data Protector GUI (Internal Database context)
* Database Size Report
* omnidbutil -info command
MESSAGE:
[138:705] Media pool "p" contains only p free media.
DESCRIPTION:
Pool has reached the threshold number of free media.
ACTION:
Add more free media to the specified pool.

Check details with:
* Data Protector GUI (Devices & Media context)
* omnimm -show_pools -detail
MESSAGE:
[138:706] Corruption in the "p" part of the Data Protector Internal Database has been detected
("p").
DESCRIPTION:
One of the modules detected possible corruption of the IDB (Data Protector Internal Database).
Note that the IDB consists of multiple parts and possible actions depend on which
part is corrupt.
ACTION:
Procedure to recover the IDB to a consistent state is as follow:

* Check for potential problems with the environment (a filesystem with an IDB part
is not mounted, ...).
* Use the omnidbcheck command to determine which part of the IDB is corrupt.
* Use the omnidbcheck command to check the corrupted part using the -detail option.
* Follow the available recovery steps.
* In the event that the above steps do not produce desired results, contact the HP Customer
Support Service.
See the Help topic "Recovering the Data Protector Internal Database".
MESSAGE:
[138:707] p session "p" of session specification "p" has errors: p.
DESCRIPTION:
Errors have been detected during the backup, copy, or consolidation session.
ACTION:
Check error messages of the session by using:

* Session Errors report
* omnidb -session <sessionID> -report
MESSAGE:
[138:708] Data Protector Event Log increased for p unexpected events in the last day.
DESCRIPTION:
The number of messages in the Data Protector Event Log has increased and reached threshold limit.
ACTION:
View and delete Data Protector Event Log messages.
MESSAGE:
[138:709] Health check message: "p" failed.
DESCRIPTION:
ACTION:
Check the following log file for more details:

* /var/opt/omni/log/HealthCheck.log (UNIX)
* <Data_Protector_home>\log\HealthCheck.log (Windows)
MESSAGE:
[138:710] User check failed with exit code p: "p".
DESCRIPTION:
User check command/script finished with non zero exit code.
ACTION:
Check if the command/script was executed at all (check for correct pathname)
and if it was proceed with the actions to remove the cause of failure.
MESSAGE:
[138:711] All mailslots of library "p" are full.
DESCRIPTION:
Library mailslots are full.
ACTION:
Media should be removed from mailslots before other media can be ejected from the library.
MESSAGE:
[138:712] Archived logs purge should be run for the Data Protector Internal Database.
DESCRIPTION:
According to the notification parameter (threshold), archived logs purge should be run.
ACTION:
Run the archived logs purge using the Data Protector command:
omnidbutil -purge_archive_logs.
MESSAGE:
[138:713] The first license will expire in p days.
DESCRIPTION:
One of the license passwords will soon expire and as a consequence some or all
Data Protector functionality will not be accessible.
ACTION:
Typically, this notification indicates expiration of the evaluation license and in this case the
permanent license should be installed.
MESSAGE:
[138:720] Scheduler logs purge should be run on the Data Protector Internal Database.
DESCRIPTION:
According to the notification parameter (threshold), scheduler logs purge should be run.
ACTION:
Run the scheduler logs purge using the Data Protector command:
omnidbutil -purge_scheduler_logs.
MESSAGE:
[138:721] Deallocation of unused space should be run on the Data Protector Internal Database.
DESCRIPTION:
According to the notification parameter (threshold), deallocation of unused space should be

performed.
ACTION:
Run the deallocation of unused space using the Data Protector command:
omnidbutil -deallocate_unused_space.
MESSAGE:
[138:722] The "p" part of the Data Protector Internal Database has reached its limit.
DESCRIPTION:
One or more parts of the Internal Database have reached their limits
according to the thresholds for this notification.
ACTION:
Check the Internal Database status using the:

* Database Size report
* omnidbutil -info command
* Data Protector GUI (the Internal Database context)
MESSAGE:
[138:723] The last backup of the Data Protector Internal Database was run on p.
DESCRIPTION:
According to the threshold, hp recommends to run a full or incremental backup of the Internal
Database.
ACTION:
Run a full or incremental IDB backup using the Data Protector GUI or CLI:
* omnib -idb_list <ListName> [-barmode IDBMode]
IDBBackupMode = { full | incr }
MESSAGE:
[138:724] Bloat of the table p detected.
DESCRIPTION:
Data Protector Internal Database tables should never grow ("bloat") due to unreclaimed dead rows.
According to bloat threshold, hp recommends to reorganize the table.
ACTION:
To reorganize a table, use the pg_reorg tool.
MESSAGE:
[138:725] Session cannot start because the maximum number of concurrently running sessions has
been reached.
DESCRIPTION:
The maximum number of concurrently running sessions is 1000.
ACTION:
Wait until some sessions complete and start the session again.
MESSAGE:
[138:726] CsaStartSession failed for datalist "p"
DESCRIPTION:
Backup could not be started because CsaStartSession function failed.
ACTION:
* Restart the backup.

* Try running datalist with omnib -session <datalist_name>
MESSAGE:
[138:742] p session "p" of the backup specification "p",backup group "p" has errors: p.
DESCRIPTION:
Errors have been detected during backup.
ACTION:
Check error messages of the session by using:

* Backup Errors report
* omnidb -session <sessionID> -report
MESSAGE:
[138:760] p successive incremental IDB backup images exist.
DESCRIPTION:
According to the threshold, hp recommends to run full backup of the Internal Database.
ACTION:
Run a full IDB backup using the Data Protector GUI or CLI:
* omnib -idb_list <ListName> -barmode full
MESSAGE:
[138:761] Backup of the Data Protector Internal Database has not been run yet.
DESCRIPTION:
hp recommends to run a full backup of the Internal Database.
ACTION:
Run a full IDB backup using the Data Protector GUI or CLI:
* omnib -idb_list <ListName> -barmode full
MESSAGE:
[138:762] Fragmentation of the table p in the column p detected.
DESCRIPTION:
According to table fragmentation threshold, hp recommends to reorganize the table on the stated
column.
ACTION:
Use the pg_reorg tool to reorganize the stated table.
MESSAGE:
[138:763] Fragmentation of the index p detected.
DESCRIPTION:
According to index fragmentation threshold, hp recommends to reorganize the index.
ACTION:
Run the following Data Protector command to reorganize an index:

* omnidbutil -reindex -index <IndexName>
MESSAGE:
[139:10] Input file doesn't exist or it was not specified by user.
DESCRIPTION:
The backint should be started with the -i <input_file> option. In the input file, the files and
directories for backup/restore/inquiry are defined. If these options are not set, data is read
from the standard input.
ACTION:
Check the following:

If the backint was started with the -i <input_file> option,
If <input_file> exists,
If the backint has got the data on the standard input.
MESSAGE:
[139:12] The backint was not started with the '-t' option or an invalid type is specified.
DESCRIPTION:
The backint must be started with the -t <type> option, where the type must be 'file'
or 'file_online'.
ACTION:
MESSAGE:
[139:13] The backint was not started with the '-f' option or an invalid type is specified.
DESCRIPTION:
The backint must be started with the -f <function> option, where the function must be
'backup' or 'restore' or 'inquiry'.
ACTION:
MESSAGE:
[139:14] The environment variable ORACLE_HOME was not set.
DESCRIPTION:
The variable ORACLE_HOME is set by the Backup Command Script, if the backup is started from Data
Protector. Otherwise the variable must be set by user. In that case the backup is started by SAP
Backup Tools.
ACTION:
Set in the environment the variable

ORACLE_HOME=<ORACLE_HOME>.
MESSAGE:
[139:17] Function ftok returns an error. Interprocess communication identifier is not created.
DESCRIPTION:
ftok() returns an error if path name does not exist or if it is not accessible to the process.
ACTION:
Check for the path name OMNITMP/sem.
MESSAGE:
[139:19] No valid setVersions found for specified <userID>.
DESCRIPTION:
The query checks in the Data Protector Internal Database, if there is any valid backup for
specified <userID>.
ACTION:
Try to start the following Data Protector commands:

OMNIBIN/omnidb -sap
OMNIBIN/omnidb -sap <Host:Set>
If there is no objects for <userID>, the backup was not done.
Otherwise report this error to your HP Support Representative.
MESSAGE:
[139:21] Brbackup doesn't respond.
DESCRIPTION:
Backint program communicates for each file with brbackup to switch tablespaces into the begin/end
backup mode. Brbackup determines whether the files are backed up. If the files are to be backed
up, brbackup switches the tablespace into begin backup mode. If the switching of tablespace lasts
more than an hour, an error is reported.
ACTION:
Try to switch the tablespace into backup mode manually. If the switching is not lasted so long,
report this error to your HP/SAP Support Representative.
MESSAGE:
[139:23] No files to be backed up specified.
DESCRIPTION:
The <input_file> file with specified objects for backup is empty or the files/directories don't
exist on the system.
ACTION:
Check for <input_file> or standard input.
MESSAGE:
[139:24] Cannot init Data Protector Cell Manager.
DESCRIPTION:
When the sapback/saprest is started, the init part to the Data Protector Cell Manager is started.
That means that the BSM/RSM is started. If the BSM/RSM is already starting, then the
sapback/saprest is connecting to the BSM/RSM.
ACTION:
MESSAGE:
[139:114] Signal SIGABRT (6) received from BRtools
DESCRIPTION:
BAR agent received a signal SIGABRT.
ACTION:
Ensure that parameter primary_db in SAP initalization file init<SID>.sap

on application system is set to LOCAL.
MESSAGE:
[139:239] Backint file in SAP R/3 executable path is not correct. Backup or restore might fail
DESCRIPTION:
For the backup to work properly backint has to be a symbolic link to

/opt/omni/lbin/backint (HP-UX and Solaris systems) or /usr/omni/bin/backint (other Unix systems).
ACTION:
Ensure that backint is a link to the correct binary. Reconfigure the instance if needed.
MESSAGE:
[139:240] The list of files manually assigned to the device #num is too long.
DESCRIPTION:
You have configured the backup specification to use manual balancing, and assigned
too many files to one of the devices.
ACTION:
Assign some of the files to a different device.
MESSAGE:
[140:100] Requested encryption key can not be found in the specified keyfile.
DESCRIPTION:
During encrypted backup of IDB encryption key was exported to the file.
That file has to be used to perform successful IDB restore.
ACTION:
Make sure that file you typed is on the file system and is one which was created during IDB
backup.
MESSAGE:
[141:15] No backup specification specified.
DESCRIPTION:
A backup specification is an important part of a backup because it contains data about the devices
to perform the backup to and other information.
ACTION:
If you have started the agent manually from the command line, you have to specify
the backup specification name as a command line option (-bar:<barname>) or through setting the
environment variable OB2BARLIST. If you have started backup using Manager, then a
serious error has occurred. Contact HP Support Representative.
MESSAGE:
[141:19] LOTUS, NOTES_DATA_DIR and Notes_ExecDirectory were not exported into environment.
DESCRIPTION:
LOTUS, NOTES_DATA_DIR and Notes_ExecDirectory environment variables must be set before

initializing the Lotus C API.
ACTION:
Please reconfigure the Lotus integration or try to export the environment variables through the "
<Data_Protector_home>\.omnirc" file.
MESSAGE:
[144:10] Input file doesn't exist or it was not specified by user.
DESCRIPTION:
The backint should be started with the -i <input_file> option. The files and directories for
backup/restore/inquiry are defined in the input file. If this option is not set, data is read from
the standard input.
ACTION:
Check the following:

If the backint was started with option -i <input_file>,
If the <input_file> exists,
If the backint has got the data on the standard input.
MESSAGE:
[144:12] The backint was not started with option '-t' or an invalid type is specified.
DESCRIPTION:
The backint must be started with the option -t <type>, where the type must be 'file'
or 'file_online'.
ACTION:
MESSAGE:
[144:13] The backint was not started with option '-f' or an invalid type is specified.
DESCRIPTION:
The backint must be started with the option -f <function>, where the function must be
'backup' or 'restore' or 'inquiry'.
ACTION:
MESSAGE:
[144:14] The environment variable ORACLE_HOME was not set.
DESCRIPTION:
The variable ORACLE_HOME is set by the Backup Command Script, if the backup is started from Data
Protector. Otherwise, set the variable yourself. In that case, the backup is started by SAP Backup
Tools.
ACTION:
Set in the environment the variable

ORACLE_HOME=<ORACLE_HOME>.
MESSAGE:
[144:17] Function ftok returns error. Interprocess communication identifier is not created.
DESCRIPTION:
ftok() returns error if path name does not exist or if it is not accessible to the process.
ACTION:
Check for the path name OMNITMP/sem.
MESSAGE:
[144:19] No valid setVersions found for specified <userID>.
DESCRIPTION:
The query checks in the Data Protector IDB, if there is any valid backup for specified <userID>.
ACTION:
Start the following Data Protector commands:

OMNIBIN/omnidb -sap
OMNIBIN/omnidb -sap <Host:Set>
If there are no objects for <userID>, the backup was not done.
Otherwise, report this error to your HP Support Representative.
MESSAGE:
[144:21] Brbackup doesn't respond.
DESCRIPTION:
Backint program communicates for each file with brbackup to switch tablespaces into the begin/end
backup mode. Brbackup determines whether the files are backed up. If the files are to be backed
up, brbackup switches the tablespace into begin backup mode. If the switching of tablespace lasts
more than an hour, an error is reported.
ACTION:
Try to switch the tablespace into backup mode manually. If the switching lasts up to a few
minutes, then report this error to your HP Support Representative, else report it to your SAP
Support Representative.
MESSAGE:
[144:23] No files to be backed up specified.
DESCRIPTION:
The <input_file> with specified objects for backup is empty or the files/directories don't exist
on the system.
ACTION:
Check for <input_file> or standard input.
MESSAGE:
[144:24] Cannot initialize the Data Protector Cell Manager.
DESCRIPTION:
When the sapback/saprest is started, the initialization part of the Data Protector Cell Manager is
started. The BSM/RSM is started, after which the sapback/saprest is connected to the BSM/RSM.
ACTION:
MESSAGE:
DESCRIPTION:
ACTION:
MESSAGE:
[144:1001] Unrecognized combination of option[s]!
DESCRIPTION:
ACTION:
MESSAGE:
[145:005] No data selected.
DESCRIPTION:
No components could be selected, because they can not be located on the system:
1) the writers, which have been selected, are not running.
2) the writers, which have been selected, do not manage selected components.
3) the filesystems, which have been selected, do not exist anymore.
ACTION:
Run 'vssadmin list writers' and make sure that selected writer is running and its state is stable.
Refer to writer's documentation for more specific details.
Example:
1) In case you are running Microsoft Exchange Writer backup, make sure that Microsoft Information
Store
service is running and that the selected storage groups are mounted.
MESSAGE:
[145:110] Timeout occurred, aborting.
DESCRIPTION:
The operation either hangs or takes more time than the timeout value.
ACTION:
1) Increase OB2VSS_TIMEOUT and OB2VSS_WAIT_TIMEOUT if more time is needed to complete the

operation.
MESSAGE:
[145:114] Tape Backup of 'p' failed.
DESCRIPTION:
The specified component could not be backed up because:

1) one of the files is missing or could not be backed up.
2) backup was aborted
ACTION:
Run 'vssadmin list writers' and make sure that writer's state is stable.
MESSAGE:
[145:116] Writer 'p' failed to prepare files for backup.
DESCRIPTION:
Writer is not in stable state, therefore VSSBAR can not backup its files.
ACTION:
Make sure writer is stable before backup is started. Run 'vssadmin list writers' to identify the
current status.
If writer is not stable check application event logs for any writer specific errors. In most cases
it helps if the writer's service/application is restarted.
Also make sure that there are no backups running of the same writer.
MESSAGE:
[145:133] There is no hardware provider,

that can create a Shadow Copy of 'p' for Transportable Backup.
DESCRIPTION:
There are no VSS Hardware Providers available for creating the Shadow Copy of the specified
volume.
Transportable Backup cannot proceed.
ACTION:
VSS Transportable Backup requires that shadow copies are created by a VSS Hardware Provider.
Check the provider's configuration and make sure that all writer's data is stored on volumes
provided by a VSS Hardware Provider.
If the data is already located on appropriate volumes, try to restart a backup session.
If the session is still failing with the same error, try to restart the VSS Hardware Provider.
Refer to provider's documentation for more specific details.
MESSAGE:
[145:220] Writer 'p' failed to prepare files for restore.
DESCRIPTION:
Writer is not in stable state, therefore VSSBAR can not restore its files.
ACTION:
Make sure writer is stable before restore is started. Run 'vssadmin list writers' to identify the
current status.
If writer is not stable check application event logs for any writer specific errors. In most cases
it helps if the
writer's service/application is restarted.
Also make sure that there are no backups running of the same writer.
MESSAGE:
[145:221] Restore of component 'p' failed.
DESCRIPTION:
The specified component could not be restored because:

1) one of the files could not be restored.
2) restore was aborted.
ACTION:
Run 'vssadmin list writers' and make sure that writer's state is stable.
MESSAGE:
[145:298] Writer 'p' failed to prepare files for restore:

Reported state: p
Expected state: p
Failure code: p
DESCRIPTION:
Writer is in unexpected state, therefore it is not possible to restore its files.
ACTION:
Make sure writer is in stable state before restore is started. Run 'vssadmin list writers'
to identify the current state. Check application event logs for any writer specific errors.
Make sure that there are no backups running of the same writer.
In some cases it helps if the writer service/application is restarted.
MESSAGE:
[145:312] Mountpoint directory 'p' already exists.
DESCRIPTION:
Specified mountpoint directory is already in use.

Mountpoint directory is combination of 'mount path' specified and 'source mountpoint' (<mount
path>\<source mountpoint>).
ACTION:
Change 'mount path' or remove existing directory.
MESSAGE:
[145:339] Volume Shadow Copy Service failed to create Shadow Copy Set.
DESCRIPTION:
Volume Shadow Copy Service reported error during creation of Shadow Copy Set.
ACTION:
Check the Windows event log for VSS service and VSS hardware provider errors to find the root
cause of the failure.
Troubleshoot the issue and retry the backup again.
This can also be a transient problem. It is recommended to wait ten minutes and try again, up to
three times.
This error can also occur on HP P6000 EVA Family if more than 3 volumes are selected for backup.
MESSAGE:
[145:346] Could not find VSS Hardware Provider for volume 'p'.
DESCRIPTION:
There is no VSS Hardware Provider, which is able to create a Shadow Copy of the volume.
ACTION:
Move the application data to a volume, that can be managed by an appropriate VSS Hardware
Provider.
MESSAGE:
[145:355] Failed to prepare files required for Exchange consistency check.
DESCRIPTION:
Files required for Exchange consistency could not be copied to temporary location.
ACTION:
Check that files, required for Exchange consistency check

(http://support.microsoft.com/default.aspx?scid=kb;en-us;244525) are available.
Check that there is enough free disk space to copy these files to <Data_Protector_home>\ mp
directory.
MESSAGE:
[145:358] Volume 'p',

which is part of backup 'p', was not removed.
DESCRIPTION:
VDS provider failed to find or remove the following volume.
ACTION:
Please check if the following disk was manually removed from the array.
If it was already manually removed, run the following command:
omnidbvss -remove session <session_id> -reference
MESSAGE:
[145:359] Cannot roll-forward selected Exchange session 'p', because it is not the latest full
session.
Logs were removed after full backup in session p.
DESCRIPTION:
Only store(s) were selected for restore. The logs are required to
perform roll-forward recovery of selected store(s).
Data Protector has detected that there was full backup performed
after the session selected for restore.
Logs are removed when full backup is done.
ACTION:
When logs are not available only point in time restore of whole
storage group, including logs, is possible.
To perform restore of currently selected session, select whole storage
group and run restore again.
MESSAGE:
[145:376] Due to local rotation setting num for volume 'p',

num of the following sessions need to be removed:
DESCRIPTION:
StorageWorks disk array XP hardware provider is in resync mode and the maximum S-VOL limit for the
specified P-VOL has been reached.
ACTION:
1)Remove appropriate sessions with the following command:

omnidbvss -remove session <sessionId>
2)Change the MU range in StorageWorks disk array XP provider configuration
3)Change the backup specification rotation setting
MESSAGE:
[145:377] Cannot perform swap restore on backup performed with

StorageWorks disk array XP VSS Hardware Provider in Resync Mode.
DESCRIPTION:
Backup was made with StorageWorks disk array XP VSS Hardware Provider in resync mode,
therefore only copyback restore is possible.
ACTION:
Perform copyback restore instead of swap restore
MESSAGE:
[145:378] Cannot perform copyback restore on backup performed with

StorageWorks disk array XP VSS Hardware Provider in VSS Compliant Mode.
DESCRIPTION:
Backup was made with StorageWorks disk array XP VSS Hardware Provider in VSS Compliant Mode,
therefore only swap restore is possible.
ACTION:
Perform swap restore instead of copyback restore
MESSAGE:
[145:379] The option 'Wait for the replica to complete' is only valid
for storage managed by P6000 EVA VSS Hardware Provider.
DESCRIPTION:
1)There are no storages in the backup session that are managed by
P6000 EVA VSS hardware provider
2)Option 'Wait for the replica to complete' is only applicable for
storages that are managed by P6000 EVA VSS Hardware Provider.
ACTION:
Disable the 'wait for replica to complete' option.
MESSAGE:
[145:380] StorageWorks disk array XP VSS Hardware Provider is in VSS Compliant Mode.
DESCRIPTION:
In VSS Compliant Mode, the replica's lifecycle is independent from the source storage
lifecycle. The replica is not in any pair relationship, therefore the number of replicas is
limited only by the number of disks. When it comes to Instant Recovery, only VDS swap of the
LUNs is possible, where StorageWorks disk array XP VDS Hardware Provider is required.
ACTION:
none
MESSAGE:
[145:381] StorageWorks disk array XP VSS Hardware Provider is in Resync Mode.
DESCRIPTION:
In StorageWorks disk array XP Resync Mode, the replica's lifecycle is tied to the source storage
lifecycle.
The replica is in suspended pair relationship with the source storage, therefore the number
of replicas is limited with number of possible pairs. When it comes to Instant Recovery, only
StorageWorks disk array XP delta resync is possible.
ACTION:
none
MESSAGE:
[145:384] Mismatch in 'p' configuration

between application host and backup host for the selected replica type.
DESCRIPTION:
There is a configuration mismatch in VSS Hardware provider

between application host and backup host.
ACTION:
Open the VSS hardware provider configuration panel and make sure that
application host and backup host are configured with the same settings.
MESSAGE:
[145:385] The StorageWorks disk array XP Hardware Provider mode has changed,
and the following backups done in previous mode exist:
DESCRIPTION:
StorageWorks disk array XP Hardware Provider mode has changed and the environment will contain
backups done in VSS Compliant Mode and backups done in Resync Mode.
Restore(Swap) of backup done in VSS Compliant Mode will only be possible
with OB2VSS_FORCE_INSTANT_RECOVERY omnirc variable. The same will apply
for restore(Copyback) of backup done in Resync mode after forced Swap restore.
ACTION:
It is recommended to recycle all backups done in previous StorageWorks disk array XP hardware
provider mode, to avoid problems with mixing Swap and Copyback restores
on the same storage.
To recycle the backup, run this command:
MESSAGE:
[145:386] The following backups need to be recycled prior to restore:
DESCRIPTION:
StorageWorks disk array XP Hardware Provider mode has changed during backups and the environment
contains backups done in VSS Compliant Mode and backups done in Resync Mode.
Restore(Swap) of backup done in VSS Compliant Mode is not allowed on storages,
which still contain backups done in Resync Mode. The same applies for restore
(Copyback) of backup done in Resync Mode after forced Swap restore.
ACTION:
1) Recycle the backups, using this command:

or
2) Set OB2VSS_FORCE_INSTANT_RECOVERY and perform restore with 'retain source'
MESSAGE:
[145:387] The following backups need to be recycled after restore:
DESCRIPTION:
StorageWorks disk array XP Hardware Provider mode has changed during backups and the environment
contains backups done in VSS Compliant Mode and backups done in Resync Mode.
Restore of the following sessions will only be allowed if
OB2VSS_FORCE_INSTANT_RECOVERY variable is set to 1.
ACTION:
1) Recycle the backups, using this command:

or
2) Keep OB2VSS_FORCE_INSTANT_RECOVERY being set
MESSAGE:
[145:388] The following pairs, which are not under Data Protector control,
need to be removed prior to restore:
DESCRIPTION:
The source mirror disks(PVOL), which are to be swapped, are in pair relationship
with other disks(SVOL), that are not under Data Protector control.
It is required to remove those pair relationships prior to restore.
ACTION:
1) Manually remove the pair relationships

2) Set OB2VSS_FORCE_INSTANT_RECOVERY and perform restore with 'retain source'
MESSAGE:
need to be removed after restore:
DESCRIPTION:
The source mirror disks(PVOL), which are to be swapped, are in pair relationship
with other disks(SVOL), that are not under Data Protector control.
It is recommended to remove those pair relationships after restore.
ACTION:
1) Manually remove the pair relationships
MESSAGE:
[145:392] VDS service needs to be stopped before Instant Recovery is started.
DESCRIPTION:
Due to problems with combination of cluster extended maintenance mode and VDS service,
the VDS service must be stopped before Instant Recovery.
ACTION:
1) Make sure there are no other backup or restore operations in progress.

2) Stop all applications that use VDS service
or
3) Stop the VDS service manually
MESSAGE:
[145:393] VDS service did not stop after the cluster resources came from cluster extended
maintenance mode.
DESCRIPTION:
Due to problems with combination of cluster extended maintenance mode and VDS service,
the VDS service must be stopped after the cluster resources get from extended maintenance mode.
Some other application, which uses VDS service, seems to be running.
ACTION:
1) Stop all applications that use VDS service
MESSAGE:
[145:396] Copyback restore requires swap of the source disks.
DESCRIPTION:
Due to swap of the source disks, it is required to swap them back in order to perform copyback
restore.
ACTION:
1)Set OB2VSS_FORCE_INSTANT_RECOVERY to 1.
MESSAGE:
[145:398] Instant recovery will not be possible,

because StorageWorks disk array XP VSS Hardware Provider is not properly configured.
DESCRIPTION:
StorageWorks disk array XP VSS Hardware Provider is in Resync Mode with recycle option turned off.
Resync restore is not possible
when source P-VOL is in PAIR relationship with other backup S-VOLs.
ACTION:
1) Turn on the recycle option

or
2) Set MU# range, so that the provider manages only one MU
MESSAGE:
[145:403] Failed to start backup on application replica.
DESCRIPTION:
Replica's host is unavailable or application replica is failed.
ACTION:
Please check if host is available and replica is healthy.

For Exchange 2007 CCR execute Power Shell command:
Get-StorageGroupCopyStatus -Server <server name>
MESSAGE:
[145:409] Waiting until the component 'p' is released.
DESCRIPTION:
The specified component is locked by other session.
ACTION:
Wait for the other session to finish.

If there is no such session and if the previous one was disrupted by force (killed processes, host
shutdown) run command :
omnidbutil.exe -free_cell_resources
on Cell Manager to free the locked resources.
This command will also free all other resource that are locked in this cell, use it with caution.
The alternative is to abort the session and rerun it.
MESSAGE:
[145:417] The Exchange database could not be dismounted.
DESCRIPTION:
The dismount of Exchange database failed. Powershell command 'Dismount-Database' returned error.
ACTION:
Check event log for possible messages and troubleshooting steps from Exchange.
If the error is a transient one, the omnirc variables OB2VSS_EXCHDB_DISMOUNT_RETRIES and
OB2VSS_EXCHDB_DISMOUNT_RETRY_DELAY
can be set to increase the number of retries and change duration between retries.
MESSAGE:
[145:428] Failed to complete mount operation.
DESCRIPTION:
Failed to mount volumes.
ACTION:
1) mount the volumes manually

or
2) stop Volume Shadow Copy service
3) stop Virtual Disk service
4) stop hp XP VSS Hardware Provider service
5) stop hpEVA VSS Hardware Provider service
6) stop Microsoft Software Shadow Copy Provider service
7) retry the session again
MESSAGE:
[145:429] Failed to complete unmount operation.
DESCRIPTION:
Failed to unmount volumes.
ACTION:

MESSAGE:
[145:430] Failed to complete present operation.
DESCRIPTION:
Failed to present luns.
ACTION:

MESSAGE:
[145:431] Failed to complete unpresent operation.
DESCRIPTION:
Failed to unpresent luns.
ACTION:

MESSAGE:
[145:432] Instant recovery failed. Troubleshoot the problem and restart the session.
DESCRIPTION:
Instant recovery failed.
ACTION:
1) Check if the selected Instant Recovery Options are supported:

- If options are unsupported, then use a supported configuration.
- Else perform the following steps:

MESSAGE:
[145:434] Required ZDB integration agent p is not found on p.
DESCRIPTION:
The binary is not present on the client.
ACTION:
Install required ZDB integration on specified client.
MESSAGE:
[145:443] Failed to complete remove operation.
DESCRIPTION:
Failed to remove luns.
ACTION:

MESSAGE:
[145:451] VSSBAR version mismatch:

p -> p
p -> p
DESCRIPTION:
There is a version mismatch between Application Host and Backup Host.
ACTION:
1) Make sure that Application Host and Backup Host have the same version.
MESSAGE:
[145:452] Snapshots from session 'p' cannot be deleted.
DESCRIPTION:
The Data Protector database indicates that the session cannot be deleted.
This can happen if the break operation failed on snapshot during backup.
Please note that in rotation newer session has to be deleted instead of indicated one.
ACTION:
Try to break or delete the snapshot manually. After the snapshot is broken or deleted,
the session can be marked for removal and purged with omnidbvss.
MESSAGE:
[145:453] Replica rotation cannot be performed.

The number of sessions that cannot be deleted has reached rotation count.
DESCRIPTION:
The number of sessions that cannot be rotated has reached maximum number of replicas that
are to be kept on disk array.
ACTION:
Increase the number of replicas if disk array supports more copies.

If this is not possible try to break or delete the snapshot manually. After the snapshot is
broken or deleted, the session can be marked for removal and purged with omnidbvss.
MESSAGE:
need to be split prior to restore:
DESCRIPTION:
The following pairs are in PAIR state, which makes resync restore impossible. To perform resync
restore, all the pairs
need to be split.
ACTION:
1) Manually split the pairs

or
2) Set OB2VSS_FORCE_INSTANT_RECOVERY to 1 to automatically split the pairs before restore
and resync them back after restore.
MESSAGE:
will be split prior to restore and resynced after restore:
DESCRIPTION:
The following pairs are in PAIR state, which makes resync restore impossible. To perform resync
restore, all the pairs
need to be split.
ACTION:
None
MESSAGE:
[145:463] Exchange 2007 Restore-As functionality will be disabled,

because the StorageWorks disk array XP VSS Hardware Provider is in Resync Mode.
DESCRIPTION:
Because the backup disks are in suspended pair relationship with the source disks,
it is impossible to perform restore to another target.
ACTION:
1) Put the StorageWorks disk array XP VSS Hardware Provider in VSS compliant mode if you want to
use Restore-As functionality.
MESSAGE:
[145:464] Restore of Exchange 2007 backup from Replication will break the Replication
Environment,
because the StorageWorks disk array XP VSS Hardware Provider is in Resync Mode.
DESCRIPTION:
Because the backup disks are in suspended pair relationship with the source disks, which are in
this case the disks in Replication Environment,
they will need to be swapped with the source disks in Production Environment. The consequence of
such restore is that the disks from
Replication Environment are presented to the Production Environment, which means that the
Replication Environment needs to be manually
reconfigured. OB2VSS_FORCE_INSTANT_RECOVERY must be set to allow such restore.
ACTION:
1) Put the StorageWorks disk array XP VSS Hardware Provider in VSS compliant mode to avoid this
situation
MESSAGE:
[145:465] The current source volume 'p'

is a valid backup volume, created in session 'p'.
DESCRIPTION:
Data Protector database contains record of this backup volume.

The volume was created in backup session and it is still recorded as a valid backup volume for
Instant Recovery.
As this volume is currently used as source volume, the backup is not possible.
ACTION:
Revert the situation, so that this backup volume will not be used as a source volume.
MESSAGE:
[145:466] The current backup volume 'p'

is a valid source volume.
DESCRIPTION:
Data Protector database contains record of this source volume.

The volume was created in current backup session and has the same storage identifier as
the recorded source volume in the database. The occurance for this situation is very low
which is why the next backup should succeed.
ACTION:
None
MESSAGE:
[145:467] The current backup volume 'p'

is a valid backup volume, created in session 'p'.
DESCRIPTION:
Data Protector database contains record of this backup volume.

The volume was created in current backup session and has the same storage identifier as
the recorded backup volume in the database. The occurance for this situation is very low
which is why the next backup should succeed.
ACTION:
Retry backup session.
MESSAGE:
[145:479] \System version mismatch:

p -> p
p -> p
DESCRIPTION:
There is an operating system version mismatch between Application Host and Backup Host.
ACTION:
1) Make sure that Application Host and Backup Host run the same operating system version.
MESSAGE:
[145:481] The Exchange database could not be mounted.
DESCRIPTION:
The mount of Exchange database failed. Powershell command 'Mount-Database' returned error.
ACTION:
Check event log for possible messages and troubleshooting steps from Exchange.
If the error is a transient one, the omnirc variables OB2VSS_EXCHDB_MOUNT_RETRIES and
OB2VSS_EXCHDB_MOUNT_RETRY_DELAY
MESSAGE:
[145:484] Online backup of Microsoft Virtual Server with hardware provider is not supported.
DESCRIPTION:
Microsoft Virtual Server Machine is in online backup mode. Online Backup with hardware provider is
not supported.
ACTION:
1) Perform Online backup with software provider

or
2) Put the Virtual Server Machine in offline mode. Add a DWORD key named after the Virtual Machine
Name in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual Server\1.0\Backup\BackupType
and set the value to 1 (offline backup).
MESSAGE:
[145:494] Eseutil can not be copied from application to backup host.
DESCRIPTION:
Eseutil, required for Exchange consistency check, can not be copied from application
to backup host.
ACTION:
During transportable backup Eseutil is copied from the application client to the backup host,
where it is used for consistency check.
If copying can not be performed automatically, the Eseutil should be made available on backup
host.
Set OB2VSS_EXCHANGE_ESEUTIL_PATH omnirc variable to the path where Eseutil can be found.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;244525 for list of binaries required.
MESSAGE:
[145:495] \System version mismatch:

p -> p
p -> p
DESCRIPTION:
There is an operating system version mismatch between the host on which the backup was performed
and the host
on which restore is being performed.
ACTION:
1) Make sure that Backup and Restore Host run the same operating system version.
MESSAGE:
[145:496] Backup session 'p' on system 'p' cannot be disabled.
DESCRIPTION:
For some reason, the backup session cannot be disabled from the backup system. It
is required to disable the backup session for Instant Recovery to continue.
ACTION:
1) Make sure that backup system is up and running

2) Make sure that OmniInet service is started on the backup system
or
3) Run omnidbvss -disable session <sessionId> -force -backhost <alternateBackupSystem>
MESSAGE:
[145:497] Backup session 'p' on system 'p' was not disabled.
DESCRIPTION:
For some reason, the backup session could not be disabled from the backup system.
Because the instant recovery was forced, the orphan backup mount points might
still reside on the backup system after instant recovery.
ACTION:
1) After Instant recovery, remove orphan backup mount points manually.
MESSAGE:
[145:498] Backup session 'p' on system 'p' was not removed.
DESCRIPTION:
For some reason, the backup session could not be removed from the backup system.
ACTION:

MESSAGE:
[145:499] Backup session 'p' on system 'p' cannot be resolved.
DESCRIPTION:
For some reason, the backup session cannot be resolved on the backup system.
ACTION:

or
3) use omnidbvss -resolve session <sessionId> -backhost <newBackupSystem>
MESSAGE:
[145:513] Backup session 'p' on system 'p' cannot be removed.
DESCRIPTION:
For some reason, the backup session cannot be removed. It is required to remove
the backup session for Instant Recovery to continue.
ACTION:

or
3) Run omnidbvss -remove session <sessionId> -force
MESSAGE:
[145:550] Manual change detected for volume 'p':

DESCRIPTION:
Nontracked manual change in environment occurred. Look below for a hint on what kind of change
occurred.
ACTION:
1) Put the environment back to a state in which Data Protector expects it to be.
or
2) Make sure that the disks are not in use for other purposes and
set OB2VSS_IGNORE_SOURCE_DISK_CHANGES and/or OB2VSS_IGNORE_BACKUP_DISK_CHANGES omnirc variable.
MESSAGE:
[145:551] Nested Volume 'p'

will be mounted on 'p'.
DESCRIPTION:
Nested Volumes cannot be mounted on read-only volumes due to Mount Point Manager limitation.
ACTION:
1) Change backup specification to mount the volumes in read/write mode.
MESSAGE:
[145:556] Failed to load source volume information of 'p'

on system 'p'.
DESCRIPTION:
Information about the source volume cannot be acquired from VSSDB, meaning that
the volume hasn't been resolved yet.
ACTION:
1) Run omnidbvss -resolve -apphost <System>.

or
2) Clear OB2VSS_DISABLE_AUTO_RESOLVE omnirc variable
or
3) Set OB2VSS_ALWAYS_RESOLVE_SOURCES omnirc variable.
MESSAGE:
[145:575] Writer 'p' failed to prepare files for backup:

Reported state: p
Expected state: p
Failure code: p
DESCRIPTION:
Writer is in unexpected state, therefore it is not possible to backup its files.
ACTION:
Make sure writer is in stable state before backup is started. Run 'vssadmin list writers' to
identify the current state.
Check application event logs for any writer specific errors.
Make sure that there are no backups running of the same writer.
In some cases it helps if the writer service/application is restarted.
MESSAGE:
[145:576] Configuration for writer 'p'

on system 'p' has changed.
DESCRIPTION:
The writer configuration has changed. Configuration update is required.
ACTION:
1) Run omnidbvss -resolve -apphost <System>
MESSAGE:
[145:578] Backup 'p' was not removed.
DESCRIPTION:
Data Protector failed to remove the specified backup session.
ACTION:
Please check if the session's disks were manually removed from the array.
If they were manually removed, run the following command:
omnidbvss -remove session <sessionId> -reference
MESSAGE:
[145:656] Failed to complete online operation.
DESCRIPTION:
Failed to put the disks online.
ACTION:
1) Stop Virtual Disk service.

2) Retry the session again.
MESSAGE:
[145:657] Failed to complete offline operation.
DESCRIPTION:
Failed to put the disks offline.
ACTION:

MESSAGE:
[145:658] Failed to complete read/write operation.
DESCRIPTION:
Failed to put the disks/volumes into read/write mode.
ACTION:

MESSAGE:
[145:659] Failed to complete read-only operation.
DESCRIPTION:
Failed to put the disks/volumes into read-only mode.
ACTION:

MESSAGE:
[145:660] Failed to complete hide operation.
DESCRIPTION:
Failed to hide volumes.
ACTION:

MESSAGE:
[145:661] Failed to lock volumes.
DESCRIPTION:
Failed to lock volumes.
ACTION:
1) Stop processes which are locking the volume.

MESSAGE:
[145:708] Disk array wait cannot be minimized, because backup LUNs have not been resolved.
DESCRIPTION:
To minimize normalization wait, the backup LUNS need to be resolved.
ACTION:
1) Make sure that VDS hardware provider installed

2) Set OB2VSS_RESOLVE_BACKUP_LUNS omnirc variable to 1
MESSAGE:
[145:709] Performing Auto-Resolve of the Application System.
DESCRIPTION:
Application System needs to be resolved due to changes in

the environment. Resolving can also be started manually via
omnidbvss -resolve -apphost <ApplicationSystem>
ACTION:
1) To disable Auto-Resolve, set OB2VSS_DISABLE_AUTO_RESOLVE to 1
MESSAGE:
[145:714] Rescanning system due to Break Shadow Copy Set failure.
DESCRIPTION:
The hardware provider does not support Break Shadow Copy Set with MASK_LUNS functionality. Because
VSS Service
uninstalled the backup disks, while the hardware provider failed to unpresent the backup luns, the
system needs to
be rescanned.
ACTION:
None
MESSAGE:
[145:730] Instant Recovery of Cluster Shared Volumes is not supported.
DESCRIPTION:
To perform Instant Recovery of Cluster Shared Volumes, the disk resources need
to be put in Available Storage.
ACTION:
1) Remove the volumes from Cluster Shared Storage group.

2) Perform Instant Recovery.
3) Put the volumes back into Cluster Shared Storage group.
MESSAGE:
[145:731] VDS Swap Instant Recovery is not possible without VDS Hardware Providers.
DESCRIPTION:
To perform VDS Swap Instant Recovery, the source and target LUNS need
to be resolved with VDS Hardware Providers.
ACTION:
1) Install VDS Hardware providers on application and backup system.

2) Resolve the application system with omnidbvss -resolve -apphost <appSystem>.
3) Resolve the backup with omnidbvss -resolve session <session_id>.
4) Restart the session.
MESSAGE:
[145:732] Backup session p was not resolved with StorageWorks disk array XP VDS Hardware
Provider.
DESCRIPTION:
The StorageWorks disk array XP Hardware provider mode has switched from Resync Mode to VSS
Compliant Mode or
vice versa. Because the specified backup was not resolved with StorageWorks disk array XP VDS
Hardware provider,
it cannot be mixed with other type of backup.
ACTION:
1) Remove the specified backup with omnidbvss -remove session <session_id>.

2) Restart the session.
or
3) Switch the provider mode back.
MESSAGE:
[145:733] VDS Swap Instant Recovery will not be possible without VDS Hardware Providers.
DESCRIPTION:
At the time of VDS Swap Instant Recovery, the source and target LUNS will need to be
resolved with VDS Hardware Providers, even though the VDS Hardware Providers are
not required during the backup.
ACTION:

4) Run Instant Recovery.
MESSAGE:
[145:734] Not breaking Shadow Copy Set.
DESCRIPTION:
Since the hardware subsystem was not resolved with VDS hardware provider, the Shadow Copy Set
cannot be broken. The backup is exposed to other VSS tools, which can perform Shadow Copy Set
management. It is also important to protect VSS hardware provider database, which is located
on the backup system in:
C:\System Volume Information\<hw_provider_guid>.{7cc467ef-6865-4831-853f-2a4817fd1bca}DB
ACTION:
1) Install VDS Hardware provider if available.

2) Run omnidbvss -resolve -apphost <apphost>.
3) Restart the backup.
MESSAGE:
[145:735] The backup LUNs cannot be unpresented since the Shadow Copy Set was left imported.
DESCRIPTION:
Since the Shadow Copy Set was left imported, the VSS service is responsible for Shadow Copy
Set management. The LUNs should not be unpresented from the system out of VSS awareness.
ACTION:
1) Install VDS Hardware provider if available.

2) Run omnidbvss -resolve -apphost <apphost>.
3) Restart the backup.
or
4) Enable "Mount the replica on backup system" option
MESSAGE:
[145:737] P6000 EVA Native Instant Recovery will not be possible without VDS Hardware Providers.
DESCRIPTION:
To perform any type of P6000 EVA Native Instant Recovery on Windows 2003, the source and target
LUNS need
ACTION:

4) Run Instant Recovery.
MESSAGE:
[145:738] VDS Swap Instant Recovery will not be possible without VDS Hardware Providers.
DESCRIPTION:
VDS Swap Instant Recovery is not possible without VDS Hardware providers. Disk backup
will be aborted.
ACTION:

3) Restart the backup session.
or
4) Set OB2VSS_ALWAYS_ALLOW_DISK_BACKUP_WITHOUT_VDS omnirc variable.
MESSAGE:
[145:739] P6000 EVA Native Instant Recovery will not be possible without VDS Hardware Providers.
DESCRIPTION:
To perform any type of P6000 EVA Native Instant Recovery on Windows 2003, the source and target
LUNS need
ACTION:

3) Restart the backup session.
or
4) Set OB2VSS_ALWAYS_ALLOW_DISK_BACKUP_WITHOUT_VDS omnirc variable.
MESSAGE:
[145:749] Disk backup of 'p' is not possible.

There is no supported Instant Recovery method for this replica type available.
DESCRIPTION:
The selected replica type is currently not supported.
ACTION:
1) Ensure that you have the latest VSS configuration update.

or
2) Try to change the replica type in the backup specification to a supported one.
MESSAGE:
[145:758] Due to local rotation setting num for volume 'p',

num of the following sessions need to be removed:
DESCRIPTION:
StorageWorks disk array XP hardware provider is in resync mode and the maximum S-VOL limit for the
specified P-VOL has been reached.
ACTION:
1) Remove appropriate sessions with the following command:

or
2) Change the MU range in StorageWorks disk array XP provider configuration
or
3) Change the backup specification rotation setting
or
4) Use the system provider, if performing incremental or differential backup
MESSAGE:
[145:759] The StorageWorks disk array XP Hardware Provider mode has changed,
and the following backups done in previous mode exist:
DESCRIPTION:
StorageWorks disk array XP Hardware Provider mode has changed and the environment will contain
backups done in VSS Compliant Mode and backups done in Resync Mode.
Restore(Swap) of backup done in VSS Compliant Mode will only be possible
with OB2VSS_FORCE_INSTANT_RECOVERY omnirc variable. The same will apply
for restore(Copyback) of backup done in Resync mode after forced Swap restore.
ACTION:
It is recommended to recycle all backups done in previous StorageWorks disk array XP hardware
provider mode, to avoid problems with mixing Swap and Copyback restores
on the same storage.
To recycle the backup, run this command:
MESSAGE:
[145:765] Manual change detected for volume 'p':
DESCRIPTION:
Nontracked manual change in environment occurred. Look below for a hint on what kind of change
occurred.
ACTION:
1) Put the environment back to a state in which Data Protector expects it to be.
or
2) Run omnidbvss -resolve -apphost <hostName>/omnidbvss -resolve session <sessionKey> if
the changes in the environment are valid.
or
3) Set OB2VSS_IGNORE_SOURCE_DISK_CHANGES and/or OB2VSS_IGNORE_BACKUP_DISK_CHANGES omnirc variable.
MESSAGE:
[145:780] Source volume 'p' has a Redirect-On-Write Snapshot,

which is not tracked by Data Protector.
Name: p
IQN: p
Rollback will not be performed.
DESCRIPTION:
While performing IR from Redirect-On-Write Snapshot, all newer snapshots are implicitly removed.
Because
the specified snapshot is not tracked by Data Protector, it needs to be removed manually.
ACTION:
1) Manually remove the specified Redirect-On-Write Snapshot.

2) Retry the Instant Recovery.
MESSAGE:
[145:781] Source volume p has a Smart-Clone of Redirect-On-Write Snapshot,

Name: p
IQN: p
Rollback will not be performed.
DESCRIPTION:
Because
the newer snapshot cannot be removed in case that Smart-Clone is attached, the Smart-Clone needs
to be removed manually.
ACTION:
1) Manually remove the specified Smart-Clone.

MESSAGE:
[145:782] Failed to resolve Redirect-On-Write Snapshot.
DESCRIPTION:
Because of this
all newer snapshots need to be resolved. Resolving of one or more of these snapshots have failed.
ACTION:
Check if the specified snapshot still exists.

1) If the snapshot no longer exists then use the following command to remove the entry from the
database:
omnidbvss -remove session <session_id> -reference
else
3) Check other error messages and fix the root cause of the resolving error.
MESSAGE:
[145:795] The following backup sessions will get removed after Instant Recovery:
DESCRIPTION:
Because of that, the session's references will also get removed.
ACTION:
1) Abort Instant Recovery if backup sessions are to be retained.
MESSAGE:
[145:796] Source and Backup volumes were not both resolved with VDS Hardware Provider.
DESCRIPTION:
It seems that Source Volumes were resolved with VDS Hardware providers while the Backup volumes
were not.
ACTION:
1) run omnidbvss -resolve session SessionKey to resolve the Backup Volumes
MESSAGE:
[145:797] Source and Backup volumes were not both resolved with VDS Hardware Provider.
DESCRIPTION:
It seems that Backup Volumes were resolved with VDS Hardware providers while the Source Volumes
were not.
ACTION:
1) run omnidbvss -resolve -apphost AppHostName to resolve the Source Volumes
MESSAGE:
[145:798] All Source Volumes were not resolved.
DESCRIPTION:
It seems that not all Source Volumes were resolved with VDS Hardware providers.
ACTION:
1) run omnidbvss -resolve -apphost AppHostName to resolve the Source Volumes
MESSAGE:
[145:799] All Backup Volumes were not resolved.
DESCRIPTION:
It seems that not all Backup Volumes were resolved with VDS Hardware providers.
ACTION:
1) run omnidbvss -resolve session SessionKey to resolve the Backup Volumes
MESSAGE:
[145:814] Unsupported VSS Hardware Provider used for backup of 'p':

Provider name: p
Provider version: p
DESCRIPTION:
A VSS Hardware Provider which is not supported is used for this backup. Backup, restore and
instant recovery is performed at your own risk!
ACTION:
Check the latest support matrix if this VSS hardware provider can be supported
MESSAGE:
[145:815] Unsupported VSS Hardware Provider used for instant recovery of 'p'
DESCRIPTION:
A VSS Hardware Provider which is not supported was used for the backup. The instant recovery is
performed at your own risk!
ACTION:
Check the latest support matrix if this VSS hardware provider can be supported
MESSAGE:
[145:818] Failed to update disk information. Retrying operation for the num. time.
DESCRIPTION:
Failed to find the newly presented disks on the host after rescanning the system. The oepration
will be retried.
ACTION:
If the error is a transient one, the omnirc variables OB2VSS_RESCAN_RETRY_NUM and

OB2VSS_RESCAN_RETRY_INTERVAL
MESSAGE:
[145:819] Cannot remove retained source disk from the disk array
DESCRIPTION:
On a swap IR the retained source disk can only be removed by using a VDS hardware provider.
On the system there is no VDS hardware provider installed therefore the source disks are left on
the array.
ACTION:
Locate the retained source disk on the disk array and remove it manually.
MESSAGE:
[145:840] System 'p' is not allowed to connect to INET on system 'p'.
DESCRIPTION:
A policy, which prevents a connection from the specific system, is set.
ACTION:
1) Check the client security settings.
MESSAGE:
[145:841] VSS Hardware Provider with ID p

could not be found on the system.
DESCRIPTION:
A VSS hardware provider required for this backup could not be found on the system.
ACTION:
1) Check whether the hardware provider is installed correctly by executing 'vssadmin list
providers'.
If the provider with the corresponding ID is not installed on the system:

2) Install the provider according to the documentation
3) Retry the backup
else:
7) stop and restart all other VSS Hardware Provider services
8) Retry the backup
MESSAGE:
[145:843] Source volume 'p' is presented using HostSet VLUNs.

Source Volume Name: p
DESCRIPTION:
Volumes that are presented using HostSet VLUNs cannot be handled using the SMI-S provider.
Instead of HostSet VLUNs, only Host-Sees VLUNs should be used.
ACTION:
1) Export the volume to all hosts contained in the HostSet using Host-Sees VLUNs.
2) Remove the HostSet VLUNs from the volume.
3) Restart the session
MESSAGE:
[145:844] Source volume 'p' has a presented snapshot attached,

DESCRIPTION:
HP Data Protector can only handle presentations for source volumes and the read-write snapshots
created by the HP P10000 3Par VSS Hardware Provider
ACTION:
1) Manually remove the presentations from the snapshot.

MESSAGE:
[145:846] Source volume 'p' is presented using PortPresent VLUNs.

DESCRIPTION:
Volumes that are presented using PortPresent VLUNs cannot be handled.

Instead of PortPresent VLUNs, only Host-Sees VLUNs should be used.
ACTION:
1) Export the volume to all hosts using Host-Sees VLUNs instead of PortPresent.
2) Remove the PortPresent VLUNs from the volume.
MESSAGE:
[145:847] Failed to connect to agent on system 'p'.
DESCRIPTION:
Data Protector could not connect to another agent required for a VSS transportable backup
ACTION:
1) Check that the VSS integration is installed on the system

2) Check that the Firewall has exceptions specified for all Data Protector agents on all profiles
MESSAGE:
[145:850] Could not find supported VSS System / Software Provider for volume 'p'.
DESCRIPTION:
There is no supported VSS System / Software Provider, which is able to create a Shadow Copy of the
volume.
ACTION:
Move the application data to a volume, that can be managed by an appropriate VSS System / Software
Provider.
MESSAGE:
[145:852] Could not delete all shadow copies in the shadow copy set.
DESCRIPTION:
The VSS Hardware Provider was not able to delete all shadow copies.
Remaining shadow copies cannot be managed by Data Protector anymore and need to be manually
removed.
ACTION:
1) Check the storage sub system for orphan replicas / shadow copies
2) Manually remove these remaining replicas from the storage sub system
MESSAGE:
[145:855] Writer 'p' failed to prepare the files for some components in the backup.
DESCRIPTION:
The VSS writer could not prepare all selected components for the backup.
Components that are not properly prepared, are inconsistent and are therefore excluded from the
backup.
ACTION:
1) Check the Windows Event Logs of all involved systems (including VM guest OS) for errors
reported by the VSS Writer.
2) Resolve the root cause of the problem
MESSAGE:
[145:856] Failed to get domain account name of the local server.
DESCRIPTION:
The Domain account name of the local server (DOMAIN\SERVER$) could not be retrieved.
ACTION:
1) Ensure that the Data Protector agent is started under a domain account with proper privileges
2) If required manually specify the domain and server using omnirc variables
'OB2VSS_VSS_FILE_SHARE_RESTORE_HOST' and 'OB2VSS_VSS_FILE_SHARE_RESTORE_DOMAIN'
MESSAGE:
[145:857] Failed to get domain account SID for account 'p'.
DESCRIPTION:
The Domain account security identifier (SID) of the given domain account could not be retrieved.
ACTION:
2) If required manually specify the domain and server using omnirc variables
'OB2VSS_VSS_FILE_SHARE_RESTORE_HOST' and 'OB2VSS_VSS_FILE_SHARE_RESTORE_DOMAIN'
MESSAGE:
[145:858] Failed to add privileges for SID 'p' on file 'p'.
DESCRIPTION:
The Data Protector agent could not add privileges on the file required for a proper restore.
ACTION:
MESSAGE:
[145:859] Failed to open Local Security Authority.
DESCRIPTION:
The Data Protector agent could not open Local Security Authority.
ACTION:
MESSAGE:
[145:860] The restore path is too long. The application may not be able to access the files.
Path: p
DESCRIPTION:
The restore path is too long. The application may not be able to access data on long paths.
To manually access the restored files use the 'subst' command to shorten the path and access the
data using
the substituted path.
ACTION:
1) Select a shorter target storage path

MESSAGE:
[145:861] In the Internal Database (IDB), there is no reference to a related full backup image of
the object
param1: param2 .
DESCRIPTION:
A full backup image must exist in order to be able to start an incremental backup session for the
same object.
ACTION:
Most probably, a full backup session for this object has not been performed yet. You should start
one before starting the incremental backup session
MESSAGE:
[147:10] MaxDB did not create transfer pipes.
DESCRIPTION:
The MaxDB database did not create named pipes for data transfer.
ACTION:
Increase the value of environment variable TimeoutWaitFiles (in seconds).
MESSAGE:
[148:26] A system error occurred when starting OBIStream module on client p.

Error message: p
DESCRIPTION:
OBIStream module did not start because of a system error.
ACTION:
Check the reported system error message.
* Verify that the SharePoint Portal integration is properly configured.

* Verify that the specified agent is installed on the client.
MESSAGE:
[148:28] Selected client p is not front end web server.
DESCRIPTION:
Integration can be configured only on front end web server.
ACTION:
Select client which is configured as front end web server in the server farm.
MESSAGE:
[148:29] Unsupported topology.
DESCRIPTION:
Backup or restore can not run on unsupported sharepoint topology configuration.
ACTION:
Configure sharepoint to a supported topology.
MESSAGE:
[148:30] Unknown internal error.
DESCRIPTION:
ACTION:
Contact your administrator.
MESSAGE:
[148:31] Pre-session preparation failed. Error: p
DESCRIPTION:
Pre-session preparation consist of reading configuration file from Cell Manager and impersonating
configured user.
ACTION:
* Check the reported system error message.

* Verify that the SharePoint Portal integration is properly configured.
* Check Data Protector debug.log for details.
MESSAGE:
[148:32] Can not get lock on SharePoint Portal farm. Error or locked by: p
DESCRIPTION:
Without lock on SharePoint Portal farm backup/restore can not continue.
ACTION:
* Check any reported application error message.

* Check information on some previous lock which can not be released.
MESSAGE:

Error message: p
DESCRIPTION:
ACTION:
* Check the reported system error message.

* Report this error to your post-sales Data Protector Support Representative.
MESSAGE:
[151:211] The catalog data protection might have expired.
DESCRIPTION:
Informations needed for restore can not be read from the catalog. The catalog data protection
might have expired.
ACTION:
Please check whether the catalog data has expired or not by executing the command
"omnidb -session sessionID -detail" from the CLI.
If the catalog protection is shown as expired, please re-import the catalog data.
MESSAGE:
[151:213] Registry key 'Recovery SG Override' is set.
DESCRIPTION:
Mailbox database(s) will be restored to original location even if Recovery Storage Group exists on
the Exchange server.
ACTION:
MESSAGE:
[151:214] Recovery SG 'p' is configured on the Microsoft Exchange Server.
DESCRIPTION:
Restore to Recovery Storage Group is not possible using Data Protector MS Exchange integration.
ACTION:
By setting the Exchange registry key 'Recovery SG Override' you can restore mailbox stores
to their original locations, even though the Recovery Storage Group exists.
To set the Recovery Storage Group Override registry key
- Start Registry editor (regedit)
- In Registry Editor, navigate to the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
- Create a new DWORD value Recovery SG Override = 1
Or remove the Recovery Storage Group from the server using MS Exchange management console or
powershell.
MESSAGE:
[151:270] Cannot back up incrementally, switching to full backup.
DESCRIPTION:
The Microsoft Exchange Server cannot be backed up incrementally because a full backup doesn't
exist in the Data Protector Internal Database. Data Protector will perform a full backup instead.
ACTION:
* Perform a full database backup of the Microsoft Exchange Server.
MESSAGE:
[152:40] Cannot backup incrementally, switching to full (master database) or differential backup.
DESCRIPTION:
The object cannot be backed up incrementally. The agent will perform a full (differential) backup
instead.
ACTION:
Some databases/tables cannot be backed up incrementally.

Read MS SQL Server documentation for additional information.
This is due to one of the following reasons:
(1) (SQL Server 6.x) The database does not have transaction logs specified.
If a database does not have transaction logs, then MS SQL Server does not
keep track of changes, but it applies changes as soon as possible.
Because of that, incremental backups are not possible.
To check whether the database has separate transaction logs, open the
SQL Enterprise Manager and click on the database properties. If the
"Log Size" does not display the log size number but displays something
like "Shared with data", the database does not have a transaction log associated.
(2) (SQL Server 6.x) The "Truncate log on checkpoint" option is checked
If the database administrator checked the "Truncate log on checkpoint" option

then transaction logs are overwritten each time MS SQL Server executes the
checkpoint process. Because of that, incremental backups are not possible.
(3) The "simple" recovery model is selected.
If the database administrator selected the "simple" recovery model then

transaction logs are overwritten each time MS SQL Server executes the checkpoint process.
Microsoft SharePoint Portal Server creates some databases with "simple" recovery model by
default.
Because of that, incremental backups are not possible.
(4) Only full backups of the master database are possible.
In all cases contact your MS SQL Server Administrator so that they can change the parameters to
enable incremental backups.
If the MS SQL Server Administrator recommends no changes, modify the
schedule to perform full instead of incremental backups.
MESSAGE:
[152:73] Error executing script!
DESCRIPTION:
An error occurred when executing the pre- or post-exec script.
ACTION:
(1) The script has to reside in the <Data_Protector_home>\bin directory.
(2) The script should always return zero (0).

If some other value is returned, Data Protector assumes an error and
displays this message. Check if your script returns this value.
(3) Check if appropriate permissions are set to allow a successful

script start. Since the Data Protector service OmniInet is responsible
to start Data Protector agents, check if the script can be executed under
the same rights as OmniInet has. If the script fails, you can grant
more rights to Data Protector OmniInet. You can do this by opening
"Control Panel" and open the "Services" program. Find "Data Protector Inet"
and click "Startup". You can modify rights in the "Log On As:"
dialog. Remember to restart (stop and then start) the OmniInet service
after you change these settings in order that changes take effect.
(4) Check both the syntax of the script and the way it is started
in the backup specification. There might be a misspelled command
that causes the script to fail.
MESSAGE:
[152:77] List of databases failed!
DESCRIPTION:
There was an error while retrieving information about databases from MS SQL Server.
ACTION:
* Check if the MS SQL Server service is still running and responding.
* You can check if MS SQL Server is running by opening the SQL Service Manager.
* You can check if MS SQL Server is responding by opening the

SQL Enterprise Manager and opening a connection to the SQL Server in question.
Try to browse databases and tables.
MESSAGE:
[152:78] Login to SQL Server failed!
DESCRIPTION:
There was an error while connecting to MS SQL Server.
ACTION:
(1) Check if the MS SQL Server service is still running and responding.
You can check if MS SQL Server is running by opening the

SQL Service Manager. You can check if MS SQL Server is responding
by opening the SQL Enterprise Manager and opening a connection to
the SQL Server in question. Try to browse databases and tables.
(2) Check if Data Protector MS SQL Agent configuration is still valid.
You can do this by opening the Data Protector Manager->Backup->Backup Specifications->MSSQL.

Create a new backup specification. If the Data Protector MS SQL Agent could
not login with current username and password, the configuration window will appear.
Specify the new configuration data and click OK. The Agent will start the configuration.
(3) Check the <Data_Protector_home>\log\debug.log file for additional information of the

error.
MESSAGE:
[152:91] Thread p reports: Incremental backup of MS SQL database tables is not possible.
DESCRIPTION:
For database tables only full backup can be started.
ACTION:
Either start a full backup for this backup specification or create a

backup specification that has the whole database selected instead of
database tables. MS SQL databases can to be backed up in the incremental
or full mode, while database tables can be backed up only in the full mode.
MESSAGE:
[152:129] You are using agent for Microsoft SQL Server 6.x with Microsoft SQL Server 7.0 or
later.
DESCRIPTION:
There are two different versions of Data Protector Agents for Microsoft SQL Server:
* Agent for SQL Server 7.0/2000

* Agent for older versions of SQL Server (this agent)
ACTION:
You can do one of the following:
* Install new SQL agent (recommended; see documentation).

* Install Microsoft SQL Server 6.5.
MESSAGE:
[152:9012] Wrong block size. Block size has to be within num and num bytes.
DESCRIPTION:
Block size for this database is not within the range required by Microsoft SQL Server.
ACTION:
Specify correct block sizes for devices, used in backup or restore.
MESSAGE:
[152:9013] Wrong block sizes.
DESCRIPTION:
Block sizes of all devices for Microsoft SQL backup have to be the same.
ACTION:
Specify the same block sizes for all devices used for backup or restore.
MESSAGE:
[152:9208] Data Protector is probably not configured for use with SQL Server on this host.
DESCRIPTION:
Data Protector has to be configured to use with SQL Server before any backups or restores
can be performed.
ACTION:
You can configure SQL Server in one of the following ways:
1. create a new backup specification for that host
2. log on to SQL Server and execute the following commands:
* set configuration
<Data_Protector_home>\bin\sql_bar conf -dbuser:<user> -password:<password>
* get configuration (double check)
<Data_Protector_home>\bin\sql_bar getconf
MESSAGE:
[152:9209] Pre-zeroing database files.
DESCRIPTION:
Pre-zeroing files process can take from a few minutes up to several hours, depending on hardware
configuration and size of database being restored. It can take from one third (according to
Microsoft) up to half (according to field reports) of entire restoration time. The process is
avoided in some cases when database files already exist.
ACTION:
The following global timeout values can be exceeded in some cases when pre-zeroing files process
takes long time:
SmMaIdleTimeout=140 # Numeric default value in minutes

SmDaIdleTimeout=120 # Numeric default value in minutes
To increase default values, open global options file residing in

<Data_Protector_home>\Config\Options\ directory on Windows Cell Manager or in the
/etc/opt/omni/options location on UNIX Cell Managers and change the values to fit your
environment. Detailed description of the mentioned options can be found in the global file.
MESSAGE:
[152:9509] Unable to restore datafile p.
DESCRIPTION:
Unable to restore datafile belonging to database backed up using concurrent streams.
ACTION:
Restore entire database.
MESSAGE:
[153:7] No backup specification specified.
DESCRIPTION:
Backup specification is an important part of backup because it contains data about

the devices to perform the backup on and other information.
ACTION:
If you have started the agent manually from the command line, you have to specify
the backup specification name as a command line option (-bar:<barname>) or through setting the
environment variable OB2BARLIST. If you have started backup using Manager, then a
serious error has occurred. Contact HP Support Representative.
MESSAGE:
[153:9] Connect to Exchange Server failed.
DESCRIPTION:
This situation can happen at backup or restore.
* One or more Microsoft Exchange Services is not running.

* Something is wrong with the Exchange Server services.
ACTION:
A. If backup has failed, check if the following services are running:
* Microsoft Exchange System Attendant

* Microsoft Exchange Directory Store
* Microsoft Exchange Information Store
B. If restore has failed, check if "Microsoft Exchange System Attendant" is the only
Microsoft Exchange service that is running.
C. If all proper services are running, try to restart them and retry backup or
restore operation. If it fails again, contact Microsoft Support.
MESSAGE:
[153:109] Data Protector Exchange Agent cannot execute script 'p'.
DESCRIPTION:
Script file does not exist or you do not have enough privileges to execute it.
Data Protector starts only the scripts that are in the <Data_Protector_home>\bin directory.
ACTION:
Check if the script exists in the <Data_Protector_home>\bin directory on the computer where
the agent is started and that you have enough privileges to execute that script. If you
are trying to execute a script that resides somewhere else on the computer, try to move the
script to <Data_Protector_home>\bin.
MESSAGE:
[153:115] Cannot backup incrementally, switching to full backup.
DESCRIPTION:
The Microsoft Exchange Server cannot be backed up incrementally because full backup doesn't exist
in Data Protector Internal Database. Data Protector will perform a full backup instead.
ACTION:
* Perform full database of a whole Microsoft Exchange Server.
MESSAGE:
[153:209] Data Protector Exchange Agent cannot create chain of backed up data to perform restore.
DESCRIPTION:
Agent could not create version chain for data restore. Possible cause is that
database agent on the Cell Manager is not running.
ACTION:
* Check if the database agent on the Cell Manager is running.

* If the Microsoft Exchange Server is running in cluster, you have to use the -restorefrom:
[ClusterName] option.
MESSAGE:
[153:210] Restored file size is not equal to backed up size for file
'p'.
DESCRIPTION:
Agent restores data into sparse files. Although file size may appear correct,
some parts of the file might not have been restored. An error might have appeared in
some of the threads and it has not restored all necessary data.
ACTION:
Check if all devices and computers to perform the restore are ready and try to restore
the data once more. If restore fails again, contact HP Support Representative.
MESSAGE:
[153:311] All log files from 'p' were not successfully deleted.
System error:num
System message: 'p'.
DESCRIPTION:
This might cause troubles when restoring Microsoft Exchange Server data to another client.
There might be some troubles starting services.
ACTION:
If you will have troubles starting services, try to delete old *.log files manually.
Old log files are those, whose names were not reported during restore session.
MESSAGE:
[153:312] Microsoft Exchange's dll 'p' could not be loaded.
DESCRIPTION:
This error might occur if the Microsoft Exchange Server is not installed or is not installed
correctly.
ACTION:
Check if Microsoft Exchange Server is installed. Check if the specified dll exists.
MESSAGE:
[153:402] Attempting to restart MS Exchange Server services.
DESCRIPTION:
Microsoft Exchange Server will perform recovery of restored database.
ACTION:
You can monitor progress of recovery in Event Viewer.
MESSAGE:
[153:405] All services were not started.
DESCRIPTION:
Agent attempted to start the services it had stopped at the beginning of the restore
session. For some reason, some of the services failed to start.
ACTION:
Check the Microsoft Exchange Server services on the machine and try to run them manually.
Check the messages in the Eventlog Viewer as well.
MESSAGE:
[153:413] Timeout. Service 'p' could not be started in num seconds. Aborting.
DESCRIPTION:
Data Protector Exchange agent has built in 15 minutes timeout to start service.
This value can be too small when restoring large databases.
ACTION:
The default 900 seconds timeout can be overridden with adding or editing registry value:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\OmniBackII\Agents\Exchange\SvcStartTimeout.
Fill in the appropriate timeout value in seconds: e.g. for 30 minutes timeout write 1800.
MESSAGE:
[153:416] The service

'p'
on the machine 'p' is not stopped.
DESCRIPTION:
Restore of the Microsoft Exchange Server database files has to be done while the Server is
offline.
This means that the Microsoft Exchange Services for Information Store and Directory must not run.
ACTION:
You can either use the option in the Data Protector Manager to inform the Data Protector
agent to stop the services automatically or to stop the services manually
before the restore. If you have started the restore from the command line, use
the -stop option.
MESSAGE:
[153:601] Error reading registry on application host p.
DESCRIPTION:
Exchange Server split mirror integration needs locations of the Exchange Server files to back up.
They are stored in the registry on Exchange Server computer.
ACTION:
* Check the installation of the Exchange Server on the computer

* Check access rights to that computer
MESSAGE:
[154:00056] Only the first num objects are displayed. Some will not be visible!
DESCRIPTION:
Displaying large quantities of objects may result in poor performance and high memory usage.
Server limits such large quantities by displaying only a subset of objects.
ACTION:
In general, limited number of displayed objects shouldn't represent a problem in functionality. If

you run into such situation, change the MaxDisplayedObjects value in the global option file on the
cell manager, and server will be able to display more objects.
MESSAGE:
[154:449] Unable to show document.
DESCRIPTION:
Error while trying to show document. You probably do not have a PDF file reader installed (Adobe
Acrobat Reader).
ACTION:
Check if the default handler for PDF files is installed on your computer (Explorer, View|Options,
File types page). If you found it there then contact your administrator. If not then install Adobe
Acrobat Reader.
MESSAGE:
[154:572] Interprocess communication problem.
DESCRIPTION:
Server error: Web request failed.
ACTION:
Ensure that the Data Protector Application Server service/process is properly configured and
running on the Cell Manager.
MESSAGE:
[154:50028] Cannot add components to the Windows Cell Manager.
DESCRIPTION:
In the list of client systems you have selected Data Protector Cell Manager. This operation cannot
be performed on the Windows Cell Manager system and will be skipped.
ACTION:
See the HP Data Protector Installation and Licensing Guide for how to install Cell Manager.
MESSAGE:
[154:50037] Cannot upgrade NT Cell Manager.
DESCRIPTION:
In the list of client systems you have selected Data Protector Cell Manager. This operation cannot
be performed on the NT Cell Manager system and will be skipped.
ACTION:
See the Installation Guide for how to install Cell Manager.
MESSAGE:
[156:1089] Cannot add client system (p) that you specified to the client system list.
DESCRIPTION:
The client system you specified could not be added to the client system list. You may want to
remedy the problem by checking the recommended action list.
ACTION:
1. Make sure that the client system you are adding is a valid network client (DNS).
2. Ensure that the client is accessible on the network (ping) and that its OmniInet service is up
and running (telnet).
3. Verify that the client system you are adding belongs to one of supported platforms
(Windows/Linux).
4. Make sure that the system you are using is not overloaded.
MESSAGE:
[156:1187] There are no objects to display!
DESCRIPTION:
No backups of the target database have been found in the recovery catalog and current control file
respectively.
ACTION:
1. Make sure that the target database is opened or mounted, and if recovery catalog is used that
it is opened.
2. In case of a disaster recovery scenario please refer to Data Protector Integration Guide for
Oracle and SAP on how to proceed.
MESSAGE:
[156:1223] Your password field contains some unsupported characters.
Proceed?
DESCRIPTION:
While specifying password you should use only regular ASCII characters up to character code 127.
This includes all uppercase and lowercase letters as well as numbers and punctuation. This
limitation origins from the characteristics of the recovery operating system, which is currently
not localized; this may prevent users from entering the correct password, rendering recovery image
unbootable.
ACTION:
* Retype the password and use only standard ASCII characters up to character code 127.
MESSAGE:
[156:1226] You failed to inject the drivers collected during the backup into the image being
created.
Insert automatically?
DESCRIPTION:
Failure to inject the drivers collected at backup time into the resulting image file might result
in the recovery operating system that does not have access to all storage / peripheral devices
(e.g. disk, network adapters).
ACTION:
* Select Yes to insert the stored drivers automatically.

* Select No to proceed without inserting the drivers collected at backup time.
* Select Cancel to abort the procedure. You can than click the Inject button to manually
manipulate the injection of the original system drivers.
MESSAGE:
[156:6006] Unsupported version of drecovery.ini file.
DESCRIPTION:
The version of drecovery.ini file of the client

you want to create ISO image for is not supported.
ACTION:
* The drecovery.ini file of your client is created with

old version of Disaster Recovery Module and is not supported
by the Disaster Recovery Module on this client. Go to the
client that has the old version of Disaster Recovery Module
and create ISO image for your client there.
MESSAGE:
[156:6007] Conflict *.p1s file version.
DESCRIPTION:
The version of *.p1s file of the client

you want to create ISO image for is not supported.
ACTION:
* The *.p1s file of your client is created with

old version of Disaster Recovery Module and is not supported
by the Disaster Recovery Module on this client. Go to the
client that has the old version of Disaster Recovery Module
and create ISO image for your client there.
MESSAGE:
[158:1131] The specified user was not found in the user list. Proceed anyway?
DESCRIPTION:
The specified user was not found in the Data Protector user list.
The backup may succeed anyway, but the user you have specified may not be able to
restore the data. Even in that case, another user with sufficient user rights
(or an Administrator) will be able to restore the data.
ACTION:
* Verify the user you have specified.

* Verify that the specified user is configured in the Data Protector user list.
MESSAGE:
[158:1132] The specified user cannot be verified because you have insufficient user rights to get
the user list.
DESCRIPTION:
Only a user that has the "User configuration" right can verify the user data when
configuring backups. Note that the specified user will be checked at backup time
by the Backup Session Manager. You can use a backup preview to verify the user you
have specified.
ACTION:
* Make sure you specify a valid user since the validity cannot be verified at this
point. You can use a backup preview to verify the user you have specified.
MESSAGE:
[158:4702] OBDR capability check of the device you selected failed. Click OK to proceed with
attempted action or Cancel to abort.
DESCRIPTION:
Cannot check OBDR capability of the device you selected due to the:
* failure of parsing the device path or
* error in processing device string or
* failure in SCSI command inquiry.
ACTION:
* Check that the device is not busy.
MESSAGE:
[159:13136] Please select only resident Data Protector media.
DESCRIPTION:
You have selected a medium that is not resident (currently not in any Data Protector configured
library), thus Data Protector cannot locate it automatically.
ACTION:
To perform this operation:
A. Insert a medium into a standalone or a stacker device.

Select the desired operation in the Device menu.
OR
B. Insert media into the library. Scan the slot(s) where the media are located.
(Alternatively, you can select all slots and scan them - this takes more
time). Media will become resident.
MESSAGE:
[159:13332] Backup Size Quota should be greater or equal to Store Size Quota
Do you want to continue?
DESCRIPTION:
Backup Size Quota should normally be greater than Store Size Quota,
as the data being backed up into the store will be deduplicated and
the size of the store on disk will be less than the original data size.
ACTION:
If you continue Store Size Quota will not be effective.
MESSAGE:
[159:13333] Backup Size Quota or Store Size Quota are not defined.
DESCRIPTION:
Backup Size Quota and Store Size Quota depend on each other. You left one of them blank.
ACTION:
If you continue the Backup Size Quota and Store Size Quota will not be effective.
MESSAGE:
[159:13334] Backup Size Quota should be greater or equal to Storage Unit Size Quota
DESCRIPTION:
Backup Size Quota should normally be greater than Storage Unit Size Quota,
as the data being backed up into the storage unit will be deduplicated and
the size of the storage unit on disk will be less than the original data size.
ACTION:
If you continue Storage Unit Size Quota will not be effective.
MESSAGE:
[159:13335] Backup Size Quota or Storage Unit Size Quota are not defined.
DESCRIPTION:
Backup Size Quota and Storage Unit Size Quota depend on each other. You left one of them blank.
ACTION:
If you continue the Backup Size Quota and Storage Unit Size Quota will not be effective.
MESSAGE:
[159:53301] Configuration of IAP devices failed.
DESCRIPTION:
Configuration of IAP device could fail because of problem in configuration on Cell Manager or on
IAP Connector machine.
Device will be created but it will not be full functional.
ACTION:
1) Make sure that data you typed are correct.
2) Please verify installation of the Cell Manager:

* Check if directory exists <Data_Protector_home>/Config/Server/certificates
* Check if you have write permissions on directory
<Data_Protector_home>/Config/Client/Certificates
3) Please verify installation of the IAP Deduplication Agent:

* Check if directory exists <Data_Protector_home>/Config/Client/certificates
* Check if you have write permissions on directory
<Data_Protector_home>/Config/Client/Certificates
* Check if executable exists <Data_Protector_home>/riss_con/bin/rte/bin/client/RIMFConfig.exe
MESSAGE:
[165:4005] Some non-critical errors were detected during the collecting

of Automatic DR data. Please review the Automatic DR log file.
DESCRIPTION:
A non-critical error was encountered during execution of the Automatic Disaster Recovery module.
This backup can most likely be used for Disaster Recovery purposes.
ACTION:
To identify the errors search for string " ERROR ".

Ignore all entries containing " WARN ".
Possible reasons:
1. Services/drivers outside the <SystemRoot> folder (e.g. virus scanners):
ERROR safeboot 'unsupported location' 'intercheck support 06' 2 u'\??\D:\Program
Files\Sophos SWEEP for NT\icntst06.sys'
- Action: None. This message may be ignored.
2. A disk larger than 7.8 Gb on Windows NT 4.0

INFO storage 'check_system_partition' 'boot' u'C:'
ERROR storage 'boot' 'volume' u'C:' 'last_cyl' 1105 ' >= 1024.' 'System may not boot after
disaster recovery.'
- Action: Check the boot/system volume size and physical location on the disk. If both of them
are physically located
below 7.8 Gb, the message may be ignored.
MESSAGE:
[165:4025] Unable to check the elevation status of the running process.
DESCRIPTION:
Verification of elevation status of the running process resulted in error.
ACTION:
N/A
MESSAGE:
[165:4026] Your user rights do not allow you to proceed with this operation.
DESCRIPTION:
Either User Account Control (UAC) is enabled and the process was started without
elevation or UAC is disabled and the process is started by an user without
permissions to start the process.
ACTION:
If UAC is enabled start the process with elevation by:

* Right clicking on the process and choose "Run as administrator" or
* Starting the process from command line using runas command and providing the
password when prompted (for example:
runas /user:<[domain\]username> "c:\Program Files\Omniback\bin\manager.exe").
If UAC is disabled start the process as user with permissions to do it.
MESSAGE:
[165:4078] Media creation host does not have the correct WAIK/ADK version installed.
DESCRIPTION:
In order to create EADR recovery image for Windows clients the media creation host must have
the correct version of the Windows Automated Installation Kit (WAIK) or Assessment and Deployment
Kit (ADK) installed. The required WAIK/ADK version is determined by the OS version of the recovery
host for which the EADR recovery image is being created.
ACTION:
Choose a media creation host which has the correct WAIK/ADK version installed or
install following WAIK/ADK version for the selected recovery host OS type:
* Windows Vista & Windows Server 2008: WAIK 1.1
* Windows 7 & Windows Server 2008R2: WAIK 3.1
* Windows 8 & Windows Server 2012: ADK 1.0
* Windows 8.1 & Windows Server 2012R2: ADK 1.1
MESSAGE:
[166:410] Account "p" does not have a unique Display Name.
DESCRIPTION:
There is one or more mailbox accounts with the same Display Name as the account selected for
backup/restore.
ACTION:
* If it is a backup session, please update barlist to select modified unique mailbox names
or a higher level for backups (group...).
* If it is a restore session, please use Restore Into Mailbox option to specify unique
mailbox to restore into. To distinguish between mailboxes use the username from LegacyExchangeDN.
For example: <display name>@@<LegacyExchangeDN username>
MESSAGE:
[166:420] Restoring of p mailbox has failed with error num.
DESCRIPTION:
This is due to one of the following reasons:
* User's mailbox has exceeded the specified size limit.

* There is not enough disk space left to restore data.
ACTION:
* Check mailbox size limit on MS Exchange Server.

* Check disk space where MS Exchange database(s) are installed.
* Check if the MS Exchange services are still running and responding.
MESSAGE:
[166:700] The list of folders that correspond to mailbox p is too long.
DESCRIPTION:
Only the whole mailbox's contents will be possible to restore.
ACTION:
Please increase the size of Ipc buffer size using OB2IPCBUFSIZE variable in order to be able to
restore single folders.
MESSAGE:
[168:011] Failed to load VDS service.
DESCRIPTION:
VDS service can not be loaded.
ACTION:
Check that Virtual Disk Service is in stopped or started state.

If it is not and cannot be neither stopped nor started, log onto the machine again
and check if system is requesting your confirmation to stop crashed VDS service. If
it is reconfigure debugger to launch automatically (this can be done by setting
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug value Auto to 1).
If above steps do not help, the Virtual Disk Service can be stopped forcefully by
terminating process vds.exe. The service will be started automatically when needed.
If Virtual Disk Service is running normally and can be stopped and started, check
if Logical Disk Manager Administrative Service is running properly. If it is not
in stopped or started state and does not respond to start/stop commands, it
can prevent Virtual Disk Service from operation properly. You can stop
Logical Disk Manager Administrative Service forcefully by terminating
process dmadmin.exe. The service will be started automatically when needed.
MESSAGE:
[168:022] Failed to resolve volume: p.
DESCRIPTION:
No VDS provider is found for specified volume.
ACTION:
Please check that VDS provider for specified volume is installed and is working properly.
Check event log for VDS errors.
For P6000 EVA Family disk array try restarting Command View service.
MESSAGE:
[168:041] Failed to present disks with properties:
DESCRIPTION:
VDS provider failed to present disk.
ACTION:
Please check that VDS provider for specified disk is installed and is working properly.
MESSAGE:
[168:046] Failed to unpresent disks with properties:
DESCRIPTION:
VDS provider failed to unpresent disk.
ACTION:
MESSAGE:
[168:102] Failed to resolve volume: p.
DESCRIPTION:
Required VDS information could not be found for specified volume.
ACTION:
Please check that if a VDS provider is installed for the specified volume that it is configured
properly.
Restart the VDS service.
MESSAGE:
[168:114] Failed to present disks with properties:
DESCRIPTION:
VDS provider failed to present disk.
ACTION:
MESSAGE:
[168:116] Failed to unpresent disks with properties:
DESCRIPTION:
VDS provider failed to unpresent disk.
ACTION:
MESSAGE:
[169:14] Virtual machine 'p': power-on started. Check if additional actions are required.
DESCRIPTION:
Data Protector VMware agent has initiated a power-on of a virtual machine.
You may need to perform additional actions in Virtual Infrastructure Client
to complete the operation.
ACTION:
Check virtual machine status in Virtual Infrastructure Client.
MESSAGE:
[169:121] Virtual machine 'p': changed snapshot state.
DESCRIPTION:
Data Protector VMware agent has detected that snapshots were
created, deleted or reverted to by user since the last backup.
ACTION:
You need to perform full snapshot backup of virtual machine.
MESSAGE:
[169:124] Virtual machine 'p' will be restore to 'p'.
DESCRIPTION:
Data Protector VMware agent was unable to connect to the host,
the files needed to recover the virtual machine will be restored to a folder in the client.
ACTION:
If the virtual machine was hosted by a ESXi server, in order to recover the virtual
machine you need to use the VMWare Converter as explained in DP documentation.
If that is not the case, reconfigure your host communication and re-run restore.
MESSAGE:
[170:313] One or more copies of database p are already being backed up in a different session.
DESCRIPTION:
Only one backup (full/incr/diff) at a time can be performed on a single database due to Exchange
federation log truncation.
ACTION:
Wait for the currently running session to complete and restart backup of this database.
If there are no other backup sessions of this database currently running and the lock is for some
reason still enabled,
please use command: omnidbutil -free_cell_resources, to disable it.
MESSAGE:
[170:411] Mounting the new Recovery database p will be skipped.

There is already mounted Recovery database p on the same client p.
DESCRIPTION:
Only one Recovery database at a time can be mounted on a single MS Exchange server.
ACTION:
Manually dismount the currently mounted Recovery database and mount the newly created Recovery
database.
MESSAGE:
[170:413] Last operation performed on database p was Restore to a point in time.
DESCRIPTION:
Restore method Repair all passive copies with failed status or Restore to the latest state can not
be
used after the same backup was used to perform restore to a point in time.
ACTION:
Perform backup after restore to a point in time. The newly created backup can be used with all
restore methods.
MESSAGE:
[170:414] Database p could not be found in current Exchange topology.
DESCRIPTION:
Getting the GUID of the database with specified name failed.
ACTION:
Please use omnir -db_guid option to specify the guid of the database you want to restore.
MESSAGE:
[170:417] An unsupported mix of IR methods has been selected for different databases.
DESCRIPTION:
It is not supported to mix IR methods

Repair all passive copies with failed status,
Restore to the latest state and
Restore to a point in time
with methods
Restore to a new mailbox database and
Restore to a temporary location
in a single IR session.
ACTION:
Please use just methods from first or second group for IR in a single session.
MESSAGE:
[170:418] IR to a different location can be performed only to one target client in a single
session.
DESCRIPTION:
It is not supported to perform IR of databases to different targets using methods

Restore to a new mailbox database and
Restore to a temporary location
in a single IR session.
ACTION:
Please use the same target client for all hosts.
MESSAGE:
[170:469] Following passive database copies have not been restored to the point in time of the
active database: p.
DESCRIPTION:
Passive database copies which were not restored will be in Failed status since they are now newer
then the active database copy.
ACTION:
Please run restore to the point in time also for the passive copies which were not restored.
Or use Microsoft Exchange GUI or PowerShell command to update (reseed) the passive copies.
MESSAGE:
[170:570] Data Protector is probably not configured for use with MS Exchange Server 2013 on this
host.
DESCRIPTION:
Data Protector has to be configured to use with MS Exchange Server 2013 before any backups or
restores
can be performed.
ACTION:
You can configure MS Exchange Server 2013 Server in one of the following ways:
1. create a new backup specification for that host
2. log on to MS Exchange Server 2013 and execute the following commands:
* set configuration
<Data_Protector_home>\bin\e2010_bar -config username:<user> password:<password>
* get configuration (double check)
<Data_Protector_home>\bin\e2010_bar -getconf
MESSAGE:
[171:10] Windows sharepoint services (help) search on 'p' creating...
DESCRIPTION:
Windows sharepoint services (help) search is not restored but re-created.
ACTION:
Recrawl the content indexed by Windows sharepoint services (help) search.
MESSAGE:
[171:16] Farm Configuration 'p' creating...
DESCRIPTION:
Operation consists of re-connecting servers to SharePoint farm and re-configuring SharePoint

servers.
This operation can take very long time depending on infrastructure and size of farm being
restored.
After configuration restore some of SharePoint windows services on individual servers will be
disabled.
Normally only these windows services are started by Data Protector SharePoint agent:
SharePoint administration, timer and tracing.
Note that restore of Single Sign-On, Shared Services Providers and Windows SharePoint services
(help) search will
automatically try to start services needed by selected component.
ACTION:
*After all needed components are restored find SharePoint windows services that are disabled on
individual SharePoint servers but were running and start them.
MESSAGE:
[171:120] Farm configuration failed.
DESCRIPTION:
Farm configuration consists of re-connecting servers to SharePoint farm

and re-configuring the servers. Farm configuration restore is only supported
to completely the same environment (same servers, patches, etc.).
ACTION:
* Check that environment is the same as in the time of backup.

* Check for error reported by Data Protector SharePoint agent and SharePoint logs.
* If an update conflict has occurred, clear the filesystem cache on all servers in the server farm
on which
Windows SharePoint Services Timer is running. For detail description of the problem and
instructions see:
http://support.microsoft.com/kb/939308
MESSAGE:
[171:131] Linking content database 'p' to 'p' failed. Error: p
DESCRIPTION:
Link adds restored content database to an web application.

Every object in SharePoint has its GUID (Globally Unique Identifier). If you tried to put
two objects with same GUID into SharePoint farm this operation will fail
(...The attach operation cannot continue because another object in this farm already contains the
same ID...).
ACTION:
*If original content database is still in the farm, remove it manually from SharePoint farm or use
"Unlink original content database" option.
*If object with same GUID is not an content database try to identify the conflicting object and
assign it a new GUID.
MESSAGE:
[171:135] 'p': operation failed 'connect'. Error: p
DESCRIPTION:
Connect joins servers into SharePoint farm. To achieve this SharePoint farm administrator
credentials or
passphrase is used. If credentials or passphrase is wrong connect will fail.
ACTION:
*Check that SharePoint farm administrator credentials or farm passphrase registered into DP are
correct.
MESSAGE:
[171:138] 'p': operation failed 'delete file system cache'. Error: p
DESCRIPTION:
SharePoint file system cache failed to delete. This may lead to an update conflict on some restore
of components.
SharePoint file system cache is normally located in %APPDATA%\Microsoft\SharePoint on every
SharePoint server
where Windows SharePoint Services Timer is running.
ACTION:
* Check for error reported by Data Protector SharePoint agent.

* If some process is locking SharePoint file system cache try to unlock it.
MESSAGE:
[171:139] Shared Service Provider administration web page was redirected.
DESCRIPTION:
In case of Shared Service Provider(SSP) administration web application redirection

SharePoint central administration web page may still show SSP administration page on original web
application.
ACTION:
* Recycle SharePoint central administration web application:

* Reset IIS on SharePoint server hosting central administration web page with "IISReset
/restart /noforce" or
* Touch web.config file of the central administration web page.
MESSAGE:
[171:143] Central Administration service is disabled.
DESCRIPTION:
Required SharePoint Central administration service in the farm is not online.

This service is normally running on first SharePoint server which was connected to farm and
on which Central Administration web application was created. Restoring this configuration backup
will require
additional manual step of provisioning central administration web application.
ACTION:
*Start "Central Administration" service on appropriate server from Central Administration web site
(Operations...Services On Server).
MESSAGE:
[171:144] Central Administration service was disabled at the time of backup.
DESCRIPTION:
Required SharePoint Central administration service in the farm was not online at the time of
backup.
This service is normally running on first SharePoint server which was connected to farm and
on which Central Administration web application was created.
After restore please follow steps in actions section.
ACTION:
*Use SharePoint psconfig command-line tool to provision central administration web application.
(e.g.: psconfig.exe -cmd adminvs -provision)
MESSAGE:
[171:147] Passphrase check failed on 'p'. Error: p
DESCRIPTION:
Passphrase is used in SharePoint to connect or reconnect servers to SharePoint farm and it is

defined during farm
creation. Data Protector will use this passphrase during SharePoint configuration restore so
passphrase stored in Data Protector needs to match to passphrase used in the SharePoint farm.
ACTION:
*Configure passphrase stored in Data Protector with GUI, omnicc or omniinetpasswd to match
the passphrase used in SharePoint farm.
*If passphrase used in SharePoint farm is lost the user can reset this passphrase with:
*Open the SharePoint Management Shell
*Enter: '$passphrase = ConvertTo-SecureString -asPlainText -Force'
*Input the new passphrase
*Enter 'Set-SPPassPhrase -PassPhrase $passphrase -Confirm'
*Reenter the passphrase and confirm
MESSAGE:
[172:2] Could not load plugin p
DESCRIPTION:
A necessary library could not be loaded
ACTION:
====
In case of an Hyper-V backup, check whether you have installed the MS Volume Shadow Copy
Integration.
MESSAGE:
[172:7] Could not find the connection information for host p.
DESCRIPTION:
The operation could not be performed due to connection problems. Configuration of the client is
missing or incomplete
ACTION:
====
Check whether the host is in the cell.
Check whether the VMware vCenter/ESX(i)/vCloud Director or Hyper-V client is correctly configured
in HP Backup.
MESSAGE:
[172:151] Virtual machine 'p': Incremental/Differential backup not enabled.
DESCRIPTION:
The backup method could not be performed
ACTION:
====
Check whether you have selected either Single or Mixed as the Snapshot handling method in
Configure Virtual Machine -> Snapshot handling
Check whether you have run a successful full backup
MESSAGE:
[172:157] Virtual Machine 'p': Could not create snapshot ...
DESCRIPTION:
Virtual Machine cannot be backed up because snapshot creation failed
ACTION:
====
Check whether you have the right user privileges to create virtual machine snapshots (Required
Priviledge: VirtualMachine.State.CreateSnapshot)
Snapshots are not supported for virtual machines with Fault tolerance turned on
MESSAGE:
[172:168] Reading blocks from disk failed.
DESCRIPTION:
The backup could not be performed due to an error while reading the virtual machine disk data.
ACTION:
====
Ensure that there's low activity on vCenter and retry the backup session.
MESSAGE:
[172:172] Error creating Virtual Machine 'p'.
DESCRIPTION:
The specified Virtual Machine could not be created on the vCenter or ESXi.
ACTION:
====
1. Ensure that there is enough space left on the datastore the VM is restored to.
2. Ensure the ESXi/vCenter is accessible from the backup host through network.
3. Ensure there is no VM with the same name in the specified location.
MESSAGE:
[172:184] Virtual Machine 'p': Configuration not supported.
DESCRIPTION:
The Virtual Machine contains user's snapshots. It is not supported to restore a single disk then.
ACTION:
====
Remove the user's snapshots, then start restore again.
MESSAGE:
[172:192] Virtual Machine 'p': Changed block tracking was not active when creating the snapshot
...
DESCRIPTION:
Changed block tracking was enbaled but the snapshot did not create a valid changeid.
ACTION:
====
Please check if you VM has been powered on. Changed block tracking requires the machine to be
powered on once.
MESSAGE:
[172:194] Virtual Machine 'p': Changed block tracking is not supported ...
DESCRIPTION:
Changed block tracking is not supported for the specific VM.
ACTION:
Please check if the VM version is 7 or higher.
MESSAGE:
[172:277] Virtual Machine 'p':

Error adding VM to cluster.
DESCRIPTION:
Your restored VM is not going to be high available. It's recommended to recreate the cluster
resource manually.
ACTION:
You can use Power Shell commands to create the cluster resource on the cluster node where the VM
is running on:
Import-Module FailoverClusters
Add-ClusterVirtualMachineRole -VirtualMachine 'vm name'
MESSAGE:

WMI Problem. Unable to add the VM to the cluster.
DESCRIPTION:
Your restored VM is not going to be high available. It's recommended to recreate the cluster
resource manually.
ACTION:
You can use Power Shell commands to create the cluster resource on the cluster node where the VM
is running on:
Import-Module FailoverClusters
Add-ClusterVirtualMachineRole -VirtualMachine 'vm name'
MESSAGE:
[172:285] Virtual Machine 'p': No disk backed up ...
DESCRIPTION:
There can be various reasons for this problem.

1. You've tried to back up a VM that does not contain any disks. This is not supported.
2. All of the VM disks failed to be backed up.
3. CBT is not supported for the VM disks but the backup was configured to use CBT.
MESSAGE:
[172:320] Virtual Machine 'p': Could not create disk 'p' because of a block size mismatch ...
DESCRIPTION:
The size of the disk is not a multiple of the blocksize of the datastore you want to restore to.
This could result in corrupt data or errors when creating the virtual disk.
See Vmware KB:
http://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1035096
ACTION:
====
Please make sure you restore to a datastore with a blocksize which matches the virtual disk block
size.
MESSAGE:
[172:325] Ambiguous virtual machine UUID
DESCRIPTION:
Virtual machines are identified using a world wide unique ID. This ID
is generated and assigned by the ESX or vCenter when a virtual machine
is created. Certain operations however, like import and restore of a
virtual machine while retaining a previous copy, can lead to a situation
where two or more copies of a virtual machine share the same ID.
You are getting this warning to inform you that such a situation has been
encountered in your environment. There is the risk that another copy
of the virtual machine is being used for the current operation than
originally intended.
ACTION:
====
In the vSphere Client in the 'VMs and Templates' view select the top level
item (vCenter or ESX). On the right pane select 'Virtual Machines'. Right
click on the column header and check 'UUID'. This adds a column called
'UUID'. Click on the header of that column to make sure the list of
virtual machines is sorted by UUID. Look for a virtual machines with
the UUID 'p'.
Make sure you remove any copies of the virtual machine that you do not need
anymore, thus leaving only one virtual machine with the given UUID.
Alternatively, if you want to keep one or more of the copies, use VMwares
cloning capabilities to create a copy with a differen UUID and remove the
copy with the ambiguous UUID.
MESSAGE:
[172:364] Virtual Machine 'p': Could not shutdown virtual machine. Powering off instead ...
DESCRIPTION:
The Virtual Machine guest system could not be shutdown, because of the following reasons. VM is:
- not powered on
- in a busy state
- not running VMware Tools
ACTION:
====
MESSAGE:
[172:366] Restoring XML file p
DESCRIPTION:
Recovering XML based configuration file, follow the action items.
ACTION:
====
Recovering with the VM configuration file in the XML format
Follow the procedure:
1. Open vSphere Client and log in to an ESX(i) Server or vCenter Server system.
If the virtual machine is still configured, remove all its hard disks:
a. In the inventory object tree, right-click the virtual machine and select Edit Settings....
b. In the Virtual Machine Properties window, in the Hardware tab, select each hard disk and click
Remove.
c. Click OK to confirm the removal.
If the virtual machine is no longer present, configure a new virtual machine without hard disks,
and use the name of the original virtual machine.
In either case, remember the associated datastore name.
2. Upload the virtual machine files that were created during the backup session:
a. In the inventory objects tree, select the ESX(i) Server system that hosts the virtual machine.
b. Click the Configuration tab and select Storage under Hardware.
c. Right-click the datastore name and select Browse Datastore.
d. In the Datastore Browser window, in the folder tree, select the virtual machine folder, and
click a corresponding icon on the window toolbar. Select Upload File. or Upload Folder. as
appropriate.
e. Select all applicable files and complete the upload.
3. Add hard disks to the virtual machine while reusing their backup copies:
a. In the inventory object tree, right-click the virtual machine and select Edit Settings.
b. In the Virtual Machine Properties window, click Add.
c. In the Add Hardware window, select Hard Disk and click Next.
d. Select Use an existing virtual disk and click Next.
e. Click Browse.
f. In the Browse Datastores window, browse to the appropriate datastore and open the virtual
machine folder. Select the virtual disk file and click OK.
g. Follow the Add Hardware wizard to complete the process.
h. Repeat the substeps from b to g for each additional hard disk for which a backup copy exists.
4. Power the virtual machine on.
MESSAGE:
[172:370] ESXi 'p': Cannot restore because it is managed by vCenter 'p' ...
DESCRIPTION:
ESXi Servers version 5.0 and higher cannot be used directly for restore if they are managed by a
vCenter.
ACTION:
====
Taken from the Vmware VDDK 5.0 release notes (http://www.vmware.com/support/developer/vddk/VDDK-
500-ReleaseNotes.html)
Restore of virtual machine fails when connected directly to ESXi host.
Sometimes you must restore a VM directly to an ESXi host, for example in disaster recovery when
ESXi hosts the vCenter Server as a VM.
A new vSphere 5 feature tries to prevent this if the ESXi 5.0 host is managed by vCenter. To
circumvent this and restore the VM, you must first disassociate the host from vCenter.
In earlier releases, vCenter management was revocable only from vCenter.

- Using the vSphere Client, connect directly to the ESXi 5.0 host.
- In the Inventory left-hand panel, select the host.
- In the right-hand panel, click Summary.
- There in the box titled Host Management, click Disassociate host from vCenter Server.
- It is not necessary to put the host in Maintenance Mode.
- Once the vCenter Server has been restored and is back in service, use it to reacquire the host.
MESSAGE:
[172:373] Virtual Machine 'p': Upload of virtual machine config file failed.
DESCRIPTION:
The configuration (vmx file) for the virtual machine could not be restored. Nevertheless the
virtual machine's disks have been restored successfully.
ACTION:
====
You can try to restore the virtual machine again or configure it manually.
MESSAGE:
[172:379] Virtual Machine 'p' not added to the backup ...
DESCRIPTION:
Unsupported special characters found in backup objects. List of unsupported characters can be
found in documentation.
ACTION:
===
1. Remove not supported special characters from virtual machine name.
2. Remove not supported special characters from datacenter name.
3. Remove not supported special characters from virtual machine datastore names.
MESSAGE:
[172:380] Unsupported characters found. Could not start restore ...
DESCRIPTION:
Unsupported special characters found. List of unsupported characters can be found in

documentation.
ACTION:
===
1. Remove unsupported special characters from target datacenter name.
2. Remove unsupported supported special characters from target datastore names.
MESSAGE:
[172:381] Virtual machine 'p' contains unsupported special characters. Virtual machine can not be
restored ...
DESCRIPTION:
Unsupported special characters found. List of unsupported characters can be found in

documentation.
ACTION:
===
1. Remove unsupported special characters from virtual machine name.
MESSAGE:
[172:385] Virtual Machine 'p': Download of virtual machine config file failed.
DESCRIPTION:
The configuration (vmx file) for the virtual machine could not be downloaded. Restore to directory
and import using vmx file will not be possible.
ACTION:
====
You can try to backup the virtual machine again.
MESSAGE:
[172:387] Virtual machine 'p': Disk consolidation failed.
DESCRIPTION:
The backup could not be performed due to an error while performing disk consolidation.
ACTION:
====
Perform disk consolidation manually in order to perform backup of virtual machine.
MESSAGE:
[172:388] Virtual Machine 'p': HP Backup snapshot(s) could not be deleted. Changed Block Tracking
cannot be enabled.
DESCRIPTION:
Changed Block Tracking cannot be enabled for this virtual machine as HP Backup snapshots cannot be
deleted.
ACTION:
====
To enable Changed Block Tracking, delete the HP Backup snapshots manually and restart the backup.
MESSAGE:
[172:390] Virtual Machine 'p': User Snapshot(s) found. Changed Block Tracking cannot be enabled.
DESCRIPTION:
Changed Block Tracking cannot be enabled for this virtual machine as user snapshots exist.
ACTION:
====
To enable Changed Block Tracking, delete user snapshot(s) for this virtual machine and restart the
backup.
MESSAGE:
[172:392] Virtual Machine 'p': Failed to delete directory 'p'.
DESCRIPTION:
Failed to delete VM transport method lock files.
ACTION:
====
Delete the VM transport method lock directory manually.
MESSAGE:
[172:396] Virtual Machine 'p': 'Delete after restore' and 'Keep for forensics' option cannot be
used on suspended VM.
DESCRIPTION:
Virtual Machine is in suspended state and can therefor not be renamed.

The 'Delete after restore' option and 'Keep for forensics' option requires to rename the Virtual
machine. This option can therefor not be used.
ACTION:
To be able to restore using the 'Delete after restore' option do one of the following:
1. Power on the VM
2. Power off the VM
MESSAGE:
[172:500] Virtual Machine 'p' not added to the backup.
DESCRIPTION:
Newer version of backup for this virtual machine have been found. Running backup again can break
backup chain.
ACTION:
====
You can run backup for this virtual machine from existing backup specification, or create a new
one.
MESSAGE:
[172:501] Backup session 'p' was created with earlier version of DP. Session can not be
restarted...
DESCRIPTION:
Backup sessions created with earlier versions of DP can not be restarted.
ACTION:
====
Create new backup and then restart of failed session will be possible.
MESSAGE:
[172:1113] VirtualDatacenter 'p': vDC was not found. Could not add VM(s) to vApp.
DESCRIPTION:
VM(s) have been restored into the vSphere Datacenter, but could not be added to the vApp.
ACTION:
Add VM(s) to vApp manually.
MESSAGE:
[172:1121] vApp 'p': Error power on ...
DESCRIPTION:
vCloud Director has thrown allocating the required resources to power on the vApp and its Virtual
Machines.
ACTION:
1. Ensure the network assigned to Virtual Machines and the vApp are accessible by the Virtual
Datacenter and the
Organization.
2. Ensure there are no IP Adress conflicts. If the restored Virtual Machines and vApps have the
same IP Adress as others
in the same Organization the vApp will not power on. To avoid this set the vApp to 'Fenced'
MESSAGE:
[172:1131] VirtualMachine 'p': Could not determine vCenter ...
DESCRIPTION:
A reference to the vCenter hosting the Virtual Machine is part of the VMs XML representation if
the user doing the API
call has sufficient priviledges. If not the information cannot be seen.
ACTION:
====
Make sure the user performing the backup has 'Administrator View' rights on the 'System'
organization.
MESSAGE:
[172:1135] Virtual Machine 'p' could not be found to import into vApp 'p' ...
DESCRIPTION:
The requested virtual machine was not found in the vCloud Director inventory.
vCloud Director sychronizes its inventory with the enabled vCenters. This can sometimes take a
while so the VM can not
be found during the restore process.
ACTION:
Try manually importing the VM to the vApp.
MESSAGE:

Could not validate restore chain.
DESCRIPTION:
The restore chain could not be validated because the necessary information was not
stored in the internal database at backup time. This is the case when the restore chain
protection was disabled at backup time (OB2_VEAGENT_DISABLE_RESTORE_CHAIN_PROTECTION=1).
ACTION:
To disable the restore chain protection in order to run the restore without validation
you have to add the following omnirc variable on the VEAgent host:
OB2_VEAGENT_DISABLE_RESTORE_CHAIN_PROTECTION=1
MESSAGE:
[175:142] Unable to update archive command in postgresql.conf.
DESCRIPTION:
If update of archive command failed restored database will continue use old location(same as
backuped up instance used) for archived log files.
ACTION:
To change location of archived log files manually do the following:

login to OS as user who owns restored IDB database files
open <RESTORE_DATA_DIR>/postgresql.conf and find line beginging with "archive_command"
change target path in copy command to new one
restart DP services(omnisv stop/start) or reload instance configuration (with pg_ctl reload -
D<RESTORE_DATA_DIR>)
MESSAGE:
[175:144] Failed to update IDB and JCE tablespace symlink target path in idb.config and in
postgres database.
DESCRIPTION:
Automatic update of the IDB and JCE tablespace symlink target path in the idb.config file and the
Internal Database database has failed. The paths need to be updated manually.
ACTION:
To update the tablespace symlink target path manually please perform the following steps:
1. Find out the new IDB and JCE tablespace symlink target path by examining the tablespace symlink
at <RESTORE_DATA_DIR>/pg_tblspc
2. Locate and open the file <DP_CONFIG>/server/idb/idb.config
3. Change the PGDATA_IDB entry in the idb.config file to show the new IDB tablespace symlink
target path
4. Change the PGDATA_JCE entry in the idb.config file to show the new JCE tablespace symlink
target path
5. Read the PGIDBNAME, PGSUPERUSER and PGPORT values from the idb.config file
6. On HPUX and Linux systems login as PGSUPERUSER using command "su - <PGSUPERUSER>"
7. Connect to the database using PSQL by executing the following command from command line:
On Windows and HPUX: <IDB_BIN>/psql "-U<PGSUPERUSER>" "-hlocalhost" "-p<PGPORT>" "postgres"
On Linux: <IDB_BIN>/psql "-U<PGSUPERUSER>" "-h/var/opt/omni/tmp" "-p<PGPORT>" "postgres"
8. Update the table pg_tablespace by executing the following SQL script : "UPDATE pg_tablespace
SET spclocation = '<new IDB tablespace symlink target path>' WHERE spcname = '<PGIDBNAME>';"
9. Update the table pg_tablespace by executing the following SQL script : "UPDATE pg_tablespace
SET spclocation = '<new JCE tablespace symlink target path>' WHERE spcname = 'hpjce';"
MESSAGE:
[175:316] Automatic replacement of the Internal Database on cluster environment not supported.
DESCRIPTION:
Automatic replacement of the Internal Database on SG(hpux and linux) cluster environment is not
supported. The database switch must be performed manually.
ACTION:
To manually switch database to restored one on SG(hpux and linux) cluster environment please
perform the following steps:
1. Edit /etc/opt/omni/server/idb/idb.config and change following keys: PGDATA_PG (put path to
restored database <other location>/pg) and
PGDATA_IDB (put <other location>/idb), PGDATA_JCE (put <other location>/jce and PGWALPATH (put
<other location>/pg/ pg_xlog_archive).
2. Change idb service to point to restored IDB instance with command: "omnidbutil -sync_srv".
3. Halt dp package with command: "cmhaltpkg <dp_package_name>"
4. While package halting is in progress in other console run: "/opt/omni/idb/bin/pg_ctl -
D<path_to_original_idb_db> stop"
This step is necessary for success of step 3. <path_to_original_idb> is value of PGDATA_PG key
in idb.config before step 1.
5. Run dp package with command: "cmrunpkg <dp_package_name>"
6. Unregister all dcbfs directories with command "omnidbutil -remove_dcdir oldPathName" (if
restore dcbfs to other directory has been performed)
If command refuses to remove old dcbf directories move them and run "omnidbutil -fixmpos" and
repeat step 6.
7. Register new dcbf directories with command "omnidbutil -add_dcdir newPathName" (if restore
dcbfs to other directory has been performed)
MESSAGE:
[210:1] Loader: Cannot find module p.
DESCRIPTION:
Loader error occurred. Loader cannot find NetWare

Loadable Module (NLM).
ACTION:
Check the installation and location of modules.

Pay attention to the search path SYS:USR\OMNI\BIN
using SEARCH console command on the Novell
Server.
MESSAGE:
[210:2] Loader: Error reading module p.
DESCRIPTION:
Loader error occurred. Loader cannot read NetWare

Loadable Module (NLM).
ACTION:
Check that module is not flagged for shared and

read deny access using MONITOR.NLM utility.
MESSAGE:
[210:3] Loader: Not NLM file format (module p).
DESCRIPTION:
Loader error occurred. Loader detected that

module's format is damaged.
ACTION:
Check that modules have been installed correctly.

If you are using FTP utility to transfer modules
watch out that binary transfer mode is enabled.
MESSAGE:
[210:4] Loader: Wrong NLM file version (module p).
DESCRIPTION:
Loader error occurred. Loader detected that file

version is not correct.
ACTION:
Check that you installed the latest Data Protector

modules.
MESSAGE:
[210:5] Loader: Re-entrant initialization failure (module p).
DESCRIPTION:
Loader error occurred. Module cannot be used

re-entrantly due to initialization failure.
ACTION:
You should free some memory by unloading not

needed modules and try again. If it still fails
add more memory to the system.
MESSAGE:
[210:6] Loader: Cannot load multiple copies (module p).
DESCRIPTION:
Loader error occurred. Module is already loaded

and cannot be loaded multiple times.
ACTION:
Check that you use the correct backup or

restore procedure.
MESSAGE:
[210:7] Loader: Already in progress (module p).
DESCRIPTION:
Loader error occurred. Loading of the module is

already in progress.
ACTION:
Check that you use the correct backup or

restore procedure.
MESSAGE:
[210:8] Loader: Not enough memory (module p).
DESCRIPTION:
Loader error occurred. There is not enough memory

to load the module.
ACTION:
You should free some memory by unloading not

needed modules and try again. If it still fails
add more memory to the system.
MESSAGE:
[210:9] Loader: Initialization failure (module p).
DESCRIPTION:
Loader error occurred. Module cannot be loaded due

to module initialization failure.
ACTION:
You should check that server's memory is

optimized and that there is enough memory
available for Data Protector modules.
MESSAGE:
[210:10] Loader: Inconsistent file format (module p).
DESCRIPTION:
Loader error occurred. Loader detected

inconsistency in module's format.
ACTION:
Check that modules have been installed correctly.

If you are using FTP utility to transfer modules
watch out that binary transfer mode is enabled.
MESSAGE:
[210:11] Loader: Cannot load at startup (module p).
DESCRIPTION:
Loader error occurred. Loader cannot load

module at startup.
ACTION:
Check that the correct Data Protector modules have

been installed.
MESSAGE:
[210:12] Loader: Auto-load modules not loaded (module p).
DESCRIPTION:
Loader error occurred. Loader cannot load module

due to dependent module loading failure.
ACTION:
Check that you have the latest dependent modules from the
latest patches installed.
MESSAGE:
[210:13] Loader: Unresolved external symbol (module p).
DESCRIPTION:

due to unresolved external symbol.
ACTION:
Check that all dependent modules are loaded.

Unresolved external symbol is located in one
of the dependent modules.
MESSAGE:
[210:14] Loader: Public symbol already defined (module p).
DESCRIPTION:

due to already exported public symbol.
ACTION:
Check that module is not already loaded.
MESSAGE:
[220:2] SMS: Error num.
DESCRIPTION:
Storage Management Services (SMS) error occurred.
ACTION:
Check the installation of Data Protector and make sure

all latest Novell patches are installed. Patches can
be found at http://support.novell.com/misc/patlst.htm.
MESSAGE:
[221:32752] SMDR: The specified TSA does not exist.
DESCRIPTION:
Storage Management Data Requestor (SMDR) reported

that proper Target Service Agent (TSA) is not
loaded.
ACTION:
Load proper Target Service Agent; if you are

backing up or restoring NetWare Directory
Services (NDS) load TSANDS.NLM.
MESSAGE:
[221:32763] SMDR: The requested function is not supported by the SMDR.
DESCRIPTION:

that function requested is not supported.
ACTION:
Check that latest versions of SMS modules are

installed.
MESSAGE:
[221:32765] SMDR: SMDR memory allocation failed.
DESCRIPTION:

that memory allocation failed.
ACTION:
Unload not needed modules to get more free memory.

If problem persists you should add more memory to
the system.
MESSAGE:
[222:32697] TSA: The requested function is not supported by this TSA.
DESCRIPTION:
Target Service Agent (TSA) reported that

function requested is not supported.
ACTION:
Check that latest versions of SMS modules are

installed.
MESSAGE:
[222:32713] TSA: The file server is out of memory or the memory allocation failed.
DESCRIPTION:
Target Service Agent (TSA) reported

that memory allocation failed.
ACTION:
Unload not needed modules to get more free memory.

If problem persists you should add more memory to
the system.
MESSAGE:
[222:32727] TSA: Cannot connect to Target Service (login denied).
DESCRIPTION:
Target Service Agent (TSA) reported

that process (VBDA.NLM or VRDA.NLM) cannot
connect.
ACTION:
Check that correct user and password information

is stored successfully to SYS:SYSTEM directory
using HPLOGIN.NLM utility.
MESSAGE:
[222:32767] TSA: Invalid username or authentication.
DESCRIPTION:
Target Service Agent (TSA) reported invalid

username or password.
ACTION:
Check that correct user and password information

is stored successfully to SYS:SYSTEM directory
using HPLOGIN.NLM utility.
MESSAGE:
[223:120] Resolving of all input objects failed.
DESCRIPTION:
The session will fail because none of the objects was successfully
resolved.
ACTION:
MESSAGE:
[223:123] Could not mount filesystem p back to

p.
(p)
DESCRIPTION:
The mount operation failed. SYMA unmounted the filesystem before

the split was done, to stop the IO and sync the disk buffers.
ACTION:
* Manually mount the filesystem back.
MESSAGE:
[223:124] Could not unmount filesystem p.

(p)
DESCRIPTION:
The filesystem has to be unmounted, to stop the IO and sync the disk
buffers. Before unmount all processes using this filesystem have to be
stopped. This has to be done in Symmetrix "Split Pre-Exec" script.
ACTION:
* Check the system error.

* Check the Symmetrix "Split Pre-Exec" script.
MESSAGE:
[223:125] Resolving of object p has failed.

(p)
DESCRIPTION:
The mapping of object to Symmetrix disks failed. The session will fail
for this object.
ACTION:
MESSAGE:
[223:126] Mapping of logical volume p to physical volume(s) has failed.

(p)
DESCRIPTION:
The mapping operation failed. The information about physical Symmetrix

disks on which the logical volume is created could not be obtained.
SYMAPI function is used for the mapping.
The second possibility is that logical volume configuration is not
supported (striped volume).
ACTION:
* Check the SYMAPI error description.
MESSAGE:
[223:127] Could not get the information about device p

from the Data Protector Symmetrix database.
(p)
DESCRIPTION:
Since the information about the device could not be obtained, the
session will fail for all objects which are created on this device.
SYMAPI function is used to get the information about device.
ACTION:
MESSAGE:
[223:128] The split operation failed for the object p.
DESCRIPTION:
The Symmetrix disks of the object were not split. The session will
fail for this object.
ACTION:
MESSAGE:
[223:129] The re-establish operation failed for the object p.
DESCRIPTION:
The Symmetrix disks of the object were not re-established. The mirrors
won't be active after the session.
ACTION:
* Check the SYMA log file /var/opt/omni/tmp/emc/R1_<SESSION-ID>.log

on HP-UX or <Data_Protector_home>\Config\ mp\emc on Windows NT.
* Manually create the device group for re-establish (SYMCLI).
* Put the devices for which the re-establish operation failed into
device group (SYMCLI).
* Re-establish the devices (SYMCLI).
MESSAGE:
[223:130] The restore link operation failed for the object p.
DESCRIPTION:
The Symmetrix disks of the object were not restored. This means that
the links were not successfully restored from the backup host to
the application host.
ACTION:
MESSAGE:
[223:131] Could not lock logical drive p. (p)
DESCRIPTION:
The logical drive has to be locked, to stop the IO and sync the disk
buffers. Before locking logical drive all processes using it have to be
stopped. This has to be done in Symmetrix "Split Pre-Exec" script.
ACTION:
MESSAGE:
[223:132] Could not unlock logical drive p.

(p)
DESCRIPTION:
Unlocking the logical drive failed. SYMA locked it before

the split was done, to stop the IO and sync the disk buffers.
ACTION:
* Abort the session or wait until the session ends. System

unlocks all logical drives when process which locked them exits.
MESSAGE:
[223:133] Mapping of the object p failed.

(p)
DESCRIPTION:
Could not get information about physical extents for the object.Backup of the object will fail.
ACTION:
MESSAGE:
[223:150] Cannot get physical device p status!
DESCRIPTION:
#Could not get meta device information about physical device.#Backup of the object will fail.
ACTION:
MESSAGE:
[223:188] Disabling of application disk on the application host for the

object p failed.
(p)
DESCRIPTION:
The preparing of application disks on the application host failed

for restore. For the restore session the application disks, which
are part of restore have to be disabled before the split of links
is done. The "Split Pre-Exec" command has to stop all processes on
these disks and unmount all filesystems, except those that will be
restored in this session.
ACTION:
MESSAGE:
[223:189] Enabling of application disks on the application host for the

object p failed.
(p)
DESCRIPTION:
The application disks could not be enabled back. The activation of

volume group failed.
ACTION:
* Manually activate the volume group.
MESSAGE:
[223:191] Could not prepare mirror disks of object p

connected to the backup host.
DESCRIPTION:
The Symmetrix disks of the object could not be prepared for the
session. This means that the session will fail for this object.
ACTION:
* Check why the activation of volume groups and mounting

of filesystems failed.
MESSAGE:
[223:192] Could not disable the mirror disks of the object p.
DESCRIPTION:
The Symmetrix disks of the object could not be disabled. This means
that perhaps the filesystems are still mounted, volume groups are
activated (HP-UX only) on the backup host.
ACTION:
* Review SYMA log file on the backup host

(/var/opt/omni/tmp/emc/R2_<SESSION-ID>.log on HP-UX or
<Data_Protector_home>\Config\ mp\emc\R2_<SESSION-ID>.log on Windows NT).
* Manually disable the mirror disks on the backup host.
* Unmount the filesystems.
* Deactivate the volume groups.
MESSAGE:
[223:193] Could not activate volume group p.
DESCRIPTION:
The volume group has to be activated, after the links are restored,
to prepare the restored application disks.
ACTION:
* Manually activate the volume group.
MESSAGE:
[223:194] Could not deactivate volume group p.
DESCRIPTION:
The volume groups has to be deactivated to disable the application

disks on the application host before the split is started. The
Symmetrix "Split Pre-Exec" script has to stop all processes using
the Symmetrix disks, to prepare the disks for deactivating of
volume group.
ACTION:
MESSAGE:
[223:230] Disks syncing failed.
DESCRIPTION:
The disks have to be synchronized before the split operation can be

started. Since the synchronization didn't complete the split won't
be started and the session will fail.
ACTION:
* If you think that the time frame for synchronization was too
short you can extend it. Set SYMA_WAIT_FOR_SYNC and
SYMA_RETRY_SINC variables in the /opt/omni/.omnirc file on HP-UX or
<Data_Protector_home>\omnirc file on Windows NT.
MESSAGE:
[223:301] Device p from Symmetrix p is not part of a BCV pair.
DESCRIPTION:
According to the selected type of Symmetrix mirror, device must have

the BCV associated.
ACTION:
* Check your configuration.
MESSAGE:
[223:303] RDF-R2 device p from Symmetrix p is not visible on the backup host.
DESCRIPTION:
All RDF-R2 device must be connected to the backup host if the selected
Symmetrix mirror is SRDF.
ACTION:
* Check your mirror configuration.
MESSAGE:
[223:306] Could not create device group p.

(p)
DESCRIPTION:
Since the device group creation failed all operations on the

device will fail. The session will fail for all object which have
devices in this device group.
ACTION:
MESSAGE:
[223:309] Could not set the type of device group (REGULAR | RDF1 | RDF2) for
device p from Symmetrix p. (p)
DESCRIPTION:
According to the Symmetrix device configuration the type of device

group is defined. The operation failed for this device.
ACTION:
* Check the Symmetrix device configuration.
MESSAGE:
[223:316] Could not split BCV links for devices in device group p.
(p)
DESCRIPTION:
The split of all objects that are created on the devices from
this device group will fail and the session for these objects will
fail.
ACTION:
MESSAGE:
[223:323] Could not associate BCV param3 from Symmetrix

param1 with device group param2.
(param4)
DESCRIPTION:
The SYMA agent failed to associate the BCV mirror to the device
group.
ACTION:
MESSAGE:
[223:324] Could not add device p from Symmetrix p

to device group p.
(p)
DESCRIPTION:
The SYMA agent failed to add the device to the device group.
The mirror could not be split.
ACTION:
MESSAGE:
[223:325] Could not activate volume group p.
DESCRIPTION:
The SYMA agent failed to activate the volume group, so the mirror
disks won't be prepared for the session and the session will fail for
all objects on this volume group.
ACTION:
* Check if you have properly imported the volume groups on the

backup system.
MESSAGE:
[223:326] Could not deactivate volume group p.
DESCRIPTION:
The SYMA agent failed to deactivate previously activated volume group.

The Symmetrix mirror disk won't be properly disabled.
ACTION:
* Deactivate the volume group manually.
MESSAGE:
[223:327] Could not mount filesystem p to p.

(p)
DESCRIPTION:
The SYMA agent failed to mount the filesystem on the backup host.
The Symmetrix mirror disk won't be prepared for the backup.
ACTION:
* Check why the mount operation failed. One of possible reasons

is that the mountpoint on the backup host doesn't exist.
* Check if drive is already mounted. Dismounted drive on the
backup system and restart backup operation.
MESSAGE:
[223:328] Could not unmount p.

(p)
DESCRIPTION:
The SYMA agent failed to unmount the filesystem on the backup host.
The Symmetrix mirror disk won't be properly disabled.
ACTION:
* Check why the unmount operation failed.

* Unmount the filesystem manually.
MESSAGE:
[223:333] Failed to read p file.

Mapping of all logical volumes on backup host will fail.
(p)
DESCRIPTION:
The SYMA agent reads the lvmtab to get the information needed for
resolving the name of the volume groups on the backup side. Since
this file could not be read, the mapping operation failed.
ACTION:
* Verify that the volume group table (file /etc/lvmtab on HP-UX systems)
exists on the system running the SYMA agent and can be accessed.
* Consult you local system administrator or UNIX guru about
possible reasons for this failure.
MESSAGE:
[223:334] Volume group p is not deactivated.
DESCRIPTION:
The volume group on the backup host have to be deactivated at the

beginning of the session. Since this is not the case the session
will fail for all object that are created on this volume group.
ACTION:
* Deactivate the volume group on the backup host before the next
session is started.
MESSAGE:
[223:335] Failed to synchronize SRDF links in device group p

before backup.
(p)
DESCRIPTION:
The synchronization of mirror disks failed. The session will fail for
all objects which have devices in this device group.
ACTION:
MESSAGE:
[223:341] Could not restore BCV links for devices in device

group p.
(p)
DESCRIPTION:
The SYMA agent failed to restore devices in the device group.
ACTION:

* Check the SYMA log file /var/opt/omni/tmp/emc/R2_<SESSION-ID>.log on HP-UX
or <Data_Protector_home>\Config\ mp\emc\R2_<SESSION-ID>.log on Windows NT.
* Manually create the device group for restore (SYMCLI).
* Put the devices for which the restore operation failed into
restore device group (SYMCLI).
* Restore the devices (SYMCLI).
MESSAGE:
[223:343] Failed to move device p from Symmetrix p into restore

device group p. (p)
DESCRIPTION:
The devices of properly restored object are moved from the original
device group into restore device group. This operation failed.
ACTION:
MESSAGE:
[223:345] Failed to associate BCV device p from Symmetrix

p to restore device group p.
(p)
DESCRIPTION:
The BCV mirrors of properly restored object are moved from the
original device group into restore device group. This operation
failed.
ACTION:
MESSAGE:
[223:349] Could not map filesystem p.
DESCRIPTION:
The SYMA agent failed to map the filesystem on the backup host.
The Symmetrix mirror disk won't be prepared for the backup.
ACTION:
* Check why the map operation failed. One of possible reasons

is that the partition on the backup host doesn't exist.
MESSAGE:

(p)
DESCRIPTION:
The session will fail for the object since the resolving failed.
ACTION:
MESSAGE:
[223:361] Split of links(s), which belong to the object p, has failed.

(p)
DESCRIPTION:
The session will fail for the object since the split failed.
ACTION:
MESSAGE:
[223:362] Re-establish of links(s), which belong to the object

p, has failed.
(p)
DESCRIPTION:
The mirror disks will be left split.
ACTION:
* Manually re-establish the links.
MESSAGE:
[223:363] Could not prepare mirror disks of object p

for backup.
(p)
DESCRIPTION:
The session will fail for the object.
ACTION:
MESSAGE:
[223:364] Could not disable mirror disk of object p.

(p)
DESCRIPTION:
The mirror disks will stay enabled.
ACTION:
* Manually disable the mirror disks.
MESSAGE:
[223:365] Restore of links(s), which belong to the object

p, has failed.
(p)
DESCRIPTION:
The restore of mirror disks to the application host failed.
ACTION:
* Manually restore or re-establish the links.
MESSAGE:
[223:366] Synchronization of links(s), which belong to the object

p, has failed.
(p)
DESCRIPTION:
The session will fail for the object since the mirror disks weren't
synchronized.
ACTION:
MESSAGE:
[223:406] Failed to initialize the SYMAPI session.

(p)
DESCRIPTION:
The SYMAPI session could not be initialized, so the agent could not
access the Symmetrix.
ACTION:

* Check if some other agent has locked the database.
MESSAGE:
[223:407] Failed to rescan host devices and rebuild Symmetrix database.

(p)
DESCRIPTION:
The discover operation of Symmetrix failed.
ACTION:
MESSAGE:
[223:507] Failed to get an exclusive access to SYMA recovery log file.

(p)
DESCRIPTION:
Every time the recovery file is updated the SYMA agent gets first
lock of the /opt/omni/lbin/.syma.lck file on HP-UX or <Data_Protector_home>\Config\emc\syma.lck.
ACTION:
MESSAGE:
DESCRIPTION:

filesystems on the system running the SYMA agent. The error message
ACTION:
* Verify that the mount table (file /etc/mnttab on HP-UX systems)

exists on the system running the SYMA agent and can be accessed.
* Consult you local system administrator or UNIX guru about
MESSAGE:
[223:512] param1
Cannot verify filesystem mount point: (param2).
DESCRIPTION:
Data Protector is unable to locate the specified mount point in the

register of mounted filesystems.
ACTION:
* Verify that the specified mount point exists on the system

running the SYMA agent and can be accessed.
* Is the specified filesystem mounted at backup time?
MESSAGE:
[223:901] param1
Cannot open() script: (param2)
DESCRIPTION:
The agent could not invoke a subshell script using the open() system
call. The error message indicates the reason as reported by the OS.
ACTION:

invocations.
* Verify that the computer running the SYMA agent has sufficient
MESSAGE:
[223:903] param1
Error reading script output (param2).
DESCRIPTION:
The SYMA process detected an error while reading from the pipe
through which it is connected with its Pre/Post-Exec process. The
error is probably cause by an ungraceful termination of the script.
ACTION:

invocations.
for possible bugs.
MESSAGE:
[223:904] Split links Pre-Exec command failed with exit code num.
DESCRIPTION:
The Split Pre-Exec command failed to prepare the environment for split.
ACTION:

invocations.
for possible bugs.
MESSAGE:
[223:905] Split links Post-Exec failed with exit code num.
DESCRIPTION:
The Split Post-Exec command failed to restart stopped processes.
ACTION:

invocations.
for possible bugs.
MESSAGE:
[223:907] Resume links Post-Exec failed with exit code num.
DESCRIPTION:
The Resume Post-Exec command failed to restart stopped processes..
ACTION:

invocations.
for possible bugs.
MESSAGE:
[223:1002] Cstat command failed. Backup might not be useful.
DESCRIPTION:
Cstat command failed. Backup might not be useful.
ACTION:
* Check if some Fastrax sessions are still active. When they complete
terminate them.
MESSAGE:
[224:8] Volume group p could not be deactivated.
DESCRIPTION:
Data Protector cannot deactivate the volume group.
ACTION:
* Check if there is a filesystem that is not included in the backup, but which uses
a volume from the problematic volume group.
* Manually split disks, dismount the filesystems and
try to deactivate the problematic volume group.
MESSAGE:
[224:75] Skipping preparation of the application system!
DESCRIPTION:
The OMNIRC variable ZDB_IR_MANUAL_AS_PREPARATION has been enabled on the

application system. Therefore, Data Protector assumes that the
application system has been manually prepared for instant recovery. Manual
preparation includes the dismounting of target filesystems and the disabling
of target volume groups.
Even when the application system has not been prepared, the instant recovery
may still be successful. In this case, you need to disable and then re-enable the
application data after the instant recovery.
ACTION:
* Verify that the application filesystems are dismounted and the corresponding
volume groups disabled.
* In case they are not, dismount the filesystems and disable volume groups
after the instant recovery, and then enable volume groups and the mount filesystems.
MESSAGE:
[224:76] Skipping resume of the application system!
DESCRIPTION:

application system. Therefore, the application system configuration must be
resumed manually after the instant recovery.
ACTION:
* Enable the volume groups where the restored filesystems are configured.
* Mount the restored filesystems.
MESSAGE:
[224:91] Legacy DSF is disabled at the backup system.
DESCRIPTION:
Legacy DSF has been disabled at the backup system and VxVM does not support
the agile DSF. Therefore VxVM diskgroups cannot be created and prepared
for the tape backup.
ACTION:
* Reenable the legacy DSF using "insf -L" command.

* Replace the backup system with a HP-UX 11.11 or 11.23 host.
MESSAGE:

(p)
DESCRIPTION:
The mapping of object to physical disks failed. The object

will not be backed up.
ACTION:
* If the problematic object is a directory, then check

if it is created on both application and backup system.
* If the problematic object is a logical volume (rvol), then
check if the volume group is correctly imported on the
backup system.
MESSAGE:
DESCRIPTION:
Data Protector can not open the register of

mounted filesystems. The error message indicates
ACTION:

exists on the system.
* Check permissions of the mount table (file /etc/mnttab on
HP-UX systems).
* Consult your local system administrator about
MESSAGE:
[224:116] Failed to read p file. Mapping of all logical volumes on backup host will fail.
(p)
DESCRIPTION:
The Data Protector agent reads the /etc/lvmtab to get the

information needed for resolving the name of the volume
groups on the backup system. Since this file could not
be read, the mapping operation failed.
ACTION:
exists on the system and can be accessed.
* Consult you local system administrator about
MESSAGE:
[224:119] Volume "p"

on target volume has not been found.
DESCRIPTION:
The Data Protector agent could not find specific volume

while listing all volumes. Device drivers may be out of sync.
ACTION:
* Rescan the disks: go to Control Panel, Administrative Tools, Computer Management,

Storage, Disk Management. In the Actions menu, click Rescan Disks.
Restart the backup.
* If using Solaris Volume Manager volumes, check whether the volume is part of a disk set.
Volumes should be specified as /dev/md/<disk set name>/dsk/d#
* If the problem persists, reboot the system and restart the backup.
MESSAGE:
[224:123] The disks that were resolved for application volume group p don't have
a matching volume group on the backup host.
DESCRIPTION:
The disks that were resolved on the backup host are not in a
volume group. SNAPA can't proceed with the session.
ACTION:
* Verify that the disks resolved in the session are part of

a volume group.
* If the disks shouldn't be used in the session, ensure that they
are in the restricted LUN list.
MESSAGE:
[224:128] Invalid Configuration for Instant Restore:

Physical volumes of a mirror in the logical volume
p span across multiple Physical Volume Groups(PVG).
DESCRIPTION:
The Physical volumes of a mirror in the logical volume

belong to multiple PVGs. Instant recovery is not possible
for such a configuration due to LVM limitation.
ACTION:
* Please disable the option "Track for Instant Recovery"

and try the backup.
MESSAGE:
[224:307] Filesystem check on p failed.

(p)
DESCRIPTION:
Filesystem check could not be performed on the replica.
ACTION:
* Check the consistency of the filesystem on the application system.

* Create a replica manually and then run the filesystem check using the fsck command.
* The problem could be that disks are under very heavy
write load on the application system during the creation of the replica.
* On HP-UX with LVM in combination with a cluster, this error occurs during the instant recovery
when the omnirc variable ZDB_IR_VGCHANGE is not set to "vgchange -a e".
MESSAGE:
[224:501] Stop/quiesce-the-application-command script failed with exit code num.
DESCRIPTION:
Stop/quiesce-the-application-command script failed.
ACTION:
* Verify that the shell command line is syntactically correct.

for possible bugs.
MESSAGE:
[224:503] Restart-the-application-command script failed with exit code num.
DESCRIPTION:
The Restart-the-application-command script failed (e.g. failed to restart stopped

processes).
ACTION:

for possible bugs.
MESSAGE:
[224:2084] The local host, p, is not the same as the master node host,
p. The disk set cannot be deported in this scenario.
DESCRIPTION:
A disk set may not be removed from a system when the master node of
the disk set is not the same as the system itself. Both the local
host and the master node must be the same system for proper cleanup
of the disk set.
ACTION:
* Check the disk set on the local host and verify that the master node
of that disk set is the local host.
* If the master node of the disk set is not the local host, attempt to
bring the environment to this configuration. A cluster IP may be
switched over to the master node, and the restore performed again.
* Refer to Solaris volume manager and cluster documentation for further
documentation on master node changes.
MESSAGE:
[225:105] Resynchronizing of pairs failed.
DESCRIPTION:
Data Protector StorageWorks Agent cannot resync pairs.

It is possible that RAID Manager instance
on the application system was killed during
backup.
ACTION:
* Check if RAID Manager instance

backup.
* Check if LDEV pairs are not in PSUE or SSUE
status.
MESSAGE:
[225:106] Splitting of pairs failed.
DESCRIPTION:
Data Protector StorageWorks Agent cannot split pairs.

backup.
ACTION:

backup.
status.
MESSAGE:
[225:109] Mapping from character device file of disk to LDEV failed for
p.
(Raid Manager Library reported: "p")
DESCRIPTION:
Data Protector StorageWorks Agent cannot find StorageWorks LDEV

of the character device file.
ACTION:
* Check with command /sbin/ioscan if the problematic

character device file is StorageWorks disk array XP LDEV.
* Check permissions of the problematic character
device file.
MESSAGE:
[225:110] Mapping from LDEV to character device file of disk failed for
LDEV p on array num.
DESCRIPTION:
Data Protector StorageWorks Agent cannot find character device

file for the StorageWorks disk array XP LDEV. It could be that LDEV is not
exported to the host.
ACTION:
* Check if the problematic LDEV is exported to a port

which is connected to the host.
* Check with command xpinfo if problematic LDEV
has character device file.
* Start command 'insf -e' to recreate character device
files.
MESSAGE:
[225:605] Resynchronizing of pairs failed.
DESCRIPTION:
Data Protector StorageWorks Agent cannot resync pairs.

backup.
ACTION:

backup.
status.
MESSAGE:
[225:606] Splitting of pairs failed.
DESCRIPTION:
Data Protector StorageWorks Agent cannot split pairs.

backup.
ACTION:

backup.
status.
MESSAGE:
[225:609] Mapping from character device file of disk to LDEV failed for
p.
(p)
DESCRIPTION:
Data Protector StorageWorks Agent cannot find StorageWorks LDEV

of the character device file.
ACTION:
* Check with command inqury256.exe if the problematic

character device file is StorageWorks disk array XP LDEV.
* Check permissions of the problematic character
device file.
MESSAGE:
[225:610] Mapping from LDEV to character device file of disk failed for
LDEV p on array num.
DESCRIPTION:
Data Protector StorageWorks Agent cannot find character device

file for the StorageWorks disk array XP LDEV. It could be that LDEV is not
exported to the host.
ACTION:
* Check with command xpinfo if problematic LDEV

has character device file.
* Check if the problematic LDEV is exported to a port
which is connected to the host.
MESSAGE:
[225:1012] Failed to get pairs for all LDEVs.
DESCRIPTION:
Some of the LDEVs might not be configured as specified in

the backup specification.
ACTION:
* Check the backup specification for mirror type and

mirror numbers.
* Check the mirror configuration for all LDEVs used in a
backup session)
* Check the LDEV exclude list using the omnidbxp command.
MESSAGE:
[225:1013] Unsupported mirror configuration.
DESCRIPTION:
You have selected an unsupported mirror configuration for the operation.
ACTION:
* Check the mirror type specification.
MESSAGE:
[225:1113] One or more disks have snapshots attached. Quick restore is not possible.
DESCRIPTION:
Quick backward pair resynchronization is not possible if the Business Copy P-VOL
has an XP Snapshot attached.
ACTION:
* Run the session again with Resync replica data to the source volume option.
MESSAGE:
[225:1114] One or more disks have an active Continuous Access link. Instant recovery is not
possible
DESCRIPTION:
One or more source disks have an active CA link. Instant recovery is only possible
when the CA links are in suspended state.
ACTION:
* Split the Continuous Access pairs and run Instant recovery again.
MESSAGE:
[225:1252] Failed to leave maintenance mode for cluster resource "p" ("p").
DESCRIPTION:
The maintenance mode on a disk resource within the cluster creates an exclusive lock for an
application.
ACTION:
In order to allow other clients to access the disk resource, the maintenance mode must be removed.
This can be done manually using the cluster.exe command-line tool.
cluster res "<cluster resource name>" /extmaint:0

cluster res "<cluster resource name>" /maint:0
MESSAGE:
[225:1403] At least one object failed backup.

Session will not be available for instant recovery.
DESCRIPTION:
At least one object failed to be backed up by the agent. The session will not
be logged into the internal database as instantly recoverable.
ACTION:
* Check the reason for failure of the backup objects.
MESSAGE:
[225:1405] At least one disk does not reside in a valid CT group, or it has a ctgid
of 0, which cannot be used effectively by the agent.
DESCRIPTION:
Data Protector StorageWorks Agent cannot properly resolve

the ctgid of one or more of the source disks. It is also possible that the
StorageWorks disk array XP volume group was created with a ctgid of 0, which cannot
currently be used by the agent.
ACTION:
* Verify that all disks in the backup are part of a properly configured CT
group. The CT group may need to be be reconfigured.
* Verify that the StorageWorks disk array XP volume group was not created
with a ctgid of 0.
* If atomic split behaviour is not strictly needed, the OMNIRC variable
that controls atomic behaviour (SSEA_ATOMIC_SPLIT) may be disabled.
* If atomic split behaviour is required within the session but not for the
specific disks, the OMNIRC variable SSEA_ATOMIC_SPLIT_MIXED_CONFIG may be
enabled. This will allow disks to be outside of a CT group when atomic
split behaviour is enabled.
MESSAGE:
[225:1409] Only one CT group was expected to be included inside this backup
specification. However, multiple CT groups have been located.
DESCRIPTION:
Data Protector StorageWorks Agent has located multiple

CT groups inside the backup specification. However, the agent expected only
one CT group.
ACTION:
* Verify that all disks in the backup are part of the same CT group. The
CT group may need to be be reconfigured.
* If atomic split behaviour is required within the session, and there are
no issues with having multiple CT groups included inside the backup, the
OMNIRC variable SSEA_ATOMIC_SPLIT_MULTIPLE_CTGROUPS may be enabled.
MESSAGE:
[225:1410] The CT group with ctgid 'num' contains one or more disks that are not one of
the source disks or mirrors of the source disks. An atomic split may not
be performed without impacting disks outside of the backup specification.
DESCRIPTION:
Data Protector StorageWorks Agent has located one or more

disks that are in the CT group but are not related to the backup specification.
An atomic split may not be performed for this CT group without affecting disks
that are outside of the backup specification.
ACTION:
* Verify that all disks in the CT group are part of backup specifciation.
The CT group may need to be be reconfigured.
MESSAGE:
[225:1503] At least one object failed backup.

Session will not be available for instant recovery.
DESCRIPTION:
At least one object failed to be backed up by the agent. The session will not
be logged into the internal database as instantly recoverable.
ACTION:
* Check the reason for failure of the backup objects.
MESSAGE:
[227:27] SNAPA was unable to resolve the expected snapshots.
DESCRIPTION:
SNAPA reported that it was unable to successfully

resolve the expected snapshots of at least one backup
object.
ACTION:
* Check the Secure Manager on the Virtual Array and that

security passwords are properly configured for SNAPA.
* Check environment for any SAN configuration or control
software and ensure that this software allows correct
paths for hardware and resources.

* Check hardware for equipment failure.
* In case of preconfigured environments, or instant
recovery sessions, check that the expected snapshots
exist, and are visible to the backup host.
MESSAGE:
[227:109] Mapping from character device file of disk to LUN failed for
p.
(p)
DESCRIPTION:
SNAPA cannot find VA LUN that the character device

file is associated with.
ACTION:
* Check if the problematic character device file exists and is

a VA LUN.
* Check access permissions of the problematic character device
file.
MESSAGE:
[227:110] Mapping from LUN to character device file of disk failed for
LUN p on array p.
(p)
DESCRIPTION:
SNAPA cannot find the character device file for the VA

LUN. It could be that the LUN is not visible to the host.
ACTION:
* Check if the problematic character device file exists and is

a VA LUN.
file.
* Check SAN environment for proper configuration and access
rights.
MESSAGE:
[227:1032] IR for VA database query has returned an unexpected number of entries.
DESCRIPTION:
When SNAPA queried the IR for VA database for session information, the
number of entries returned did not match the expected number of entries.
ACTION:
* Check to ensure that the datalist has not been modified.

* Check IR for VA database consistency.
* Check for changes to backup objects.
MESSAGE:
[227:1151] Child LUNs exist on the Virtual Array that are outside of
the IR for VA database for this datalist. Restore will not
proceed.
DESCRIPTION:
LUNs that are child snapshots of the LUNs being restored to exist
on the Virtual Array and are not known of within the IR for VA
database. The restore cannot proceed if any child snapshots exist
outside of the rotated session entries for the datalist that has
created these session entries..
ACTION:
* Check the Virtual Array for child snapshots (outside of the session
rotated LUNs) of the objects that are being restored to.
* Check the IR for VA database for duplicated session objects that may
still exist on the Virtual Array.
* Clean the SAN environment of extraneous child LUNs.
MESSAGE:
[227:2013] There is not enough free RAM to complete the operation.
DESCRIPTION:
The system has run out of memory. The operation could not
be completed.
ACTION:
* Check the system memory settings.

* Check that there is sufficient swap space.
* Add system memory or extra swap areas for system usage.
MESSAGE:
[227:2018] The correct permission is not available for the specified

device.
DESCRIPTION:
SNAPA was unable to properly access the specified device.
ACTION:
* Check permissions for the specified device.

* Check permissions for LUN 0.
* Check if Secure Manager is enabled on the Virtual Array.
MESSAGE:
[227:2101] There is not enough unallocated physical disk space

to create a LUN of the specified size.
DESCRIPTION:
SNAPA was not able to create a LUN with the present amount
of unallocated physical disk space.
ACTION:
* Allocate or reallocate physical disk space

* Delete unused LUNs
MESSAGE:
[227:2102] The snapshot LUN ID specified does not exist or is

not valid.
DESCRIPTION:
SNAPA was unable to find the LUN ID specified. Please check

that the ID is valid and operational.
ACTION:
* Check if the LUN ID is valid.

* Create a LUN with the specified ID.
* Check if the LUN ID is visible to the host.
MESSAGE:
[227:2103] The parent LUN ID specified does not exist or is

not a valid parent object.
DESCRIPTION:
SNAPA was unable to find the parent with the specified

LUN ID. Either the parent does not exist or the LUN ID is not
be valid.
ACTION:
* Check to see if the parent LUN exists.

* Check if the parent LUN ID is valid.
MESSAGE:
[227:2104] The device is locked by another application or process.
DESCRIPTION:
SNAPA was unable to access the device properly. The device

is locked by another application or process.
ACTION:
* Release the target device.

* Ensure no other application is accessing the device.
MESSAGE:
[227:2200] An unexpected error occurred.
DESCRIPTION:
The agent has experienced an unexpected error. The array has

returned an unknown state.
ACTION:
* Check the physical devices.

* Check the environment and systems for problems.
* Check SAN environment for proper configuration.
MESSAGE:
[227:2201] An ioctl call returned an unexpected error value.
DESCRIPTION:
SNAPA has received an unexpected error value originating

from an ioctl call.
ACTION:
* Check the SCSI configuration

* Check if physical devices are operating properly.
MESSAGE:
[227:2202] A SCSI command returned an unexpected error.
DESCRIPTION:
SNAPA has received an unexpected error value originating

from a SCSI command.
ACTION:

* Check that physical devices are operating properly.
MESSAGE:
[227:2203] An unexpected number of sense bytes were returned.
DESCRIPTION:
SNAPA has received an unexpected number of sense bytes.
ACTION:

* Check that physical devices are operating properly.
MESSAGE:
[227:2250] An unexpected and possibly critical error has occurred.

The array has returned an unknown state. The agent is
unsure how to proceed with the array response.
DESCRIPTION:
SNAPA has experienced an unexpected and critical error.

The array has returned an unknown state. The agent is
unsure how to proceed with the array response.
ACTION:
* Check the physical devices.

* Check the environment and systems for problems.
* Check SAN environment for proper configuration.
MESSAGE:
[227:3000] No configuration detected on the backup system while SNAPA is

instructed to use an existing snapshot.
DESCRIPTION:
====
SNAPA was instructed to use an existing snapshots, and none were
found on the backup system.
ACTION:
=======
* Check that snapshots are created and visible on the backup host.
* Check that an existing snapshot is not a member of the IR for VA
database and available or use.
* Check the SAN environment and Secure Manager setup on the Virtual
Array.
MESSAGE:
[228:103] Failed to initialize access to P6000 EVA Command View (CV).
DESCRIPTION:
P6000 EVA Family reported that it was unable to obtain information from P6000 EVA Command View
(CV).
ACTION:
* Check access to P6000 EVA Command View (CV) with either SSSU or a
Web browser.
* Use the OMNIDBEVA command to set/update P6000 EVA Command View (CV) access information (login).
MESSAGE:
DESCRIPTION:
ACTION:
* Check if there is a filesystem that is not included in the backup, but which uses
a volume from the problematic volume group.
* Manually dismount the filesystems and
try to deactivate the problematic volume group.
MESSAGE:
[228:2000] P6000 EVA Family agent was unable to map the created target volumes to
corresponding character device files on the backup system.
DESCRIPTION:
P6000 EVA Family reported that it was unable to access created target
volumes from the backup system.
ACTION:
* Check the environment for any SAN configuration or control software and
ensure that this software allows correct paths for hardware and resources.
* Check the hardware for equipment failure.
MESSAGE:
[228:2006] Failed to map the character device file p to a corresponding

P6000 EVA Family virtual disk.
(p)
DESCRIPTION:
P6000 EVA Family agent cannot access the source volume through the resolved
character device file.
ACTION:
* Check if the problematic character device file exists

file.
* Check if the character device file is associated with a valid
P6000 EVA Family virtual disk, which resides on a supported
version of the P6000 EVA Family box.
MESSAGE:
[228:2053] Source volumes have existing target volumes of different snapshot types.
This is not supported!
DESCRIPTION:
Source volumes have existing target volumes of different snapshot types.

P6000 EVA Family hardware limitations prevent Data Protector
from making a backup session with the specified options.
ACTION:
* If the type of target volumes that are used in the backup

session is not important to you, then setting the snapshot type policy to LOOSE might solve the
problem.
* Use the OMNIDBEVA tool to find in the replica set any target volumes that
have been replicated from the same source volumes which were used in this
session. Consider deleting these target volumes if their snapshot type
doesn't match your preferred choice.
* If you cannot locate the problematic target volumes within the replica
set, check if some non-Data Protector snapshots are
causing the problem.
Find the source volumes within your P6000 EVA Family environment and
check the type of existing snapshots. Consider deleting any
snapshots of the source volumes that do not match your selected snapshot type.
MESSAGE:
[228:2054] The following source volume has existing target volumes, which do not match
the snapshot type selection:
Virtual disk name: p
P6000 EVA Family name: p
DESCRIPTION:
Source volume has existing target volumes, which do not match the snapshot type
selection. P6000 EVA Family hardware limitations prevent Data Protector
from making a backup session with the specified options.
ACTION:
* If the type of target volumes that are used in the backup

session is not important to you, then setting the snapshot type policy to LOOSE might solve the
problem.
* Use the OMNIDBEVA tool to find in the replica set any target volumes that
have been replicated from the specified source volume. Consider deleting
these target volumes (if you no longer need them).
* If you cannot locate the problematic target volume within the replica set, check if some non-
Data Protector snapshots are causing the
problem.
Find the source volume within your P6000 EVA Family environment and
check the type of existing snapshot. Consider deleting any
snapshots of the source volume that do not match your selected snapshot type.
MESSAGE:
[228:2083] All target volumes have unexpected presentations attached. Aborting session.
DESCRIPTION:
Target volumes cannot be reused until all the presentations are removed.
ACTION:
* Make sure that it is safe to delete the problematic presentations and

use P6000 EVA Command View (CV) to find and delete them.
MESSAGE:
[236:2] Failed to resolve object(s):

p
(p)
DESCRIPTION:
The mapping of the object to physical disks failed. The object

will not be backed up.
ACTION:
* If the problematic object is a directory, then check

if it is created on both application and backup system.
* If the problematic object is a logical volume (rvol), then

check if the volume group is correctly imported on the
backup system.
MESSAGE:
[236:14] p mirror of the logical volume \'p\'

has its members in the arrays of the primary mirror.
Physical Volume Group: p.
Array IDs of the primary mirror p.
DESCRIPTION:
For higher availability it is recommended to use non-primary

mirrors in arrays other than the primary mirror.
ACTION:
MESSAGE:
[236:21] An associated filesystem has been detected that is not selected for backup.
Volume name: p
Mount point: p
DESCRIPTION:
The associated filesystem will be replicated within this session because

it resides on the same disks as objects that have been selected for backup.
The data on this filesystem may be replicated inconsistently.
ACTION:
* Reconfigure your environment so that the filesystems that should not be replicated
do not reside on the same disks as the filesystems selected for backup.
MESSAGE:
[236:26] A filesystem is not mounted on the expected mount point.

Volume name: p
Expected mount point: p
DESCRIPTION:
Filesystem configuration has changed.
ACTION:
* Check the reason of filesystem configuration change.

* Alternatively you may rerun the IR session with configuration check option disabled.
MESSAGE:
[236:28] An additional associated filesystem has been detected.

Volume name: p
Mount point: p
DESCRIPTION:
Filesystem configuration includes an additional filesystem that had not

been selected within the backup.
ACTION:
* Check the reason for filesystem configuration change.

* Alternatively you may rerun the IR session with configuration check option disabled.
MESSAGE:
[236:32] An associated volume group has been detected that is not selected for backup.
Volume group name: p
DESCRIPTION:
The associated volume group will be replicated within this session because
it resides on the same disks as objects that have been selected for backup.
The data on this volume group may be replicated inconsistently.
ACTION:
* Reconfigure your environment so that the volume groups that should not be replicated
do not reside on the same disks as the objects selected for backup.
MESSAGE:
[236:34] Volume group residing on one of selected storage volumes is spanning to another
storage volume which is not selected within the backup specification.
DESCRIPTION:
Minimal set of data that can be backed up with SMIS agent is a storage volume. In
the current backup specification, one of the volume groups residing on specified storage volume
is spanning to another storage volume which is not included. If a backup is performed,
this volume group would not be in a consistent state and could produce data loss at Instant
Recovery time.
ACTION:
* Reconfigure your backup specification to include all the associated volume groups and
their storage volumes.
* Disable Instant Recovery option.
MESSAGE:
[236:35] Resolving of device file p has failed.

(p)
DESCRIPTION:
Unrecognized device file.
ACTION:
* Verify if all objects in Backup Specification reside on EVA/3PAR disks.
MESSAGE:
[236:51] Failed to resolve a storage volume on the host.

Storage volume: p
DESCRIPTION:
This storage volume was presented to the host but the system did not
recognize the presentation.
ACTION:
* Verify that the host is properly configured within the P6000 EVA Family provider.
* Set the OMNIRC ZDB_DELAY_AFTER_RESCAN environment variable to increase the
wait period for the system to become aware of the new presentations.
* Set the OMNIRC ZDB_DELAY_BEFORE_RESCAN environment variable to an
appropriate wait time between creation of presentations and initiation
of disk rescan on the host.
MESSAGE:
[236:52] Failed to resolve a storage volume on the host.

Storage volume: p
DESCRIPTION:
This storage volume was presented to the host but the system did not
recognize the presentation.
ACTION:
* Verify that the host is properly configured within the P6000 EVA Family provider.
MESSAGE:
[236:53] Failed to resolve filesystems tied to this physical drive.

Physical drive: p
DESCRIPTION:
A storage volume was presented to this host and it was assigned this
physical drive number. However, no filesystem information from it
has been recognized by the operating system.
ACTION:
* Set the OMNIRC ZDB_DELAY_AFTER_RESCAN environment variable to increase the

wait period for the system to become fully aware of the new presentations.
MESSAGE:
[236:54] Multisnap ZDB sessions can only involve one P6000 EVA Family unit.
DESCRIPTION:
Multisnap creation of replicas for all source disks used in the session can
only be performed on the same disk array.
Multisnap functionality is required since either Oracle ASM ZDB session is in
progress or multisnapping is enforced with the SMISA_ENFORCE_MULTISNAP
omnirc variable.
ACTION:
MESSAGE:
[236:55] Multisnap functionality is not supported by the P6000 EVA Family unit.
DESCRIPTION:
Multisnap functionality is not supported either by the firmware revision or the

Command View version of the P6000 EVA Family unit.
omnirc variable.
ACTION:
MESSAGE:
[236:56] Maximum number of virtual disks used in the multisnap session exceeded.
DESCRIPTION:
Replica creation for all source disks used in the session cannot be performed
with one multisnap operation.
omnirc variable.
ACTION:
MESSAGE:
[236:57] Multisnap ZDB sessions can only involve one HP 3PAR unit.
DESCRIPTION:
Multisnap creation of replicas for all source disks used in the session can
only be performed on the same disk array.
Multisnap functionality is required since Oracle ASM ZDB session is in
progress.
ACTION:
MESSAGE:
[236:2003] A filesystem could not be mounted.

Filesystem name : p
Mount point : p
Error description : p
DESCRIPTION:
This can happen if target mount point already exists on Backup host.
This can occur if Use the same mountpoints as on application system option is selected or
if hostname is selected under Add directories to the mount path.
ACTION:
* Select the option Automatically dismount file systems at destination mountpoints or

* change backup specification to use different mount points in each session.
MESSAGE:
[236:2004] A filesystem could not be dismounted.

Filesystem name : p
Mount point : p
Error description : p
DESCRIPTION:
A process has opened a handle to an object from the filesystem to be dismounted.
ACTION:
* Identify the process and make sure it will release the handle.
* If this is a Windows Server 2008 system you can use omnirc variable
SMISA_FORCE_DISMOUNT to enable force dismounting of volumes.
MESSAGE:
[236:2010] The target mount-point folder could not be created.

Mount-point folder: p
Error description: p
DESCRIPTION:
This error may occur if no volume on which the target mount-point folder
should be created is mounted to the root directory specified in the option
Root of the mount path on the backup system.
ACTION:
* Change your zero downtime backup specification to use a different target mount-point.
* Manually create the target mount-point at the desired location and
run the zero downtime backup session again.
MESSAGE:
[236:2013] The HP P6000 EVA / HP 3PAR SMI-S agent

failed to enable automatic mounting of new volumes on the operating system.
DESCRIPTION:
The HP P6000 EVA / HP 3PAR SMI-S agent disabled

Automatic mounting of new volumes on the operating system before replica presentation.
ACTION:
* No action needed.
* Enable the operating system option: Automatic mounting of new volumes In Command Prompt window,
run the command: mountvol /E.
MESSAGE:
[236:2014] The HP P6000 EVA / HP 3PAR SMI-S agent

failed to disable Automatic mounting of new volumes on the operating system.
DESCRIPTION:
The HP P6000 EVA / HP 3PAR SMI-S agent

does not support Automatic mounting of new volumes on the operating system.
ACTION:
* Disable the operating system option: Automatic mounting of new volumes In Command Prompt
window, run the command: mountvol /N.
MESSAGE:
[236:2101] Waiting for the following resources to be released:p
DESCRIPTION:
Specific resources can only be manipulated by one Data Protector

agent at a time. Another agent has exclusively locked
at least one of the listed resources. This agent must
wait until the other agent releases the lock.
ACTION:
No action is required. The agent will continue normal operation

once the lock on the requested resources is successfully obtained.
MESSAGE:
[236:2504] Disk p is resolved as p (unsupported type).
DESCRIPTION:
The SMIS agent does not support Dynamic or GPT disks.
ACTION:
* Do not use Dynamic or GPT disks in the backup specification.
MESSAGE:
DESCRIPTION:
Data Protector cannot open the register of

mounted filesystems. The error message indicates
the reason as reported by the operating system.
ACTION:

exists on the system.
* Check permissions of the mount table (file /etc/mnttab on
HP-UX systems).
* Consult your local system administrator about

MESSAGE:
DESCRIPTION:
ACTION:
* Check if there is a filesystem that is not included in the backup,

but which uses a volume from the problematic volume group.
* Manually split disks, dismount the filesystems and try to deactivate
the problematic volume group.
MESSAGE:
[236:3501] Failed to read p file. Mapping of all logical volumes on backup host will fail.
(p)
DESCRIPTION:
The Data Protector agent reads the /etc/lvmtab to

get the information needed for resolving the name of the volume
groups on the backup system. Since this file could not be read,
the mapping operation failed.
ACTION:
exists on the system and can be accessed.
* Consult you local system administrator about
MESSAGE:
[236:4016] An unsupported combination of options for ZDB preview has been passed to the
P6000 EVA SMI-S agent. Preview will be aborted.
DESCRIPTION:
Preview of ZDB session combined with tape backup is not currently supported.
ACTION:
1) Start a 'disk only' preview session for the same backup specification.
In this way you will be able to run the ZDB part of session preview.
2) Create a backup specification with the same media device as in the ZDB session.
Add a dummy file from the backup host to this backup specification.
Run the preview session of this backup specification.
In this way you will be able to run the tape backup part of session preview.
MESSAGE:
[236:4039] The following storage volumes have been presented to some host
and will not be removed from the ZDB database:
p
DESCRIPTION:
Target volumes marked for purge are still presented.
ACTION:
1) Manually remove presentations for listed target volumes using the

P6000 EVA Family GUI or CLI tools.
2) Use the Data Protector CLI interface to run purge with

the force option enabled:
omnidbsmis -purge -force
MESSAGE:
[236:4080] The following sessions are excluded from use by the agent:
p
DESCRIPTION:
The listed sessions are excluded from use by the agent.

The disks created in these sessions will not be deleted.
ACTION:
* To include a session into use by the agent use the

"omnidbsmis|omnidbzdb -include -session" command.
MESSAGE:
[236:4081] The session p is excluded from use by the agent.
DESCRIPTION:
Excluded sessions cannot be used in instant recovery.
ACTION:
* To include a session into use by the agent use the

"omnidbsmis -include -session" command.
MESSAGE:
[236:4103] Changing of the write cache policy has not finished yet.
Proceeding with the session.
DESCRIPTION:
Agent changed the write cache policy on some storage volumes.

This is a long lasting operation and can take some time.
Agent reached the maximum number of retries
while waiting for the operation to complete.
ACTION:
* To change the total number of times that agent will check for status of
this operation and containers creation/allocation,
set next omnirc variable:
SMISA_BACKUPPREPARE_RETRY
* To change the time between two status checks, set next omnirc variable:
SMISA_BACKUPPREPARE_DELAY
* To change the time between two status update messages, set next omnirc variable:
SMISA_MSGWAITING_INTERVAL
MESSAGE:
[236:4108] Container creation has not finished yet. Proceeding with the session.
DESCRIPTION:
Creation of container is a long lasting operation and can take some time.
ACTION:
* To change the total number of times the agent checks the status of
this operation and the write cache policy change to complete,
set next omnirc variable:
SMISA_BACKUPPREPARE_RETRY
* To change the time between two status checks, set next omnirc variable:
SMISA_BACKUPPREPARE_DELAY
MESSAGE:
[236:4109] Container creation has not finished yet. Proceeding with the session.
DESCRIPTION:
Creation of container is a long lasting operation and can take some time.
ACTION:
* To change the number of times that agent will check for creation completion,
set next omnirc variable: SMISA_CONTAINERCREATION_RETRY
* To change the time between two checks set next omnirc variable:
SMISA_CONTAINERCREATION_DELAY
MESSAGE:
[236:4113] Clone creation/normalization has not finished yet.

DESCRIPTION:
Creation/normalization of clones is a long lasting operation and can take some time.
Agent will wait until creation is complete or
until it reaches the maximum time that it should wait before it proceeds.
ACTION:
* To change the maximum allowed time that agent will wait for the clone
creation to be done, change your backup specification
* To change the time between two status checks set next omnirc variable:
EVA_CLONECREATION_QUERY_INTERVAL
EVA_MSGWAITING_INTERVAL
MESSAGE:
[236:4118] Deletion of storage volumes has not finished yet. Proceeding with the session.
DESCRIPTION:
Deletion of storage volumes is a long lasting operation and can take some time.
Agent will wait until deletion is completed or
ACTION:
* To change the maximum allowed time that agent will wait for the deletion to complete,
set next omnirc variable: EVA_DELETEREPLICA_QUERY_TIMEOUT
EVA_DELETEREPLICA_QUERY_INTERVAL
MESSAGE:
[236:4128] Restore from replica has not finished yet.

DESCRIPTION:
Restore from replicas is long lasting operatiosn and can take some time.
Agent will wait until restore from replicas is complete or
ACTION:
* To change the maximum allowed time that agent will wait for the restore
from replicas to be done, change your backup specification
3PAR_COPYBACKSTS_QUERY_INTERVAL
3PAR_MSGWAITING_INTERVAL
MESSAGE:
[236:4131] The Snapshot Policy LOOSE is not supported anymore. The Snapshot Policy STRICT is used
instead.
DESCRIPTION:
The Snapshot Policy LOOSE is obsolete with this release. This warning is generated
if the backup specification contains the Snapshot Policy LOOSE. The policy
will be automatically changed to STRICT. Please note, the backup specification
itself will not be changed. Please see the action section how to change it.
ACTION:
To change the backup specification execute the following steps:

* Open the backup specification in Data Protector
* Change a property in the backup specification
* Save the backup specification (click Apply)
The LOOSE policy option will be removed from the backup specification. In the
next run, the warning will not be printed again.
MESSAGE:
[236:4140] At least one object failed resolve phase.

Session will not continue as it would fail at later time.
DESCRIPTION:
At least one object failed to be resolved by the agent. The session will not
continue as disk only sessions need to be successful for all objects.
ACTION:
* Verify if all objects are mounted to mountpoints provided in backup specification.

* Verify if all objects are P6000 EVA Family disks.
MESSAGE:
[236:4510] Target object p is presented.
DESCRIPTION:
Target disk is presented to some hosts. Since option "Force removal of all
replica storage presentations" has not been selected, this object cannot be
restored.
ACTION:
* Manually remove all presentations for this object using hp OpenView Storage
Management Appliance.
* Restart IR session with option "Force removal of all replica storage
presentations" selected.
MESSAGE:
[236:4511] Skipping preparation of the application system!
DESCRIPTION:

application system, therefore Data Protector assumed that the
application system has been manually prepared for Instant Recovery. Manual
preparation includes dismounting of the target filesystems and disabling
the target volume groups.
Even when the application system has not been prepared, the instant recovery
may still be successful. In this case you need to disable and re-enable the
application data after the instant recovery.
ACTION:
* Verify that the application filesystems are dismounted and the corresponding
volume groups disabled.
* In case they are not, dismount the filesystems and disable volume groups
after the instant recovery and then enable volume groups and mount filesystems.
MESSAGE:
[236:4512] Skipping resume of the application system!
DESCRIPTION:

application system, therefore the application system configuration must be
resumed manually after the Instant Recovery.
ACTION:
* Enable the volume groups where the restored filesystems are configured.
* Mount the restored filesystems.
MESSAGE:
[236:4526] At least one of the target storage volumes is presented to a different

system than 'p'.
DESCRIPTION:
At least one of the target disks is presented to at least one different host
than the one P6000 EVA SMI-S agent was started on. The agent cannot
safely clean up the presentations to other hosts.
ACTION:
* Manually remove the target disks from use on the other hosts and remove
the presentations to them using hp OpenView Storage Management Appliance.
* Repeat the action with the option "Force removal of all replica storage
MESSAGE:
[236:4528] At least one of the target storage volumes has at least one presentation
to a host.
DESCRIPTION:
At least one of the target disks is presented to at least one host. 3PAR
instant recovery from a target disk is not possible if the target disk
is presented to any host.
ACTION:
* Manually remove the target disks from use on the hosts and remove
the presentations to them using HP 3PAR Management Console.
MESSAGE:
[236:4530] During this session, actions were taken to perform the instant recovery
which may have resulted in changes to some storage volumes. The storage
volumes are the application system volumes for which the instant recovery
was requested.
DESCRIPTION:
During the attempted instant recovery, some changes were made to storage volumes
involved in the instant recovery on the application system. However, some issue
or environment problem prevented the P6000 EVA SMI-S agent from completely
returning the application environment to the state prior to the attempted instant
recovery. These issues may be network-related or tied to instability of the P6000 EVA SMI-S
provider or the system where that provider is running. These changes may be
irrecoverable or may allow reconfiguration of the environment to return the
application system to its original state.
ACTION:
* If the restore options chosen were to copy data back to the source location and
to not retain the source for forensics, storage volumes were most likely converted
to containers and have their data contents copied from restore storage volumes.
In this scenario, be advised that the original application data contents on these
volumes no longer exist.
* Likewise, if application storage volumes are now in the container state, the
P6000 EVA Family CLI or GUI tools may be used to create a snapclone into
that container. After this action, an instant recovery may be started again, but
the option to check the data configuration consistency may need to be deselected.
* If the restore options chosen was to switch to the replica or the combination of
the options of copy data back to the source location and to retain the source for
forensics, the identities of the source storage volumes may not be consistent with
the identities prior to the restore. Using session output, please verify that
each storage volume with a specific UUID also has the correct WWN and comment.
After this action, an instant recovery may be started again.
MESSAGE:
[236:4536] A cluster resource failed to leave maintenance mode.

Cluster resource : p
DESCRIPTION:
The maintenance mode on a disk resource within the cluster creates an

exclusive lock for an application.
ACTION:
In order to allow other clients to access the disk resource, the maintenance
mode must be removed. This can be done manually using the cluster.exe command-line
tool.
cluster res "<cluster resource name>" /extmaint:0
cluster res "<cluster resource name>" /maint:0
MESSAGE:
[236:4557] An omnirc variable was set to enable replica creation in a non-multisnap operation
(unsupported by Oracle ASM).
DESCRIPTION:
If multisnap replica creation does not succeed, target volumes will

be created sequentially. This behavior is enabled with the omnirc variable
SMISA_ALLOW_NONMULTISNAP_ASM_ZDB. Note that it may result in an inconsistent
Oracle ASM disk group backup.
ACTION:
MESSAGE:
[236:4700] At least one of the replica is presented to a system. Instant recovery is not
possible.
DESCRIPTION:
Instant recovery session can only be run for replicas which are not presented to any system.
ACTION:
* Run the instant recovery session again using the Data Protector omnir command.
In the omnir command line, specify the -force option to remove target volume presentations.
MESSAGE:
[236:5002] Split links pre-exec command failed with exit code num.
DESCRIPTION:
The split pre-exec command failed (for example failed to prepare the
environment for split).
ACTION:

for possible bugs.
MESSAGE:
[236:5005] Split post-exec script failed with exit code num.
DESCRIPTION:
The split post-exec script failed (for example failed to restart stopped
processes).
ACTION:

for possible bugs.
MESSAGE:
[236:5006] Cleanup on host p has failed.
DESCRIPTION:
Cleanup on host has failed. Since option "Force removal of all replica storage
presentations" has not been selected, this object cannot be restored.
ACTION:
* Manually remove the target disks from use on this host and remove
the presentations to it using hp OpenView Storage Management Appliance.
MESSAGE:
[236:6000] Cannot connect to the cell server.

(p)
DESCRIPTION:
The P6000 EVA SMI-S agent failed to connect to the Cell Manager
system and retrieve the configuration data.
ACTION:
* Use the Data Protector GUI to verify if the administrator user

of the backup system is specified as an administrator or operator on the
backup cell.
* Add an administrator user of the backup system as the
Data Protector backup cell administrator or operator users.
MESSAGE:
[236:6004] Found a source volume that is already logged as a target volume:

Session ID: p
Target volume name: p
The source volume will be excluded from the ZDB session.
DESCRIPTION:
Using Data Protector-created target volumes as source volumes

while still under Data Protector's IR-management is illegal.
ACTION:
* Remove the old backup session by running:

omnidbsmis -delete <sessionID>
* Modify the backup specification so the target volume will not be included.
MESSAGE:
[236:6006] A snapshot for the mirrorclone exists in the database:

Session ID: p
Storage volume name: p
DESCRIPTION:
The mirrorclone cannot be removed if there are snapshots attached to it.
ACTION:
* Use the following Data Protector command to remove the snapshot created with this session:
omnidbsmis -delete <sessionID>
MESSAGE:
[236:6050] Syntax error detected at the line num in the disk group pair settings.
DESCRIPTION:
The error occurred while parsing the stored disk group pair settings.
This may lead to unwanted behavior where the snapclones are not created
inside of the desired disk-groups.
ACTION:
1) Download the stored disk group pair settings:

omnidbsmis -dgrules -get C:\DG_FILE.txt
2) Using a text-editor of your choice, check and edit the disk group pair
settings file:
notepad C:\DG_FILE.txt
3) Upload the disk group pair settings back to the Cell Manager system:
omnidbsmis -dgrules -put C:\DG_FILE.txt
Alternately, you may want to overwrite the content with the pre-defined
template:
omnidbsmis -dgrules -init
MESSAGE:
[236:6051] Syntax error detected at the line num in the CA Configuration settings.
DESCRIPTION:
The error occurred while parsing the stored DR Configuration settings.
ACTION:
1) Download the stored CA Configuration settings:

omnidbsmis -caconf -get C:\CACONF_FILE.txt
2) Using a text-editor of your choice, check and edit the CA Configuration

settings file:
notepad C:\CACONF_FILE.txt
3) Upload the CA Configuration settings back to the Cell Manager system:

omnidbsmis -CAconf -put C:\CACONF_FILE.txt
template:
omnidbsmis -caconf -init
MESSAGE:
[236:6052] Syntax error detected in the CA Configuration settings.
DESCRIPTION:
The error occurred while parsing the stored DR Configuration settings.
ACTION:
1) Download the stored CA Configuration settings:

omnidbsmis -caconf -get C:\CACONF_FILE.txt
2) Using a text-editor of your choice, check and edit the CA Configuration

settings file:
notepad C:\CACONF_FILE.txt
3) Upload the CA Configuration settings back to the Cell Manager system:

omnidbsmis -CAconf -put C:\CACONF_FILE.txt
template:
omnidbsmis -caconf -init
MESSAGE:
[236:7002] A P6000 EVA SMI-S provider did not respond correctly.

The entered configuration is:
Host machine: p
Host port : num
User name : p
Namespace : p
DESCRIPTION:
The P6000 EVA SMI-S agent communicates to a P6000 EVA SMI-S

provider in order to manipulate P6000 EVA Family units. However, a configured
provider did not respond in a timely or correct fashion.
ACTION:
* Check that all P6000 EVA SMI-S providers are running and operating
correctly.
* Double check the configuration of this provider within the ZDB database.
If this information is incorrect, it should be removed from the ZDB
database and re-entered.
MESSAGE:
[236:7005] Failed to load shared library p
DESCRIPTION:
There is no SMISA agent installed for the specific array which is used.
ACTION:
* Check whether the agent for the array is installed.

* Install the agent using the Data Protector installation wizard.
* Configure the agent using the agent specific CLI.
MESSAGE:
[236:7051] The ZDB database does not contain any valid P6000 EVA SMI-S
provider information.
DESCRIPTION:
There are no P6000 EVA SMI-S provider entries configured within

the ZDB database.
ACTION:
* List the P6000 EVA SMI-S provider entries in the ZDB database using:
omnidbsmis -ompasswd
* Add a provider entry to the ZDB database using:
omnidbsmis -ompasswd -add <hostname> ...
MESSAGE:
[236:7103] The resolve of this storage volume has failed.
DESCRIPTION:
The P6000 EVA SMI-S agent was unable to locate the storage volume
on any P6000 EVA Family unit. The P6000 EVA SMI-S providers
that were queried did not contain valid information regarding this storage
volume.
ACTION:
correctly.
* Ensure that all appropriate P6000 EVA SMI-S providers have been
configured.
* Double check the configuration of each provider within the ZDB database.
If this information is incorrect, it should be removed from the ZDB
database and re-entered.
* Ensure that this storage volume has not been deleted outside of the control
of the P6000 EVA SMI-S agent. An inconsistency between the ZDB
database and the actual storage volumes on the P6000 EVA Family units
will occur in this situation. The Data Protector CLI interface
can be run to verify the situation:
omnidbsmis -sync_check [-host <hostname>]
[-session <session ID> | -datalist <datalist name>]
To delete the reference from the database the following command can be used:
omnidbsmis -delete {-session <session ID> | -datalist <datalist name>}
[-reference] [-preview] [-force] [-host <hostname>]
* Ensure that any P6000 EVA Family units are operational.
* Check storage area network (SAN) configuration and status. A faulty or
improperly configured SAN may produce unpredictable results.
MESSAGE:
[236:7106] Multiple storage volumes have been detected with the same WWN.
P6000 EVA Family name : p
Storage volume WWN : p
Matching storage volumes :

p
DESCRIPTION:
Multiple storage volumes sharing the same WWN have been discovered
on the P6000 EVA Family. The agent cannot determine which
storage volume should be used in this session.
ACTION:
Manually change the WWN of the conflicting storage volumes.
MESSAGE:
[236:7120] There are 7 target volumes attached to a source volume. This may
prevent the creation of another target volume for:
Storage volume name : p
DESCRIPTION:
P6000 EVA Family hardware limitations currently allow a maximum of
7 full-allocated or demand-allocated snapshots to be attached to a storage

volume. This maximum has been reached.
ACTION:
* Manually remove any unneeded snapshots that are outside of Data Protector
control, using the P6000 EVA Family GUI or CLI tools.
* Use the Data Protector CLI interface to remove one or
more unneeded sessions that contain target volumes:
omnidbsmis -delete -session <session ID> [-preview] [-force] [-host]
* If any target volumes exist within the purge portion of the ZDB database, use the
Data Protector CLI interface to run purge:
omnidbsmis [-list] -purge [-force] [-host]
MESSAGE:
[236:7122] No P6000 EVA SMI-S provider has been found that would manage
a P6000 EVA Family unit with the WWN returned by SCSI inquiry.
P6000 EVA Family WWN : p
DESCRIPTION:
The P6000 EVA SMI-S agent communicates to a P6000 EVA SMI-S

provider in order to manipulate P6000 EVA Family units. However, no configured
provider manages a P6000 EVA Family unit with the specified WWN.
ACTION:
* Check that the configured P6000 EVA SMI-S providers are running
and operating correctly.
* Check that the required P6000 EVA SMI-S provider has been
configured correctly. If this information is incorrect, it should be
removed from the ZDB database and re-entered.
MESSAGE:
[236:7153] P6000 EVA SMI-S has failed to create a target volume for:
Source volume name : p
DESCRIPTION:
A snapshot or snapclone could not be created for the specified source

volume.
ACTION:
* Check the P6000 EVA Family environment to ensure that sufficient disk
space for target volumes is available.
* Check the P6000 EVA Family environment to ensure that the maximum
number of snapshots for a specific storage volume has not been reached.
MESSAGE:
Source volume name : p
Please delete the target volume if it exists.
Target storage volume : p
DESCRIPTION:
A snapshot or snapclone could not be created for the specified source volume due to communication
issueswith P6000 EVA SMI-S provider.
ACTION:
* Please rerun the backup.
MESSAGE:
[236:7191] The following storage volume currently has a synchronization relationship

with another storage volume.
Storage volume : p
DESCRIPTION:
The storage volume will not be able to be converted into a storage container.
This will prevent the restore attempt from being successful.
ACTION:
* Check the P6000 EVA Family environment to ensure that the specific
storage volume does not have any fully-allocated or demand-allocated
snapshots attached to it.
* Check that the specific storage volume is not involved in any snapclone
normalization process. If so, wait until this process is complete
before attempting another restore with this storage volume.
MESSAGE:
[236:7201] An attempt to delete a storage volume has returned an error.
DESCRIPTION:
An existing storage volume could not be successfully deleted.
ACTION:
* Using the P6000 EVA Family GUI or CLI tools, check that the storage volume
does not have any snapshots or snapclones currently attached to it. This will
prevent deletion.
MESSAGE:
[236:7210] BC license not available
DESCRIPTION:
The array must have a local replication license.
ACTION:
MESSAGE:
[236:7213] Redundancy Less than Or Equal to Parent required
DESCRIPTION:
The redundancy (Vraid) level of a mirrorclone can be the same,

lower, or higher than the source.
ACTION:
MESSAGE:
[236:7214] Different Allocation Policy is already in Use
DESCRIPTION:
All snapshots of the same virtual disk must be the same type
(demand allocated or fully allocated) and redundancy (Vraid) level.
ACTION:
MESSAGE:
[236:7215] Snapshot creation is Not Supported on Snapshot
DESCRIPTION:
Snapshots cannot be created when the disk to be replicated is a snapshot
ACTION:
MESSAGE:
[236:7216] Mirror clone or Snapshot already exists
DESCRIPTION:
The maximum number of mirrorclones per source is one.

A mirrorclone cannot be created if the intended source virtual disk:
* is a snapshot or has any snapshots.
* Has any snapclones that are in the process of being normalized.
ACTION:
MESSAGE:
[236:7218] Error creating replica
DESCRIPTION:
There was error at target creation
ACTION:
correctly.
space for target volumes is available.
* Check the P6000 EVA Family environment to ensure that the maximum number
of replicas for a specific storage volume has not been reached.
MESSAGE:
[236:7255] A presentation cannot be created. No host objects were found in the

P6000 EVA Family unit that match the backup host.
DESCRIPTION:
P6000 EVA SMI-S agent creates a presentation of a storage

volume to a specific host. However, the agent could not match the current
host to a host object within a P6000 EVA Family unit.
ACTION:
* Check the P6000 EVA Family environment to ensure that there is a valid
host object for the current host.
* Using the OMNIRC variable EVA_HOSTNAMEALIASES, redirect the host name into
a valid host object within a P6000 EVA Family unit.
MESSAGE:
[236:7301] The snapshot type is being switched from fully-allocated to demand-allocated

snapshots.
DESCRIPTION:
One or more source storage volumes have demand-allocated snapshots

attached to them. The snapshot policy of LOOSE allows the session's
snapshot type to be changed to match this. Demand-allocated snapshots
will now be created.
ACTION:
* If the type of target volume created is not important, the snapshot

type may be changed to demand-allocated.
* If the type of target volume created is important, the snapshot policy
should be changed to STRICT to ensure that only fully-allocated snapshots
will be made.
* Existing demand-allocated snapshots attached to the source volume may
be deleted. Unneeded snapshots that are outside of Data Protector
control may be deleted using the P6000 EVA Family GUI or CLI tools.
The Data Protector CLI interface may also be used to remove
one or more unneeded sessions that contain the target volumes.
MESSAGE:
[236:7302] The snapshot type is being switched from demand-allocated to fully-allocated

snapshots.
DESCRIPTION:
One or more source storage volumes have fully-allocated snapshots

snapshot type to be changed to match this. Fully-allocated snapshots
ACTION:

type may be changed to fully-allocated.
should be changed to STRICT to ensure that only demand-allocated snapshots
will be made.
* Existing fully-allocated snapshots attached to the source volume may
MESSAGE:
[236:7304] One or more source volumes have demand-allocated snapshots already attached.
Fully-allocated snapshots may not be created.
DESCRIPTION:
Demand-allocated snapshots exist whose source is one or more of the

storage volumes involved in this session. A snapshot policy of STRICT
prevents the snapshot type from being changed to match this.
ACTION:
* If the type of target volume created is not important, the snapshot policy
may be changed to LOOSE to allow the P6000 EVA SMI-S agent
to adjust the snapshot type to match existing target volumes.
* If the type of target volume created is not important, the snapshot type
may be changed to demand-allocated snapshots to match the existing style
of target volumes.
MESSAGE:
[236:7305] One or more source volumes have fully-allocated snapshots already attached.
Demand-allocated snapshots may not be created.
DESCRIPTION:
Fully-allocated snapshots exist whose source is one or more of the storage

volumes involved in this session. A snapshot policy of STRICT prevents
the snapshot type from being changed to match this.
ACTION:
may be changed to fully-allocated snapshots to match the existing style
of target volumes.
MESSAGE:
[236:7306] Demand-allocated and fully-allocated snapshots are already attached to several of

the source volumes.
DESCRIPTION:
Both fully-allocated snapshots and demand-allocated snapshots exist

whose source are some of the storage volumes involved in this session.
Only one snapshot type may be used within a session.
ACTION:
1) Choose whether fully-allocated or demand-allocated snapshots are the

desired snapshot type and adjust the policy within the backup specification.
2) Existing snapshots that conflict with this choice and are attached to
the source volume may be deleted. Unneeded snapshots that are outside
of Data Protector control may be deleted using the
P6000 EVA Family GUI or CLI tools. The Data Protector
CLI interface may also be used to remove one or more unneeded sessions
that contain the target volumes.
MESSAGE:
[236:7312] A disk group redirection has been defined, but the specified disk group
target could not be located. The storage volume, the P6000 EVA Family
unit, and the current disk group name are:
Storage volume name : p
P6000 EVA Family unit name : p
Target disk group : p
DESCRIPTION:
A set of disk group rules have been configured. However, the specified
configuration is not valid. The disk group being redirected to could not
be located within the P6000 EVA Family.
ACTION:
* Check the disk group rules to ensure that a valid configuration has been
entered.
* Check the P6000 EVA Family unit to ensure that the disk group being
redirected to does exist.
MESSAGE:
[236:7320] The snapshot type is being switched from snapclone to fully-allocated

snapshots.
DESCRIPTION:
One or more source storage volumes have fully-allocated snapshots

snapshot type to be changed to match this. Fully-allocated snapshots
ACTION:

type may be changed to fully-allocated.
should be changed to STRICT to ensure that only snapclones will be made.
MESSAGE:
[236:7321] One or more source volumes have fully-allocated snapshots already attached.
Snapclones may not be created.
DESCRIPTION:
Fully-allocated snapshots exist whose source is one or more of the

ACTION:
may be changed to fully-allocated snapshots to match the existing style
of target volumes.
MESSAGE:
[236:7322] The snapshot type is being switched from snapclone to demand-allocated

snapshots.
DESCRIPTION:
One or more source storage volumes have demand-allocated snapshots

snapshot type to be changed to match this. Demand-allocated snapshots
ACTION:

type may be changed to demand-allocated.
should be changed to STRICT to ensure that only snapclones will be made.
MESSAGE:
[236:7323] One or more source volumes have demand-allocated snapshots already attached.
Snapclones may not be created.
DESCRIPTION:
Demand-allocated snapshots exist whose source is one or more of the

ACTION:
may be changed to demand-allocated snapshots to match the existing style
of target volumes.
MESSAGE:
[236:7341] Host objects could not be resolved for this P6000 EVA Family.
P6000 EVA Family Name: p
P6000 EVA Family WWN: p
DESCRIPTION:
P6000 EVA SMI-S agent creates a presentation of a storage volume

to a specific host. However, for this specific P6000 EVA SMI-S,
the agent could not locate any host objects. Creating presentations to the
backup host for any created copies will not be possible.
ACTION:
* Check the P6000 EVA Family environment to ensure that valid host objects,
for the current backup host, are configured.
* Check that any P6000 EVA SMI-S providers are running and operating
correctly.
MESSAGE:
[236:7342] A host object that matches the backup host does not appear to be configured
for this P6000 EVA Family.
P6000 EVA Family Name: p
P6000 EVA Family WWN: p
DESCRIPTION:
P6000 EVA SMI-S agent creates a presentation of a storage volume

to a specific host. However, for this specific P6000 EVA SMI-S,
the agent could not locate a host object that matched the backup host. Creating
presentations to the backup host for any created copies will not be possible.
ACTION:
* Check the P6000 EVA Family environment to ensure that a host object for
the current backup host is configured.

* Modify the OMNIRC file on the backup host, using the variable EVA_HOSTNAMEALIASES
to define a set of aliases for the backup host. This set of aliases will also be
used to match host objects on a P6000 EVA Family unit.
* Check that any P6000 EVA SMI-S providers are running and operating
correctly.
MESSAGE:
[236:7352] A disk group redirection has been defined, but the specified target disk
group could not be located. The P6000 EVA Family unit, tsource
disk group name, and the unresolved target disk group are:
P6000 EVA Family : p
Source disk group : p
DESCRIPTION:
A set of disk group rules have been configured, but the specified configuration
does not appear to be valid. The disk group being redirected to could not be
located within the P6000 EVA Family. As a result, disk group redirection
could not be performed.
ACTION:
correctly.
* Check the P6000 EVA Family unit to ensure that the disk group being
redirected to does exist.
* Check the disk group rules to ensure that a valid configuration has been entered.
Care must be taken in that disk group names within the P6000 EVA Family are
case sensitive. For example, both "FATA" and "fata" refer to different disk groups.
MESSAGE:
[236:7381] This storage volume has one or more replicas attached, which have a vraid level
different from the vraid level specified in the backup specification. The vraid
level of the replica that will be created, will automatically match this existing vraid level.
Source storage volume : p
Existing replica vraid : p
DESCRIPTION:
A specific vraid level has been selected in the backup specification. However,
one or more replicas already exist that have a vraid level different from the one
that is specified. Any additional replicas from this storage volume must have the
same vraid level as existing replicas.
ACTION:
* Check the backup configuration to ensure that an appropriate vraid level choice
has been selected.
* If vraid levels are not considered important, change the vraid level configuration
to the default option.
* If the replica type is not considered important, change the snapshot type to
snapclones. Snapclones based on containers may be of any vraid type.
* If the replicas are not required, remove them from the P6000 EVA Family.
Replicas that are outside of Data Protector control may be deleted

using the P6000 EVA Family GUI or CLI tools. The Data Protector
CLI interface may also be used to remove one or more unneeded sessions that contain
the target volumes.
MESSAGE:
[236:7382] The vraid level specified in the backup specification cannot be used
for a target storage volume based on this source storage volume.
The vraid level generated will match the source storage volume.
Source storage volume vraid : p
Specified vraid : p
DESCRIPTION:
A specific vraid level has been selected in the backup specification. However, a
replica with this vraid level cannot be created from the source storage volume. This
is due to the P6000 EVA Family requirement that a replica may not be based on a
higher redundancy that its source storage volume. The vraid level of the source storage
volume will be used instead of the specified vraid level.
ACTION:
* Check the backup configuration to ensure that an appropriate vraid level choice
has been selected.
* If vraid levels are not considered important, change the vraid level configuration
to the default option.
* If the replica type is not considered important, change the snapshot type to
snapclones. Snapclones based on containers may be of any vraid type.
MESSAGE:
[236:7383] Current P6000 EVA Family configuration does not support Vraid6.
The redundancy level was reverted to Vraid5.
DESCRIPTION:
To be able to use the redundancy level Vraid6, the P6000 EVA Family firmware version
must be XCS 095xxxxx or newer and an enhanced disk group must be used as the
target disk group.
ACTION:
* Create an enhanced disk group and use the Data Protector command omnidbsmis -dgrules to
change the target disk group in the P6000 EVA Family disk group pairs configuration file
accordingly.
* Upgrade the <<<BC_SURESTORE_EVA>> firmware version to XCS 0950xxxx or newer.
MESSAGE:
[236:7436] A storage volume is in a data replication group. Restore is not possible.
DESCRIPTION:
Restore on a storage volume with an active DR group is not possible.
ACTION:
* Delete the data replication group and run instant recovery again.
MESSAGE:
[236:7437] A storage volume is in a data replication group. Restore is not possible.
DESCRIPTION:
Restore on a storage volume with an active DR group is not possible.
ACTION:
* Suspend the data replication group and run instant recovery again.
MESSAGE:
[236:7445] Failed to resolve target storage volume of this data replication group.
Group name: p
Storage volume : p
DESCRIPTION:
The information required to resolve the target storage volume of this Data
Replication group is not available at the P6000 EVA SMI-S provider.
ACTION:
correctly.
* Ensure that source and target P6000 EVA Family are managed by the same
P6000 EVA SMI-S provider.
MESSAGE:
[236:7468] This P6000 EVA SMI-S provider is not currently

responding correctly.
DESCRIPTION:
There is a problem with connecting to the provider.
ACTION:
* Double check the configuration parameters for the failed provider using
omnidbsmis -ompasswd -list command.
Try to reconfigure this provider by running omnidbsmis -ompasswd -add
* Check whether provider is running.

Try to connect to the Command View on this host using the same login/password.
* Check if the user that is running the command has sufficient privileges to connect to the Cell
Server.
MESSAGE:
[236:7469] The following mirrorclones are still synchronizing:

p
DESCRIPTION:
Mirrorclone synchronization for one or more storage volumes did not finish
within expected time frame. The actualized copy of data on mirrorclone is
required for creation of point in time backup.
ACTION:
* Manually synchronize mirrorclone
* Change omnirc variable SMISA_WAIT_MIRRORCLONE_PENDING_TIMEOUT on backup host

to some higher value.
MESSAGE:
[236:7490] The resolve of mirrorclones has failed.
DESCRIPTION:
The resolve of mirrorclone relationships has failed.
ACTION:
* Verify that there are mirrorclones attached to source storage volumes on array.
* Change backup specification to use a non mirrorclone backup.
MESSAGE:
[236:7491] The following mirrorclones are not synchronized with source storage volume:
p
DESCRIPTION:
The backup specification requires that the storage-volume to mirrorclone-relationship

is in a synchronized state.
ACTION:
* Manually resynchronize storage volume to mirrorclone

* Turn on "Synchronize if fractured" option in the backup specification
MESSAGE:
[236:7494] No mirrorclones of the following storage volumes exist on the disk array.
SMI-S Agent will create them automatically.
p
DESCRIPTION:
Mirrorclones were selected for the backup source while no mirrorclones exist
on the disk array for the selected source storage volumes.
SMI-S Agent will create them automatically, and track them in the ZDB database with the label
"Mirrorclone".
ACTION:
To remove the mirrorclones, use the Data Protector omnidbsmis -delete -datalist command.
MESSAGE:
[236:7495] Mirrorclone creation for the following source storage volumes failed:
p
DESCRIPTION:
Snapshots already exist on the disk array for the selected source storage volumes.
ACTION:
* Using P6000 EVA Command View (CV), remove the snapshots from the disk array.
MESSAGE:
[236:7496] Mirrorclone creation failed for the following source volumes:

p
DESCRIPTION:
For the listed source volumes, newly-created snapshots not detected by the Data Protector
HP P6000 EVA SMI-S Agent may exist on the disk array.
ACTION:
* Using P6000 EVA Command View (CV), check if such snapshots exist. If they do, remove them from
the disk array and restart
the zero-downtime backup session.
MESSAGE:
[236:7498] The following mirrorclones cannot be removed as their snapshots exist on the disk
array:
DESCRIPTION:
Mirrorclones cannot be removed if there are snapshots attached to them.
ACTION:
* Snapshot may still be referenced in the ZDB database.

To remove references to such snapshots, use the Data Protector omnidbsmis -purge command.
* Using P6000 EVA Command View (CV), remove the snapshots from the disk array.
* Recently-deleted snapshots may still be detected by the Data Protector
HP P6000 EVA SMI-S Agent.
In this case use the CLIRefreshTool.bat tool to refresh the HP P6000 EVA SMI-S provider cache or
wait
until the cache is refreshed automatically.
MESSAGE:
[236:7499] Mirrorclone session is started with Instant Recovery enabled but P6000 EVA Family
firmware
does not support Instant Recovery from mirrorclone replica.
DESCRIPTION:
Instant Restore from mirrorclone requires firmware version newer then XCS 6.1xx.
ACTION:
* Upgrade firmware to XCS 6.2xx or newer

* Disable the Instant Recovery
* Change backup specification to create backup from source storage volume.
MESSAGE:
DESCRIPTION:
A demand-allocated or fully-allocated snapshot could not be created for the

specified source volume.
ACTION:
MESSAGE:
[236:7511] P6000 EVA SMI-S has failed to create a container that matches the
source storage volume:

DESCRIPTION:
A container could not be created that matches the request characteristics of a

specific storage volume within a specific disk group.
ACTION:
correctly.
MESSAGE:
[236:7512] P6000 EVA SMI-S has failed to create a container that matches the
source storage volume due to the lack of space:
DESCRIPTION:
A container could not be created that matches the request characteristics of a

specific storage volume within a specific disk group.
The reason is that there is not enough space within the target disk group for containers
to be created.
ACTION:
space within the target disk group for containers is available.
MESSAGE:
[236:7523] Replica creation for at least one source disk failed or the replica cannot be created
with a single multisnap operation.
DESCRIPTION:
Replica creation for at least one of the source disks used in the session
failed or cannot be created in one multisnap operation.
omnirc variable.
ACTION:
MESSAGE:
[236:7551] An attempt to delete a storage volume has returned an error.
DESCRIPTION:
An existing storage volume or container could not be successfully

deleted. There may be some issue with contacting the HP P6000 EVA SMI-S
provider, or there may be some issue with the volume itself. A storage
volume will not respond to deletion if it acts as the source for any copy
relationships or if it is still in the process of being allocated on the array.
ACTION:
correctly.
* Using the P6000 EVA Family GUI or CLI tools, check that the storage volume
does not have any snapshots or snapclones currently attached to it. This will
prevent deletion.
* If this storage volume is a container, it may still be in an allocation state. In
this state, it may not be deleted. When this state completes, the following
session will automatically purge it. Alternately, the AppRM CLI interface may
be used to run purge interactively:
omnidbsmis -purge
MESSAGE:
[236:7560] Following storage volume is locked, therefore it cannot be used.

Storage volume name: p
Owner/details of the lock: p
DESCRIPTION:
Lock on a storage volume is preventing SMI-S Agent to successfully complete desired action.
ACTION:
* Using P6000 EVA Command View (CV), remove the lock from the storage volume.
MESSAGE:
[236:7605] This source volume has one or more fully-allocated snapshots already
attached. A demand-allocated snapshots may not be created.
Storage volume : p
DESCRIPTION:
One or more fully-allocated snapshots exist whose source is one of the storage
volumes involved in this session. With current P6000 EVA Family
limitations, a demand-allocated snapshot may not be created for this storage volume.
ACTION:
* Existing fully-allocated snapshots attached to the source volume may be

deleted. Unneeded snapshots that are outside of Data Protector

* If the type of target volume created is flexible, the snapshot type may
be changed to demand-allocated snapshots to match the existing style of
target volumes.
MESSAGE:
[236:7606] This source volume has a mirrorclone already attached. A demand-allocated

snapshot may not be created.
Storage volume : p
DESCRIPTION:
A mirrorclone exists whose source is one of the storage volumes involved

in this session. With current P6000 EVA Family limitations, a
demand-allocated snapshot may not be created for this storage volume.
ACTION:
* The existing mirrorclone attached to the source volume may be deleted

or detached using the P6000 EVA Family GUI or CLI tools.
MESSAGE:
[236:7607] This source volume appears to be a demand-allocated snapshot.

Storage volume : p
DESCRIPTION:
The source volume appears to be a demand-allocated snapshot already. This

is not a permitted configuration as further copies may not be created from
a snapshot.
ACTION:
* Verify that the backup specification is correct.

* Verify the host environment configuration, specifically checking that
the presented storage volumes are not demand-allocated snapshots.
MESSAGE:
[236:7610] This source volume has one or more demand-allocated snapshots already
attached. A fully-allocated snapshot may not be created.
Storage volume : p
DESCRIPTION:
One or more demand-allocated snapshots exist whose source is one of the storage
volumes involved in this session. With current P6000 EVA Family limitations,
a fully-allocated snapshot may not be created for this storage volume.
ACTION:
* Existing demand-allocated snapshots attached to the source volume may be

be changed to fully-allocated snapshots to match the existing style of
target volumes.
MESSAGE:
[236:7611] This source volume has a mirrorclone already attached. A fully-allocated

snapshot may not be created.
Storage volume : p
DESCRIPTION:

fully-allocated snapshot may not be created for this storage volume.
ACTION:

MESSAGE:
[236:7612] This source volume appears to be a fully-allocated snapshot.

Storage volume : p
DESCRIPTION:
The source volume appears to be already a fully-allocated snapshot. This

is not a permitted configuration as further copies may not be created from
a snapshot.
ACTION:

the presented storage volumes are not fully-allocated snapshots.
MESSAGE:
[236:7615] This source volume has one or more fully-allocated snapshots already
attached. A snapclone may not be created.
Storage volume : p
DESCRIPTION:
One or more fully-allocated snapshots exist whose source is one of the storage
a snapclone may not be created for this storage volume.
ACTION:
* Existing fully-allocated snapshots attached to the source volume may be

target volumes.
MESSAGE:
[236:7616] This source volume has one or more demand-allocated snapshots already
attached. A snapclone may not be created.
Storage volume : p
DESCRIPTION:
One or more demand-allocated snapshots exist whose source is one of the storage
a snapclone may not be created for this storage volume.
ACTION:
* Existing demand-allocated snapshots attached to the source volume may be

target volumes.
MESSAGE:
[236:7617] This source volume has a mirrorclone already attached. A snapclone may
not be created.
Storage volume : p
DESCRIPTION:

snapclone may not be created for this storage volume.
ACTION:

MESSAGE:
[236:7620] This source volume appears to be the target of a mirrorclone.

Storage volume : p
DESCRIPTION:
The source volume appears to be the target of a mirrorclone. This is a

potentially dangerous situation as any data on this storage volume will
be overwritten by the source of the mirrorclone, if the mirrorclone is
resynced.
ACTION:

the presented storage volumes are not the target of a mirrorclone.
* The existing mirrorclone may be detached from the source of the mirrorclone
using the P6000 EVA Family GUI or CLI tools.
MESSAGE:
[236:7621] Maximum number of snapshots reached for following storage volume.

Storage volume : p
DESCRIPTION:
The source volume has reached maximum number of snapshots.

Check P6000 EVA Family documentation for specific limitations.
ACTION:
* Change option 'Number of replicas rotated' to the same value as stated in limitations.
* Existing snapshots attached to the source volume may be deleted.
Unneeded snapshots that are outside of Data Protector
MESSAGE:
[236:7730] The following mirrorclones are presented to one or more systems:

p
DESCRIPTION:
Mirrorclones cannot be presented to a system during zero-downtime backup or

instant recovery session.
ACTION:
* Remove mirrorclone presentations and restart the session.
MESSAGE:
[236:8001] This pair of source and target storage volumes are not the same size.
Source size : p GB
Target size : p GB
DESCRIPTION:
The source storage volume and target storage volume are a different size.
This is caused most likely by the an increase of shrinkage of one of the
storage volumes using P6000 EVA Family functionality.
This may create an issue for restore, dependent on the type of restore that
has been requested.
ACTION:
* If the difference in size of the restore volume to the source volume

is not critical, the restore may be started again in some scenarios.
If the restore method is either a switch to the replica or the
combination of copying the replica data to the source location and
preserving the source volumes, the restore may be started again, but
with deselection of the option to check the data configuration.
* Using P6000 EVA SMI-S CLI or GUI tools, a lun shrink or
lun grow may be attempted on either storage volume, so that both of
the volumes are the same size. Refer to P6000 EVA SMI-S
documentation for best practises regarding these techniques.
MESSAGE:
[236:8002] This pair of source and target storage volumes do not have the same VRAID level.
Source VRAID level : p
Target VRAID level : p
DESCRIPTION:
The source storage volume and target storage volume have different VRAID
levels. A restore may still be performed successfully, however, this may
result in differences in storage volume redundancy or performance on the
P6000 EVA Family. Care must be taken to ensure that expected levels
of performance, redundancy, or other criteria will be maintained after
the restore.
ACTION:
* If the VRAID levels are not considered important, the restore may be
started again, with the deselection of the option to check the data
configuration.
* If the VRAID levels of the source storage volume should be maintained
across the restore, another method of restore may be selected. The
restore may be started again, with the selection of the option to copy
the replica data to the source location.
MESSAGE:
[236:8003] This pair of source and target storage volumes are not in the same disk
group.
Source disk group : p
DESCRIPTION:
The source storage volume and target storage volume are in different disk
groups. A restore may still be performed successfully, however, this will
result in different physical drives forming the basis of the storage volume.
This may have an impact on performance or generate other issues. Care must
be taken to ensure that expected levels of performance, redundancy, or other
criteria will be maintained after the restore.
ACTION:
* If the characteristics of the disk group are not considered important,

the restore may be started again, with the deselection of the option to
check the data configuration.
* If the disk group with the source storage volume is to be maintained across
the restore, another method of restore may be selected. The restore may be
started again, with the selection of the option to copy the replica data to
the source location.
MESSAGE:
[236:8005] This current source storage volume acts as the source for some storage
relationship.
Storage volume : p
DESCRIPTION:
This storage volume acts as the source for some storage relationship, such
as snapclone normalization or continuous access. Depending on the restore
options chosen, this may prevent or complicate the restore.
ACTION:
* Verify the type of storage relationship that exists on the P6000 EVA Family.
If this relation is transient, the restore may be run again, after whatever
process has completed. If the relationship is long-lasting, the environment
may need to be modified to remove the relationship.
* In some configurations, the restore may be started again with the deselection
of the option to check the data configuration.
* Refer to Data Protector documentation for more information
about restore troubleshooting.
MESSAGE:
[236:8006] This current source storage volume acts as the target for some storage
relationship.
Storage volume : p
DESCRIPTION:
This storage volume acts as the target for some storage relationship, such
ACTION:
MESSAGE:
[236:8007] This current restore storage volume acts as the source for some storage
relationship.
Storage volume : p
DESCRIPTION:
This storage volume acts as the source for some storage relationship, such
ACTION:
MESSAGE:
[236:8008] This current restore storage volume acts as the target for some storage
relationship.
Storage volume : p
DESCRIPTION:
This storage volume acts as the target for some storage relationship, such

ACTION:
MESSAGE:
[236:8030] The following storage volume reached maximum allowed number of snapshots,
retain source for forensics is not possible.
Storage volume : p
DESCRIPTION:
The maximum number of allowed snapshots for a storage volume has been reached.
Retaining source for forensics is not possible.
ACTION:
* Delete one of the storage volume's snapshots and run the session again.
Use omnidbsmis command line tool if deleting snapshots made with
Data Protector.
* Run Instant Recovery without retain source for forensics option.
MESSAGE:
[236:8040] A target volume is located in a different folder than the source volume.
Source storage volume folder : p
Target storage volume folder: p
DESCRIPTION:
The target volume is located in a different folder than the source volume.
Therfore, after the instant recovery, the restored storage volume will be located
in the target storage volume folder.
ACTION:
* Using P6000 EVA Command View (CV), move the original volume to the desired folder.
MESSAGE:
[236:8213] The identities of this source and target pair have not been successfully verified.
DESCRIPTION:
Some issue occurred during the attempt to return the identity of a source and target
pair to states prior to the start of instant recovery. The identity of the source
storage volume should be manually verified.
ACTION:
* With the information from Data Protector session output, verify the
current characteristics of the storage volumes. The P6000 EVA Family CLI or
GUI tools provide this information. The UUID should be used as the key to locate
any storage volumes.
MESSAGE:
[236:8908] This P6000 EVA SMI-S provider is not currently

DESCRIPTION:
ACTION:
correctly.
* Double-check the configuration parameters for the failed provider using
omnidbsmis -ompasswd -list
If misconfigured, reconfigure a specific P6000 EVA SMI-S provider
with
omnidbsmis -ompasswd -add
MESSAGE:
[236:9001] The ZDB database does not contain any valid P4000
provider information.
DESCRIPTION:
There are no P4000 provider entries configured within

the ZDB database.
ACTION:
* List the P4000 provider entries in the ZDB database using:

omnidbp4000 --ompasswd --list
omnidbsmis --ompasswd --add <hostname> ...
MESSAGE:
[236:9008] This P4000 provider is not currently
DESCRIPTION:
ACTION:
* Check that all P4000 providers are running and operating

correctly.
omnidbp4000 --ompasswd --list
If misconfigured, reconfigure a specific P4000 provider
with
omnidbp4000 --ompasswd --add
MESSAGE:
[236:9101] The ZDB database does not contain any valid HP 3PAR
provider information:
Array ID: p
DESCRIPTION:
There are no HP 3PAR provider entries configured within

the ZDB database.
ACTION:
* List the HP 3PAR provider entries in the ZDB database using:

omnidbzdb --diskarray P10000 --ompasswd --list
omnidbzdb --diskarray P10000 --ompasswd --add <hostname> ...
MESSAGE:
[236:9108] This HP 3PAR provider is not responding correctly.
DESCRIPTION:
ACTION:
* Check that all HP 3PAR providers are running and operating

correctly.
omnidbzdb --diskarray P10000 --ompasswd --list
If misconfigured, reconfigure a specific HP 3PAR provider
with
omnidbzdb --diskarray P10000 --ompasswd --add <hostname> ...
MESSAGE:
[236:9210] A SMI-S call to the array did not behave as expected.

Failed volume: p
Returned message: p
DESCRIPTION:
The SMI-S provider was unable to perform the requested operation or returned
incorrect data.
ACTION:
* Check that all SMI-S providers are running and operating

correctly
* Ensure that the configured user has sufficient privileges on the array
to perform the requested operation
* Check the connection of existing entries using:
omnidbzdb --diskarray <type> --ompasswd --check
MESSAGE:
[236:9211] No valid credentials were found to perform the requested operation on the
following volume:
Volume WWN: p
Volume Name: p
DESCRIPTION:
The SMI-S provider was unable to perform the requested operation due to
missing credentials or insufficient privileges.
ACTION:
to perform the requested operation
* List the provider entries in the ZDB database using:
omnidbzdb --diskarray <type> --ompasswd --list
* If needed, add a provider entry to the ZDB database using:
omnidbzdb --diskarray <type> --ompasswd --add <hostname> ...
MESSAGE:
[236:9212] The following volume was not found on the array because it doesn't exist or
no configured user is able to see it.
Volume WWN: p
Volume Name: p
DESCRIPTION:
The SMI-S provider was unable to find the volume on the array. The volume might
not exist or it is not visible/accessible with the given permissions.
ACTION:
* Verify that a volume with that name and WWN exists on the array
* For HP 3PAR arrays ensure that the volume and its CPG are
in the same domain (or none) as the configured user
to see the volume
MESSAGE:
[236:9232] This presentation type is currently not supported.
DESCRIPTION:
The volume is presented with an unsupported presentation type and therefore

cannot be unpresented or it should be presented with an unsupported
presentation type.
ACTION:
* Refer to the HP Data Protector Zero Downtime Backup Administrator's Guide to check which
presentation
types are supported for your array type
* For unpresent operations ensure that the volume does not have any unsupported
presentations
MESSAGE:
[236:9233] Source volume 'p' is presented using HostSet VLUNs.

Source Volume WWN: p
DESCRIPTION:
Volumes that are presented using HostSet VLUNs are not supported.
Instead of HostSet VLUNs, Host-Sees or Matched-Set VLUNs should be used.
ACTION:
1) Export the volume to all hosts contained in the HostSet using Host-Sees or Matched-Set VLUNs.
2) Remove the HostSet VLUNs from the volume.
MESSAGE:
[236:9234] Source volume 'p' is presented using PortPresent VLUNs.

Source Volume WWN: p
DESCRIPTION:
Volumes that are presented using PortPresent VLUNs are not supported.
Instead of PortPresent VLUNs, Host-Sees or Matched-Set VLUNs should be used.
ACTION:
1) Export the volume to all hosts using Host-Sees or Matched-Set VLUNs.

2) Remove the PortPresent VLUNs from the volume.
MESSAGE:
[236:9242] This replica type is currently not supported.
DESCRIPTION:
The requested replica type is not supported by the array or the agent.
ACTION:
* Refer to the HP Data Protector Zero Downtime Backup Administrator's Guide to check which replica
types are supported for your array type
MESSAGE:
[242:33] NDMP p operation has failed.
DESCRIPTION:
NDMP operation has failed. Please check

If the provoided parametres like filesystem, backup device, environment variables etc are correct.
If pre-requisites are met for volumes.
ACTION:
Make sure the pre-requisites are met before starting the operation.
Correct the parametres like filesystem, backup device, environment variables etc, if incorrect.
Check if there are Data protector session logs for operation failure and correct accordingly.
If you are doing single/multiple file restore with NetApp version 8.1.x please set NDMP
environment variable ENHANCED_DAR_ENABLED=F.

Troubleshooting - Data Protector PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting - Data Protector PDF

Uploaded by

Copyright:

Available Formats

1/10/2019 https://cgrfiles.cgr.go.cr/publico/ver9/hpux/DP_DEPOT/DATA-PROTECTOR/OMNI-DOCS/opt/omni/help/C/Trouble.

[12:5] Internal error in ("p":num) => process aborted

Please verify the Data Protector medium format.

[12:1000] Table allocation error. (No more free entries!).

Table allocation error.

[12:1010] Error in protocol.

Install the newest version of Data Protector.

[12:1012] Cannot access the file.

Check if the appropriate files exist in the Data Protector directory.

[12:1015] The number of configured clients is greater than the number of

Not enough licenses.

Add new licenses or change the configuration.

Configuration file which resides on the client host cannot be accessed.

* Check debug.log located on the CM and client host in <Data_Protector_home>\log\ on NT

integration is not correctly installed. (Re-install the Oracle integration).

[12:1031] Unrecognized option "p" !

[12:1032] Invalid parameter "p" for option "p" !

The program received a -read option or an input redirection operator

[12:1034] Maxiumum number of connections to CRS reached!

Maxiumum number of connections to CRS reached!

Close idle connections.

[12:1035] Maxiumum number of session manager startup retries exceeded!

Maxiumum number of session manager startup retries exceeded!

[12:1036] Interprocess communication problem.

[12:1040] Agent failed to obtain home directory from registry.

An agent that was started to fulfill the request (possibly remotely on

* Check the version of the agent on the client.

[12:1041] Agent failed to open the message catalog.

An agent that was started to fulfill the request (possibly remotely on

* Check the version of the agent on the client.

[12:1049] Service/daemon failed to write to configuration files and/or registry.

Service/daemon failed to write to configuration files and/or registry.

* Verify that the service account has administrative privileges.

[12:1051] Client security violation. Access denied.

* Check and update the client's list of cell authorities.

[12:1115] Internal Database is probably corrupt.

The Data Protector Internal Database is probably corrupt.

[12:1117] Cannot lock Internal Database - currently unavailable.

Try rescheduling some backups to run them in sequence (instead of parallel).

If daily purge is running you can configure it in the

[12:1118] Cannot open database/file.

On a UNIX Cell Manager:

On a Windows Cell Manager:

[12:1121] Cannot open database.

Wait for the omnidbcheck or omnidbutil command, then restart the

[12:1122] Cannot open Internal Database in exclusive mode.

Message is usual at merging mmdb database to central mmdb database. It

[12:1130] Object details in this object version are corrupted.

Select another object version for restore, or

[12:1162] Not enough disk space for Internal Database.

On a UNIX Cell Manager:

On a Windows Cell Manager:

omnidbutil -purge -filenames command to delete obsolete data from

[12:1164] Internal Database key files have been corrupted.

Use the omnidbcheck -keybuild command to fix the index file.

[12:1165] Internal Database network communication error.

On a Unix Cell Manager:

On a Windows Cell Manager:

The Internal Database services are not running.

For example, in order to configure additional module files size

/opt/omni/sbin/omnidbutil -extend pathname -maxsize size_MD

[12:1168] There is no more space in the Internal Database for filenames.