Data Protector 9.04 Patch for Linux/64

dataprotector9.
04forLinux/64HPSo wareSupport
h ps://so waresupport.hp.com/group/so waresupport/searchresu...
dataprotector9.04forLinux/64
Feedback
Title :
data protector 9.04 for Linux/64
Document ID :
DPLNXBDL_00904
Product - Version:
data protector 9.0 9.01 9.02 9.03 9.04 ;
OS :
Linux
Updated :
2015-Aug-05
Critical :
yes
Summary :
Product: data protector; Version: 9.0, 9.01, 9.02, 9.03, 9.04; OS: intelLinux; Critical: Yes
Register to receive e-mail notification about patch updates for data protector, 9.0,9.01,9.02,9.03,9.04, Linux
Register to receive e-mail notifications
Table of contents:
Should I download? Download Information History Products Hardware Platforms - OS
Releases Critical Enhancements Resolved Known Problems Change Requests
Installation Information Other Dependencies Installation Instructions Special Installation
Instructions
Patch Contents Supersedes Patch Files sum(1) Output
Download Information
Patch ID:
Download
patch:
Patch size:
MD5 hash:
DPLNXBDL_00904
DPLNXBDL_00904.tar
1.54 GB
ec981deeffbbf3537bc804e2a0d2841d
History
2015-Jul-31: The patch was created.
2015-Aug-05: The patch was released.
Products
data protector 9.0 data protector 9.01 data protector 9.02 data protector 9.03 data protector 9.04
Hardware Platforms - OS Releases

Linux: CentOS6-x86_64 OracleEL6-x86_64 RedHat5-x86_64 RedHat6-x86_64 Linux: SuSE11-x86_64
Critical
Yes DPLNXBDL_00904: QCCR2A51672 QCCR2A55832 QCCR2A56429 QCCR2A57217 QCCR2A57225 QCCR2A57311
QCCR2A57442 QCCR2A57880 QCCR2A57986 QCCR2A57998 QCCR2A58036 QCCR2A58163 QCCR2A58166
QCCR2A62632 QCCR2A62799 QCCR2A62914 DPLNX_00317: CORRUPTION CORRUPTION QCCR2A54772
1of32
9/14/20151:58PM
dataprotector9.04forLinux/64HPSo wareSupport
DPLNX_00316: HANG ABORT CORRUPTION HANG QCCR2A51421 HANG QCCR2A52604 HANG QCCR2A55709 ABORT
QCCR2A51881 ABORT QCCR2A52780 ABORT QCCR2A54260 CORRUPTION QCCR2A54772 CORRUPTION
QCCR2A55079 DPLNXBDL_00903: QCCR2A55832 QCCR2A56429 QCCR2A56617 QCCR2A57217 QCCR2A57225
QCCR2A60503 DPLNXBDL_00902: QCCR2A50354 QCCR2A50896 QCCR2A50919 QCCR2A51260 QCCR2A51264
QCCR2A55769 QCCR2A56349 QCCR2A56430 QCCR2A56980
Enhancements
Yes DPLNXBDL_00904: Change Request: QCCR2A47623: Symptom: Support for enabling the MAXDB restore only to an
offline database is not available in Data Protector. Resolution: Data Protector introduces support for a new option in the SAP
DB restore option page: "Force restore if database is online". There is an equivalent option for the CLI ("-force"). This option is
not selected by default. When selected, it allows you to overwrite an online database. Otherwise, the restore fails with a
warning message. Change Request: QCCR2A48239: Symptom: This is an enhancement request to enable Data Protector to
support network encryption in Sybase. Resolution: Data Protector now supports Sybase network encryption feature. Change
Request: QCCR2A50732: Symptom: Support for GUID Partition Table (GPT) disks in a VMware Granular Recovery Extension
(GRE) Web plug-in is not available with Data Protector. Resolution: Data Protector introduces support for GUID Partition Table
(GPT) disks in a VMware Granular Recovery Extension (GRE) Web plug-in. Change Request: QCCR2A50776: Symptom:
Support for EMC storage (VMAX) on Linux x64 Servers is not available with Data Protector. Resolution: Data Protector
introduces support for EMC storage (VMAX) on Linux x64 servers. Change Request: QCCR2A51483: Symptom: Support for
Intel Enterprise Edition for Lustre (IEEL) version 2.4 file system and extended Access Control List (ACL) backup is not available
with Data Protector. Resolution: Data Protector introduces support for Intel Enterprise Edition for Lustre (IEEL) version 2.4 file
system and extended Access Control List (ACL) backup. Change Request: QCCR2A51672: Symptom: Support for handling
more than 1200 connections by the Data Protector Cell Request Server (CRS) process is not available with Data Protector.
Resolution: Data Protector introduces support for enabling the Cell Request Server (CRS) to handle more than 1200
connections. Change Request: QCCR2A52116: Symptom: Support for removing the "Read Error. Retrying to read from disk"
warnings from the session reports is not available with Data Protector. Resolution: Data Protector introduces support for
moving both backup and restore warning messages for retry/resume of read/write to VEPA debug logs. Change Request:
QCCR2A52732: Symptom: Support for snap creation for 3PAR at either end of the replication group is not available with Data
Protector. Resolution: Data Protector introduces support for 3PAR remote copy with the remote replication mode. Change
Request: QCCR2A53010: Symptom: Support for SUSE Linux Enterprise 11 Service Pack 3 to boot from SAN is not available
with the Data Protector Enhanced Automated Disaster Recovery (EADR) method. Resolution: Data Protector introduces
support in the disaster recovery (DR) module for new features on SUSE 11 SP3, which impact the DR process to work
correctly (support for the "btrfs" file system). Change Request: QCCR2A53079: Symptom: The default timeout value for Data
Protector OMNIRC variable "OB2SCTLMOVETIMEOUT" used to define timeout value for SCSI "MOVE MEDIUM" commands
is just 4 minutes and this is too short duration for commands to complete. Resolution: The default timeout value for Data
Protector OMNIRC variable "OB2SCTLMOVETIMEOUT" is now changed to 10 minutes. Change Request: QCCR2A55461:
Symptom: Support for ACLs for fourth extended filesystem (ext4) on Linux systems is not available with Data Protector.
Resolution: Data Protector introduces support for ACLs for fourth extended filesystem (ext4) on Linux systems. Change
Request: QCCR2A56021: Symptom: Support for on-line backup of MySQL v5.5 on RedHat Linux 5.5 64-bit and individual
Database object restore is not available with Data Protector GUI. Resolution: Data Protector introduces support for backup and
restore of MySQL Server 5.5, 5.6 on Linux and Windows. Change Request: QCCR2A57750: Symptom: Support for Automated
Replication Synchronization is not available with Data Protector. Resolution: Data Protector introduces support for Automated
Replication Synchronization for backup metadata. Change Request: QCCR2A57752: Symptom: Support for remote installation
of Site Specific Patches (SSPs) and Test Modules (TMs) is not available with Data Protector. Resolution: Data Protector
introduces support for remote installation of Site Specific Patches (SSPs) and Test Modules (TMs). Change Request:
QCCR2A57988: Symptom: Support for improved troubleshooting and logging capabilities in the Internal Database (IDB) is not
available with Data Protector. Resolution: Data Protector introduces support for improved troubleshooting and logging
capabilities in the IDB. Change Request: QCCR2A58265: Symptom: Support for a mechanism to reduce the amount of time
needed for gathering the debug logs is not available with Data Protector. Resolution: Data Protector introduces support for
enhanced "omnidlc" command. Change Request: QCCR2A58456: Symptom: Support for 3PAR LUN in Remote Copy Group is
not available with Data Protector. Resolution: Data Protector introduces support for storage volumes in Remote Copy Group.
Change Request: QCCR2A59027: Symptom: Support for 3PAR ZDB VMware (Virtual Infrastructure) restore from Snapshot is
not available with Data Protector. Resolution: Data Protector introduces support for 3PAR ZDB VMware (Virtual Infrastructure)
restore from Snapshot. Change Request: QCCR2A59029: Symptom: Support for Power ON and Live Migrate of VMware
(Virtual Infrastructure) from Smart Cache device is not available with Data Protector. Resolution: Data Protector introduces
support for Power ON and Live Migrate of VMware (Virtual Infrastructure) from Smart Cache device. Change Request:
QCCR2A59114: Symptom: Support for Power ON and Live Migrate of 3PAR ZDB VMware (Virtual Infrastructure) from
Snapshot is not available with Data Protector. Resolution: Data Protector introduces support for Power ON and Live Migrate of
3PAR ZDB VMware (Virtual Infrastructure) from Snapshot. Change Request: QCCR2A59433: Symptom: Data Protector allows
VMware Changed Block Tracking (CBT) enabled backups to fallback to inefficient non-CBT backup mode. Resolution: Data
Protector now makes the VMware Changed Block Tracking (CBT) backup mode as default and the inefficient non-CBT backup
mode is removed. Change Request: QCCR2A60081: Symptom: Support for Data Protector interoperability in a VMware
2of32
9/14/20151:58PM
vSphere 6.0 environment and VMware Virtual Disk Development Kit (VDDK) 6.0 API(s): backup, restore, and granular recovery
of the backed up data is not available with Data Protector. Resolution: Data Protector introduces support for interoperability in
a VMware vSphere 6.0 environment and VDDK 6.0 API(s): backup, restore, and granular recovery of the backed up data.
Change Request: QCCR2A61242: Symptom: Data Protector does not support the backup and restore of Virtual Machine(s)
(VM) on VMware VVol datastores with the HP 3PAR storage. Resolution: Data Protector introduces support for the backup and
restore of VM on VMware VVol datastores with the HP 3PAR storage. Change Request: QCCR2A61511: Symptom: This is an
enhancement request to enable and document Data Protector cluster-aware Cell Manager configuration on Veritas Cluster
Server environment. Resolution: Data Protector introduces support for cluster-aware Cell Manager configuration on Veritas
Cluster Server environment and document the required procedures. Change Request: QCCR2A62050: Symptom: SMIS Agent
and VEP Agent does not support EMC storage (VNX) disk arrays. Resolution: Data Protector is modified to allow disk resolve
and array operations on EMC storage (VNX) disk arrays. Change Request: QCCR2A62810: Symptom: Support of quiescence
operation for Virtual Machines (VMs) hosting Microsoft SQL, Microsoft Exchange, Microsoft SharePoint, and Oracle
applications is not available with Data Protector. Resolution: Data Protector introduces support for VMware quiescence
operation for virtual machines hosting Microsoft SQL, Microsoft Exchange, Microsoft SharePoint, and Oracle applications.
Change Request: QCCR2A62813: Symptom: Support for enabling VMware GRE from a 3PAR Replica for virtual machine disks
greater than 256GB is not available with Data Protector. Resolution: Data Protector introduces support for VMware GRE from
a 3PAR Replica for virtual machine disks greater than 256GB. DPLNXBDL_00903: Change Request: QCCR2A51166:
Symptom: The encrypted control communication is not enabled by default. Resolution: Data Protector encrypted control
communication has been enhanced and now supports the following functionality: - enable ECC on clients by default during
push install or import - disable ECC for a client - use one CA per cell, reusing the CA currently used for JBoss - use the
simplified GUI or the CLI to decide if you want to use the existing certificates or regenerate them - add your own external
script (predefined name gencert.pl) to incorporate your own certificate generation process - replace the CA file for the whole
cell - enable ECC in the MoM environment, the MoM server and then all the member Cell Managers. Change Request:
QCCR2A57748: Symptom: Data Protector was supporting an older version of OpenSSL. Resolution: Data Protector now
supports OpenSSL 1.0.1j. Data Protector "Vepa" and "VMware GRE" modules are still using OpenSSL 0.9.8za since they are
dependent on that specific version. DPLNXBDL_00902: Change Request: QCCR2A50354: Symptom: Support for DB2 10.1
database and archived Log backup using IBM DB2 database standards on SUSE Linux Enterprise Server (SLES) 11 SP3 is
not available in Data Protector. Resolution: Data Protector now supports DB2 database and archive logs backups using IBM
DB2 "VENDOR" option for all operating systems supported by Data Protector DB2 Integration. Change Request:
QCCR2A52510: Symptom: The Data Protector session manager fails when StoreOnce Catalyst Stores do not have available
connections. Resolution: The Data Protector session manager and backup media agent are modified to queue sessions until
connections are available. Change Request: QCCR2A53792: Symptom: When the user abort is initiated during the
replication session, the Abort command is not sent to the Catalyst API of the D2D box. Resolution: Data Protector introduces
support for the user abort initiation during the replication session. The Abort command is sent to the source and target stores
through the Catalyst API. After this step, any media that is replicated during the session (either wholly or partially) is deleted.
*NOTE:* Due to the asynchronous nature of some Catalyst commands, this abort may take slightly longer than other aborts
(for example, object copy). Change Request: QCCR2A54205: Symptom: Support for displaying VM name in the Data
Protector GUI and CLI report is not available with Data Protector. Resolution: Data Protector introduces support for
displaying VM name along with the other information in the Data Protector GUI and CLI report. Change Request:
QCCR2A54369: Symptom: Support for licence reporting for Capacity Based Licensing (CPL) is not available in Data
Protector. Resolution: Data Protector introduces support for licence reporting for Capacity Based Licensing (CPL). Change
Request: QCCR2A54899: Symptom: Support for handling the application database and device concurrency during backup is
not available with Data Protector. Resolution: Data Protector introduces support for handling application database and device
concurrency for the following database integration: 1. MS SQL 2. MS Sharepoint 3. Sybase 4. SAP MaxDB 5. IDB (Postgres
SQL) 6. Lotus Change Request: QCCR2A55398: Symptom: Support for 3PAR based VMware GRE feature is not available
with Data Protector. Resolution: Data Protector 9.02 introduces support for 3PAR based VMware GRE feature. Change
Request: QCCR2A55399: Symptom: Support for 3PAR integration for VMware (Virtual Infrastructure) is not available with
Data Protector. Resolution: Data Protector introduces support for 3PAR integration for VMware (Virtual Infrastructure).
Change Request: QCCR2A57443: Symptom: Support for pausing the running backup sessions automatically when the
scheduled higher priority jobs share the same device is not available with Data Protector. Resolution: Data Protector
introduces support for pausing the lower priority backup sessions when the scheduled higher priority jobs share the same
device. The paused jobs are resumed once the device is available. Change Request: QCCR2A57446: Symptom: Support for
managing replication between Data Domain devices is not available with Data Protector. Resolution: Data Protector
introduces support for managing replication between Data Domain devices. Change Request: QCCR2A57448: Symptom:
Support for StoreOnce software version 3.12 is not available with Data Protector. Resolution: Data Protector introduces
support for StoreOnce software version 3.12 and its features. Change Request: QCCR2A57481: Symptom: Support for using
the Granular Recovery Extension (GRE) plugin on Linux vCenters is not available with Data Protector. Resolution: Data
Protector introduces support for the following: - vCenter 5.1 or vCenter 5.5.0 and its continuity with the old FLEX functionality.
- vCenter 5.5 update 1 onwards with a new look and feel for the GRE plugin, supporting Windows and Linux vCenter, and
single vCenter communication between multiple Cell Managers. Change Request: QCCR2A57495: Symptom: Support for
VEPA Hardening including the following is not available with Data Protector: - Consolidation of all VMware API(s) to
ViAPI/vddk5.5.3. - Display of Virtual Machine (VM) name details in GUI, CLI, and reporting. Resolution: Data Protector
introduces support for VEPA Hardening including: - Consolidation of all VMware API(s) to ViAPI/vddk5.5.3. - Display of
Virtual Machine (VM) name details in GUI, CLI, and reporting. Change Request: QCCR2A57571: Symptom: Support for
localizing the Data Protector 9.00 documentation in French is not available with Data Protector. Resolution: Data Protector
introduces support for localizing the Data Protector 9.00 documentation in French. Change Request: QCCR2A57572:
Symptom: Support for localizing the Data Protector 9.00 documentation in Japanese is not available with Data Protector.
3of32
9/14/20151:58PM
Resolution: Data Protector introduces support for localizing the Data Protector 9.00 documentation in Japanese. Change
Request: QCCR2A57575: Symptom: Support for localizing the Data Protector 9.00 documentation in Simplified Chinese is
not available with Data Protector. Resolution: Data Protector introduces support for localizing the Data Protector 9.00
documentation in Simplified Chinese. DPLNXBDL_00901: This patch delivers code changes to - Support the NetApp
SnapManager integration for VMware (Virtual Infrastructure) with Data Protector. - Support copying virtual machine backups
to HP public cloud storage with Data Protector.
Resolved Known Problems

DPLNXBDL_00904: Change Request: QCCR2A43877: Symptom: The Data Protector Backup Session Manager (BSM) fails
with the following error message: |Major| From: BSM@<host name> "dbsvr1_dr" <Date Time> |61:3003| Lost connection to
VBDA named "/custom_index" on host <client system>. Ipc subsystem reports: "IPC Invalid Handle Number" Resolution: The
Data Protector Backup Session Manager (BSM) component is modified to correctly handle the client. Change Request:
QCCR2A48840: Symptom: On a file system, the Data Protector enhanced incremental backup session backs up unwanted
additional files. Resolution: The Data Protector Volume Backup Disk Agent (VBDA) is modified to correctly handle the
enhanced incremental backup sessions. Change Request: QCCR2A50478: Symptom: The integration of Data Protector 8.0
client on SUSE Linux Enterprise Server 11 (x86_64) with Sybase Adaptive Server Enterprise (ASE) 15.7 fails with the following
error message: "Adaptive Server requires encryption of the login password on the network" Resolution: The integration
completes successfully. Change Request: QCCR2A51458: Symptom: Import of the Data Protector Network Data Management
Protocol (NDMP) server object spanning multiple media fails with the following error message: "object version exists"
Resolution: The Data Protector Media Session Manager (MSM) is modified to correctly handle reconstruction of sequence
numbers from the media.log data file. This is controlled by the omnirc variable "OB2_GENSEQ_SM". Change Request:
QCCR2A51470: Symptom: The Data Protector "omnicellinfo -cell" command displays the Data Protector Network Data
Management Protocol (NDMP) Server integration identification as plain text. Resolution: The Data Protector "omnicellinfo -cell"
command is modified to execute correctly. Change Request: QCCR2A51905: Symptom: The Data Protector "omniofflr -idb
-autorecover" command fails with the following error message: |Normal| From: OMNIOFFLR@hostname "" Time: <Date>
<Time> Scanning obrindex.dat: preparing for restore... |Major| From: OMNIOFFLR@hostname"" Time: <Date><Time> cannot
select session for restore. (No valid successfully completed backup session in the log.) Resolution: The Data Protector
"omniofflr" command is modified to correctly display logs and/or sessions for restore. Change Request: QCCR2A52094:
Symptom: The Data Protector 7.01 backup session completes with the "Completed/Failures" status even though there are no
messages with the level higher than the warning displayed in the session report. Resolution: The Data Protector 7.01 is
modified to correctly handle backup sessions, without any failures. Change Request: QCCR2A52748: Symptom: The Data
Protector 8.1 backup session fails with the following error message: |Warning| From: BSM@hostname "" Time: <Date><Time>
|60:1023| Medium "" labeled "" of data format "<name_1>" is not compatible with device "" of data format "<name_2>" .
Resolution: Data Protector is modified to correctly handle the format incompatibility. Change Request: QCCR2A53188:
Symptom: The Data Protector 7.03 Oracle integration backup session on Windows Server 2008 fails with the following error
message: |Major| From: ob2rman@<hostname> "" Time: <Date><Time> The database reported error while performing
requested operation. RMAN-00571: RMAN-00569: ERROR MESSAGE STACK FOLLOWS RMAN-00571: RMAN-03009:
failure of allocate command on dev_0 channel at <Date><Time> ORA-19554: error allocating device, device type: SBT_TAPE,
device name: ORA-27211: Failed to load Media Management Library Resolution: The Data Protector Secure Socket Layer
(SSL) libraries are modified to correctly unload at the end of every backup. NOTE: Restart the Oracle services to begin with a
clean state. Change Request: QCCR2A53589: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) reports the
following segmentation fault: # ./vbda -vol /opt/app -out /dev/null -profile -debug 1-999,T:1000,C:51200 VBDA.DBG >
/tmp/vbda_w_debug.txt Segmentation fault (core dumped)85 (kB), done: 0 (%) Resolution: The Data Protector Volume Backup
Disk Agent (VBDA) is modified to correctly handles backup of path names longer than 1024. Change Request: QCCR2A53697:
Symptom: After upgrading from Data Protector 8.1 to Data Protector 8.11, Advanced Scheduler does not allow creation of
incremental schedules for Exchange Single Mailbox Backup. Resolution: The Data Protector GUI is modified to correctly
handle the creation of incremental schedules for Exchange Single Mailbox Backup within Advanced Scheduler. Change
Request: QCCR2A53852: Symptom: The Data Protector online/internal virtual disk is deleted during the restore session.
Resolution: Data Protector is modified to correctly handle the "restore as" operation of individual disks. Change Request:
QCCR2A54060: Symptom: The restore process ends abnormally when restoring from an incremental backup with an expired
corresponding full version. Resolution: The Data Protector facade binary is modified to correctly handle the expired object
versions. Change Request: QCCR2A54143: Symptom: When using physical tapes, the following Input Output error message is
displayed: Cannot write to device |5| I/O error Resolution: The Data Protector Media Agent (MA) binaries are modified to
correctly handle the backup of physical or virtual tapes. Change Request: QCCR2A54642: Symptom: Documentation is
missing: - The "kpartx" application is required for disks with LVM partitions - If you cannot contact the ESX server from the
MountProxy, add the ESX hostname and IP address in the host file. Resolution: The Granular Recovery Extension User Guide
for VMware vSphere addresses the following: - kpartx (required for disks with LVM partitions) Note: Ensure that the ESX server
hostname is resolved from the MountProxy. If you cannot contact the ESX server from the MountProxy, add the ESX hostname
and IP address in the host file. Change Request: QCCR2A54682: Symptom: After the restore session of IBM DB2 databases,
the following message in the debug.log file is displayed: <Date><Time> OB2BAR_DB2ARCH.6384.0 |"/lib/cmn/unix.c $Rev:..|
A.08.10 b154 execvp failed! (/db2/db2r27/db2_softwarebin/db2level) errno=2 Arg list: db2level <Date><Time>
OB2BAR_DB2ARCH.6376.0 |"/integ/db2/db2arch/main.c$Rev:...| A.08.10 b154 |setDb2Lvl| Can not start /db2/db2r27
/db2_softwarebin. Error: |2| Details unknown. Resolution: Data Protector 8.12 is modified to correctly handle the debug.log file.
Change Request: QCCR2A54694: Symptom: The Data Protector Cell Request Server (CRS) process does not respond when
the schedule granularity is set to 1 minute. Resolution: The Data Protector omnitrig binary is modified to correctly handle the
overhead and limit schedule parsing to current day only. Change Request: QCCR2A55199: Symptom: Data Protector Media
Catalog File (MCF) import of Network Data Management Protocol (NDMP) media fails. Resolution: Data Protector is modified
to correctly handle the Network Data Management Protocol (NDMP) MSG_FBIN. Change Request: QCCR2A55813: Symptom:
4of32
9/14/20151:58PM
Overwriting a medium created by a medium copy fails with the following error message: |Major| From: MSM@<hostname> ""
Time:<Date><Time> |65:99| Import failed with possible cause: this media already has valid copy in DB. Resolution: The Data
Protector Media Agent (MA) is modified to correctly handle the "original medium ID" field of the medium header when
overwriting the medium. Change Request: QCCR2A55832: Symptom: Import of a tape from an old server to a new server fails
with the following error message: |Critical| From: MSM@<hostname> "" Time: <Date><Time> |65:6| Internal Database layer
reports: "Internal error: DbaXXXX functions." Resolution: The Data Protector facade library is modified to correctly import a tape
from an old server to a new server. Change Request: QCCR2A55982: Symptom: Data Protector stops responding if the the
mirror device is disabled. Resolution: Data Protector is modified to correctly handle the mirror device when it is disabled.
Change Request: QCCR2A56340: Symptom: The Data Protector Internal Database (IDB) backup does not back up Detailed
Catalog Binary Files (DCBF) or Session Message Binary Files (SMBF) when configuration backup fails with the following error
message: |Major| From : OB2BAR_POSTGRES_BAR@<hostname> "" Time :<Date><Time> The OS reported error while
entering /ProgramData/OmniBack/config/server/Sessions/checkpoint/test.txt : |5| Entrance is denied. |Critical| From :
OB2BAR_POSTGRES_BAR@<hostname> "" Time :<Date><Time> Backup of the object ConfigurationFiles failed Resolution:
The Data Protector Internal Database (IDB) is modified to correctly handle the backup. Change Request: QCCR2A56429:
Symptom: During catalog browsing in the restore context of the GUI for hosts with a large number of object versions, the
Database Session Manager (DBSM) becomes unresponsive sometimes for hours at a time. Resolution: The Data Protector
Database Session Manager (DBSM) and facade binaries are optimized to improve performance while dealing with a large
number of object versions. Change Request: QCCR2A56438: Symptom: The Data Protector vCD restore session fails with the
following error message: |Warning| From: VEPALIB_VCD@<hostname> "" Time: <Date><Time> vApp "": Error updating
network... Resolution: Data Protector is modified to correctly handle the vCD restore session. Change Request:
QCCR2A56542: Symptom: The Data Protector backup, object copy or consolidation session fails with the following error
message: |61:3003| Lost connection to MMD named "noname" on host cell.domain.com Ipc subsystem reports: "IPC Write
Error System error: |10054| Connection reset by peer" Resolution: The Data Protector Media Management Daemon (MMD) is
modified to correctly handle timeouts when sending messages. Change Request: QCCR2A56568: Symptom: After upgrading
to Data Protector 8.13, the application integration backups may fail with the following error message: |Critical| From:
BSM@<hostname> "" Time: <Date><Time> |61:12019| Mismatch in backup group device and application database
concurrency configuration. Application database concurrency is 10. Resolution: The Data Protector Backup Session Manager
(BSM) binary is modified to correctly handle integration backups to an implicit gateway. Change Request: QCCR2A56630:
Symptom: The Data Protector restore session of an OpenVMS system disk backup fails with the following error message:
|Major| From: RSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to Filesystem restore DA named "" on
host <hostname>. Ipc subsystem reports: "Bad message format." Resolution: Data Protector is modified to correctly handle the
restore session of an OpenVMS system disk backup. Change Request: QCCR2A56639: Symptom: An unknown internal error
occurs in the Data Protector GUI when connecting to few clients in the restore context. Resolution: Data Protector is modified
to correctly handle browsing of duplicate files by adding a global variable. Change Request: QCCR2A56724: Symptom: The
backup of Encrypting File System (EFS) encrypted files takes a long time. Resolution: The Data Protector Volume Backup Disk
Agent (VBDA) and Raw Backup Disk Agent (RBDA) binaries are modified to correctly handle the backup performance of
Encrypting File System (EFS) encrypted files. Change Request: QCCR2A56766: Symptom: The Cell Request Server (CRS)
randomly ends abnormally. Resolution: The Cell Request Server (CRS) is modified to handle heavy load environments reliably.
Change Request: QCCR2A56788: Symptom: The pre-upgrade Detail Catalog Binary Files (DCBF) directory in IDB with "\ " in
path name cannot be removed from Data Protector 8.0. Resolution: The omnidbutil is modified to handle Detail Catalog Binary
Files (DCBF) directory in IDB with "\ " in path name. Change Request: QCCR2A56823: Symptom: The "storeonceinfo"
command does not return any information about objects from the (HW) store. Resolution: The "storeonceinfo" command is
modified to correctly print logs to file. Change Request: QCCR2A56845: Symptom: The HP Data Protector Granular Recovery
Extension GUI display backups as "Staged" instead of "Non-Staged". Resolution: The HP Data Protector "vmwaregre-agent" is
modified to correctly display non-staged backups. Change Request: QCCR2A56846: Symptom: The Data Protector Reporting
functionality sending SNMP traps does not work with the Data Protector 8.12 on HP-UX 11.31 systems. Resolution: The Data
Protector "omnirpt" binary is modified to correctly handle the SNMP traps. Change Request: QCCR2A56859: Symptom:
Configuring report of "List of Pools" with "Media in selected libraries" (Libraries Tab) section causes DBSM to end abnormally.
If "Do not care" option is selected in reporting, the report works correctly. Resolution: The Library filter is modified to function as
expected for stand alone devices. Change Request: QCCR2A56958: Symptom: The Data Protector "Change Data and catalog
protection after successful copy" object copy option changes the data and catalog protection even when the object copy
session fails or terminates. Resolution: The "csm" binary is modified to ensure that the data and catalog protection does not
change after a failed copy. Change Request: QCCR2A57013: Symptom: The MS SQL application integration backups,
configuration or modification fails with the following error: |Critical| From: BSM@<hostname> "" Time: <Date><Time> None of
the Disk Agents completed successfully. Session has failed. Resolution: The Data Protector "crs" binary is modified to correctly
handle the integration backups. Change Request: QCCR2A57081: Symptom: The Data Protector disk agent does not display
a status message when a pre/post-exec script is executed for an individual object. There is no such issue when the script is
executed for a session. Resolution: The Data Protector VBDA, VRDA, RBDA and RRDA modules have been modified to
display the status message when the pre/post-exec script is executed on a per object basis. Change Request: QCCR2A57090:
Symptom: An import session that has a duplicate session ID is unsuccessful. Furthermore, a restore session of such objects
also fails, with the following error: "object not found". Resolution: The Data Protector facade binaries have been modified and
now the importing of sessions that have duplicate session IDs are functioning correctly. Change Request: QCCR2A57185:
Symptom: The Data Protector graphical user interface (GUI) ignores the global parameter "MMFairLimit" and uses a default
setting. Resolution: The Data Protector GUI is modified to function correctly when setting the "MMFairLimit" parameter. Change
Request: QCCR2A57217: Symptom: The Data Protector VEAgent backup configuration, that has a Linux backup host on
RHEL 6.4 fails with the following unspecific error: "IDPMissingObjectException" Resolution: The Data Protector VEPA
post-install script is modified to correctly update the configuration files. Change Request: QCCR2A57220: Symptom: During a
disaster recovery backup session, the Volume Backup Disk Agent (VBDA) fails with the following error message: |Major| From:
VBDA@<hostname> "/CONFIGURATION" Time: <Date><Time> |81:145| Automatic DR information could not be collected.
5of32
9/14/20151:58PM
Aborting the collecting of system recovery data. Resolution: The Data Protector VBDA module is modified and now the backup
session completes successfully. Change Request: QCCR2A57225: Symptom: The import process of the StoreOnce D2D
media is unsuccessful. Resolution: The Data Protector Media Agent is modified and the import of StoreOnce D2D media is
functioning correctly. Change Request: QCCR2A57235: Symptom: The Data Protector command "omnirpt -report
single_session -session -ascii" ends abnormally. Resolution: The Data Protector facade library is modified to correctly handle
the Data Protector command "omnirpt -report single_session -session -ascii". Change Request: QCCR2A57261: Symptom:
When configuring a backup specification for VMware Virtual Cloud Director, the following error is displayed: "Error during
vepa_util browse.*RETVAL*8010". Resolution: The ViAPI, vCloudAPI and vepalib_vcd files are modified to function correctly
during a backup session. Change Request: QCCR2A57268: Symptom: The Oracle server ends abnormally when performing a
backup in a cell, where maximum number of running sessions exceeds its limit. Resolution: The orasbt library and crs files are
modified to correctly handle the Oracle server when maximum number of cell server sessions exceed its limit. Change Request:
QCCR2A57311: Symptom: Media allocation fetches an excessively large candidate cartridge/medium set from the Data
Protector internal database (IDB) and then filters it down to only a few. Resolution: Data Protector is modified to correctly
handle the media allocation queries to fetch only relevant candidates from IDB. Change Request: QCCR2A57375: Symptom:
When trying to restore an object during replication, the media is locked and marked as "poor media". Data Protector assumes
that the media is unavailable. Resolution: The rma and bma binaries are modified to ensure that the Data Protector media is
available when trying to restore an object during replication. Change Request: QCCR2A57386: Symptom: The Media Agent
ends abnormally when reading from a catalyst store media: |Major| From: CSM@<hostname> "Interactive" Time: <Date>
<Time> |61:1005| Got unexpected close from CMA on <hostname>. Resolution: The Media Agent is modified to correctly read
from a catalyst store media. Change Request: QCCR2A57401: Symptom: The Data Protector "Session_errors" report does not
display the correct result if the "-hosts" option is specified. The report always contains |Common| messages. Resolution: The
Data Protector facade and libfacade files are modified to function correctly when the "Session_errors" report is executed with
the "-hosts" option. Change Request: QCCR2A57406: Symptom: After a failed object, the status of successful object displays
incorrect details. The object appears to be successful but displays "Missing Media", which cannot be restored. Resolution: The
bma, bsm, and rsm binaries are modified to correctly display objects and restore them. Change Request: QCCR2A57442:
Symptom: The Data Protector Media Management Daemon (MMD) service ends abnormally, on an unexpected medium
protection change request. Resolution: The Data Protector MMD service is fixed to correctly handle an unexpected medium
protection change request. Change Request: QCCR2A57456: Symptom: If a Data Protector restore session is stopped, the
devices are not unlocked. The device selection process is replacing the unavailable devices multiple times. Resolution: The
Data Protector Restore Session Manager binaries are modified to correctly handle the unlocking of devices during a restore
session. Change Request: QCCR2A57458: Symptom: When a previously failed backup session is restarted, the following error
message is displayed: |Major| From: OB2BAR_SBT_CHANNEL@<hostname> "" Time: <Date><Time> Query
incomplete/failed (Catalog not loaded, message #1206 in set 12) Resolution: The Data Protector facade files are modified and
the backup session completes successfully. Change Request: QCCR2A57463: Symptom: After upgrading from Data Protector
8.0 to 8.12, all the backup sessions using VTL drives fail with the following error message: |Warning| From:
BMA@<hostname> "" Time: <Date><Time> The device "" could not be opened("Serial number has changed") |Normal| From:
BMA@<hostname> "" Time: <Date><Time> Starting the device path discovery process. |Critical| From: BMA@<hostname> ""
Time: <Date><Time> |90:1004| Device address not found. Resolution: The Data Protector UMA and Devbra binaries are
modified to correctly recognize the VTL device serial numbers during a backup session. Change Request: QCCR2A57483:
Symptom: The Data Protector Command Line Interface (CLI) stops responding after import of a MCF file with the following
error message:. |Normal| From: MSM@<hostname> "" Time: <Date><Time> MCF import session ended. 1 out of 1 media
successfully imported. Resolution: The Data Protector Media Session Manager (MSM) is modified and the media container
format (MCF) import session completes successfully. Change Request: QCCR2A57503: Symptom: The restore session of a
single file from the Data Protector Internal Database (IDB) configuration, fails with the following error message: |Critical| From:
OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date><Time> An internal error occurred Resolution: The Data
Protector postgres integration client is modified to correctly restore single files from IDB configuration backup. Change
Request: QCCR2A57505: Symptom: The Data Protector reporting command "omnirpt -report hosts_statistics" does not display
the correct results for the Disk Agents (DA) objects. Resolution: The Data Protector facade and libfacade files are modified and
now the omnirpt command executes and displays the correct result. Change Request: QCCR2A57578: Symptom: The Data
Protector media files are not unloaded correctly if the media copy job is aborted. Resolution: The Data Protector Backup Media
Agent (BMA) binaries are modified to correctly handle the unloading of media, when the media copy job is aborted. Change
Request: QCCR2A57582: Symptom: The Data Protector AIX clients are disconnected after long periods of inactivity, and the
following error message is displayed: |Major| From: BSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to
Data Protector Inet named "" on host <hostname>. Ipc subsystem reports: "IPC Read Error System error: |10054| Connection
reset by peer" Resolution: The Data Protector Inet and omniinet.exe files are modified to enabled the TCP keepalive feature in
AIX platforms. The TCP keepalive feature is enabled on all platforms that support sockopt. Change Request: QCCR2A57584:
Symptom: A full backup session is displayed as an incremental session, when the backup is resumed. Resolution: The Data
Protector Backup Session Manager is modified to correctly handle backup sessions that are resumed. Change Request:
QCCR2A57599: Symptom: Data Protector documentation needs to be updated to indicate the correct Data Protector
replication configuration. Resolution: The Data Protector documentation is updated to correctly indicate the replication
configuration. Change Request: QCCR2A57629: Symptom: The Data Protector Detail Catalog Binary Files (DCBF) records
can get lost after a medium overwrite. Resolution: An issue has been fixed in Data Protector Backup and Copy&Consolidation
Session Managers (BSM/CSM) that were causing the Data Protector Internal Database (IDB) to lose DCBF records on
medium overwrite. Change Request: QCCR2A57647: Symptom: The Data Protector Oracle application integration backup
session fails with the following error message: RMAN-03009: failure of release command on dev_0 channel at <Date><Time>
ORA-03113: end-of-file on communication channel Recovery Manager complete. |Major| From: ob2rman@<oracle_client> ""
<Date><Time> External utility reported error. Resolution: The Data Protector liborasbt, orasbt.dll and Omnirc.tmpl files are
modified, and now the backup session completes successfully. Change Request: QCCR2A57686: Symptom: The Data
Protector command "omniofflr -forcedirect" fails to execute, and displays the following error message: |Critical| From:
6of32
9/14/20151:58PM
OMNIOFFLR@<hostname> "Offline Restore" Time: <Date><Time> Unknown option -forcedirect Resolution: The Data
Protector command "omniofflr" is modified to correctly execute without any errors. Change Request: QCCR2A57699: Symptom:
The Data Protector Access Control List (ACL) items are not restored correctly restored and do not correspond to the backed
up items. Resolution: The Data Protector vbda binaries are modified and the VxFS ACL support is also verified. The ACL items
are restored correctly. Change Request: QCCR2A57716: Symptom: Data Protector command "sanconf -configure" ends
abnormally during execution. Resolution: Data Protector command "sanconf -configure" is working and library gets properly
updated in the Data Protector graphical user interface (GUI). Change Request: QCCR2A57814: Symptom: The Data Protector
copy to Media Container Format (MCF) functionality does not export the catalog data correctly. Resolution: The Data Protector
"libob2ecdb" function is modified and now, the copy to MCF functionality correctly exports the complete catalog. Change
Request: QCCR2A57880: Symptom: The Data Protector Media Management Demon (service) (MMD) ends abnormally at the
end of each day. Resolution: The Data Protector MMD files are modified and the service is functioning correctly. Change
Request: QCCR2A57885: Symptom: The Data Protector Data Protector Virtual Environment Integration (VEPA) component
backs up the wrong folder, which has a previously used folder name. Resolution: The Data Protector vepalib binaries are
modified and the VEPA component backs up virtual machines from the correct folder. Change Request: QCCR2A57932:
Symptom: When multiple sessions are running in parallel, the Data Protector GUI fails with the following error: "IPC Read error
12:3017" Resolution: The Data Protector Cell Request Server (CRS) files are modified to function correctly when multiple
sessions are running in parallel. Change Request: QCCR2A57951: Symptom: The Data Protector MCF import from NDMP
media ends abnormally. Resolution: The Data Protector Media Session Manager is modified and now the import from MCF
media files, when media contains NDMP data succeeds. Change Request: QCCR2A57968: Symptom: The Data Protector
"omniofflr -idb" command ends abnormally when a B2D device is used. Resolution: The omniofflr binary is modified to
successfully execute the Data Protector "omniofflr -idb" command when a B2D device is used. Change Request:
QCCR2A57986: Symptom: The Data Protector backup session fails with the following error message: |Major| From:
BMA@<hostname> "" Time: <Date><Time> |90:51| \am-dp-one-1.l<name>\AMDD1/... Cannot write to device (JSONizer error:
Invalid inputs) Resolution: The Data Protector backup session is modified to complete successfully. Change Request:
QCCR2A57998: Symptom: The Data Protector Restore Media Agent (RMA) fails with the following error message: |Major|
From: CSM@<hostname> "" Time: <Date><Time> |61:1005| Got unexpected close from RMA on client.com. Resolution: The
Data Protector Restore Media Agent (RMA) is modified to complete successfully. Change Request: QCCR2A58002: Symptom:
The Data Protector GUI fails to restore the objects when the Object Mirror is performed with a tape device. Resolution: The
Data Protector is modified to correctly handle restore operations of mirrored objects. Change Request: QCCR2A58010:
Symptom: Session writing to catalyst stores often fails with the following error message: |Major|From: BMA@<hostname> ""
Time: <Date><Time> |90:51| \\<ip address>\<device>\976815ac... Cannot write to device (StoreOnce error: The object is
already locked and multiple open sessions not supported) Resolution: StoreOnceSoftware is modified to release items after
OB2_STOREONCESOFTWARE_SESSION_IDLE_TIMEOUT passes. Change Request: QCCR2A58036: Symptom: The Copy
Session Manager (CSM) fails when it uses a device that is already in use by another backup session. Resolution: The Copy
Session Manager (CSM) is modified to successfully complete the Object copy session. Change Request: QCCR2A58049:
Symptom: Backup to Catalyst stores fails with the following error message: |Major| From: BMA@<hostname> "" Time: <Date>
<Time> |90:51| \\|...| Cannot write to device (JSONizer error: Invalid inputs) Resolution: The xMA binary is modified to
successfully complete the backup session. Change Request: QCCR2A58066: Symptom: The Data Protector command
"omnidb -auditing -last 1 -detail" reports an error. Resolution: The Data Protector command "omnidb -auditing -last 1 -detail" is
modified to correctly execute without any errors. Change Request: QCCR2A58082: Symptom: When the "Restore As/Into"
option is used, the Data Protector restore session fails with the following error message: "Error - Details Unknown" Resolution:
The Database Session Manager (DBSM) is modified to function correctly. Change Request: QCCR2A58096: Symptom: After
upgrading to Data Protector 8.13, the Data Protector SG package fails to start. Resolution: The omnisv binary is modified to
correctly handle the Data Protector SG package. Change Request: QCCR2A58098: Symptom: Object with status
"Completed/Errors" are copied more than one time. Resolution: The Data Protector is modified to correctly copy objects with
status "Completed/Errors" with regards to the value of "Include only objects with number of copies less than" option. Change
Request: QCCR2A58142: Symptom: Data Protector source side deduplication backup session using Catalyst over Fiber
Channel configuration fails with the following error message: StoreOnce error: StoreOnce device offline, network error
occurred or secure communication failed while contacting the StoreOnce device Resolution: The bsm binary is modified to
correctly handle the Source side deduplication communication with the StoreOnce device. Change Request: QCCR2A58163:
Symptom: After an upgrade to Data Protector 7.03, the device serial number is not detected correctly. Resolution: The Data
Protector UMA and Devbra binaries are modified to correctly detect the device serial number. Change Request:
QCCR2A58166: Symptom: The Data Protector Backup Session Manager (BSM) ends abnormally during a backup session.
Resolution: The Data Protector Backup Session Manager (BSM) is modified to function correctly. Change Request:
QCCR2A58200: Symptom: The Data Protector Virtual Environment Integration backup session fails with the following error
message: |Critical| From: VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> No Objects found for backup.
Resolution: The Data Protector Virtual Environment Integration backup session is modified to complete successfully. Change
Request: QCCR2A58208: Symptom: In Data Protector 9.01 on HP-UX 11.31, the restore by query fails with the following error
message: Error: No matches found. Resolution: The Database Session Manager (DBSM) is modified to correctly handle the
pattern search. Change Request: QCCR2A58264: Symptom: The Data Protector restore session from catalyst gateway stops
responding. Resolution: The rsm binary is modified to correctly handle the Data Protector restore session. Change Request:
QCCR2A58285: Symptom: The Data Protector Internal Database (IDB) backup session fails with the following error message::
"Error reaching the database". Resolution: The facade library is modified to correctly handle the Data Protector Internal
Database (IDB) backup session. Change Request: QCCR2A58291: Symptom: The Data Protector GUI fails to display the
correct information about the used or available space for mediums. Resolution: The Media Management Daemon (MMD) and
facade library is modified to correctly handle the Data Protector GUI. Change Request: QCCR2A58304: Symptom: Data
Protector fails to report the DB2 related errors or warnings on time. For example, when the restore fails with the following error
message: |Normal| From: OB2BAR_DB2BAR@<hostname> "db2qdb" Time: <Date><Time> Starting DB2 restore of database
EBI on node 0 |Major| From: OB2BAR_DB2BAR@<hostname> "db2qdb" Time: <Date><Time> DB2 returned error:SQL1051N
7of32
9/14/20151:58PM
The path "/db2/QDB/sapdata0" does not exist or is not valid. SQLSTATE=57019 Resolution: The db2bar binary is modified to
correctly handle the Data Protector to display a warning when the target folder is not found. Change Request: QCCR2A58306:
Symptom: The Data Protector Backup Media Agent (BMA) and Backup Session Manager (BSM) fails to execute the
OB2MACHECKCAPACITY=1 omnirc variable. Resolution: The rsm binary is modified to correctly handle the Data Protector
"omnirc" variable. Change Request: QCCR2A58312: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) fails
with the following error message: |Major| From: VBDA@<hostname> "/CONFIGURATION" Time: <Date><Time> |81:145|
Automatic DR information could not be collected. Aborting the collecting of system recovery data. Resolution: The Data
Protector backup session is modified to complete successfully. Change Request: QCCR2A58322: Symptom: After successful
restore of the IBM DB2 Universal Database Server with Data Protector 8.13, rollforward recovery fails as some archive logs
are missing. Resolution: The db2arch binary is modified to correctly handle the rollforward recovery. Change Request:
QCCR2A58332: Symptom: The Data Protector backup session is unable to restart failed objects due to connection issues with
Inet, and the session fails with the following error message: |Major| From: BSM@<hostname> "" Time: <Date><Time> Restart
is not supported for specified session. Resolution: The facade library is modified to correctly handle the Data Protector backup
session. Change Request: QCCR2A58336: Symptom: Oracle backup session fails with the follwoing error message: |Normal|
From: OB2BAR_SBT_CHANNEL@<hostname> "" Time: <Date><Time> Starting OB2BAR Backup:
oracle_client.com:BARLIST<...>.dbf "Oracle8" |Major| From: BSM@<hostname> "BARLIST" Time: <Date><Time> |61:3003|
Lost connection to Data Protector Inet named "noname" on host oracle_client.com. Ipc subsystem reports: "IPC Read Error
System error: |10054| Connection reset by peer" |Normal| From: BSM@<hostname> "BARLIST" Time: <Date><Time>
OB2BAR application on "oracle_client.com" disconnected. Resolution: The bsm and omnib binaries are modified to prevent
multiple backup sessions at the same time. Change Request: QCCR2A58341: Symptom: The Data Protector "global" file on
UNIX systems includes unexpected strings. Resolution: Data Protector is modified to correctly handle the creation of a "global"
file. Change Request: QCCR2A58342: Symptom: Restore devices cannot be changed since the restore sessions always use
the original device. Resolution: The Restore Session Manager (RSM) was modified to successfully change the restore
devices. Change Request: QCCR2A58407: Symptom: Data Protector 7.03 MMA ends abnormally during a replication session
between D2D systems with the following error message: |Normal] From: MMA@<hostname> "" Time: <Date><Time> Loading
medium from slot "" |Major| From: CSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to MMA named "" on
host "" Ipc subsystem reports: "IPC Read Error System error: |10054| Connection reset by peer Resolution: The xMA binary is
modified to correctly handle the Data Protector D2D replication. Change Request: QCCR2A58414: Symptom: After the
upgrade to Data Protector 8.13, the StoreOnceSoftware daemon ends abnormally at startup. Resolution: Added OpenSSL
thread-safety into libipc, moved IPC initialization functions. Change Request: QCCR2A58437: Symptom: The Data Protector
VEPA_BAR ends abnormally with the following error message during the restore session: |Normal| From:
VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> Virtual Machine "": Virtual machine configuration uploaded
successfully. Assertion failed: px != 0, file S:\bin\NT\boost\... This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more information. |Major| From: RSM@<hostname> "" Time:
<Date><Time> |61:3003| Lost connection to OB2BAR restore DA named "" on host "". Ipc subsystem reports: "IPC Read Error
System error: |10054| Connection reset by peer" Resolution: The ViAPI library is modified to correctly restore the network
information. Change Request: QCCR2A58480: Symptom: Data Protector media scanning, barcode scanning, or import of
media may fail with the following error message: |65:73| Media Management daemon reports: "Internal error: DbaXXXX
functions." for SCAN, BARCODE SCAN, rarely even IMPORT Resolution: Data Protector is modified to successfully complete
the media scanning, barcode scanning, or import of media. Change Request: QCCR2A58512: Symptom: Data Protector fails to
correctly import the duplicate session ID. Resolution: The facade library is modified to successfully import the duplicate session
ID. Change Request: QCCR2A58530: Symptom: The Data Protector Microsoft Exchange Server 2007 integration restore
session fails with the following error message: |Critical| From: OB2BAR_MBV6-402@<hostname> "" Time: <Date><Time>
ESE subsystem or operating system reported error for "": 0xc7ff0bc7: destination name returned by server is invalid
Resolution: The dbsm binary is modified to successfully complete the restore from an earlier version of Data Protector. Change
Request: QCCR2A58609: Symptom: The Data Protector 9.02 "omnidbcheck -media_consistency" command reports false
positives. Resolution: The Data Protector "omnidbcheck" binary is modified to handle errors. Change Request:
QCCR2A58630: Symptom: When performing a large query to Media Management Daemon process (MMD), for example,
FUN_LISTREPOSITORY, the Data Protector Backup Session Manager (BSM) and Copy and Consolidation Session Manager
(CSM) stop responding. Resolution: The MMD binary is modified to correctly handle the Data Protector Backup Session
Manager (BSM) and Copy and Consolidation Session Manager (CSM). Change Request: QCCR2A58632: Symptom: During
the import of vCenter 5.5 update 1, the plugin registration fails with the following error message: Error (s) during registration
plugin : vCenter Version 5,0 is not supported using Angular GUI Resolution: The vmwaregre-agent.exe file is modified to
correctly handle the import of vCenter 5.5 update 1. Change Request: QCCR2A58642: Symptom: A significant amount of the
Media Management Daemon (MMD) time (~15%) is spent in querying the store information. Resolution: The Media
Management Daemon (MMD) is modified to avoid Backup Session Manager (BSM) fetching slots when the store information is
queried. Change Request: QCCR2A58693: Symptom: The Data Protector Internal Database (IDB) backup session issues
warning about the missing non-essential file: |Warning| From: OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time:
<Date><Time> A non-essential file cannot be found, backup continues Resolution: The Data Protector Internal Database (IDB)
backup session completes successfully. Change Request: QCCR2A58697: Symptom: The Data Protector "Recycle data and
catalog protection of failed source objects after successful copy" option does not function correctly. The terminated and failed
objects are not recycled after an object copy session. Resolution: The facade library is modified to correctly recycle failed
objects, if specified. Change Request: QCCR2A58706: Symptom: The Data Protector Backup Session Manager (BSM) and
Copy and Consolidation Session Manager (CSM) are not functioning correctly. Resolution: The Data Protector Backup
Session Manager (BSM) and Copy and Consolidation Session Manager (CSM) are modified to not end unexpectedly. Change
Request: QCCR2A58717: Symptom: The Data Protector backup session fails with the following error message: |Major| From:
BMA@<hostname> "" Time: <Date><Time> \90:51| \\...\VM\... Cannot write to device (StoreOnce error: Daemon is low on
memory, rejecting operations) Resolution: The StoreOnceSoftware binary is modified to count the buffered and cached
memory as free memory. Change Request: QCCR2A58751: Symptom: The Data Protector Import session returns no errors
8of32
9/14/20151:58PM
even if the DCBF file cannot be created. Resolution: The Data Protector is modified to report errors during import session
when the DCBF file cannot be created. Change Request: QCCR2A58778: Symptom: Unable to continue backup on mirrored
device when a new tape is inserted after a mount request, whereas final session status shows as completed. Resolution: The
Backup Session Manager (BSM) is modified to correctly handle the new tapes of source and mirror devices when a mount
request is issued for the mirrored device. Change Request: QCCR2A58781: Symptom: In the HP Data Protector GUI Restore
context, few directories are displayed as files. Resolution: The Data Protector GUI displays the correct filesystem information.
Change Request: QCCR2A58788: Symptom: The HP Data Protector Internal Database (IDB) backup session completes with
the following errors: |Critical| From: OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" <Date><Time> An internal error
occurred. Resolution: The postgres_bar.exe is modified to successfully complete the HP Data Protector Internal Database
(IDB) backup session. Change Request: QCCR2A58828: Symptom: The Data Protector "omnirpt" command ends abnormally.
Resolution: The Data Protector "omnirpt" command is modified to execute correctly. Change Request: QCCR2A58829:
Symptom: The Data Protector Virtual Environment Integration (VEPA) backup session fails with the following error message:
"Aborting connection to BSM. Abort code -1." Resolution: The Data Protector Virtual Environment Integration backup session
completes successfully. Change Request: QCCR2A58848: Symptom: The backup session terminates immediately when
device filtering is enabled and devfilters file is created on the Cell Manager (containing a list of logical devices and
corresponding tags), if the omnirc "OB2DEVICEFILTER" variable is not set on one of the clients. Resolution: The Backup
Session Manager (BSM) is modified to correctly handle backup sessions with device filtering enabled and without setting the
"OB2DEVICEFILTER" omnirc variable on clients. Change Request: QCCR2A58889: Symptom: Scanning StoreOnce media
returns errors for media containing failed objects. Resolution: The Data Protector Copy Session Manager (CSM) is modified to
correctly handle catalog protection for failed objects. Change Request: QCCR2A58898: Symptom: After upgrading to Data
Protector 9.02, the Restore Media Agent (RMA) ends unexpectedly during the object copy session with the following error
message: |Major| From: CSM@<hostname> "" Time: <Date><Time> |61:1005| Got unexpected close from RMA on
mahostname Resolution: The Media Agent (MA) module is modified to correctly handle the object copy session. Change
Request: QCCR2A58899: Symptom: The Mount.bat script does not start on the Data Protector 8.13 Windows Cell Manager.
Resolution: All session managers are modified to correctly start the Mount.bat script on the Data Protector 8.13 Windows Cell
Manager. Change Request: QCCR2A58903: Symptom: The Data Protector GUI stops responding when trying to restart or
resume the session. Resolution: The Data Protector GUI is modified to function correctly when trying to restart or resume the
session. Change Request: QCCR2A58928: Symptom: The replication session fails with the following error message: |Major|
From: CSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to MMA named " on host "". Ipc subsystem
reports: "IPC Read Error System error:|10054| Connection reset by peer Resolution: The Data Protector replication session
completes successfully. Change Request: QCCR2A58972: Symptom: The Data Protector backup session fails with Media
Management Database (MMD) ending abnormally: |Warning| From: BSM@<hostname> "" Time: <Date><Time> Cannot
establish connection with the Media Management database. Backup is waiting for the Media Management database to be
reachable. Resolution: The Data Protector facade library is modified to correctly handle the backup session. Change Request:
QCCR2A58984: Symptom: Any failed backup session without any device associated with it results as an "Interactive" device in
the "device_flow" report. Resolution: The Internal Database (IDB) schema is modified to correctly filter out entries without
associated device. Change Request: QCCR2A59084: Symptom: The Data Protector 7.03 Media Agent (MA) fails with the
following error message: |Warning| From: BMA@<hostname> "" Time: <Date><Time> The device "" could not be opened
("Device could not be approached") Resolution: The Data Protector omnirc variable is modified to set the SCSI protocol
version as follows: OB2FORCE_AIX_FC_SCSI_VER = 0 //SCSI Vesion 0 OB2FORCE_AIX_FC_SCSI_VER = 1 //SCSI Vesion
1 (also default if not set or different then 0,1,2) OB2FORCE_AIX_FC_SCSI_VER = 2 //SCSI Vesion 2 Change Request:
QCCR2A59134: Symptom: After an upgrade from Data Protector 7.03 to 8.1, there seems to be inconsistencies with the
internal database: upgraded IDB has problem when browsing files in the Data Protector GUI. Resolution: The upgrade
procedure is modified to correctly handle browsing of files in the Data Protector GUI. Change Request: QCCR2A59171:
Symptom: The Data Protector Media Session Manager (MSM) ends abnormally during a tape import. Resolution: The Data
Protector facade library is modified to correctly handle the Media Session Manager (MSM) during a tape import. Change
Request: QCCR2A59216: Symptom: The Data Protector backups sessions become unresponsive, if connection to the Media
Management Daemon (MMD) is lost: |Major| From: BSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to
MMD named "noname" on host <hostname>. Ipc subsystem reports: "IPC Read Error System error: |10054| Connection reset
by peer This happens if session managers are unresponsive for a while and unable to respond to MMD messages. Resolution:
The Media Management Daemon (MMD) is modified to communicate with session managers asynchronously, improving
behaviour in presence of temporarily unresponsive sessions. Change Request: QCCR2A59221: Symptom: After an upgrade
from Data Protector 9.01 to 9.02, the backup of some Virtual Machines (VMs) fail with the following error message: |Major|
From: VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> Could not read block from "". Resolution: The Data Protector
Virtual Environment Integration (VEPA) is modified to correctly handle the backup of some VMs. Change Request:
QCCR2A59272: Symptom: The Data Protector 9.0 restore session of a Data Protector 7.x Microsoft Exchange Server backup
using the Volume Shadow Copy Service (VSS) technology cannot create path to fileset. Resolution: The DMA binary is
modified to successfully handle the Data Protector 9.0 restore session. Change Request: QCCR2A59282: Symptom: The use
of "Include only objects with number of copies less than" filter does not work for Cross Cell Replication. Resolution: The
following point is added in the Limitations section of Cross CM Replication topic: The "Include only objects with number of
copies less than" option is not supported for the Cross Cell Manager Replication procedure. Change Request: QCCR2A59337:
Symptom: An interactive object copy session from SOS store of Exchange full backup session to the tape device does not
display the correct percentage of copied objects. Resolution: The RMA and CSM binaries are modified to correctly reflect the
percentage completed in the Data Protector GUI. Change Request: QCCR2A59350: Symptom: The Data Protector "omnidbutil
-show_locked_devs" or "omnidbutil -free_locked_devs" command uses the local hostname instead of the Cell Manager's name.
Resolution: The Data Protector "omnidb" utility is modified to use the virtual hostname instead of the local name and filter
locks. Change Request: QCCR2A59351: Symptom: After an upgrade from Data Protector 7.03 to 9.02, the following error
occurs: # omnidb -WinFS ""' -session <date><time> -catalog Protection Owner Group Size |B| Time Path
============================================== d----w---- -2 -2 0 <date><time>/batch ----r----- -2 -2 8294454
9of32
9/14/20151:58PM
<date><time>/batch/BGInfo.bmp ----r----- -2 -2 599 <date><time>/batch/SendMail.ps1 ----r----- -2 -2 751 <date><time>/batch

/eng_snapshot.cmd ----r----- -2 -2 4117 <date><time>/batch/engel.bgi No catalog available for WinFS "" within session <date>
<time>. Resolution: The Data Protector "dbsm" binary is modified to remove the "No catalog available . . ." error, if the catalog
is already listed from the new DCBF. Change Request: QCCR2A59381: Symptom: The Data Protector 8.1x and 9.0x "omnirpt
-report session_statistics" command reports erroneous values. Resolution: The sessions_statistics report is modified to display
correct values. Change Request: QCCR2A59388: Symptom: Replication session stops responding, if there is an error: |Major|
From: CMA@<hostname> "" Time: <Date><Time> |90:54| \\ |...| Cannot open device (StoreOnce error: The object is already
locked and multiple open sessions not supported, or the server is unable to lock any more objects due to resource constraints)
Resolution: The csm and bsm binaries are modified to print error message when the object is already locked. However, the
replication finishes. Change Request: QCCR2A59397: Symptom: The Data Protector "omnicellinfo -dlinfo" command output is
incomplete. While all backup sessions in the cell have a pre-script assigned, the "omnicellinfo -dlinfo" fails to display the script
for a subset of the backup specifications (IDB, VEAgent). Resolution: The Data Protector "omnicellinfo" binary is modified to
include pre-exce scripts for IDB and VEAgent backup specifications. Change Request: QCCR2A59401: Symptom: The "omnib
-datalist <wrong_name>" does not generate a session ID, while the "omnib -mssql_list <wrong_name>" does (as other
bar_lists do too). Resolution: The Backup Session Manager (BSM) is modified to generate session ID when non-existent
datalist name is used. Change Request: QCCR2A59504: Symptom: Protection of failed/aborted objects are not set to "none"
after the failure of the objects. Resolution: The Backup Session Manager (BSM) is modified to correctly reset the protection of
the failed/aborted objects to none. Note: An omnirc option "ClearAbortedObjectsProtectionAfterBackup=2" is introduced to
remove the protection of the filesystem objects. Change Request: QCCR2A59533: Symptom: The setup routine does not
properly share the directory structure. Resolution: The "setupdll" library file is modified to correctly handle the creation of
Installation Server (IS) depot share during cluster-aware CM installation and IS component selection. Change Request:
QCCR2A59599: Symptom: The Data Protector "Session list" report takes a long time to generate. Resolution: The "Session
list" report is optimized to take significantly less time to generate. Change Request: QCCR2A59610: Symptom: LUNs migrated
from EVA to 3PAR results in following error with 3PAR SAP R/3 ZDB integration backups: |Major| From: SMISA@<hostname>
"SMISA" Time: <Date><Time> |236:9211| No valid credentials were found to perform the requested operation on the following
volume: Volume WWN: 6001438009B006CE0000C00000DE0000 Resolution: The smisa binary is modified to correctly handle
the backup session when disks are migrated from EVA to 3PAR. Change Request: QCCR2A59617: Symptom: The restore of
DB2 database using omnir fails when db2cli is started as the root user. The Data Protector restore session using omnir as the
DB2 user fails with the following error message: |Major| From: OB2BAR_DB2BAR@<hostname> "" Time: <Date><Time> DB2
returned error: SQL1092N "ROOT" does not have the authority to perform the requested command or operation. Resolution:
The omnir binary is modified to correctly handle the restore session by accepting db2 user for starting db2cli. Change Request:
QCCR2A59637: Symptom: The Media sessions deleting unprotected media (daily maintenance jobs) are displayed as
"Completed" in the Monitor or Internal Database (IDB) context of Data Protector GUI but are in fact still running and working
(they do not stop responding). Such sessions in IDB have start-date but no end-date, and cannot be viewed in detail for
"Deleted" status in the Monitor or double-click Data Protector GUI to view a pop-up with the "session already completed, refer
to IDB for details ..." message. Resolution: The Data Protector Media Session Manager (MSM) is modified to correctly report
the status of delete-unprotected-media sessions. Change Request: QCCR2A59652: Symptom: The Data Protector Database
Session Manager (DBSM) restore browsing performance on large environments does not function correctly. Resolution: The
Data Protector Database Session Manager (DBSM) is modified to improve the restore browsing performance. Change
Request: QCCR2A59694: Symptom: The Data Protector StoreOnce object copy session fails with the following error message:
|Major|From: RMA@<hostname> "" Time: <Date><Time> |90:54| \\|...| Cannot open device (StoreOnce error: The object is
already locked and multiple open sessions not supported, or the server is unable to lock any more objects due to resource
constraints) Resolution: The Data Protector StoreOnceSoftware binary is modified to correctly handle the StoreOnce object
copy session. Change Request: QCCR2A59700: Symptom: The backup session of the SL3000 library fails after an upgrade
from Data Protector 6.21 to Data Protector 8.13, because wrong serial numbers are returned for the SL3000 library devices.
Resolution: The UMA and Devbra binaries are modified, and now backup of the SL3000 library is successful after an upgrade
from Data Protector 6.21 to Data Protector 8.13. Change Request: QCCR2A59704: Symptom: Backups of the Internal
Database (IDB) were slow because the logs contained additional and unwanted information about purged sessions, and these
logs could not be deleted. Resolution: The Data Protector IDB files were modified, and now the backup time is as expected.
Change Request: QCCR2A59705: Symptom: The Data Protector command "omnirpt -report obj_lastbackup -datalist" was
displaying incorrect results, and the last backup information was duplicated. Resolution: The facade.dll (Windows) and
libfacade (Unix) files were modified, and now the command "omnirpt -report obj_lastbackup -datalist" is displaying the correct
information. Change Request: QCCR2A59725: Symptom: The Graphical User Interface (GUI) is not displaying the correct
directories if a time interval of 3 months is selected for the backup sessions. Resolution: The Data Protector "dbsm" and
"facade" files are modified, and now the browsing of the directories in the GUI functions correctly. Change Request:
QCCR2A59754: Symptom: The Data Protector Session Statistics and Client Statistics reports display different values for the
same parameters, when the same time frame is set. Resolution: The "dbscripts" files are modified, and now the Session
Statistics and Client Statistics reports display consistent values for the same parameters. Change Request: QCCR2A59773:
Symptom: The IDB restore session (restoring configuration files) with the "File conflict handling: Overwrite" option enabled,
does not restore some of the configuration files correctly. Resolution: The Data Protector "postgres_bar.exe" file is modified,
and now the IDB restore session restores all files correctly. Change Request: QCCR2A59797: Symptom: The restore session
of virtual machines (VMs) with disks that belong to different data stores, restores all the disks to the same data store.
Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified, and now the restore session of virtual
machines (VMs) with disks that belong to different data stores restores all the disks to correct location. Change Request:
QCCR2A59799: Symptom: The "List of sessions" report displays backup specifications that were not selected in the report
criteria. Resolution: The Data Protector "facade" files are modified, and now the "List of sessions"_ _report displays the correct
backup specifications. Change Request: QCCR2A59810: Symptom: The Data Protector object copy session is successful, but
overwrites the object protection properties of the target media. Resolution: The Data Protector csm.exe files are modified to
change the protection properties of the source object correctly. Change Request: QCCR2A59831: Symptom: The Data
10of32
9/14/20151:58PM
Protector command "omnidbutil -clear" does not display the correct end-time in the session report, when unsuccessful sessions
are set as "Failed". Resolution: The Data Protector command "omnidbutil -clear" is modified, and now it displays the correct
end-time for the "Failed" sessions in the sessions reports. Change Request: QCCR2A59839: Symptom: The Data Protector
Cell Request Server process (service) (CRS) ends abnormally. Resolution: The Data Protector_ "_crs" files are modified, and
now the Cell Request Server (CRS) service is executed correctly. Change Request: QCCR2A59852: Symptom: The Sybase
integration backup in the Data Protector version 8.13 is executed over one stream instead of the specified number of streams.
This is because the Backup Session Manager incorrectly parses the number of streams from the barlist specification.
Resolution: The Data Protector Backup Session Manager is modified, and now the Sybase integration backups are executed
correctly. Change Request: QCCR2A59902: Symptom: The Data Protector restore chain was incorrectly executed when the
"Owner" of the Data Protector Virtual Environment integration (VEPA) backup session with quiescence, was set in the Windows
client. Resolution: The Data Protector Virtual Environment Integration Agent (VEPA) is modified, and now the restore chain
calculation is functioning correctly. Change Request: QCCR2A59929: Symptom: The order of the pre-allocated media during
allocation is not preserved in the Data Protector Media Management Daemon process (service) (MMD). Resolution: The Data
Protector facade files of the CSM are modified, and now the order of the pre-allocated media is preserved for strict pools.
Change Request: QCCR2A59931: Symptom: The Data Protector Sybase SQL Server integration restore session takes a long
time to respond, and has to be stopped. Resolution: The dacmn library files were modified, and now the Sybase SQL Server
integration restore is successful. Change Request: QCCR2A59936: Symptom: After an upgrade from Data Protector 7.03 to
Data Protector 9.01, tapes that were present in the Non-Appendable media pool were used for standalone device backups.
Resolution: The facade and_ _libfacade files are modified, and now tapes that were present in the Non-Appendable media
pool will not be used for standalone device backups. Change Request: QCCR2A60040: Symptom: The Data Protector Internal
Database (IDB) backup sessions fail with uniqueness violation issues after changes to the database. Resolution: The Data
Protector "dbscripts" file is modified, and now the IDB backup sessions are successful. Change Request: QCCR2A60055:
Symptom: The Data Protector restore session of the DB2 database version 10.5 fails, and the archive logs are written to the
wrong path. Resolution: The Data Protector db2arc, db2bar, and db2arch files are modified, and now during the restore the
archive logs are written to the right path, and the restore session completes successfully . Change Request: QCCR2A60157:
Symptom: The Data Protector Solaris backup session fails with the following error: "Symptoms:|12:5| Internal error in ("/da/bda
/posix.c $Rev: 41393 $ $Date:: Time: <Date><Time>) => process ended" Resolution: The Data Protector Volume Backup Disk
Agent (VBDA) is modified, and Solaris backup session is successful. Change Request: QCCR2A60176: Symptom: The import
session of the Catalog Media Data from the Media Container Format (MCF) files in Data Protector 8.13, ends unexpectedly.
Resolution: The Data Protector libfacade, libormapper, facade, and ormapper files are modified, and now the import session of
the Catalog Media Data from the Media Container Format (MCF) files is successful. Change Request: QCCR2A60206:
Symptom: After an upgrade to Data Protector 8.13 build 206 GR patches to the Manager-of-Managers (MOM) environment,
the Media Management Daemon process (MMD) reports the following error messages during the restore session: |Critical|
From: RSM@<hostname> "" Time: <Date><Time> Error when trying to reach the Media Management daemon, in line 1138,
file rslotmreq.c. Media Management daemon subsystem reports: "Medium not found." |Major| From: RSM@<hostname> ""
Time: <Date><Time> |61:1005| Got unexpected close from MMD on <hostname>. |Major| From: RSM@<hostname> "" Time:
03/05/2015 12:29:46 PM |61:1002| The RMA named "<RMA name>" on host <hostname> reached its inactivity timeout of
8400 seconds. The agent on host will be shutdown. Resolution: The Data Protector Internal Database (IDB) is modified to
function correctly when media is not found in the Media Management Database (MMDB). Change Request: QCCR2A60249:
Symptom: The Data Protector 8.12 Restore Media Agent (RMA) on the HP-UX 11.31 fails when a large filesystem is used,
because the RMA allocates a large amount of memory during the restore. Resolution: The Data Protector Restore Media Agent
(RMA) is modified to handle restores of large filesystems, and the restore session is successful. Change Request:
QCCR2A60434: Symptom: The Data Protector Copy and Consolidation Session Manager (CSM), Backup Session Manager
(BSM), Backup media Agent (BMA) end unexpectedly with heap corruption fault on Windows Server 2012 R2 Cell Manager
(CM). Resolution: The Data Protector Copy and Consolidation Session Manager does not end unexpectedly. Change Request:
QCCR2A60458: Symptom: Currently licenses are not properly recognized if the kernel parameter for HP-UX 11.31 systems has
been set to "expanded_node_host_names=1". Resolution: Licenses are properly recognized if the kernel parameter for HP-UX
11.31 systems has been set to "expanded_node_host_names=1". Change Request: QCCR2A60461: Symptom: Since upgrade
to Data Protector 9.02, the Data Protector graphical user interface (GUI) takes long time to expand the list of devices.
Resolution: The dpidb_upgrade.sql was modified and the device list expansion speed has been significantly improved. Change
Request: QCCR2A60484: Symptom: The Data Protector 9.02 Virtual Environment integration (VEPA) restore fails with the
following error message: |Critical| From: VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> Virtual Machine 'name':
Error restoring item \...\ Resolution: Modifications were made in invoking revertToSnapshot and revertToCurrentSnapshot APIs
and code added to display in debug logs soap fault strings. The failed restore session will have more debugging information of
issue. Change Request: QCCR2A60496: Symptom: Media scan and backup sessions fail with "STATUS_VOLUME_IN_USE" if
debug level is set to 1-98 (or less) or debugs are disabled. With debug level set to 1-99 or more media scan and backup
sessions work as expected. Resolution: Media scan and backup sessions are working with or without debugs. Change
Request: QCCR2A60501: Symptom: The "Session Queuing Time" in "Restore Statistics" on Data Protector 9.02 on Windows
Server 2012 R is not correct. It counts the session runtime instead of the Queuing time. Resolution: Data Protector BSM files
are modified to show actual queuing time in the "Session Queuing Time" in "Restore Statistics". Change Request:
QCCR2A60503: Symptom: While backing up Exchange 2010 via MS VSS integration, all incremental backups are sent to disk
and then copied to tape. Most of the incremental backups copied to tape are currently unrestorable. Resolution: The problem
occurs because of the call to the "omnidbutil -check_graph". The code tries to correct restore chains, but in case of
integrations the restore chain is not used and the data should not be changed. The object_version_service.cpp is modified and
restore from incremental backups copied to tape to be successful Change Request: QCCR2A60562: Symptom: The offline
restore of the Data Protector IDB fails with the following error message: |Critical| From: OMNIOFFLR@<hostname> "Offline
Restore" Time: <Date><Time> cannot open obrindex.dat file for parsing. (Backup copy of Recovery Index Log file not defined
in global option.) Resolution: The Data Protector "omniofflr" command is modified to properly handle multiple daIDs within
single "-daid" option. The offline restore of the Data Protector IDB is successful. Change Request: QCCR2A60566: Symptom:
11of32
9/14/20151:58PM
The HP Data Protector "Debug.log" file keeps growing with the following message: |gbs_running_bar| variable value
exceeded, type=global name=glSmWaitForNewBackupClient value=40 default=30 Resolution: Data Protector CS module is is
modified to remove excessive and repeated logging when integration agent does not connect in time interval specified with the
"SmWaitForNewBackupClient" global variable. Change Request: QCCR2A60578: Symptom: Advanced schedules for hourly
SQL backups are not starting. Resolution: The Data Protector JCE is modified to function correctly when starting scheduled
sessions. Change Request: QCCR2A60602: Symptom: The Data Protector message "Copy session SessionID started." is not
displayed in the "omnidb -session SessionID -report" command output. Resolution: Data Protector's Copy Session Manager
(CSM) is modified to properly store session ID in the session log of interactive copy sessions. Change Request:
QCCR2A60606: Symptom: After installing Data Protector 9.02 patch bundle (build 102), the following is reported: |Critical|
From: BDA-NET@<hostname> "" Time: <Date><Time> Cannot handshake with Media Agent (Details unknown.) => aborting.
Resolution: The Core modules in Windows and Unix environment is modified and valid connections are no longer dropped.
Change Request: QCCR2A60651: Symptom: Data Protector scheduler is not properly enabled after exiting maintenance mode
(the "omnisv -maintenance -stop" command is executed). Scheduled sessions do not start after stopping the maintenance
mode unless the DP services are restarted. Resolution: Data Protector CS module is modified to properly initialize scheduler
after exiting maintenance mode. Change Request: QCCR2A60674: Symptom: When a file within an object is selected for
restore, the backup versions displayed are not complete if longer search intervals are selected. Explicitly specifying a shorter
timeframe shows the other backups from which the restore should be possible. Resolution: Data Protector's CS module has
been modified to include backup object versions of copies if originals are missing in the Internal Database (IDB). Change
Request: QCCR2A60705: Symptom: The information about no filesystems for restart is displayed inconsistently and with the
wrong severity: |Major| From: BSM@<hostname> "" Time: <Date><Time> |61:2051| All mount points on host "" are excluded.
Nothing will be backed up. Resolution: The BSM module is modified to consistently report message for all type of objects, and
with _correct_ report severity. The error message is displayed correctly during resume session. Change Request:
QCCR2A60773: Symptom: When medium is full then used capacity is displayed as 100% but if medium has some free space
then it doesn't show correct capacity. The problem appears with all LTO4 media. C:\Users\Administrator>omnimm -list_media ""
-detail Object name: gkc-bkp:/D 'D: |New Volume|' Object type: WinFS Object status: Completed Started: <Day><Date>
<Time> Finished: <Day><Date><Time> Object size: 12449395 KB Backup type: Full Protection: Permanent Catalog retention:
Same as data protection Access: Private Number of warnings: 0 Number of errors: 0 SessionID: <session_ID> Device name:
<device_name> Copy ID: <Copy_ID> (Orig) Encrypted: No Resolution: The Data Protector CS module is modified and the
command line (CLI)) "omnimm" command and the Data Protector user interface (GUI) display correct sizes for the used and
maximum medium capacity. Change Request: QCCR2A60791: Symptom: Normally the configured replication runs via "gw1".
The "gw2" should only be used in case of an outage of the "gw1". During a Data Protector 9.02 post-backup replication
session and forced connection issue on the "gw1" host, replications of storeonce stores on B6200 fail if one of two configured
gateways is not reachable. Resolution: The Data Protector CSM module is modified and missing check for disabled gateways
is added while starting MMA during the session. Change Request: QCCR2A60800: Symptom: After an upgrade to Data
Protector 8.13, the Data Protector backup session of the Internal Database (IDB) intermittently fails with the following error
message: "Check of the Internal Database consistency failed" The "omnidbcheck -media_consistency -fix" command displays
the status of DCBF (presence and size) as "failed", however the "omnidbcheck -bf" command reports "OK" status. Resolution:
The Data Protector "omnidbcheck -bf" command executes correctly. Change Request: QCCR2A60804: Symptom: Scheduled
backup sessions in the Advanced Scheduler do not start and the following is logged in the server.log file: <Date><Time>,897
ERROR [<hostname>jce.dispatcher.executionmanagement.PriorityJob] (JceDispatcherScheduler_Worker-2) no device info
Spec name: linuxapp5-complete-FS, job type: EXECUTE_DP_BACKUP, priority: 3000, pause Enabled: false, session ID:
unknown, status: QUEUED, device(s): || Resolution: The Data Protector JCE is modified to function correctly when starting
scheduled sessions. Change Request: QCCR2A60825: Symptom: The Single Server Edition (SSE) license is not correctly
processed by the Data Protector Cell Request Server process (CRS). Resolution: The Data Protector SM and CS modules are
modified and the Single Server Edition (SSE) license is properly processed by the Data Protector Cell Request Server process
(CRS). Change Request: QCCR2A60828: Symptom: The Data Protector Detail Catalog Binary Files (DCBF) are not saved for
the media that are not protected regardless if the possible catalog retention is longer that data protection. Resolution: Modified
the flag to let IDB backup all DCBF files. The Internal Database (IDB) backup session is now backing up files properly. Change
Request: QCCR2A60838: Symptom: Performance problems with the Data Protector Internal Database (IDB) related queries:
/opt/omni/bin/omniobjcopy -copylist "" -scheduled -debug 1-200,t:1000 copy.txt The session is checking one FileLibrary for
objects to copy. There is only 1 FileDepot in that Library. That depot contains 1 object that is expired for days and therefore not
to be copied. Resolution: The Data Protector IDB files are modified and Protection, time-frame and media filters are performed
on the database-side to speed up the initial copy job object version selection phase. Change Request: QCCR2A60856:
Symptom: The Data Protector Volume Restore Disk Agent (VRDA) fails with the following error message: |Critical| From:
VRDA@<hostname> "" Time: <Date><Time> Missing of data block detected, expecting block 3224! Session fails because of
the Input/output error. Resolution: The Data Protector MA module is modified and the backup session are executed
successfully also changing mediums during each session. Change Request: QCCR2A60929: Symptom: After changing the
backup from StoreOnce Catalyst to StoreOnce VTL through FC, restore session fails due to device error with the following
error messages: |Major| From: RMA@<hostname> "" Time: <Date><Time> |90:52| Tape "" Cannot read from device (|87| The
parameter is incorrect.) |Major| From: RMA@<hostname> "" Time: <Date><Time> |90:53| Tape "" Cannot seek to requested
position (|87| The parameter is incorrect.) Resolution: The Data Protector GUI, facade library, rsm, and csm binaries are
modified to correctly handle the restore session from StoreOnce Catalyst to StoreOnce VTL through FC. Change Request:
QCCR2A60995: Symptom: The Data Protector Network Data Management Protocol (NDMP) Server Integration restore
session to an alternate volume fails with the following error message: |Normal| From: RMA-NDMP@<hostname>t "" Time:
<Date><Time> RESTORE : ERROR: All files must be restored to the same volume on the file system |Major| From:
RMA-NDMP@<hostname> "" Time: <Date><Time> |242:33| NDMP Restore operation has failed. Resolution: The bsm binary
is modified, and the omnirc variable "OB2_NDMPSKIPCONFIG" is added to successfully complete the Data Protector Network
Data Management Protocol (NDMP) Server Integration restore session. Change Request: QCCR2A61026: Symptom: Data
protector fails with the following StoreOnce errors when trying to access the corrupt media stored in StoreOnce Software
12of32
9/14/20151:58PM
(SOS) stores: "Cannot read from device, internal error..." Resolution: The Data Protector Object Copy Session Manager (CSM)
and backup Session Manager (BSM) are modified to undo empty slots if Media Agent (MA) fails to initialize the SOS or B2D
media. Change Request: QCCR2A61074: Symptom: The VCenter appliance Advanced-GRE fails with Data Protector 9.02 on
Windows systems. The "loading..." screen is displayed continuously. Resolution: The Ang-GRE is modified to to ensure that
the VCenter appliance Advanced-GRE functions correctly on Windows systems.. Change Request: QCCR2A61075: Symptom:
The ObjectstoreClientCli.exe fails to contact the disk to disk (D2D) backup devices. Resolution: Data Protector includes
support for OSCLT V6, to ensure that the ObjectStoreClientCLI can reach disk to disk (D2D) devices. Change Request:
QCCR2A61082: Symptom: While creating an advanced schedule, the Data Protector fails to select a time earlier than the
current time. Resolution: The Data Protector Advanced Scheduler is modified to correctly set start time of scheduled session.
Change Request: QCCR2A61114: Symptom: The Data Protector "omnidbrestore -autorecover -skiprestore -save" command on
HP-UX 11.31 systems ends abnormally. Resolution: The Data Protector "omnidbrestore" command is modified to increase the
buffer of options strings by 500 times. Change Request: QCCR2A61171: Symptom: Robotics configs file update fails when
there are large number of slots (10,000) Resolution: Internal store serialization buffer is enlarged to accommodate stores with a
large number of slots. Change Request: QCCR2A61196: Symptom: If the Data Protector omnirc variables are not properly set,
the "Rollforward" option for the Data Protector IBM DB2 UDB Integration restore session fails with the following error message:
SQL1273N An operation reading the logs on database "T01" cannot continue because of a missing log file "S0000529.LOG"
on database partition "0" and log stream "0" Resolution: The HP Data Protector 9.00 Integration Guide is updated with steps
on how to set the environment variables in the omnirc file before restoring to a DB2 database using the automatic Roll forward.
Change Request: QCCR2A61262: Symptom: The Data Protector backup session fails with the following error message:
|Critical| From: BSM@<hostname> "" Time: <Date><Time> "|61:4001| Error trying to reach the database, in line 1337, file "".
Database subsystem reports: "|12:1166| Internal Database error. The IDB services are most probably not running." Resolution:
The facade library is modified to successfully complete the Data Protector backup session. Change Request: QCCR2A61299:
Symptom: The Data Protector Backup Session Manager (BSM) on HPUX systems fails in semop() call due to the semmnu
kernel limit. Resolution: The HP Data Protector 9.00 Installation guide is modified to correctly handle the semmnu kernel limit.
Change Request: QCCR2A61420: Symptom: Copy sessions allocate more gateways in source SOS store than destination
gateways are configured. The gateways on the source side show the status "running" but no data transfer is displayed for
them. In fact the maximum value of configured gateways can be allocated leaving no more free gateways for backup sessions
and causing them the queue/fail. Resolution: The Data Protector documentation was updated accordingly. Change Request:
QCCR2A61431: Symptom: After an upgrade to Data Protector 9.03, the Novell OES restore session fails and the Volume
Restore Disk Agent (VRDA) reports the following error message: |Critical| From: VRDA@<hostname> "" Time: <Date><Time>
|210:1| Loader: Cannot find module liboes_vrda.so. Resolution: The Volume Restore Disk Agent (VRDA) is modified to
successfully complete the Novell OES NSS volume File system restore session. Change Request: QCCR2A61497: Symptom:
During the object copy session, the Data Protector Copy and Consolidation Session Manager process (CSM) fails with the
following error message: |Critical| From: BMA@<hostname> "" Time: <Date><Time> |12:5| Internal error in ("/ma/xma/bma.c
$Rev: 40744 $ $Date:: <Date><Time>:6263) => 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. |Major| From: CSM@<hostname> "" Time: <Date><Time>
|61:3003| Lost connection to BMA named "" on host <hostname>. Ipc subsystem reports: "IPC Read Error System error:
|10054| Connection reset by peer" Resolution: The Data Protector Copy and Consolidation Session Manager (CSM), Backup
Session Manager (BSM), and Backup Media Agent (BMA) are modified, and now the object copy session is successfully
completed. Change Request: QCCR2A61598: Symptom: The Data Protector GUI fails when the object copy session is open in
the Monitor context. Resolution: The Data Protector GUI is modified to function correctly. Change Request: QCCR2A61614:
Symptom: The Data Protector documentation should be updated with File Conflict Handling availability for Data Protector
Network Data Management Protocol (NDMP) Server Integration restore sessions. Resolution: The Data Protector online Help
topic "F1 Help: Filesystem Restore Destination" was updated with the following: File Conflict Handling is not available for
NDMP restore as NDMP can be configured in only two ways; Perform NDMP restore or not. Hence, the Overwrite button is
selected but greyed out in the GUI. Change Request: QCCR2A61703: Symptom: Any Data Protector session scheduled
through the "Advanced Schedule" is never submitted/executed. Resolution: The Data Protector Advanced Scheduler is
modified to execute submitted jobs via scheduler without any problems. Change Request: QCCR2A61757: Symptom: The Data
Protector documentation should be updated with limitations to be considered while setting up a new replication specification,
so that the Data Protector GUI functions correctly. Resolution: The HP Data Protector Concepts Guide and the HP Data
Protector 9.00 Deduplication technical white paper is updated with the following limitations: 1. The devices selected for
replication must be capable of replication. 2. The source and target device types must be the same. 3. Within the StoreOnce
library, the source and target devices must belong to different stores. 4. The source device must be configured in at least one
backup specification. Change Request: QCCR2A61758: Symptom: The Data Protector documentation needs to be updated
regarding the cluster device files (cDSFs). Resolution: The following footnote is added in the HP Data Protector 9.00 Zero
Downtime Backup and Instant Recovery Support Matrix for HP P6000 EVA Disk Array Family Using SMI-S Agent: For HP-UX
11.31 and ServiceGuard cluster, new device special files (DSF) are supported for LVM only. cDSF is not supported. Change
Request: QCCR2A61761: Symptom: The firewall closes the connection between the Data Protector Backup Session Manager
(BSM) and Inet after a period of inactivity. Resolution: The TCP keep alive has been made a default in all Data Protector
connections. Previously, you could use environment (omnirc) variables to enable and configure keep alive:
OB2IPCKEEPALIVE = 1 # enable keep alive OB2IPCKEEPALIVETIME = 600 # windows specific: how many seconds of
inactivity to allow before sending keep alive packet (actually ACK) OB2IPCKEEPALIVEINTERVAL= 600 # windows specific:
how many seconds between two keep alive packets These variables are still respected, only the default has been changed to
"enabled". Change Request: QCCR2A61794: Symptom: The Data Protector raw disk restoration fails with the following error
messages: |Major| From: RRDA@<hostname> "" Time: <Date><Time> |85:300| /dev/rnewlv01vg02 Object is a mounted
filesystem => not restored. |Minor| From: RRDA@<hostname> "" Time: <Date><Time> /dev/rlv01vg02 Section has not been
restored! Resolution: Raw disk restore (disk image) restore on AIX is successful. Change Request: QCCR2A61822: Symptom:
The Data Protector object copy session started with the Data Protector command-line interface (CLI) "omniobjcopy" command
13of32
9/14/20151:58PM
completes immediately without error messages. Resolution: In case that flag glLimitInitGatewayExpansion and max being -1
(not initialized) we set it to default (1). Change Request: QCCR2A61826: Symptom: The Data Protector Media Management
Daemon (MMD) process (service) spends substantial time persisting its internal state to disk (the mmd.ctx file). Resolution:
The frequency with which the Data Protector Media Management Daemon (MMD) process persists its internal state to disk is
now configurable. Change Request: QCCR2A61827: Symptom: The Data Protector Media Management Daemon (MMD)
process spends substantial time in reloading cell info files on the Data Protector Media Management Database (MMDB)
server. Resolution: The Data Protector Media Management Daemon (MMD) is modified to reload cell info files only when
changed and/or after a certain configurable period has passed to reduce the load. Change Request: QCCR2A61828:
Symptom: The Data Protector Media Management Daemon (MMD) process needs to be restarted for changes in global
options to take effect. Resolution: The Data Protector "mmd -reload_options" command is modified to successfully reload the
global options without a restart. Change Request: QCCR2A61923: Symptom: The object copy session is displayed as
completed on the Data Protector GUI when the "omnistat" command is still running. Resolution: Data Protector Copy Session
Manager (CSM) is modified to correctly display the copy or replication or consolidation session statistics only after the catalog,
data, and media protection change procedure is completed. Change Request: QCCR2A62025: Symptom: After an upgrade to
Data Protector 9.03, enabling Encrypted Control Communication (ECC) fails with the following error message: |59:53346|
Interprocess communication problem. Details: Certificates generation for one of the clients might not be complete in time.
Consequently, the current connection to the Cell Manager might got broken. Resolution: The omnigencert.pl script is modified
to successfully enable Encrypted Control Communication (ECC). Change Request: QCCR2A62131: Symptom: Data Protector
documentation should be updated with information on how to restore the Internal Database (IDB) database on a different Cell
Manager Host. Resolution: Data Protector documentation now includes information on how to restore the Internal Database
(IDB) database on a different Cell Manager Host. Change Request: QCCR2A62142: Symptom: The Data Protector "omnimm
-delete_unprotected_media" command fails to delete the blank slots in Backup to Disk (B2D) libraries. Resolution: The msm
binary is modified to ensure that the "omnimm -delete_unprotected_media" command successfully deletes the blank slots in
Backup to Disk (B2D) libraries. Change Request: QCCR2A62293: Symptom: The Data Protector documentation needs to be
updated regarding the procedure on how to set up the modular ServiceGuard (SG) package. Resolution: The ServiceGuard
section in the HP Data Protector Installation Guide is modified to address the procedure for setting up the modular SG
package. Change Request: QCCR2A62326: Symptom: The Data Protector "omnib2dinfo -list_objects -b2ddevice" command
reports the following error message: Cannot get the B2D information of device "DEVNAME". Resolution: The Data Protector
storeonceinfo binary is modified to list all store items without reporting any errors including the items with zero creation and
modification time. Change Request: QCCR2A62340: Symptom: The Granular Recovery Extension (GRE) requests in the
Advanced GRE GUI are not visible if vCenter is imported using the IP address in the Cell Manager. The Advanced Granular
Recovery Extension (GRE) Web Plug-in does not display the error message sent by the GRE agent. Resolution: The VMware
GRE Agent binary is modified to correctly view the GRE requests in the Advanced GRE GUI if vCenter is imported using the IP
address in the Cell Manager. The Data Protector Advanced Granular Recovery Extension (GRE) Web Plug-in is modified to
correctly report the error message from the agent. Change Request: QCCR2A62526: Symptom: An unexpected error appears
when running backup session through Japanese Data Protector graphical user interface (GUI) to StoreOnce device.
Resolution: The Data Protector backup session completes successfully. Change Request: QCCR2A62632: Symptom: The
Data Protector documentation needs to be updated regarding moving from a Clustered Data Protector Cell Manager (CM)
configuration to a Single Cell Manager environment. Resolution: The Data Protector documentation is updated accordingly.
Change Request: QCCR2A62751: Symptom: The Data Protector VMware GRE documentation needs to be updated regarding
ownership, ACLs, and file attributes. Resolution: The Data Protector documentation is updated accordingly. Change Request:
QCCR2A62799: Symptom: The Data Protector documentation needs to be updated regarding the incremental backup
functionality for Hyper-V 2012. Resolution: The HP Data Protector Integration Guide > Virtualization > Hyper-V > Integration
Concepts > Backup considerations was updated with the following: Incremental backup of virtual disks, when the virtual
machine is running, is possible only with Microsoft Hyper-V Server 2012. Change Request: QCCR2A62914: Symptom: Data
Protector fails to establish connection with StoreOnce using Catalyst over Fiber Channel because number of initiators on
Media Agent reached the hard limit of 16 connections. Resolution: The HP Data Protector 9.00 Product Announcements,
Software Notes, and References is modified to address the issue. Change Request: QCCR2A62975: Symptom: The Data
Protector documentation needs to be updated about the certificate requirements for StoreOnce Software (SOS) when the
Encrypted Control Communication (ECC) is enabled. Resolution: The Data Protector Installation Guide is updated to indicate
the certificate requirements for StoreOnce Software (SOS) when the Encrypted Control Communication (ECC) is enabled.
Change Request: QCCR2A63076: Symptom: The Data Protector copy to tape session causes loss of catalog protection of
backup sessions that were part of the copy activities. Resolution: The Data Protector Copy and Consolidation Session
Manager (CSM) issue has been fixed that lead to source objects losing catalog protection if any of the target objects failed
during object copy. DPLNX_00317: Change Request: QCCR2A54772: Symptom: The Data Protector "omnidbcheck"
command fails with corrupted Detailed Catalog Binary Files (DCBF) error reporting different header and physical size.
Resolution: The Data Protector "omnidbcheck" utility is modified to function correctly. DPLNX_00316: Change Request:
QCCR2A49228: Symptom: The Data Protector 8.0 GUI incorrectly displays the media allocation order. Resolution: The Cell
Server module is modified to correctly display the media allocation order in the Data Protector 8.0 GUI. Change Request:
QCCR2A50234: Symptom: Expanding objects in the Data Protector GUI restore context takes a long time. Resolution: The
database queries are modified to improve the performance of expanding objects in the Data Protector GUI restore context.
Change Request: QCCR2A50896: Symptom: The Data Protector Internal Database (IDB) consistency check fails. Resolution:
The Data Protector omnidbcheck binary is modified to not report the Internal Database (IDB) as inconsistent under low
memory conditions. Change Request: QCCR2A51260: Symptom: After an upgrade to Data Protector 8.1, the backup session
of NSS volumes on Novell OES 11 ends abnormally with the following error message, if the folder and filenames contain
non-English characters: |Normal| From: VBDA@<hostname> "" Time: ABORTED Disk Agent for <hostname>:/media
/nss/VOL1 "" |Critical| From: BSM@<hostname> "" Time: <Date><Time> |61:4001|Error reading the database, in line 1764,
file bcsmutil.c. Database subsystem reports: "Internal error: DbaXXXX functions." Resolution: The facade and ormapper
binaries are modified to correctly handle the Data Protector backup session of NSS volumes. Change Request:
14of32
9/14/20151:58PM
QCCR2A51326: Symptom: The import of media-related catalog data from Media Container Format (MCF) files fail with the
following error: 1241. Resolution: The facade binary is modified to correctly handle copy of a catalog from source to target
cell in Media Container Format (MCF). Here, the source object positions are relinked to target object for duplicate ones.
Change Request: QCCR2A51421: Symptom: The Data Protector "omnimm -delete_unprotected_media" command stops
responding. Resolution: The Data Protector Internal Database (IDB) schema is modified to improve the performance of the
Data Protector "omnimm -delete_unprotected_media" command. Change Request: QCCR2A51680: Symptom: The Data
Protector restore session fails with the following error message: |Major| From: RSM@<hostname> Time: <Date><Time>
Restore of object XXXXX:PS1.YY named "" may be incomplete because some medium is missing. Resolution: The Data
Protector Media Session Manager is modified to successfully complete the restore session. Change Request:
QCCR2A51705: Symptom: The Data Protector GUI fails with the following error message when some of the Data Protector
Network Data Management Protocol (NDMP) server integration objects are expanded: More than one line returned by a
subquery used in an Expression. Resolution: The Data Protector Internal Database (IDB) schema is modified for proper
functioning of the GUI when the Data Protector Network Data Management Protocol (NDMP) server integration objects are
expanded. Change Request: QCCR2A51880: Symptom: The Data Protector Internal Database (IDB) backup session fails
with the following error message: |Critical| From: OB2BAR_POSTGRES_BAR@<hostname> "" Time: <Date><Time> An
internal error occurred. Resolution: The postgres_bar.exe file is modified to correctly handle the Data Protector Internal
Database (IDB) backup session. Change Request: QCCR2A51881: Symptom: The Data Protector 8.1 backup session fails
with the following error message: |Normal| From: BMA@<hostname> "" Time: <Date><Time> STARTING Media Agent ""
|Normal| From: BMA@<hostname> "" Time: <Date><Time> Loading medium from slot \\media_agent.com\... |Major| From:
BMA@<hostname> "" Time: <Date><Time> |90:54| \\media_agent.com\... Cannot open device (StoreOnce error: StoreOnce
device offline, network error occurred or secure communication failed while contacting the StoreOnce device) |Major| From:
BMA@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to BMA named "" on host media_agent.com. Ipc
subsystem reports: "IPC Read Error System error: |10054| Connection reset by peer" |Normal| From: BMA@<hostname> ""
Time: <Date><Time> STARTING Media Agent "" This loop will continue until the session is aborted. Resolution: The bsm
binary is modified to correctly handle the Data Protector 8.1 backup session. Change Request: QCCR2A52063: Symptom: All
tapes are not displayed when the Data Protector 8.1 "omnimm -list_scratch_media" command is executed. Resolution: The
Internal Database (IDB) module is modified to correctly display all tapes when the Data Protector 8.1 "omnimm
-list_scratch_media" command is executed. Change Request: QCCR2A52223: Symptom: When the Data Protector "omnirpt
-repot dl_info" command is executed on HP-UX 11.31 IA 64 system, the output does not display Microsoft SQL, Oracle, or the
file systems. Resolution: The dbsm binary is modified to correctly execute the "omnirpt -report dl_info" and "omnirpt -report
dl_sched" commands, and display the complete output. Change Request: QCCR2A52578: Symptom: After an upgrade from
Data Protector 6.21 to 8.x in a Linux Manager-of-Managers (MoM) environment, the media consistency checks fail on the
Cell Manager. Resolution: The Data Protector omnidbcheck functionality is modified to correctly return the media
consistency check report. Change Request: QCCR2A52592: Symptom: The Data Protector "omnirpt -report obj_lastbackup"
command fails with the following error message: Error creating the report "Interactive": Bad file format. System error: Syntax
error at line 1, column 170. Expected 'token->type= =token_string || token->type==token_number', got EOF. Near: ''
Resolution: The dbsm binary is modified to correctly execute the Data Protector "omnirpt -report obj_lastbackup" command.
Change Request: QCCR2A52604: Symptom: The Data Protector 6.21 Centralized Media Management Database (CMMDB)
stops responding. Resolution: The facade binary is modified to correctly handle the Data Protector Centralized Media
Management Database (CMMDB). Change Request: QCCR2A52660: Symptom: During the execution of Data Protector
"omnidbutil -purge_daily" command, the Internal Database (IDB) records "orphan" DCBF_INFO entries and their
corresponding Detail Catalog Binary Files (DCBF) from disk. Resolution: The omnidbutil binary is modified to clean up
invalid Detail Catalog Binary Files (DCBF) records from Internal Database (IDB) and their corresponding files from disk.
Change Request: QCCR2A52664: Symptom: The Data Protector 8.1 "Object copies" and "Object's latest backup" reports fail
to list the Virtual Machine (VM) name in the Mountpoint field. Resolution: The Data Protector omnirc variable
"OB2_RPT_VEPA_MOUNTPOINT_TO_VMPATH=1" is set to correctly list the Virtual Machine (VM) name in the Mountpoint
field. Change Request: QCCR2A52780: Symptom: After an upgrade to Data Protector 8.11 on Windows Server 2008, the
Data Protector object copy session from File Library to Tape fails with the following error message: |Critical| From:
CSM@<hostname> "" Time: <Date><Time> No objects to copy. The session will abort. |Normal| From: CSM@<hostname>
"" Time: <Date><Time> Resolution: The facade binary is modified to copy objects from the File Library to tape. Change
Request: QCCR2A53142: Symptom: When querying reports using the Data Protector "omnirpt" command on Windows Server
2008 R2 up to a certain timeframe, the report gets truncated and displays (null) at the bottom of the page. Resolution: The
facade binary is modified to correctly handle the Data Protector "omnirpt" command. Change Request: QCCR2A53228:
Symptom: The Data Protector backup session on HP-UX 11.31 IA64 fails with the following error message: |Major| From:
BSM@<hostname> "" Time: <Date><Time> Internal error. Allocation from library failed. The Media Management daemon
reports: "Medium not found." Resolution: The facade binary is modified to correctly handle the Data Protector backup session
on HP-UX 11.31 IA64. Change Request: QCCR2A53330: Symptom: While copying objects from a restarted session, the
following error message is displayed: |Critical| From: CSM@<hostname> "" Time: <Date><Time> |62:1001| Specified device
for the object not found. |Major| From: CSM@<hostname> "" Time: <Date><Time> FAILED copy of "" from session <Date>
<Time> Resolution: The csm binary is modified to skip resumed object versions without catalog during the restore or object
copy. Change Request: QCCR2A53433: Symptom: The Data Protector "omnirpt -report single_session" command does not
calculate the correct object status. Resolution: The facade binary is modified to correctly calculate the session object states
completed with errors. Change Request: QCCR2A53449: Symptom: After an upgrade from Data Protector 6.20 to 8.1, the
Data Protector "Session per client report" does not display the correct information. Resolution: The dbsm binary is modified
to correctly handle the Data Protector "Session per client report". Change Request: QCCR2A53663: Symptom: After an
upgrade from Data Protector 7.0 to 8.11, changing the data or catalog protection on a single object in the Data Protector GUI
15of32
9/14/20151:58PM
changes the protection for both the original and copy object. Resolution: The Data Protector GUI is modified to change data
or catalog protection only on a selected object. Change Request: QCCR2A53775: Symptom: The Data Protector "omnidbutil
-purge -dcbf" command takes a long time to complete. Resolution: The Data Protector Internal Database (IDB) scripts are
modified to ensure improved performance during daily maintenance. Change Request: QCCR2A53783: Symptom: The Data
Protector 8.11 Session flow report does not mark queuing sessions and statistics reports as blue color. Sometimes, the
queuing statistics reports appear incorrectly. Resolution: The facade binaries are modified to correctly handle queuing
sessions and statistics reports. Change Request: QCCR2A53884: Symptom: When the Data Protector 8.12 "omnidbutil-purge
-daily" command is executed, the following error message is displayed: Operation failed. Resolution: The omnidbutil binary
is modified to correctly execute the Data Protector "omnidbutil -purge -daily" command. Change Request: QCCR2A54030:
Symptom: The backup of Data Protector 8.01 Internal Database fails. Resolution: The postgres_bar.exe binary file is
modified to successfully backup the Data Protector Internal Database. Change Request: QCCR2A54071: Symptom: The
email notification for the Data Protector Internal Database (IDB) backup is not readable when using the Japanese language.
Resolution: The Data Protector Internal Database (IDB) backup now uses one codepage for all messages. Change Request:
QCCR2A54093: Symptom: The Data Protector reporting command "omnirpt" fails with the following error message: /opt/omni
/bin/omnirpt -report session_errors -timeframe 800 800 Error creating the report "Interactive": File/directory not found. System
error: |2| No such file or directory. Resolution: The libfacade and facade binaries are modified to correctly execute the Data
Protector reporting command "omnirpt". Change Request: QCCR2A54195: Symptom: The Data Protector GUI becomes
unresponsive and takes a long time when objects in the restore context are expanded. Resolution: The Data Protector GUI is
modified to function correctly when objects in the restore context are expanded. Change Request: QCCR2A54215: Symptom:
The Data Protector GUI restore context fails for an incremental (Incr1) backup and displays the media of a full backup
session. Resolution: The Restore Session Manager (RSM) is modified to select a media copy for restore, if the copy exists.
Change Request: QCCR2A54250: Symptom: The Data Protector Internal Database (IDB) backup session fails with the
following error message: |Major| From:OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date><Time> Cannot
parse DBSM message (Details unknown.) |Critical| From: OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date>
<Time> An internal error occurred. Resolution: The facade.dll file is modified to correctly handle the Data Protector Internal
Database (IDB) backup session. Change Request: QCCR2A54256: Symptom: The Data Protector backup and object copy
sessions fail with the following error message: |Critical| From: BSM@<hostname> "" Time: <Date><Time> Cannot
synchronize the Media Management and Catalog database. The session will terminate. Resolution: The Data Protector is
modified to minimize Media Management and Catalog database synchronization failures. Change Request: QCCR2A54260:
Symptom: The Data Protector restore session fails with the following error message: |Normal| From: RSM@<hostname> ""
<Date><Time> Restore session "" started. =========================== Session aborted!
=========================== Resolution: The rsm and dbsm binaries are modified to function correctly during a
restore session. Change Request: QCCR2A54302: Symptom: The Data Protector object copy session ends abnormally after
installing the Data Protector 8.12_202 Cell Server and Core patches. Resolution: The Data Protector Copy and Consolidation
Session Manager (CSM) is modified to function correctly during object copy sessions. Change Request: QCCR2A54328:
Symptom: The restore from multiple segments using the Data Protector Volume Restore Disk Agent (VRDA) takes longer
duration. Resolution: The rsm binary is modified to correctly handle the restore from multiple segments. Change Request:
QCCR2A54476: Symptom: The "Single session" and "List Sessions" reports display different backup success rates.
Resolution: The reporting functionality is modified to display consistent values in the "Single session" and "List Sessions"
reports. Change Request: QCCR2A54633: Symptom: The output of the Data Protector "omnirpt session_objects" command
for the VEAgent fails to display VM names in the mount point field. Instead, it displays the UUID when the
"OB2_RPT_VEPA_MOUNTPOINT_TO_VMPATH" variable is set to 1. Resolution: The facade library is modified to correctly
display the VM name in the mount point field. Change Request: QCCR2A54656: Symptom: After an upgrade to Data
Protector 8.12, the "omnirpt -report session_statistics" command displays unrealistic high values as follows: Data Written
|GB|: 4473589651.61 <=== wrong value Resolution: The reporting functionality is modified to display real values in the
"session_statistics" report. Change Request: QCCR2A54681: Symptom: The Data Protector Daily Purge deletes sessions
with object versions that are still protected. Resolution: The Data Protector Daily Purge functionality is modified to behave
correctly. Change Request: QCCR2A54751: Symptom: After an upgrade to Data Protector 8, the backup sessions report the
following warning message: "A non-essential file cannot be found, backup continues". Resolution: The non-essential list is
modified to exclude the missing Session Manager Binary Files (SMBF) and ensure that the backup behaves correctly.
Change Request: QCCR2A54772: Symptom: The Data Protector "omnidbcheck" command fails with corrupted Detailed
Catalog Binary Files (DCBF) error reporting different header and physical size. Resolution: The Data Protector
"omnidbcheck" utility is modified to function correctly. Change Request: QCCR2A54826: Symptom: The Data Protector
protected media in the Internal Database must not loose links to the Detailed Catalog Binary Files (DCBF). Resolution: The
Data Protector Daily Purge functionality is modified to function correctly. Change Request: QCCR2A54856: Symptom: The
Data Protector "omnidb -session SessionID -purge" command fails for replication sessions with the following error message:
Internal error: DbaXXXX functions. Resolution: The purging sessions functionality is modified to correctly handle replication
sessions. Change Request: QCCR2A55011: Symptom: The media with protected objects is not protected after an import
operation. Resolution: The facade library is modified to protect media with protected objects after an import operation.
Change Request: QCCR2A55068: Symptom: The Data Protector Restore Session Manager (RSM) ends abnormally when
trying to restore from an incremental backup with an expired full backup. Resolution: The Data Protector facade library is
modified to successfully restore the selected data without any Restore Session Manager (RSM) failures. Change Request:
QCCR2A55079: Symptom: The Detailed Catalog Binary Files (DCBF) are corrupted, which reports different header and
physical size. Resolution: The Data Protector "omnidbcheck" command is modified to correctly handle the Detailed Catalog
Binary Files (DCBF). Change Request: QCCR2A55709: Symptom: The csm allocates several gigabytes of memory and stops
responding. Resolution: The csm binary is modified for all types of automated copy jobs to reduce memory and CPU usage.
16of32
9/14/20151:58PM
DPLNXBDL_00903: Change Request: QCCR2A48840: Symptom: On a file system, the Data Protector enhanced incremental
backup session backs up unwanted additional files. Resolution: The Data Protector Volume Backup Disk Agent (VBDA) is
modified to correctly handle the enhanced incremental backup sessions. Change Request: QCCR2A51458: Symptom: Import
of the Data Protector Network Data Management Protocol (NDMP) server object spanning multiple media fails with the
following error message: "object version exists" Resolution: The Data Protector Media Session Manager (MSM) is modified
to correctly handle reconstruction of sequence numbers from the media.log data file. This is controlled by the omnirc variable
"OB2_GENSEQ_SM". Change Request: QCCR2A51905: Symptom: The Data Protector "omniofflr -idb -autorecover"
command fails with the following error message: |Normal| From: OMNIOFFLR@hostname "" Time: <Date><Time> Scanning
obrindex.dat: preparing for restore... |Major| From: OMNIOFFLR@hostname"" Time: <Date><Time> cannot select session for
restore. (No valid successfully completed backup session in the log.) Resolution: The Data Protector "omniofflr" command is
modified to correctly display logs and/or sessions for restore. Change Request: QCCR2A52094: Symptom: The Data
Protector 7.01 backup session completes with the "Completed/Failures" status even though there are no messages with the
level higher than the warning displayed in the session report. Resolution: The Data Protector 7.01 is modified to correctly
handle backup sessions, without any failures. Change Request: QCCR2A53188: Symptom: The Data Protector 7.03 Oracle
integration backup session on Windows Server 2008 fails with the following error message: |Major| From:
ob2rman@<hostname> "" Time: <Date><Time> The database reported error while performing requested operation.
RMAN-00571: RMAN-00569: ERROR MESSAGE STACK FOLLOWS RMAN-00571: RMAN-03009: failure of allocate
command on dev_0 channel at <Date><Time> ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library Resolution: The Data Protector Secure Socket Layer (SSL) libraries
are modified to correctly unload at the end of every backup. NOTE: Restart the Oracle services to begin with a clean state.
Change Request: QCCR2A53589: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) reports the following
segmentation fault: # ./vbda -vol /opt/app -out /dev/null -profile -debug 1-999,T:1000,C:51200 VBDA.DBG >
/tmp/vbda_w_debug.txt Segmentation fault (core dumped)85 (kB), done: 0 (%) Resolution: The Data Protector Volume
Backup Disk Agent (VBDA) is modified to correctly handles backup of path names longer than 1024. Change Request:
QCCR2A53697: Symptom: After upgrading from Data Protector 8.1 to Data Protector 8.11, Advanced Scheduler does not
allow creation of incremental schedules for Exchange Single Mailbox Backup. Resolution: The Data Protector GUI is
modified to correctly handle the creation of incremental schedules for Exchange Single Mailbox Backup within Advanced
Scheduler. Change Request: QCCR2A53852: Symptom: The Data Protector online/internal virtual disk is deleted during the
restore session. Resolution: Data Protector is modified to correctly handle the "restore as" operation of individual disks.
Change Request: QCCR2A54060: Symptom: The restore process ends abnormally when restoring from an incremental
backup with an expired corresponding full version. Resolution: The Data Protector facade binary is modified to correctly
handle the expired object versions. Change Request: QCCR2A54143: Symptom: When using physical tapes, the following
Input Output error message is displayed: Cannot write to device |5| I/O error Resolution: The Data Protector Media Agent
(MA) binaries are modified to correctly handle the backup of physical or virtual tapes. Change Request: QCCR2A54682:
Symptom: After the restore session of IBM DB2 databases, the following message in the debug.log file is displayed: <Date>
<Time> OB2BAR_DB2ARCH.6384.0 |"/lib/cmn/unix.c $Rev:..| A.08.10 b154 execvp failed! (/db2/db2r27/db2_softwarebin
/db2level) errno=2 Arg list: db2level <Date><Time> OB2BAR_DB2ARCH.6376.0 |"/integ/db2/db2arch/main.c$Rev:...|
A.08.10 b154 |setDb2Lvl| Can not start /db2/db2r27/db2_softwarebin. Error: |2| Details unknown. Resolution: Data Protector
8.12 is modified to correctly handle the debug.log file. Change Request: QCCR2A54694: Symptom: The Data Protector Cell
Request Server (CRS) process does not respond when the schedule granularity is set to 1 minute. Resolution: The Data
Protector omnitrig binary is modified to correctly handle the overhead and limit schedule parsing to current day only. Change
Request: QCCR2A55199: Symptom: Data Protector Media Catalog File (MCF) import of Network Data Management Protocol
(NDMP) media fails. Resolution: Data Protector is modified to correctly handle the Network Data Management Protocol
(NDMP) MSG_FBIN. Change Request: QCCR2A55813: Symptom: Overwriting a medium created by a medium copy fails
with the following error message: |Major| From: MSM@<hostname> "" Time:<Date><Time> |65:99| Import failed with
possible cause: this media already has valid copy in DB. Resolution: The Data Protector Media Agent (MA) is modified to
correctly handle the "original medium ID" field of the medium header when overwriting the medium. Change Request:
QCCR2A55832: Symptom: Import of a tape from an old server to a new server fails with the following error message:
|Critical| From: MSM@<hostname> "" Time: <Date><Time> |65:6| Internal Database layer reports: "Internal error: DbaXXXX
functions." Resolution: The Data Protector facade library is modified to correctly import a tape from an old server to a new
server. Change Request: QCCR2A55982: Symptom: Data Protector stops responding if the the mirror device is disabled.
Resolution: Data Protector is modified to correctly handle the mirror device when it is disabled. Change Request:
QCCR2A56340: Symptom: The Data Protector Internal Database (IDB) backup does not back up Detailed Catalog Binary
Files (DCBF) or Session Message Binary Files (SMBF) when configuration backup fails with the following error message:
|Major| From : OB2BAR_POSTGRES_BAR@<hostname> "" Time :<Date><Time> The OS reported error while entering
/ProgramData/OmniBack/config/server/Sessions/checkpoint/test.txt : |5| Entrance is denied. |Critical| From :
OB2BAR_POSTGRES_BAR@<hostname> "" Time :<Date><Time> Backup of the object ConfigurationFiles failed
Resolution: The Data Protector Internal Database (IDB) is modified to correctly handle the backup. Change Request:
QCCR2A56429: Symptom: During catalog browsing in the restore context of the GUI for hosts with a large number of object
versions, the Database Session Manager (DBSM) becomes unresponsive sometimes for hours at a time. Resolution: The
Data Protector Database Session Manager (DBSM) and facade binaries are optimized to improve performance while dealing
with a large number of object versions. Change Request: QCCR2A56438: Symptom: The Data Protector vCD restore session
fails with the following error message: |Warning| From: VEPALIB_VCD@<hostname> "" Time: <Date><Time> vApp "": Error
updating network... Resolution: Data Protector is modified to correctly handle the vCD restore session. Change Request:
QCCR2A56542: Symptom: The Data Protector backup, object copy or consolidation session fails with the following error
message: |61:3003| Lost connection to MMD named "noname" on host cell.domain.com Ipc subsystem reports: "IPC Write
17of32
9/14/20151:58PM
Error System error: |10054| Connection reset by peer" Resolution: The Data Protector Media Management Daemon (MMD) is
modified to correctly handle timeouts when sending messages. Change Request: QCCR2A56568: Symptom: After upgrading
to Data Protector 8.13, the application integration backups may fail with the following error message: |Critical| From:
BSM@<hostname> "" Time: <Date><Time> |61:12019| Mismatch in backup group device and application database
concurrency configuration. Application database concurrency is 10. Resolution: The Data Protector Backup Session Manager
(BSM) binary is modified to correctly handle integration backups to an implicit gateway. Change Request: QCCR2A56617:
Symptom: When importing media from Data Protector 6.21, the restore fails with the following error message: |Critical| From:
RSM@<hostname> "" Time: <Date><Time> |62:1009| No objects to restore. Session will be aborted! Resolution: The Data
Protector facade library is modified to correctly handle the imported media from Data Protector 6.21. Change Request:
QCCR2A56630: Symptom: The Data Protector restore session of an OpenVMS system disk backup fails with the following
error message: |Major| From: RSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to Filesystem restore
DA named "" on host <hostname>. Ipc subsystem reports: "Bad message format." Resolution: Data Protector is modified to
correctly handle the restore session of an OpenVMS system disk backup. Change Request: QCCR2A56639: Symptom: An
unknown internal error occurs in the Data Protector GUI when connecting to few clients in the restore context. Resolution:
Data Protector is modified to correctly handle browsing of duplicate files by adding a global variable. Change Request:
QCCR2A56724: Symptom: The backup of Encrypting File System (EFS) encrypted files takes a long time. Resolution: The
Data Protector Volume Backup Disk Agent (VBDA) and Raw Backup Disk Agent (RBDA) binaries are modified to correctly
handle the backup performance of Encrypting File System (EFS) encrypted files. Change Request: QCCR2A56766:
Symptom: The Cell Request Server (CRS) randomly ends abnormally. Resolution: The Cell Request Server (CRS) is
modified to handle heavy load environments reliably. Change Request: QCCR2A56788: Symptom: The pre-upgrade Detail
Catalog Binary Files (DCBF) directory in IDB with "\ " in path name cannot be removed from Data Protector 8.0. Resolution:
The omnidbutil is modified to handle Detail Catalog Binary Files (DCBF) directory in IDB with "\ " in path name. Change
Request: QCCR2A56823: Symptom: The "storeonceinfo" command does not return any information about objects from the
(HW) store. Resolution: The "storeonceinfo" command is modified to correctly print logs to file. Change Request:
QCCR2A56845: Symptom: The HP Data Protector Granular Recovery Extension GUI display backups as "Staged" instead of
"Non-Staged". Resolution: The HP Data Protector "vmwaregre-agent" is modified to correctly display non-staged backups.
Change Request: QCCR2A56846: Symptom: The Data Protector Reporting functionality sending SNMP traps does not work
with the Data Protector 8.12 on HP-UX 11.31 systems. Resolution: The Data Protector "omnirpt" binary is modified to
correctly handle the SNMP traps. Change Request: QCCR2A56859: Symptom: Configuring report of "List of Pools" with
"Media in selected libraries" (Libraries Tab) section causes DBSM to end abnormally. If "Do not care" option is selected in
reporting, the report works correctly. Resolution: The Library filter is modified to function as expected for stand alone devices.
Change Request: QCCR2A56958: Symptom: The Data Protector "Change Data and catalog protection after successful copy"
object copy option changes the data and catalog protection even when the object copy session fails or terminates.
Resolution: The "csm" binary is modified to ensure that the data and catalog protection does not change after a failed copy.
Change Request: QCCR2A57013: Symptom: The MS SQL application integration backups, configuration or modification fails
with the following error: |Critical| From: BSM@<hostname> "" Time: <Date><Time> None of the Disk Agents completed
successfully. Session has failed. Resolution: The Data Protector "crs" binary is modified to correctly handle the integration
backups. Change Request: QCCR2A57081: Symptom: The Data Protector disk agent does not display a status message
when a pre/post-exec script is executed for an individual object. There is no such issue when the script is executed for a
session. Resolution: The Data Protector VBDA, VRDA, RBDA and RRDA modules have been modified to display the status
message when the pre/post-exec script is executed on a per object basis. Change Request: QCCR2A57090: Symptom: An
import session that has a duplicate session ID is unsuccessful. Furthermore, a restore session of such objects also fails, with
the following error: "object not found". Resolution: The Data Protector facade binaries have been modified and now the
importing of sessions that have duplicate session IDs are functioning correctly. Change Request: QCCR2A57185: Symptom:
The Data Protector graphical user interface (GUI) ignores the global parameter "MMFairLimit" and uses a default setting.
Resolution: The Data Protector GUI is modified to function correctly when setting the "MMFairLimit" parameter. Change
Request: QCCR2A57217: Symptom: The Data Protector VEAgent backup configuration, that has a Linux backup host on
RHEL 6.4 fails with the following unspecific error: "IDPMissingObjectException" Resolution: The Data Protector VEPA
post-install script is modified to correctly update the configuration files. Change Request: QCCR2A57220: Symptom: During
a disaster recovery backup session, the Volume Backup Disk Agent (VBDA) fails with the following error message: |Major|
From: VBDA@<hostname> "/CONFIGURATION" Time: <Date><Time> |81:145| Automatic DR information could not be
collected. Aborting the collecting of system recovery data. Resolution: The Data Protector VBDA module is modified and now
the backup session completes successfully. Change Request: QCCR2A57225: Symptom: The import process of the
StoreOnce D2D media is unsuccessful. Resolution: The Data Protector Media Agent is modified and the import of StoreOnce
D2D media is functioning correctly. Change Request: QCCR2A57235: Symptom: The Data Protector command "omnirpt
-report single_session -session -ascii" ends abnormally. Resolution: The Data Protector facade library is modified to correctly
handle the Data Protector command "omnirpt -report single_session -session -ascii". Change Request: QCCR2A57261:
Symptom: When configuring a backup specification for VMware Virtual Cloud Director, the following error is displayed: "Error
during vepa_util browse.*RETVAL*8010". Resolution: The ViAPI, vCloudAPI and vepalib_vcd files are modified to function
correctly during a backup session. Change Request: QCCR2A57268: Symptom: The Oracle server ends abnormally when
performing a backup in a cell, where maximum number of running sessions exceeds its limit. Resolution: The orasbt library
and crs files are modified to correctly handle the Oracle server when maximum number of cell server sessions exceed its
limit. Change Request: QCCR2A57375: Symptom: When trying to restore an object during replication, the media is locked
and marked as "poor media". Data Protector assumes that the media is unavailable. Resolution: The rma and bma binaries
are modified to ensure that the Data Protector media is available when trying to restore an object during replication. Change
Request: QCCR2A57386: Symptom: The Media Agent ends abnormally when reading from a catalyst store media: |Major|
18of32
9/14/20151:58PM
From: CSM@<hostname> "Interactive" Time: <Date><Time> |61:1005| Got unexpected close from CMA on <hostname>.
Resolution: The Media Agent is modified to correctly read from a catalyst store media. Change Request: QCCR2A57401:
Symptom: The Data Protector "Session_errors" report does not display the correct result if the "-hosts" option is specified.
The report always contains |Common| messages. Resolution: The Data Protector facade and libfacade files are modified to
function correctly when the "Session_errors" report is executed with the "-hosts" option. Change Request: QCCR2A57406:
Symptom: After a failed object, the status of successful object displays incorrect details. The object appears to be successful
but displays "Missing Media", which cannot be restored. Resolution: The bma, bsm, and rsm binaries are modified to
correctly display objects and restore them. Change Request: QCCR2A57442: Symptom: The Data Protector Media
Management Daemon (MMD) service ends abnormally, on an unexpected medium protection change request. Resolution:
The Data Protector MMD service is fixed to correctly handle an unexpected medium protection change request. Change
Request: QCCR2A57456: Symptom: If a Data Protector restore session is stopped, the devices are not unlocked. The device
selection process is replacing the unavailable devices multiple times. Resolution: The Data Protector Restore Session
Manager binaries are modified to correctly handle the unlocking of devices during a restore session. Change Request:
QCCR2A57458: Symptom: When a previously failed backup session is restarted, the following error message is displayed:
|Major| From: OB2BAR_SBT_CHANNEL@<hostname> "" Time: <Date><Time> Query incomplete/failed (Catalog not
loaded, message #1206 in set 12) Resolution: The Data Protector facade files are modified and the backup session
completes successfully. Change Request: QCCR2A57463: Symptom: After upgrading from Data Protector 8.0 to 8.12, all the
backup sessions using VTL drives fail with the following error message: |Warning| From: BMA@<hostname> "" Time:
<Date><Time> The device "" could not be opened("Serial number has changed") |Normal| From: BMA@<hostname> "" Time:
<Date><Time> Starting the device path discovery process. |Critical| From: BMA@<hostname> "" Time: <Date><Time>
|90:1004| Device address not found. Resolution: The Data Protector UMA and Devbra binaries are modified to correctly
recognize the VTL device serial numbers during a backup session. Change Request: QCCR2A57483: Symptom: The Data
Protector Command Line Interface (CLI) stops responding after import of a MCF file with the following error message:.
|Normal| From: MSM@<hostname> "" Time: <Date><Time> MCF import session ended. 1 out of 1 media successfully
imported. Resolution: The Data Protector Media Session Manager (MSM) is modified and the media container format (MCF)
import session completes successfully. Change Request: QCCR2A57503: Symptom: The restore session of a single file from
the Data Protector Internal Database (IDB) configuration, fails with the following error message: |Critical| From:
OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date><Time> An internal error occurred Resolution: The Data
Protector postgres integration client is modified to correctly restore single files from IDB configuration backup. Change
Request: QCCR2A57505: Symptom: The Data Protector reporting command "omnirpt -report hosts_statistics" does not
display the correct results for the Disk Agents (DA) objects. Resolution: The Data Protector facade and libfacade files are
modified and now the omnirpt command executes and displays the correct result. Change Request: QCCR2A57578:
Symptom: The Data Protector media files are not unloaded correctly if the media copy job is aborted. Resolution: The Data
Protector Backup Media Agent (BMA) binaries are modified to correctly handle the unloading of media, when the media copy
job is aborted. Change Request: QCCR2A57582: Symptom: The Data Protector AIX clients are disconnected after long
periods of inactivity, and the following error message is displayed: |Major| From: BSM@<hostname> "" Time: <Date><Time>
|61:3003| Lost connection to Data Protector Inet named "" on host <hostname>. Ipc subsystem reports: "IPC Read Error
System error: |10054| Connection reset by peer" Resolution: The Data Protector Inet and omniinet.exe files are modified to
enabled the TCP keepalive feature in AIX platforms. The TCP keepalive feature is enabled on all platforms that support
sockopt. Change Request: QCCR2A57584: Symptom: A full backup session is displayed as an incremental session, when
the backup is resumed. Resolution: The Data Protector Backup Session Manager is modified to correctly handle backup
sessions that are resumed. Change Request: QCCR2A57647: Symptom: The Data Protector Oracle application integration
backup session fails with the following error message: RMAN-03009: failure of release command on dev_0 channel at
<Date><Time> ORA-03113: end-of-file on communication channel Recovery Manager complete. |Major| From:
ob2rman@<oracle_client> "" <Date><Time> External utility reported error. Resolution: The Data Protector liborasbt,
orasbt.dll and Omnirc.tmpl files are modified, and now the backup session completes successfully. Change Request:
QCCR2A57686: Symptom: The Data Protector command "omniofflr -forcedirect" fails to execute, and displays the following
error message: |Critical| From: OMNIOFFLR@<hostname> "Offline Restore" Time: <Date><Time> Unknown option
-forcedirect Resolution: The Data Protector command "omniofflr" is modified to correctly execute without any errors. Change
Request: QCCR2A57699: Symptom: The Data Protector Access Control List (ACL) items are not restored correctly restored
and do not correspond to the backed up items. Resolution: The Data Protector vbda binaries are modified and the VxFS ACL
support is also verified. The ACL items are restored correctly. Change Request: QCCR2A57814: Symptom: The Data
Protector copy to Media Container Format (MCF) functionality does not export the catalog data correctly. Resolution: The
Data Protector "libob2ecdb" function is modified and now, the copy to MCF functionality correctly exports the complete
catalog. Change Request: QCCR2A57880: Symptom: The Data Protector Media Management Demon (service) (MMD) ends
abnormally at the end of each day. Resolution: The Data Protector MMD files are modified and the service is functioning
correctly. Change Request: QCCR2A57885: Symptom: The Data Protector Data Protector Virtual Environment Integration
(VEPA) component backs up the wrong folder, which has a previously used folder name. Resolution: The Data Protector
vepalib binaries are modified and the VEPA component backs up virtual machines from the correct folder. Change Request:
QCCR2A57932: Symptom: When multiple sessions are running in parallel, the Data Protector GUI fails with the following
error: "IPC Read error 12:3017" Resolution: The Data Protector Cell Request Server (CRS) files are modified to function
correctly when multiple sessions are running in parallel. Change Request: QCCR2A57951: Symptom: The Data Protector
MCF import from NDMP media ends abnormally. Resolution: The Data Protector Media Session Manager is modified and
now the import from MCF media files, when media contains NDMP data succeeds. Change Request: QCCR2A57968:
Symptom: The Data Protector "omniofflr -idb" command ends abnormally when a B2D device is used. Resolution: The
omniofflr binary is modified to successfully execute the Data Protector "omniofflr -idb" command when a B2D device is used.
19of32
9/14/20151:58PM
Change Request: QCCR2A57986: Symptom: The Data Protector backup session fails with the following error message:
|Major| From: BMA@<hostname> "" Time: <Date><Time> |90:51| \am-dp-one-1.l<name>\AMDD1/... Cannot write to device
(JSONizer error: Invalid inputs) Resolution: The Data Protector backup session is modified to complete successfully. Change
Request: QCCR2A57998: Symptom: The Data Protector Restore Media Agent (RMA) fails with the following error message:
|Major| From: CSM@<hostname> "" Time: <Date><Time> |61:1005| Got unexpected close from RMA on client.com.
Resolution: The Data Protector Restore Media Agent (RMA) is modified to complete successfully. Change Request:
QCCR2A58002: Symptom: The Data Protector GUI fails to restore the objects when the Object Mirror is performed with a
tape device. Resolution: The Data Protector is modified to correctly handle restore operations of mirrored objects. Change
Request: QCCR2A58010: Symptom: Session writing to catalyst stores often fails with the following error message:
|Major|From: BMA@<hostname> "" Time: <Date><Time> |90:51| \\<ip address>\<device>\976815ac... Cannot write to
device (StoreOnce error: The object is already locked and multiple open sessions not supported) Resolution:
StoreOnceSoftware is modified to release items after OB2_STOREONCESOFTWARE_SESSION_IDLE_TIMEOUT passes.
Change Request: QCCR2A58036: Symptom: The Copy Session Manager (CSM) fails when it uses a device that is already in
use by another backup session. Resolution: The Copy Session Manager (CSM) is modified to successfully complete the
Object copy session. Change Request: QCCR2A58049: Symptom: Backup to Catalyst stores fails with the following error
message: |Major| From: BMA@<hostname> "" Time: <Date><Time> |90:51| \\|...| Cannot write to device (JSONizer error:
Invalid inputs) Resolution: The xMA binary is modified to successfully complete the backup session. Change Request:
QCCR2A58066: Symptom: The Data Protector command "omnidb -auditing -last 1 -detail" reports an error. Resolution: The
Data Protector command "omnidb -auditing -last 1 -detail" is modified to correctly execute without any errors. Change
Request: QCCR2A58082: Symptom: When the "Restore As/Into" option is used, the Data Protector restore session fails with
the following error message: "Error - Details Unknown" Resolution: The Database Session Manager (DBSM) is modified to
function correctly. Change Request: QCCR2A58096: Symptom: After upgrading to Data Protector 8.13, the Data Protector SG
package fails to start. Resolution: The omnisv binary is modified to correctly handle the Data Protector SG package. Change
Request: QCCR2A58098: Symptom: Object with status "Completed/Errors" are copied more than one time. Resolution: The
Data Protector is modified to correctly copy objects with status "Completed/Errors" with regards to the value of "Include only
objects with number of copies less than" option. Change Request: QCCR2A58142: Symptom: Data Protector source side
deduplication backup session using Catalyst over Fiber Channel configuration fails with the following error message:
StoreOnce error: StoreOnce device offline, network error occurred or secure communication failed while contacting the
StoreOnce device Resolution: The bsm binary is modified to correctly handle the Source side deduplication communication
with the StoreOnce device. Change Request: QCCR2A58163: Symptom: After an upgrade to Data Protector 7.03, the device
serial number is not detected correctly. Resolution: The Data Protector UMA and Devbra binaries are modified to correctly
detect the device serial number. Change Request: QCCR2A58166: Symptom: The Data Protector Backup Session Manager
(BSM) ends abnormally during a backup session. Resolution: The Data Protector Backup Session Manager (BSM) is
modified to function correctly. Change Request: QCCR2A58200: Symptom: The Data Protector Virtual Environment
Integration backup session fails with the following error message: |Critical| From: VEPALIB_VMWARE@<hostname> ""
Time: <Date><Time> No Objects found for backup. Resolution: The Data Protector Virtual Environment Integration backup
session is modified to complete successfully. Change Request: QCCR2A58208: Symptom: In Data Protector 9.01 on HP-UX
11.31, the restore by query fails with the following error message: Error: No matches found. Resolution: The Database
Session Manager (DBSM) is modified to correctly handle the pattern search. Change Request: QCCR2A58264: Symptom:
The Data Protector restore session from catalyst gateway stops responding. Resolution: The rsm binary is modified to
correctly handle the Data Protector restore session. Change Request: QCCR2A58285: Symptom: The Data Protector Internal
Database (IDB) backup session fails with the following error message:: "Error reaching the database". Resolution: The
facade library is modified to correctly handle the Data Protector Internal Database (IDB) backup session. Change Request:
QCCR2A58291: Symptom: The Data Protector GUI fails to display the correct information about the used or available space
for mediums. Resolution: The Media Management Daemon (MMD) and facade library is modified to correctly handle the
Data Protector GUI. Change Request: QCCR2A58304: Symptom: Data Protector fails to report the DB2 related errors or
warnings on time. For example, when the restore fails with the following error message: |Normal| From:
OB2BAR_DB2BAR@<hostname> "db2qdb" Time: <Date><Time> Starting DB2 restore of database EBI on node 0 |Major|
From: OB2BAR_DB2BAR@<hostname> "db2qdb" Time: <Date><Time> DB2 returned error:SQL1051N The path "/db2/QDB
/sapdata0" does not exist or is not valid. SQLSTATE=57019 Resolution: The db2bar binary is modified to correctly handle the
Data Protector to display a warning when the target folder is not found. Change Request: QCCR2A58306: Symptom: The
Data Protector Backup Media Agent (BMA) and Backup Session Manager (BSM) fails to execute the
OB2MACHECKCAPACITY=1 omnirc variable. Resolution: The rsm binary is modified to correctly handle the Data Protector
"omnirc" variable. Change Request: QCCR2A58312: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) fails
with the following error message: |Major| From: VBDA@<hostname> "/CONFIGURATION" Time: <Date><Time> |81:145|
Automatic DR information could not be collected. Aborting the collecting of system recovery data. Resolution: The Data
Protector backup session is modified to complete successfully. Change Request: QCCR2A58322: Symptom: After successful
restore of the IBM DB2 Universal Database Server with Data Protector 8.13, rollforward recovery fails as some archive logs
are missing. Resolution: The db2arch binary is modified to correctly handle the rollforward recovery. Change Request:
QCCR2A58332: Symptom: The Data Protector backup session is unable to restart failed objects due to connection issues
with Inet, and the session fails with the following error message: |Major| From: BSM@<hostname> "" Time: <Date><Time>
Restart is not supported for specified session. Resolution: The facade library is modified to correctly handle the Data
Protector backup session. Change Request: QCCR2A58336: Symptom: Oracle backup session fails with the follwoing error
message: |Normal| From: OB2BAR_SBT_CHANNEL@<hostname> "" Time: <Date><Time> Starting OB2BAR Backup:
oracle_client.com:BARLIST<...>.dbf "Oracle8" |Major| From: BSM@<hostname> "BARLIST" Time: <Date><Time> |61:3003|
Lost connection to Data Protector Inet named "noname" on host oracle_client.com. Ipc subsystem reports: "IPC Read Error
20of32
9/14/20151:58PM
System error: |10054| Connection reset by peer" |Normal| From: BSM@<hostname> "BARLIST" Time: <Date><Time>
OB2BAR application on "oracle_client.com" disconnected. Resolution: The bsm and omnib binaries are modified to prevent
multiple backup sessions at the same time. Change Request: QCCR2A58341: Symptom: The Data Protector "global" file on
UNIX systems includes unexpected strings. Resolution: Data Protector is modified to correctly handle the creation of a
"global" file. Change Request: QCCR2A58342: Symptom: Restore devices cannot be changed since the restore sessions
always use the original device. Resolution: The Restore Session Manager (RSM) was modified to successfully change the
restore devices. Change Request: QCCR2A58407: Symptom: Data Protector 7.03 MMA ends abnormally during a replication
session between D2D systems with the following error message: |Normal] From: MMA@<hostname> "" Time: <Date>
<Time> Loading medium from slot "" |Major| From: CSM@<hostname> "" Time: <Date><Time> |61:3003| Lost connection to
MMA named "" on host "" Ipc subsystem reports: "IPC Read Error System error: |10054| Connection reset by peer Resolution:
The xMA binary is modified to correctly handle the Data Protector D2D replication. Change Request: QCCR2A58414:
Symptom: After the upgrade to Data Protector 8.13, the StoreOnceSoftware daemon ends abnormally at startup. Resolution:
Added OpenSSL thread-safety into libipc, moved IPC initialization functions. Change Request: QCCR2A58437: Symptom:
The Data Protector VEPA_BAR ends abnormally with the following error message during the restore session: |Normal| From:
VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> Virtual Machine "": Virtual machine configuration uploaded
successfully. Assertion failed: px != 0, file S:\bin\NT\boost\... This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more information. |Major| From: RSM@<hostname> "" Time:
<Date><Time> |61:3003| Lost connection to OB2BAR restore DA named "" on host "". Ipc subsystem reports: "IPC Read Error
System error: |10054| Connection reset by peer" Resolution: The ViAPI library is modified to correctly restore the network
information. Change Request: QCCR2A58480: Symptom: Data Protector media scanning, barcode scanning, or import of
media may fail with the following error message: |65:73| Media Management daemon reports: "Internal error: DbaXXXX
functions." for SCAN, BARCODE SCAN, rarely even IMPORT Resolution: Data Protector is modified to successfully
complete the media scanning, barcode scanning, or import of media. Change Request: QCCR2A58512: Symptom: Data
Protector fails to correctly import the duplicate session ID. Resolution: The facade library is modified to successfully import
the duplicate session ID. Change Request: QCCR2A58609: Symptom: The Data Protector 9.02 "omnidbcheck
-media_consistency" command reports false positives. Resolution: The Data Protector "omnidbcheck" binary is modified to
handle errors. Change Request: QCCR2A58630: Symptom: When performing a large query to Media Management Daemon
process (MMD), for example, FUN_LISTREPOSITORY, the Data Protector Backup Session Manager (BSM) and Copy and
Consolidation Session Manager (CSM) stop responding. Resolution: The MMD binary is modified to correctly handle the
Data Protector Backup Session Manager (BSM) and Copy and Consolidation Session Manager (CSM). Change Request:
QCCR2A58632: Symptom: During the import of vCenter 5.5 update 1, the plugin registration fails with the following error
message: Error (s) during registration plugin : vCenter Version 5,0 is not supported using Angular GUI Resolution: The
vmwaregre-agent.exe file is modified to correctly handle the import of vCenter 5.5 update 1. Change Request:
QCCR2A58693: Symptom: The Data Protector Internal Database (IDB) backup session issues warning about the missing
non-essential file: |Warning| From: OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date><Time> A
non-essential file cannot be found, backup continues Resolution: The Data Protector Internal Database (IDB) backup session
completes successfully. Change Request: QCCR2A58697: Symptom: The Data Protector "Recycle data and catalog
protection of failed source objects after successful copy" option does not function correctly. The terminated and failed objects
are not recycled after an object copy session. Resolution: The facade library is modified to correctly recycle failed objects, if
specified. Change Request: QCCR2A58706: Symptom: The Data Protector Backup Session Manager (BSM) and Copy and
Consolidation Session Manager (CSM) are not functioning correctly. Resolution: The Data Protector Backup Session
Manager (BSM) and Copy and Consolidation Session Manager (CSM) are modified to not end unexpectedly. Change
Request: QCCR2A58717: Symptom: The Data Protector backup session fails with the following error message: |Major| From:
BMA@<hostname> "" Time: <Date><Time> \90:51| \\...\VM\... Cannot write to device (StoreOnce error: Daemon is low on
memory, rejecting operations) Resolution: The StoreOnceSoftware binary is modified to count the buffered and cached
memory as free memory. Change Request: QCCR2A58751: Symptom: The Data Protector Import session returns no errors
even if the DCBF file cannot be created. Resolution: The Data Protector is modified to report errors during import session
when the DCBF file cannot be created. Change Request: QCCR2A58781: Symptom: In the HP Data Protector GUI Restore
context, few directories are displayed as files. Resolution: The Data Protector GUI displays the correct filesystem
information. Change Request: QCCR2A58788: Symptom: The HP Data Protector Internal Database (IDB) backup session
completes with the following errors: |Critical| From: OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" <Date><Time> An
internal error occurred. Resolution: The postgres_bar.exe is modified to successfully complete the HP Data Protector Internal
Database (IDB) backup session. Change Request: QCCR2A58828: Symptom: The Data Protector "omnirpt" command ends
abnormally. Resolution: The Data Protector "omnirpt" command is modified to execute correctly. Change Request:
QCCR2A58829: Symptom: The Data Protector Virtual Environment Integration (VEPA) backup session fails with the
following error message: "Aborting connection to BSM. Abort code -1." Resolution: The Data Protector Virtual Environment
Integration backup session completes successfully. Change Request: QCCR2A58848: Symptom: The backup session
terminates immediately when device filtering is enabled and devfilters file is created on the Cell Manager (containing a list of
logical devices and corresponding tags), if the omnirc "OB2DEVICEFILTER" variable is not set on one of the clients.
Resolution: The Backup Session Manager (BSM) is modified to correctly handle backup sessions with device filtering
enabled and without setting the "OB2DEVICEFILTER" omnirc variable on clients. Change Request: QCCR2A58889:
Symptom: Scanning StoreOnce media returns errors for media containing failed objects. Resolution: The Data Protector
Copy Session Manager (CSM) is modified to correctly handle catalog protection for failed objects. Change Request:
QCCR2A58898: Symptom: After upgrading to Data Protector 9.02, the Restore Media Agent (RMA) ends unexpectedly during
the object copy session with the following error message: |Major| From: CSM@<hostname> "" Time: <Date><Time>
|61:1005| Got unexpected close from RMA on mahostname Resolution: The Media Agent (MA) module is modified to
21of32
9/14/20151:58PM
correctly handle the object copy session. Change Request: QCCR2A58899: Symptom: The Mount.bat script does not start on
the Data Protector 8.13 Windows Cell Manager. Resolution: All session managers are modified to correctly start the
Mount.bat script on the Data Protector 8.13 Windows Cell Manager. Change Request: QCCR2A58903: Symptom: The Data
Protector GUI stops responding when trying to restart or resume the session. Resolution: The Data Protector GUI is modified
to function correctly when trying to restart or resume the session. Change Request: QCCR2A58928: Symptom: The
replication session fails with the following error message: |Major| From: CSM@<hostname> "" Time: <Date><Time>
|61:3003| Lost connection to MMA named " on host "". Ipc subsystem reports: "IPC Read Error System error:|10054|
Connection reset by peer Resolution: The Data Protector replication session completes successfully. Change Request:
QCCR2A58972: Symptom: The Data Protector backup session fails with Media Management Database (MMD) ending
abnormally: |Warning| From: BSM@<hostname> "" Time: <Date><Time> Cannot establish connection with the Media
Management database. Backup is waiting for the Media Management database to be reachable. Resolution: The Data
Protector facade library is modified to correctly handle the backup session. Change Request: QCCR2A59084: Symptom: The
Data Protector 7.03 Media Agent (MA) fails with the following error message: |Warning| From: BMA@<hostname> "" Time:
<Date><Time> The device "" could not be opened ("Device could not be approached") Resolution: The Data Protector omnirc
variable is modified to set the SCSI protocol version as follows: OB2FORCE_AIX_FC_SCSI_VER = 0 //SCSI Vesion 0
OB2FORCE_AIX_FC_SCSI_VER = 1 //SCSI Vesion 1 (also default if not set or different then 0,1,2)
OB2FORCE_AIX_FC_SCSI_VER = 2 //SCSI Vesion 2 Change Request: QCCR2A59134: Symptom: After an upgrade from
Data Protector 7.03 to 8.1, there seems to be inconsistencies with the internal database: upgraded IDB has problem when
browsing files in the Data Protector GUI. Resolution: The upgrade procedure is modified to correctly handle browsing of files
in the Data Protector GUI. Change Request: QCCR2A59216: Symptom: The Data Protector backups sessions become
unresponsive, if connection to the Media Management Daemon (MMD) is lost: |Major| From: BSM@<hostname> "" Time:
<Date><Time> |61:3003| Lost connection to MMD named "noname" on host <hostname>. Ipc subsystem reports: "IPC Read
Error System error: |10054| Connection reset by peer This happens if session managers are unresponsive for a while and
unable to respond to MMD messages. Resolution: The Media Management Daemon (MMD) is modified to communicate with
session managers asynchronously, improving behaviour in presence of temporarily unresponsive sessions. Change Request:
QCCR2A59221: Symptom: After an upgrade from Data Protector 9.01 to 9.02, the backup of some Virtual Machines (VMs)
fail with the following error message: |Major| From: VEPALIB_VMWARE@<hostname> "" Time: <Date><Time> Could not
read block from "". Resolution: The Data Protector Virtual Environment Integration (VEPA) is modified to correctly handle the
backup of some VMs. Change Request: QCCR2A59272: Symptom: The Data Protector 9.0 restore session of a Data
Protector 7.x Microsoft Exchange Server backup using the Volume Shadow Copy Service (VSS) technology cannot create
path to fileset. Resolution: The DMA binary is modified to successfully handle the Data Protector 9.0 restore session.
Change Request: QCCR2A59337: Symptom: An interactive object copy session from SOS store of Exchange full backup
session to the tape device does not display the correct percentage of copied objects. Resolution: The RMA and CSM
binaries are modified to correctly reflect the percentage completed in the Data Protector GUI. Change Request:
QCCR2A59350: Symptom: The Data Protector "omnidbutil -show_locked_devs" or "omnidbutil -free_locked_devs" command
uses the local hostname instead of the Cell Manager's name. Resolution: The Data Protector "omnidb" utility is modified to
use the virtual hostname instead of the local name and filter locks. Change Request: QCCR2A59381: Symptom: The Data
Protector 8.1x and 9.0x "omnirpt -report session_statistics" command reports erroneous values. Resolution: The
sessions_statistics report is modified to display correct values. Change Request: QCCR2A59401: Symptom: The "omnib
-datalist <wrong_name>" does not generate a session ID, while the "omnib -mssql_list <wrong_name>" does (as other
bar_lists do too). Resolution: The Backup Session Manager (BSM) is modified to generate session ID when non-existent
datalist name is used. Change Request: QCCR2A59627: Symptom: During an upgrade from Data Protector 7.03 to Data
Protector 9.02 the following error occur: |Normal| From: BSM@<hostname> "" Time: <Date><Time> OB2BAR application on
"client" successfully started. Unknown encoding 'UCS-2LE' at /opt/omni/lib/perl/Omniback.pm line 2015 Resolution: Backup
session completes successfully. Change Request: QCCR2A59852: Symptom: The Sybase integration backup in the Data
Protector version 8.13 is executed over one stream instead of the specified number of streams. This is because the Backup
Session Manager incorrectly parses the number of streams from the barlist specification. Resolution: The Data Protector
Backup Session Manager is modified, and now the Sybase integration backups are executed correctly. Change Request:
QCCR2A59902: Symptom: The Data Protector restore chain was incorrectly executed when the "Owner" of the Data Protector
Virtual Environment integration (VEPA) backup session with quiescence, was set in the Windows client. Resolution: The
Data Protector Virtual Environment Integration Agent (VEPA) is modified, and now the restore chain calculation is functioning
correctly. Change Request: QCCR2A59936: Symptom: After an upgrade from Data Protector 7.03 to Data Protector 9.01,
tapes that were present in the Non-Appendable media pool were used for standalone device backups. Resolution: The
facade and_ _libfacade files are modified, and now tapes that were present in the Non-Appendable media pool will not be
used for standalone device backups. Change Request: QCCR2A60111: Symptom: The HP Data Protector 9.0 documentation
needs to be updated that the Data Protector GRE for VMware vSphere does not work if the encrypted control communication
(ECC) is enabled. Resolution: Fixed and updated in the following guides: Installation Guide - VMware Client, under
considerations - page 147 GREGuide - Part 3- VMware GRE, chapter 16 - Installation - Page 123 Data Protector VMware
GRE does not work if encrypted control communication is enabled on machines that comunicate with the GRE Plug-in
(Mount Proxy machines and the vCenter). Encrypted control communication can be enabled on the Cell Server. However, the
Mount proxy machines and the vCenter must be added to the exception list. Change Request: QCCR2A60176: Symptom:
The import session of the Catalog Media Data from the Media Container Format (MCF) files in Data Protector 8.13, ends
unexpectedly. Resolution: The Data Protector libfacade, libormapper, facade, and ormapper files are modified, and now the
import session of the Catalog Media Data from the Media Container Format (MCF) files is successful. Change Request:
QCCR2A60434: Symptom: The Data Protector Copy and Consolidation Session Manager (CSM), Backup Session Manager
(BSM), Backup media Agent (BMA) end unexpectedly with heap corruption fault on Windows Server 2012 R2 Cell Manager
22of32
9/14/20151:58PM
(CM). Resolution: The Data Protector Copy and Consolidation Session Manager does not end unexpectedly. Change
Request: QCCR2A60503: Symptom: While backing up Exchange 2010 via MS VSS integration, all incremental backups are
sent to disk and then copied to tape. Most of the incremental backups copied to tape are currently unrestorable. Resolution:
The problem occurs because of the call to the "omnidbutil -check_graph". The code tries to correct restore chains, but in case
of integrations the restore chain is not used and the data should not be changed. The object_version_service.cpp is modified
and restore from incremental backups copied to tape to be successful DPLNXBDL_00902: Change Request: QCCR2A46153:
Symptom: The Data Protector "omnidbutil -show_locked_devs" command does not display locks. Resolution: The Data
Protector "omnidbutil" binary is modified to correctly display locked devices. Change Request: QCCR2A46897: Symptom:
After an upgrade to Data Protector 7.01 on Solaris 10, the restore operation fails with the following error message: <Date>
<Time> RMA.23991.0 |"/ma/spt/sctl.c $Rev: 35661 $ $Date:: <Date><Time>":3328| A.07.00 b103 DbgStack: DbgFcnOut()
function does not match function on stack! ExitFcn="SCTL_Read", StackFcn="SCTL_SolBackSR" Resolution: The Data
Protector Media Agent binaries are modified to correctly handle the debug.log file on Solaris 10 during a restore operation.
Change Request: QCCR2A48585: Symptom: Oracle backups do not use the devfilter option (/etc/opt/omni/server
/cell/devfilters) when StoreOnce Catalyst Stores are selected as the destination device and using source side devices. The
Oracle backup fails with the following error message: |Major| From: BSM@<hostname> "" Time: <Date><Time> No device
that matches object BAR client.com:""<>.dbf "" with device filter "" was found. Client will terminate. Resolution: The bsm
binary is modified to correctly handle the Oracle backup. Change Request: QCCR2A48627: Symptom: An object copy
session fails with the following warning message: |Warning| From: CSM@<hostname> "" Time: <Date><Time> There are no
available connections on gateway "" for the device named "". Resolution: The Data Protector Copy Session Manager (CSM)
is modified to correctly handle the connections on gateway for devices. Change Request: QCCR2A48923: Symptom: The
Data Protector GUI displays incorrect values for objects during a copy session. Resolution: The csm binary is modified to
correctly display object values during a copy session in the Data Protector GUI. Change Request: QCCR2A49228: Symptom:
The Data Protector 8.0 GUI incorrectly displays the media allocation order. Resolution: The Cell Server module is modified
to correctly display the media allocation order in the Data Protector 8.0 GUI. Change Request: QCCR2A50000: Symptom:
After a successful replication session between the two B6200 devices, the copy to tape fails due to one of the following
errors: 1) Media issues, No more media for restore on device |Normal| From: RMA-NDMP@<hostname> "" Time: <Date>
<Time> Loading medium from slot \\... to device "" |Warning| From: CSM@<hostname> "" Time: <Date><Time> No more
media for restore on device "". Aborting running Disk Agents. |Normal| From: RMA-NDMP@<hostname> "" Time: <Date>
<Time> Unloading medium to slot \\... from device "". |Normal| From: RMA-NDMP@<hostname> "" Time: <Date><Time>
ABORTED Media Agent "". 2) JSON errors |Major| From: RMA-NDMP@<hostname> "" Time: <Date><Time> |90:52| Cannot
read from device (JSONizer error: Device read failure) Resolution: The mma binary is modified to successfully complete the
Data Protector object copy session to tape. Change Request: QCCR2A50234: Symptom: Expanding objects in the Data
Protector GUI restore context takes a long time. Resolution: The database queries are modified to improve the performance
of expanding objects in the Data Protector GUI restore context. Change Request: QCCR2A50504: Symptom: After an
upgrade from Data Protector 7.01 to 8.0, the Media Agent of clients running on Solaris 10 OS produces Gigabytes of logs in
the /var/opt/omni/log/debug.log with the following messages: ==> <Date><Time> BMA.8846.0 |""| A.08.00 b596 DbgStack:
DbgFcnOut() and level already 0! ExitFcn="SCTL_Write" Resolution: The bma, cma, devbra, mma, rma, SANconf, and uma
binaries are modified to ensure that the Data Protector debug.log file does not include the space consuming messages.
Change Request: QCCR2A50540: Symptom: During an object copy session after a failed backup session, the following error
is displayed: |Major]|From: RMA@<hostname> "" Time: <Date><Time> |90:48| Medium is corrupted, trying to reconstruct.
Resolution: The bma, rma, and mma binaries are modified to correctly reconstruct the medium within a required time limit.
Change Request: QCCR2A50778: Symptom: The Data Protector "omnidb -list_changed_protection" command does not
execute correctly on Windows and Linux operating systems. Resolution: The libfacade and facade binaries are modified to
correctly execute the Data Protector "omnidb -list_changed_protection" command. Change Request: QCCR2A50844:
Symptom: Large environments that are using Data Protector to write on StorageTek devices like STK T10000C drives are not
able to fully utilize the cartridge capacity of 5 terabytes (TB), since the current Data Protector limit is 4 TB. Resolution: The
Data Protector Media Agent binaries are modified to handle the large media size. Change Request: QCCR2A50896:
Symptom: The Data Protector Internal Database (IDB) consistency check fails. Resolution: The Data Protector omnidbcheck
binary is modified to not report the Internal Database (IDB) as inconsistent under low memory conditions. Change Request:
QCCR2A50919: Symptom: The Data Protector restore session with omnirc option "ENHANCED_DAR_ENABLED=T" enabled
on HP-UX 11.31 IA64 system fails with the following error message: |Major| From: RMA-NDMP@<hostname> "" Time:
<Date><Time> |242:33| NDMP Restore operation has failed. |Normal| From: RMA-NDMP@<hostname> "" Time: <Date>
<Time> ABORTED Media Agent "" Resolution: The rma and bma binaries are modified to correctly handle the Data Protector
Direct Access Restore (DAR) functionality on NetApp. Change Request: QCCR2A51260: Symptom: After an upgrade to Data
Protector 8.1, the backup session of NSS volumes on Novell OES 11 ends abnormally with the following error message, if
the folder and filenames contain non-English characters: |Normal| From: VBDA@<hostname> "" Time: ABORTED Disk Agent
for <hostname>:/media/nss/VOL1 "" |Critical| From: BSM@<hostname> "" Time: <Date><Time> |61:4001|Error reading the
database, in line 1764, file bcsmutil.c. Database subsystem reports: "Internal error: DbaXXXX functions." Resolution: Data
Protector now supports backup trees containing non-UTF-8 filenames. Change Request: QCCR2A51264: Symptom: The
Data Protector Devbra functionality on AIX 6.1 systems with a 16 GB FC adapter does not return any device information.
Resolution: The Data Protector Media Agent binaries are modified to correctly handle the Data Protector Devbra functionality
on AIX 6.1 systems. Change Request: QCCR2A51266: Symptom: The Data Protector backup session fails with the following
error message: |Critical| From: BSM@<hostname> "" Time: <Date><Time> |61:6002| Error receiving catalog data from the
BMA@<hostname> "". Ipc subsystem reports: "IPC Read Error System error: |110| Connection timed out" Resolution: The
Data Protector Backup Session Manager (BSM) is modified to correctly receive the catalog data from the Data Protector
Backup Media Agent (BMA). Change Request: QCCR2A51326: Symptom: The import of media-related catalog data from
23of32
9/14/20151:58PM
Media Container Format (MCF) files fail with the following error: 1241. Resolution: The facade binary is modified to correctly
handle copy of a catalog from source to target cell in Media Container Format (MCF). Here, the source object positions are
relinked to target object for duplicate ones. Change Request: QCCR2A51421: Symptom: The Data Protector "omnimm
-delete_unprotected_media" command stops responding. Resolution: The Data Protector Internal Database (IDB) schema is
modified to improve the performance of the Data Protector "omnimm -delete_unprotected_media" command. Change
Request: QCCR2A51551: Symptom: The SNMP trap for "EndOfSession" event in the Data Protector fails to display the
correct parameters in the Parameter string. Resolution: The "omnirpt" binary is modified to correctly display parameters in
the Parameter string. Change Request: QCCR2A51680: Symptom: The Data Protector restore session fails with the following
error message: |Major| From: RSM@<hostname> Time: <Date><Time> Restore of object XXXXX:PS1.YY named "" may be
incomplete because some medium is missing. Resolution: The Data Protector Media Session Manager is modified to
successfully complete the restore session. Change Request: QCCR2A51705: Symptom: The Data Protector GUI fails with
the following error message when some of the Data Protector Network Data Management Protocol (NDMP) server integration
objects are expanded: More than one line returned by a subquery used in an Expression. Resolution: The Data Protector
Internal Database (IDB) schema is modified for proper functioning of the GUI when the Data Protector Network Data
Management Protocol (NDMP) server integration objects are expanded. Change Request: QCCR2A51718: Symptom: The
users configured in the Operator Data Protector user group are unable to browse the filesystems to easily create and save
backup specifications as it requires user impersonation. Resolution: The dbsm binary is modified to permit users configured
in the Operator Data Protector user group to browse filesystems for creating and saving backup specifications. Change
Request: QCCR2A51879: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) timeout occurs. Resolution: The
Data Protector Volume Backup Disk Agent (VBDA) is functioning correctly. Change Request: QCCR2A51880: Symptom: The
Data Protector Internal Database (IDB) backup session fails with the following error message: |Critical| From:
OB2BAR_POSTGRES_BAR@<hostname> "" Time: <Date><Time> An internal error occurred. Resolution: The
postgres_bar.exe file is modified to correctly handle the Data Protector Internal Database (IDB) backup session. Change
Request: QCCR2A51881: Symptom: The Data Protector 8.1 backup session fails with the following error message: |Normal|
From: BMA@<hostname> "" Time: <Date><Time> STARTING Media Agent "" |Normal| From: BMA@<hostname> "" Time:
<Date><Time> Loading medium from slot \\media_agent.com\... |Major| From: BMA@<hostname> "" Time: <Date><Time>
|90:54| \\media_agent.com\... Cannot open device (StoreOnce error: StoreOnce device offline, network error occurred or
secure communication failed while contacting the StoreOnce device) |Major| From: BMA@<hostname> "" Time: <Date>
<Time> |61:3003| Lost connection to BMA named "" on host media_agent.com. Ipc subsystem reports: "IPC Read Error
System error: |10054| Connection reset by peer" |Normal| From: BMA@<hostname> "" Time: <Date><Time> STARTING
Media Agent "" This loop will continue until the session is aborted. Resolution: The bsm binary is modified to correctly
handle the Data Protector 8.1 backup session. Change Request: QCCR2A51908: Symptom: The Data Protector VMware
Granular Recovery Extension (GRE) restore session stops responding when the Media Agent (MA) on the StoreOnce device
is started. Resolution: The Data Protector Backup Session Manager and the Restore Session Manager is modified to
successfully complete the Data Protector VMware Granular Recovery Extension (GRE) restore session. Change Request:
QCCR2A51920: Symptom: The Data Protector "omnidb -oracle8 -detail" command fails with the following error message, and
also fails to report the data for the rest of the oracle8 objects. "No query data found." Resolution: The omnidb binary is
modified to correctly handle the Data Protector "omnidb -oracle8-detail" command and report data for the remaining oracle8
objects. Change Request: QCCR2A52010: Symptom: The Backup Session Manager (BSM) ends abnormally during the
backup sessions on HP-UX 11.31 and IA-64 platform. Resolution: The bsm binary is modified to correctly handle the backup
sessions on HP-UX 11.31 and IA-64 platform. Change Request: QCCR2A52063: Symptom: All tapes are not displayed when
the Data Protector 8.1 "omnimm -list_scratch_media" command is executed. Resolution: The Internal Database (IDB) module
is modified to correctly display all tapes when the Data Protector 8.1 "omnimm -list_scratch_media" command is executed.
Change Request: QCCR2A52079: Symptom: The Data Protector SAP HANA Appliance integration restore session fails with
the following error message: ERROR RECOVERY Missing backup in backint: /usr/sap/H22/SYS/global/hdb/backint
/COMPLETE_DATA_BACKUP_databackup_0_1 20140320.000010:93d |111014| The backup with backup id "" cannot be
used for recovery.. Resolution: The Data Protector SAP HANA backint binary is modified to successfully complete the SAP
HANA Appliance integration restore session. Change Request: QCCR2A52223: Symptom: When the Data Protector "omnirpt
-repot dl_info" command is executed on HP-UX 11.31 IA 64 system, the output does not display Microsoft SQL, Oracle, or the
file systems. Resolution: The dbsm binary is modified to correctly execute the "omnirpt -report dl_info" and "omnirpt -report
dl_sched" commands, and display the complete output. Change Request: QCCR2A52337: Symptom: The Data Protector
Oracle integration Zero Downtime Backup (ZDB) solution using the backup set method fails with the following error message:
RMAN-00571: ==== RMAN-00569: ====ERROR MESSAGE STACK FOLLOWS === RMAN-00571: ==== RMAN-03002:
failure of backup command at <Date><Time> RMAN-06056: could not reach datafile 1Recovery Manager complete. |Major|
From: ob2rman@<hostname> "" Time: <Date><Time> External utility reported error. Resolution: The SMB files, the SSEA
and the SYMA binaries are modified to correctly authenticate the user credentials or authorization on the backup host.
Change Request: QCCR2A52418: Symptom: The Data Protector backup sessions on Linux systems fails with the following
error message: |Major| From: BMA@<hostname> "" Time: <Date><Time> |90:65| /dev/nst11 Cannot append to medium
(Invalid device block size 1024KB,should be 512KB.) Resolution: The Data Protector 7.03 Backup Session Manager is
modified to successfully complete the backup sessions on Linux systems. Change Request: QCCR2A52428: Symptom: The
Data Protector debug.log file displays the following error messages: Time: <Date><Time> BSM.844.1204 |"/sm/bsm2
/breconn.c Rev: 40401 Time: <Date><Time>:517| A.08.00 bSSPNT800_006 DbgStack: DbgFcnOut() function does not match
function on stack! ExitFcn="BsmOnCloseReconnect", StackFcn="brecon_checkHandle" Resolution: The "bsm" and "omnidlc"
binaries are modified to avoid displaying the following message: "DbgStack: DbgFcnOut() function does not match function
on stack! ExitFcn="BsmOnCloseReconnect", StackFcn="brecon_checkHandle" Change Request: QCCR2A52442: Symptom:
The importing of the Data Protector Network Data Management Protocol (NDMP) Server Integration media on Windows
24of32
9/14/20151:58PM
Server 2008 R2 Standard fails with the following error message: |Major| From: MSM@<hostname> "" Time: <Date><Time>
|65:99| Import failed with possible cause: this media already has valid copy in DB. |Critical| From: MSM@<hostname> ""
Time: <Date><Time> Failed to allocate memory. System error: |8| Not enough storage is available to process this command.
Resolution: The Data Protector Media Session Manager (MSM) is modified to correctly handle the import of the Data
Protector NDMP media. Change Request: QCCR2A52474: Symptom: The Virtual Environment Integration (VEPA)
component builds slowly. Resolution: The Virtual Environment Integration (VEPA) component is modified to build correctly.
Change Request: QCCR2A52479: Symptom: The Data Protector object consolidation session on Windows Server 2008
(64-bit) fails with the following error message: |Normal| From: CSM@<hostname> "" Time: <Date><Time> STARTING
consolidation of "" from session <Date>. |Major| From: CSM@<hostname> "" Time: <Date><Time> |61:3003| Lost
connection to RMA named "" on host <name>. Ipc subsystem reports: "IPC Read Error System error: |10054| Resolution: The
rma binary is modified to successfully complete the Data Protector object consolidation session. Change Request:
QCCR2A52497: Symptom: The Data Protector Copy and Consolidation Session Manager (CSM) process ends abnormally
during large replication sessions. Resolution: The Data Protector Copy and Consolidation Session Manager (CSM) process
is modified to successfully complete large replication sessions. Change Request: QCCR2A52578: Symptom: After an
upgrade from Data Protector 6.21 to 8.x in a Linux Manager-of-Managers (MoM) environment, the media consistency checks
fail on the Cell Manager. Resolution: The Data Protector omnidbcheck functionality is modified to correctly return the media
consistency check report. Change Request: QCCR2A52592: Symptom: The Data Protector "omnirpt -report obj_lastbackup"
command fails with the following error message: Error creating the report "Interactive": Bad file format. System error: Syntax
error at line 1, column 170. Expected 'token->type= =token_string || token->type==token_number', got EOF. Near: ''
Resolution: The dbsm binary is modified to correctly execute the Data Protector "omnirpt -report obj_lastbackup" command.
Change Request: QCCR2A52604: Symptom: The Data Protector 6.21 Centralized Media Management Database (CMMDB)
stops responding. Resolution: The facade binary is modified to correctly handle the Data Protector Centralized Media
Management Database (CMMDB). Change Request: QCCR2A52660: Symptom: During the execution of Data Protector
"omnidbutil -purge_daily" command, the Internal Database (IDB) records "orphan" DCBF_INFO entries and their
corresponding Detail Catalog Binary Files (DCBF) from disk. Resolution: The omnidbutil binary is modified to clean up
invalid Detail Catalog Binary Files (DCBF) records from Internal Database (IDB) and their corresponding files from disk.
Change Request: QCCR2A52664: Symptom: The Data Protector 8.1 "Object copies" and "Object's latest backup" reports fail
to list the Virtual Machine (VM) name in the Mountpoint field. Resolution: The Data Protector omnirc variable
"OB2_RPT_VEPA_MOUNTPOINT_TO_VMPATH=1" is set to correctly list the Virtual Machine (VM) name in the Mountpoint
field. Change Request: QCCR2A52754: Symptom: During the object copy session, the Data Protector Copy and
Consolidation Session Manager process (CSM) attempts to copy objects that are not selected in the object copy
specification. Resolution: The Data Protector Copy and Consolidation Session Manager process (CSM) is modified to
correctly copy only the selected objects in the object copy specification. Change Request: QCCR2A52780: Symptom: After
upgrading to Data Protector 8.11 on Windows Server 2008, the Data Protector object copy session from File Library to Tape
fails with the following error message: |Critical| From: CSM@<hostname> "" Time: <Date><Time> No objects to copy. The
session will abort. |Normal| From: CSM@<hostname> "" Time: <Date><Time> Resolution: The facade binary is modified to
correctly copy objects from the file library to tape. Change Request: QCCR2A52848: Symptom: The Data Protector Microsoft
SQL Server integration backup session with the server-side deduplication fails with the following error message: |Normal|
From: BSM@<hostname> "" Time: <Date><Time> Server-side Deduplication Statistics for "". Using device: "": Mbytes Total:
........... - 23 MB Mbytes Written to Disk: ....1 MB Deduplication Ratio: .....- 23.9 : 1 Resolution: The Data Protector Microsoft
SQL Server integration is modified to correctly handle the backup session with the server-side deduplication. Change
Request: QCCR2A52936: Symptom: The Data Protector 8.0 backup session fails with the following error message: |Critical|
From: BMA@hostname "Device" Time: <Date><Time> IPC Cannot Allocate Shared Memory Segment. Resolution: Data
Protector 8.0 is modified to correctly handle the backup session. Change Request: QCCR2A52972: Symptom: The Data
Protector backup session displays the following error message: |Warning| From: BMA@<hostname> "" Time: <Date><Time>
Tape0:0:2:0C Tape Alert |15|: The memory in the tape cartridge has failed, which reduces performance. Do not use the
cartridge for further backup operations. Resolution: The Data Protector Media Agent binaries are modified to correctly handle
the backup session without any error messages. Change Request: QCCR2A53053: Symptom: The Data Protector restore
session of Microsoft SQL 2012 backup fails with the following error message: |Normal| From: SMISA@hostname "Device"
Time: Check for proper signatures of the replica(s). |Minor| From: SMISA@hostname "Device" Time: Failed to write disk
identification signature to disk "". Resolution: The Data Protector SMIS integration is modified to function correctly when
writing the disk identification signature to disk. Change Request: QCCR2A53142: Symptom: When querying reports using the
Data Protector "omnirpt" command on Windows Server 2008 R2 up to a certain timeframe, the report gets truncated and
displays (null) at the bottom of the page. Resolution: The facade binary is modified to correctly handle the Data Protector
"omnirpt" command. Change Request: QCCR2A53146: Symptom: After upgrading from Data Protector 6.21, the Data
Protector Copy and Consolidation Session Manager (CSM) process locks multiple source devices during an object copy
session. Resolution: The Data Protector Copy and Consolidation Session Manager (CSM) process is modified to correctly
handle the multiple source devices during an object copy session. Change Request: QCCR2A53177: Symptom: The Data
Protector Cell Request Server process (service) fails with the following error 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. System error: |111|
Connection refused Resolution: The Data Protector Cell Request Server (CRS) and Media Management Daemon (MMD)
binaries are modified to correctly handle the Cell Request Server process (service). Change Request: QCCR2A53228:
Symptom: The Data Protector backup session on HP-UX 11.31 IA64 fails with the following error message: |Major| From:
BSM@<hostname> "" Time: <Date><Time> Internal error. Allocation from library failed. The Media Management daemon
reports: "Medium not found." Resolution: The facade binary is modified to correctly handle the Data Protector backup session
on HP-UX 11.31 IA64. Change Request: QCCR2A53248: Symptom: The backup of a Virtual Machine (VM) managed by a
25of32
9/14/20151:58PM
vCenter cannot be restored to an ESX server not managed by a vCenter. The restore session fails with the following error
message: |Major| From: VEPALIB_VMWARE@hostname "" Time: <Date><Time> Restore failed. Resolution: The Data
Protector Virtual Environment Protection Agent (VEPA) is modified to successfully complete the restore session to an ESX
server not managed by a vCenter. Change Request: QCCR2A53251: Symptom: After upgrading to Data Protector 7.0 on
Windows Server 2008, the Catalog protection for the filesystem backup sessions is not set correctly when the protection is
set to "Same as data protection". Resolution: The Backup Session Manager (BSM) is modified to set the option "-keepcatalog
same_as_data_protection" correctly to datalist when the Catalog protection is set to "Same as data protection" during the
backup configuration. Change Request: QCCR2A53275: Symptom: When the Data Protector "omnicheck" command is
executed with the "-dns -full" option, the Data Protector "omniinet.exe" process on the Cell Manager ends unexpectedly.
Resolution: The inet binary is modified to correctly handle the Data Protector 8.01 "omniinet.exe" process on the Cell
Manager. Change Request: QCCR2A53300: Symptom: The Data Protector replication session fails with the following error
message when more than 1000 objects are replicated: |Warning| From: CSM@<hostname> "" Time: <Date><Time> Got
error: "StoreOnce error: Bad address filter" when contacting "" B2D device! |Normal| From: MMA@<hostname> "" Time:
<Date><Time> ABORTED Media Agent "" Resolution: The Data Protector Media Agent module is modified to correctly
handle the Data Protector replication session. Change Request: QCCR2A53330: Symptom: While copying objects from a
restarted session, the following error message is displayed: |Critical| From: CSM@<hostname> "" Time: <Date><Time>
|62:1001| Specified device for the object not found. |Major| From: CSM@<hostname> "" Time: <Date><Time> FAILED copy
of "" from session <Date><Time> Resolution: The Data Protector Copy Session Manager (CSM) is modified to correctly
handle resumed object versions without catalog during the restore or object copy. Change Request: QCCR2A53381:
Symptom: When the NSS file systems data is used for enhanced incremental backup and later for consolidation, the object
consolidation session ends abnormally with the following error message: |Normal| From: CSM@<hostname> "" Time:
<Date><Time> STARTING catalog analysis of FileSystem disk_agent_client.com:"" from session <Date><Time>.
Resolution: The Data Protector Media Agent (MA) is modified to correctly handle the object consolidation session. Change
Request: QCCR2A53392: Symptom: After upgrading from Data Protector 6.21 to 7.03, the Volume Backup Disk Agent
(VBDA) stops responding and displays the following error message: |Major| From: BSM@<hostname> "" Time: <Date>
<Time> |61:1002| The VBDA named "" on host client.com reached its inactivity timeout of 7200 seconds. The agent on host
will be shutdown. Resolution: The Data Protector Volume Backup Disk Agent (VBDA) is modified to correctly handle the
VBDA inactivity timeout. Change Request: QCCR2A53417: Symptom: The Data Protector administrative command "devbra"
stops responding when running on Windows Server 2003. Resolution: The DEVBRA binary is modified to correctly function
when running on Windows Server 2003. Change Request: QCCR2A53419: Symptom: The Data Protector Volume Backup
Disk Agent (VBDA) ends abnormally with the following error message: |Critical| From: VBDA@<hostname> "" Time: <Date>
<Time> Connection to Media Agent broken => aborting. Resolution: All Data Protector modules are rebuilt to correctly
handle port scans. Change Request: QCCR2A53433: Symptom: The Data Protector "omnirpt -report single_session"
command does not calculate the correct object status. Resolution: The facade binary is modified to correctly calculate the
session object states completed with errors. Change Request: QCCR2A53446: Symptom: The Data Protector Backup
Session Manager (BSM) on HP-UX 11.31 stops responding when the "OMNI_HOSTS" environment variable is used.
Resolution: The Data Protector "OMNI_HOSTS" variable is not added to the host cache to ensure that the Backup Session
Manager (BSM) functions correctly. Change Request: QCCR2A53449: Symptom: After upgrading from Data Protector 6.20 to
8.1, the Data Protector "Session per client report" does not display the correct information. Resolution: The Data Protector
Database Session Manager (DBSM) is modified to correctly handle the Data Protector "Session per client report". Change
Request: QCCR2A53483: Symptom: The Data Protector 8.0 debug.log on Windows Server 2008 includes the following error
messages: <Date><Time> RMA-NET.6040.6636 |" Date:: <Date><Time>":161| A.08.00 ""_TM2 DbgStack: DbgFcnOut() and
level already 0! ExitFcn="MaProtocolCheck" Resolution: The Data Protector Media Agent (MA) is modified to correctly
handle entries in the debug.log file. Change Request: QCCR2A53584: Symptom: The Data Protector 8.1 Context-Sensitive
Help (F1) does no longer include detail information provided as pop-ups. Resolution: The Data Protector Context-Sensitive
Help is modified to correctly handle popup settings, so that F1 help popups are displayed correctly. Change Request:
QCCR2A53593: Symptom: The Data Protector media import session fails with the following error: |Critical| From:
MSM@<hostname> "" Time: <Date><Time> 4/2014 14:30:27 |65:6| Internal Database layer reports: "Internal error: DbaXXX
functions." |10| Last agent disconnected. Session completed, status=5 Resolution: The Data Protector Media Session
Manager (MSM) is modified to correctly report the media import session with relevant errors. Change Request:
QCCR2A53639: Symptom: Concurrent Data Protector Oracle Integration backup sessions that use same devices fail to
complete successfully. Resolution: The Data Protector Media Management Daemon (MMD) is modified to correctly handle
concurrent Data Protector Oracle Integration backup sessions and lock backup devices. Change Request: QCCR2A53663:
Symptom: After upgrading from Data Protector 7.0 to 8.11, changing the data or catalog protection on a single object in the
Data Protector GUI changes the protection for both the original and copy object. Resolution: The Data Protector GUI is
modified to correctly change data or catalog protection on the selected object only. Change Request: QCCR2A53760:
Symptom: The Data Protector SSEA component (HP P9000 XP Agent) searches for "hp_rescan" in the /usr/sbin/ location, but
fibreutils-3.2-6 is present in /usr/bin. Resolution: The Data Protector SSEA is modified to correctly handle the "hp_rescan"
command. Change Request: QCCR2A53775: Symptom: The Data Protector "omnidbutil -purge -dcbf" command takes a long
time to complete. Resolution: The Data Protector Internal Database (IDB) scripts are modified to correctly handle
performance during the daily maintenance. Change Request: QCCR2A53783: Symptom: The Data Protector 8.11 Session
flow report does not mark queuing sessions and statistics reports with the Blue color. Sometimes, the queuing statistics
reports appear incorrectly. Resolution: The facade binaries are modified to correctly handle queuing sessions and statistics
reports. Change Request: QCCR2A53815: Symptom: The Data Protector Cell Request Server (CRS) process (service)
creates additional/unwanted debugs in all StoreOnce Software (SOS) clients. This happens when CRS is started on the Cell
Manager in the Debug mode (through the trace file or the "omnisv -start" command) and the backup session uses an SOS
26of32
9/14/20151:58PM
device on the RedHat client. Resolution: The Data Protector Cell Request Server (CRS) is modified to function correctly and
not create additional/unwanted debugs on the Store Once Software (SOS) clients. Change Request: QCCR2A53821:
Symptom: The Data Protector Oracle integration backup session fails with the following error message for the first Oracle
object that connects: |Major| From: BSM@<hostname> "" Time: <Date><Time> No device that matches object "" with device
filter "" was found. Client will be aborted. Resolution: The Data Protector Backup Session Manager (BSM) is modified to
correctly select devices that match the device filter criteria. Change Request: QCCR2A53827: Symptom: The Data Protector
8.12 backup session on Windows Server 2012 Cell Manager and VMware backup host with the Changed Blocked Tracking
(CBT) option fails, while the full backup sessions complete successfully. Resolution: A Data Protector omnirc variable
"OB2_VEAGENT_VCENTER_CONNECTION_LIMIT_INCR" is added and set to 4. This adjusts the connection limit for
incremental backups only. Change Request: QCCR2A53884: Symptom: When the Data Protector 8.12 "omnidbutil-purge
-daily" command is executed, the following error message is displayed: "Operation failed." Resolution: The Data Protector
omnidbutil binary is modified to correctly execute the "omnidbutil -purge -daily" command. Change Request: QCCR2A53970:
Symptom: The Data Protector documentation does not clearly state whether the Data Protector Cell Manager is supported on
HPUX-PA RISC processors or not. Resolution: The Data Protector 8.1x platform support matrix is modified to reflect the
correct information. Change Request: QCCR2A54030: Symptom: The Data Protector Internal Database (IDB) fails after
upgrading to 8.01 version. Resolution: The postgres_bar.exe binary file is modified to successfully backup the Data Protector
Internal Database (IDB). Change Request: QCCR2A54071: Symptom: The email notification for the Data Protector Internal
Database (IDB) backup is not readable when using the Japanese language. Resolution: The Data Protector Internal
Database (IDB) backup now uses one codepage for all messages. Change Request: QCCR2A54089: Symptom: The Data
Protector "omnimm -delete_unprotected_media" command fails to delete the missing media in the target Backup to Disk
(B2D) stores, preventing the deletion of the related Internal database (IDB) information, including the Detail Catalog Binary
Files (DCBFs). Resolution: The omnimm and the msm binaries are modified to delete all unprotected media from the IDB,
including the missing media in the target B2D stores. Change Request: QCCR2A54093: Symptom: The Data Protector
reporting command "omnirpt" fails with the following error message: /opt/omni/bin/omnirpt -report session_errors -timeframe
800 800 Error creating the report "Interactive": File/directory not found. System error: |2| No such file or directory. Resolution:
The libfacade and facade binaries are modified to correctly execute the Data Protector reporting command "omnirpt". Change
Request: QCCR2A54132: Symptom: Multiple backups of different specifications that use mirroring stops responding if the
first backup session is terminated. Resolution: The Backup Session Manager is modified to correctly handle multiple
backups during mirroring. Change Request: QCCR2A54166: Symptom: The Data Protector times out while enumerating
virtual machines. Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified to improve
performance. If just one backup fails, only backup for that Virtual Machine will fail. Change Request: QCCR2A54195:
Symptom: The Data Protector GUI becomes unresponsive and takes a long time when objects in the restore context are
expanded. Resolution: The bsm, csm, rsm, asm, msm, dbsm, and facade binaries are modified to correctly handle the Data
Protector GUI when objects in the restore context are expanded. Change Request: QCCR2A54215: Symptom: The Data
Protector GUI restore context fails for an incremental (Incr1) backup and displays the media of a full backup session.
Resolution: The Restore Session Manager (RSM) is modified to select a media copy for restore, if the copy exists. Change
Request: QCCR2A54228: Symptom: The Data Protector VMware restore session on Windows Server 2008 R2 is performed
on the wrong cluster. Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified to correctly
use the cluster for the Restore session. Change Request: QCCR2A54250: Symptom: The Data Protector Internal Database
(IDB) backup session fails with the following error message: |Major| From:OB2BAR_POSTGRES_BAR@<hostname>
"DPIDB" Time: <Date><Time> Cannot parse DBSM message (Details unknown.) |Critical| From:
OB2BAR_POSTGRES_BAR@<hostname> "DPIDB" Time: <Date><Time> An internal error occurred. Resolution: The
facade.dll file is modified to correctly handle the Data Protector Internal Database (IDB) backup session. Change Request:
QCCR2A54256: Symptom: The Data Protector backup and object copy sessions fail with the following error message:
|Critical| From: BSM@<hostname> "" Time: <Date><Time> Cannot synchronize the Media Management and Catalog
database. The session will terminate. Resolution: The Data Protector is modified to minimize Media Management and
Catalog database synchronization failures. Change Request: QCCR2A54260: Symptom: The Data Protector restore session
fails with the following error message: |Normal| From: RSM@<hostname> "" <Date><Time> Restore session "" started.
=========================== Session aborted! =========================== Resolution: The rsm and dbsm
binaries are modified to function correctly during a restore session. Change Request: QCCR2A54280: Symptom: Several
backup sessions fail simultaneously and the Backup Media Agents (BMAs) ends abnormally. |Major| From:
BSM@<hostname> "" <Date><Time> |61:3003| Lost connection to BMA named "" on host <hostname>. Ipc subsystem
reports: "IPC Read Error System error: |10054| Connection reset by peer Resolution: The bma binary is modified to correctly
handle the various backup sessions. Change Request: QCCR2A54295: Symptom: The Data Protector scheduled object copy
session ends abnormally. Resolution: The Data Protector Copy and Consolidation Session Manager (CSM) is modified to
function correctly during scheduled object copy sessions. Change Request: QCCR2A54302: Symptom: The Data Protector
object copy session ends abnormally after installing the Data Protector 8.12_202 Cell Server and Core patches. Resolution:
The Data Protector Copy and Consolidation Session Manager (CSM) is modified to function correctly during object copy
sessions. Change Request: QCCR2A54327: Symptom: When reporting creates an HTML file, the Lotus Notes versions 8.5
and 9.0 fails with the following error message: "MORE THAN 64 COLUMNS IN HTML TABLE" Resolution: The Data
Protector omnirc variable "OB2_RPT_FLOW_LOTUS_COMPATIBLE" is added to reduce the number of columns from 82 to
64, and below. Change Request: QCCR2A54328: Symptom: The restore from multiple segments using the Data Protector
Volume Restore Disk Agent (VRDA) takes longer duration. Resolution: The rsm binary is modified to correctly handle the
restore from multiple segments. Change Request: QCCR2A54392: Symptom: When running the full backup of Changed
Block Tracking (CBT), the following error message appears: Virtual Machine 'VM': Could not gather changed blocks on disk
scsi0:0... Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified to correctly perform the
27of32
9/14/20151:58PM
full backup of Changed Block Tracking (CBT) without any error messages. Change Request: QCCR2A54416: Symptom:
When running more than four backup sessions in parallel with B2D device, the Data Protector backup session fails with the
following error message: |Normal From: BSM@<hostname> "" <Time>: <Date><Time> Backup session "" started. |Warning|
From: BSM@<hostname> "" <Time>: <Date><Time> There are no available connections on store "" for the device named ""
|GW 6768:0:107626430073417|. Resolution: The Media Management Daemon (MMD) is modified to correctly handle the
number of free connections and successfully complete the backup session. Change Request: QCCR2A54476: Symptom: The
"Single session" and "List Sessions" reports display different backup success rates. Resolution: The reporting functionality is
modified to display consistent values in the "Single session" and "List Sessions" reports. Change Request: QCCR2A54489:
Symptom: The mirror backup to two Store Once software devices stops responding when the store on the original device
stops responding. Resolution: The Data Protector Backup Session Manager (BSM) is modified to correctly handle the mirror
backup to two Store Once software devices when the store on the original device stops responding. Change Request:
QCCR2A54549: Symptom: The Data Protector "omnib2dinfo" command fails to execute correctly in Japanese environment.
Resolution: The StoreOnceInfo utility tool is modified to correctly execute the Data Protector "omnib2dinfo" command in
Japanese environment. Change Request: QCCR2A54561: Symptom: Investigate the restore issue by verifying all arguments
passed to the db2Restore() API call. Resolution: The db2bar binary is modified to internally display additional information
about the db2Restore() API call. Change Request: QCCR2A54623: Symptom: The Data Protector A.08.11 or SCSI-II library
repository slots are sorted incorrectly. Resolution: The facade and admin libraries are modified to correctly sort the Data
Protector SCSI-II library repository slots. Change Request: QCCR2A54656: Symptom: After an upgrade to Data Protector
8.12, the "omnirpt -report session_statistics" command displays unrealistic high values as follows: Data Written |GB|:
4473589651.61 <=== wrong value Resolution: The reporting functionality is modified to display real values in the
"session_statistics" report. Change Request: QCCR2A54681: Symptom: The Data Protector Daily Purge deletes sessions
with object versions that are still protected. Resolution: The Data Protector Daily Purge functionality is modified to function
correctly. Change Request: QCCR2A54706: Symptom: After an object copy session with "Change data and catalog protection
after successful copy" set to "None", the protection of original versions is still not set. Resolution: The csm and msm binaries
are modified to set all copy session objects to the desired value. Change Request: QCCR2A54749: Symptom: The restore of
a single VM as a new VM fails with the following error message: |Warning| From: VEPALIB_VMWARE@<hostname> ""
Time: <Date><Time> Virtual Machine "": Skipping restore ... |Normal| From: RSM@<hostname> "" Time: <Date><Time>
OB2BAR application on <hostname> disconnected. |Normal| From: RSM@<hostname> "" Time: <Date><Time> Session
abort request received by user ""@<hostname>. Resolution: The Virtual Environment Protection Agent (VEPA) is modified to
correctly restore a single Virtual Machine (VM) as a new VM. Change Request: QCCR2A54751: Symptom: After an upgrade
to Data Protector 8, the backup sessions report the following warning message: "A non-essential file cannot be found, backup
continues". Resolution: The non-essential list is modified to exclude the missing Session Manager Binary Files (SMBF) and
ensure that the backup behaves correctly. Change Request: QCCR2A54752: Symptom: When backing up VMWare Virtual
Machines through vCenter, the backup fails to resolve the vCenter by a short name. Resolution: The Virtual Environment
Protection Agent (VEPA) is modified with the addition of Data Protector "OB2_VEAGENT_DISABLE_DNS_RESOLVE"
omnirc variable to resolve vCenter and ESXi, and enable backup session to skip the DNS resolve. Change Request:
QCCR2A54760: Symptom: The daily purge activity deletes the object versions and detailed catalog of protected media or
sessions. Resolution: The Data Protector global option "DeleteUnprotectedMediaFreq=0" is added to avoid the deletion of
object versions and detailed catalog of protected media or sessions. Change Request: QCCR2A54772: Symptom: The Data
Protector "omnidbcheck" command fails with corrupted Detailed Catalog Binary Files (DCBF) error reporting different header
and physical size. Resolution: The Data Protector "omnidbcheck" utility is modified to report correctly the header and
physical size of Detailed Catalog Binary Files (DCBF). Change Request: QCCR2A54826: Symptom: The Data Protector
protected media in the Internal Database must not loose links to the Detailed Catalog Binary Files (DCBF). Resolution: The
Data Protector Daily Purge functionality is modified to function correctly. Change Request: QCCR2A54856: Symptom: The
Data Protector "omnidb -session SessionID -purge" command fails for replication sessions with the following error message:
Internal error: DbaXXXX functions. Resolution: The facade binary is modified to correctly handle replication sessions.
Change Request: QCCR2A54874: Symptom: The Data Protector Volume Backup Disk Agent (VBDA) fails with the following
error message: |Major| From: BSM@<hostname> "" Time:<Date><Time> |61:1002| The VBDA named "" on <hostname>
reached its inactivity timeout of 300 seconds. The agent on host will be shutdown. Resolution: The bsm binary is modified to
correctly handle the Data Protector Volume Backup Disk Agent (VBDA) timeouts. Change Request: QCCR2A54890:
Symptom: The restore of a virtual machine from the second imported disk fails with the following error message: |Major|
From: VEPALIB_VMWARE@<hostname> "" Time:<Date><Time> Restore failed. Resolution: The Data Protector Virtual
Environment Protection Agent (VEPA) is modified to correctly restore the virtual machine from the second imported disk.
Change Request: QCCR2A54902: Symptom: The Data Protector "omnib2dinfo" command fails to execute when one of the
gateways of a Backup to Disk (B2D) device does not function. Resolution: The Data Protector "omnib2dinfo" utility is
modified to correctly skip the non-functional gateways. Change Request: QCCR2A54930: Symptom: The Data Protector
Manager of Managers (MoM) licensing distribution server fails to recognize the assigned licences. Resolution: The "crs"
binary is modified to correctly distribute licenses in Data Protector Manager of Managers (MoM) environment. Change
Request: QCCR2A54935: Symptom: Object consolidations to a Store Once Software (SOS) device fails with the following
error: "Number of devices used is smaller than MIN value of load balancing." Resolution: The csm binary is modified to
correctly handle the minimum value of load balancing for Disk to Disk (D2D) devices. Change Request: QCCR2A54961:
Symptom: Tape capacity is incorrect after the format. Resolution: The Media Session Manager (MSM) is modified to accept
negative value and set the determined medium size. Change Request: QCCR2A54991: Symptom: When device mirroring is
used on Backup to Disk (B2D) devices, and the primary device is disabled, the backup operation fails on the mirror device.
The fault tolerance benefit is defeated. Resolution: The Data Protector Backup Session Manager (BSM) is modified to
correctly handle the backup operation on mirror devices. Change Request: QCCR2A55011: Symptom: The media with
28of32
9/14/20151:58PM
protected objects is not protected after an import operation. Resolution: The facade library is modified to protect media with
protected objects after an import operation. Change Request: QCCR2A55051: Symptom: VEPA considers wrong information
for disk name during quiescence backup, which results in wrong disk name after restore. Resolution: The vepalib_vmware.dll
file is modified to correctly backup machines. Change Request: QCCR2A55066: Symptom: During a filesystem restore on
AIX clients, the following error message is displayed: |Minor| From: VRDA@<hostname> <OBJECT> <TIME><DATE>
<FILENAME> Cannot set ACL: (|22| Invalid argument). Resolution: The vbda binary is modified to backup VXFS volume on
AIX clients without any errors. Change Request: QCCR2A55068: Symptom: The Data Protector Restore Session Manager
(RSM) ends abnormally when trying to restore from an incremental backup with an expired full backup. Resolution: The Data
Protector facade library is modified to successfully restore the selected data without any Restore Session Manager (RSM)
failures. Change Request: QCCR2A55077: Symptom: The Virtual Machine (VM) restore to a non-managed ESXi 5.5 server
fails with the following error message: |Major|] From: RSM@<hostname> "" <Date><Time> |61:3003| Lost connection to
OB2BAR restore DA named "" on host <hostname>. Ipc subsystem reports: "IPC Read Error System error: |10054|
Connection reset by peer Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified to
successfully allow VM restore to a non-managed ESXi 5.5 server. Change Request: QCCR2A55079: Symptom: The Detailed
Catalog Binary Files (DCBF) are corrupted, which reports different header and physical size. Resolution: The Data Protector
"omnidbcheck" command is modified to correctly handle the Detailed Catalog Binary Files (DCBF). Change Request:
QCCR2A55127: Symptom: When snapshot handling is set to "disabled" for non-CBT backups, few snapshots are not
removed. Resolution: The Data Protector Virtual Environment Protection Agent (VEPA) is modified to correctly handle the
deletion of Data Protector snapshot at the end of the backup. Change Request: QCCR2A55145: Symptom: The
OB2BAR_DB2LIB does not use OB2BARHOSTNAME environment variable resulting in wrong object names during backup.
Resolution: The libob2db2 binary is modified to correctly handle the global variable OB2BARHOSTNAME and create correct
object names during backup. Change Request: QCCR2A55148: Symptom: The Data Protector "omnirpt -report obj_avesize"
functionality reports only a single IDB backup object (ConfigurationFiles) for the IDB backup. Resolution: The facade library
is modified to display the real average for the IDB backup size. Change Request: QCCR2A55153: Symptom: The Data
Protector GUI displays incorrect values for "Used Media (GB)" in "Devices & Media" - "Pools" context. Resolution: The Data
Protector GUI is modified to display reasonable values for "Used Media (GB)" till the medium is overwritten for the first time.
By doing so, the latter values appear correctly. Change Request: QCCR2A55222: Symptom: The Data Protector Copy and
Consolidation Session Manager binary "csm" ends abnormally after a session abort request. Resolution: The Data Protector
Copy and Consolidation Session Manager binary "csm" is modified to correctly handle the session abort request. Change
Request: QCCR2A55287: Symptom: When trying to backup few virtual machines, the following error is displayed: |Critical|
From: VEPALIB_VMWARE@<hostname> "" <date><time> No Objects found for backup... Resolution: The vepa library is
modified to correctly handle Virtual machine backup without depending on the configuration file. Change Request:
QCCR2A55385: Symptom: When performing an SRD update on a Cell Manager and Data Protector Internal Database (IDB)
backup on mirrored devices, the Data Protector "omnisrdupdate" utility or GUI ends abnormally. Resolution: The Data
Protector "omnisrdupdate" utility or GUI is modified to correctly handle the SRD update on a Cell Manager and Data
Protector IDB backup on mirrored devices. Change Request: QCCR2A55405: Symptom: Restore of Data Protector VMware
vApp application integration fails with a "cannot write to disk" error. Resolution: The Virtual Environment Protection Agent
(VEPA) is modified to successfully restore the Data Protector VMware vApp application integration. Change Request:
QCCR2A55417: Symptom: The Barcode scan does not run properly with the special msm binary from QCCR2A54706_TM2.
An improved msm fix has been requested. Resolution: The msm binary is modified to ensure that the Barcode scan executes
as expected. Change Request: QCCR2A55423: Symptom: The restore of a Virtual Machine (VM) as a new VM fails with the
following error message: Error restoring item <filename>.vmx Resolution: The Virtual Environment Protection Agent (VEPA)
is modified to restore a Virtual Machine (VM) as a new VM. Change Request: QCCR2A55478: Symptom: The output of the
Data Protector "omnidb -rpt <sess_id> -detail" command displays session size that does not match the session report.
Resolution: The Data Protector "omnidb" utility is modified to correctly calculate the session size information. Change
Request: QCCR2A55500: Symptom: The backup of Data Protector application integration of EMC Symmetrix disk arrays fails
with the following error: |Major| From: SYMA@<hostname> "" Time: <Date><Time> Volume group /dev/vgdp81 has logical
volume(s) with errors. Too many disks have failed. Resolution: The Data Protector application integration of EMC Symmetrix
disk arrays is modified to function correctly when a customer initiates a backup. Change Request: QCCR2A55619: Symptom:
The Data Protector reporting functionality "omnirpt -report dl_info" fails to list the post-backup copy lists. Resolution: The
dbsm binary is modified to display the post-backup copy lists. Change Request: QCCR2A55709: Symptom: During an object
copy, the "csm" consumes several gigabytes of memory and stops responding. Resolution: The Data Protector facade library
is modified to reduce the use of memory and CPU in all types of automated copy jobs. Change Request: QCCR2A55769:
Symptom: The media consistency check fails for a medium that apparently does not exist. root@<hostname> sbin#
./omnidbcheck -media_consistency -detail Media consistency: Failed 0501020a:53546f58:435f:0002 root@<hostname> bin#
./omnimm -media_info "0501020a:53546f58:435f:0002" -detail Medium not found. Resolution: The Data Protector
"omnidbcheck" utility is modified to correctly handle the media consistency check. Change Request: QCCR2A55793:
Symptom: In Direct Backup category with 1 TB NDMP, the Licensing check displays incorrect values for License capacity.
Resolution: The bsm binary is modified to display correct values for License capacity during Licensing check. Change
Request: QCCR2A55872: Symptom: The serial numbers are not populated correctly from tape devices to tape library.
Resolution: The Data Protector "devbra" functionality is modified to populate serial numbers correctly from tape devices to
tape library. Change Request: QCCR2A55887: Symptom: The Data Protector replication session stops responding when all
gateway connections are used in other sessions. Resolution: The csm binary is modified to wait for all the required
replication devices to become available and proceed after the required devices are locked. Change Request:
QCCR2A55892: Symptom: When performing an SRD update on a Cell Manager and Data Protector Internal Database (IDB)
incremental backup on mirrored devices, the Data Protector "omnisrdupdate" utility or data protector user interface (GUI)
29of32
9/14/20151:58PM
ends abnormally. Resolution: The Data Protector "omnisrdupdate" utility or GUI is modified to correctly handle the SRD
update on a Cell Manager, and Data Protector IDB full and incremental backup on mirrored devices. Change Request:
QCCR2A55916: Symptom: The Data Protector "omnirpt -report session_errors -timeframe 24 24" command fails when a
specific hostname is specified by the "-hosts" option. Resolution: The Data Protector reporting functionality is modified to
correctly handle the "-host" parameter. Change Request: QCCR2A56349: Symptom: The "Housekeeping" feature of
StoreOnce is not working as expected for all stores. Some stores might be running while the HouseKeeper is not. The
consequence is that the HK jobs are not being executed and disk space is not being freed. Resolution: The
StoreOnceSoftware utility is modified to handle "housekeeper jobs" correctly for all stores. In case that HK encounters any
kind of problem Store is stopped until the proper manual resolution is applied. SPECIAL NOTE: To check if suffering from
this problem please navigate to store root and search for content of the "retired" folder. Multiple entries in retired folder mean
that the HK of corresponding store is not running. If this is the case, then probably stores will not start when upgraded to this
patch level. Please consult support on how to approach this problem and manually resolve the HK problems in order to make
stores start. Change Request: QCCR2A56430: Symptom: When recovering files using the HP Data Protector Granular
Recovery Extension with the NDMP component, the following error message is displayed: "Unable to present shared disks Invalid parameters to enter share" Resolution: The Data Protector vmwaregre-agent.exe is modified to function with the
NDMP component. Change Request: QCCR2A56433: Symptom: The Data Protector object mirroring fails with the following
error message: |Major| From: BSM@<hostname> "" Time: <Date><Time> FAILED to start mirror of object FileSystem "" "".
No mirror device with suitable block size found. Resolution: The bsm binary is modified to check the maximum number of
load balancing in all mirrored and original devices and use that number to start gateway instances. Change Request:
QCCR2A56669: Symptom: The Data Protector GUI ends abnormally during the SAPDB backup configuration. Resolution:
The Data Protector GUI is modified to function correctly when configuring SAPDB backup configuration. Change Request:
QCCR2A56794: Symptom: The Data Protector "omnirpt" command does not display data with the TAB option:
|root@cell_server mars| # omnirpt -rep single_session -ses <SessionID> -level critical -tab #Single Session Report #Cell
Manager: cell_server #Creation Date: <date><time> #Session Information #Headers Resolution: The Data Protector
"omnirpt" command is modified to display correct data with the TAB option. Change Request: QCCR2A56980: Symptom:
Cannot write to a StoreOnce device. |Major| From: _BMA@<hostname>_ Time: <Date><Time> |90:51| Cannot write to
device (StoreOnce error: The object store is not ready) Resolution: The StoreOnceSoftware utility is modified to cleanup the
recycle folder and prevent the store from stopping. Change Request: QCCR2A57227: Symptom: The Data Protector
documentation does not state that the object copy requires licenses for both reading (source) and writing (target) devices,
unlike restore where no licenses are required for reading (source) devices. Resolution: The HP Data Protector 9.00
Installation Guide is modified to reflect a NOTE in the Traditional licensing section. Change Request: QCCR2A57355:
Symptom: The Data Protector documentation does not state that the Data Protector GUI fails with a "bad file format" error
message during the Data Protector 8.12 LDAP authentication. Resolution: The following guides are modified to reflect the
details: - HP Data Protector 9.00 Administrator's Guide - HP Data Protector 9.00 Installation Guide Change Request:
QCCR2A57405: Symptom: The existing restore chain changes when a media is imported and the following changes are
visible in the restore context: - Missing media. - Missing object version. Replication in D2D devices are implemented
internally as an import, which means that replication is also affected. Resolution: The Data Protector "omnidbutil" utility
repairs or corrects the existing database contents and facade library corrects the issue. Steps to repair IDB: 1. Make sure that
no Data Protector sessions are running 2. Stop Data Protector services by running omnisv stop 3. Start Data Protector IDB
services by running omnisv start -idb_only 4. Call omnidbutil -check_graph -all_objects The time it takes to correct the IDB
depends on the number of objects/object versions in the database. During this time no sessions should be started.
Alternatively, the -check_graph can be called object by object: omnidbutil -check_graph -object <OBJECT> 5. Restart the
services omnisv stop omnisv start DPLNXBDL_00901: Change Request: QCCR2A44987: Symptom: Support for the NetApp
SnapManager integration for VMware (Virtual Infrastructure) is not available with Data Protector. Resolution: Data Protector
introduces support for the NetApp SnapManager integration for VMware (Virtual Infrastructure). Change Request:
QCCR2A53699: Symptom: Support for copying virtual machine backups to HP public cloud storage is not available with Data
Protector. Resolution: Data Protector introduces support for copying virtual machine backups to and from HP public cloud
storage with the help of a new device.
Change Requests
30of32
9/14/20151:58PM

QCCR2A62810 QCCR2A62813 QCCR2A62914 QCCR2A62975 QCCR2A63076
Other Dependencies
To apply the fix documented in QCCR2A53188, make sure you restart the Oracle services to start from a clean state.
Installation Instructions
Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and
conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch.
------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the
patch to a temporary directory: /tmp/DPLNXBDL_00904. Make sure that there exist no other files in the temporary directory. 4.
Please extract the patch DPLNXBDL_00904.tar using: tar xvf DPLNXBDL_00904.tar 5. Please find all the Data Protector
processes running on the system and close them all before installing the patch. 6. Run omnisetup.sh to install the patch,
omnisetup.sh -bundleadd b904 NOTE: The patch documentation is available on the HP support website at
https://softwaresupport.hp.com/group/softwaresupport/search-result /-/facetsearch/document/LID/DPLNXBDL_00904. How to
Remove the Patch ======================= NOTE: Uninstallation of the patch will revert all the components which are
part of the patch to the original product release. Hence, any previously installed patch for this component will be erased. 1.
Before uninstalling the patch, make sure that all the upgraded patches that were potentially installed after DPLNXBDL_00904
31of32
9/14/20151:58PM
have been uninstalled from the system. 2. Back up your system before uninstalling the patch. 3. Please find all the Data
Protector processes running on the system and close them all before uninstalling the patch. 4. To remove the patch execute
the omnisetup.sh script as shown below: omnisetup.sh -bundlerem b904 5. Individual components from the patch can be
uninstalled manually from the system by following the Data Protector patch uninstall procedures mentioned below. However,
you should do so, only if advised by HP Support because other installed patches may depend on the one you are uninstalling.
For example: If you want to remove core patch, execute the command # rpm -qa | grep CORE_Patch, the Output of the above
# command will be "CORE_Patch-A.09.00-1" To remove the patch execute rpm -e CORE_Patch-A.09.00-1
Special Installation Instructions

DPLNXBDL_00904: NOTE! This patch must be installed on both, the Installation Server(IS) host and the Cell Server(CS)
host. This patch DPLNXBDL_00904 contains and installs the following Data Protector components. DPLNX-00369 - Core
patch DPLNX-00370 - Cell Server patch DPLNX-00371 - Disk Agent patch DPLNX-00378 - Media Agent patch DPLNX-00379 Cell Console patch DPLNX-00380 - Documentation patch DPLNX-00381 - DR patch DPLNX-00382 - VE Agent patch
DPLNX-00383 - VMWARE-GRE patch DPLNX-00384 - NETAPP patch DPLNX-00385 - SMISA patch DPLNX-00386 - DB2
patch DPLNX-00387 - EMC patch DPLNX-00388 - SAP HANA patch DPLNX-00389 - SOS patch DPLNX-00390 - SSEA patch
DPLNX-00391 - EMCVNX patch DPLNX-00392 - EMCVMAX patch DPLNX-00393 - MySQL patch DPLNX-00394 - Sybase
patch If the patch is installed on a Cell Server system, only the CS patch will be installed on the system. To get fixes for other
agents on the Cell Server, please install the patch on an IS and then update the CS. The Data Protector client systems must
be updated from the IS after the installation of the patch in order to get the fixes into effect. WARNING! The components of the
patch DPLNXBDL_00904 have dependencies on each other, thus the complete patch should be installed as a whole. Never
try to install the individual components from the patch forcefully unless told by Data Protector support. Installation of individual
components from the patch may cause malfunctions in Data Protector. Similarly, never uninstall an individual component from
the patch. To install/uninstall the patch, please see the above instructions. This patch does not include Site Specific Patches.
Supersedes
DPLNX_00317: Core patch DPLNX_00316: Cell Server patch DPLNXBDL_00903: data protector 9.03 for Linux/64
DPLNXBDL_00902: data protector 9.02 for Linux/64 DPLNXBDL_00901: Linux - Data Protector 9.01
Patch Files
DPLNXBDL_00904.tar
sum(1) Output
md5 ec981deeffbbf3537bc804e2a0d2841d DPLNXBDL_00904.tar
32of32
9/14/20151:58PM

Data Protector 9.04 Patch for Linux/64

Uploaded by

Document Information

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

Data Protector 9.04 Patch for Linux/64

Uploaded by

Copyright:

Available Formats

dataprotector9.

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

Hardware Platforms - OS Releases

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

Resolved Known Problems

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

<date><time>/batch/BGInfo.bmp ----r----- -2 -2 599 <date><time>/batch/SendMail.ps1 ----r----- -2 -2 751 <date><time>/batch

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

QCCR2A54132 QCCR2A54143 QCCR2A54166 QCCR2A54195 QCCR2A54205 QCCR2A54215 QCCR2A54228

h ps://so waresupport.hp.com/group/so waresupport/searchresu...

Special Installation Instructions

You might also like