dpwinbdl 00902 wins

7/17/2019 Dpwinbdl 00902 Wins

http://slidepdf.com/reader/full/dpwinbdl-00902-wins 1/23

Title :

Data Protector 9.0

Document ID :DPWINBDL_00902Product - Version:

data protector 9.0 9.01 9.02 ;OS :

Updated :

2014-Dec-22Critical :

yesSummary :

Product: data protector; Version: 9.0, 9.01, 9.02; OS: Windows; Critical: Yes» Register to receive e-mail notification about patch updates for data protector, 9.0,9.01,9.02,» Register to receive e-mail notifications

Table of contents:

» Should I download? » Download Information » History » Products »Hardware Platforms - OS Releases » Critical » Enhancements »Symptoms » Defect Descriptions » Change Requests » Installation Information » Installation Instructions » Special InstallationInstructions » Patch Contents » Supersedes

Pat ch I D: DPWINBDL_00902

Downl oadpat ch:

DPWI NBDL_ 00902. exe

Pat ch si ze: 1. 65 GB

MD5 hash: 4f 3f 036320d205d3836a6d6145daf bd2

2014- Dec- 12: The pat ch was cr eat ed.

2014- Dec- 22: The pat ch was rel eased.

data protector 9.0 data protector 9.01 data protector 9.02

Data Protector 9.0

Feedback

rch Result - HP Software Support https://softwaresupport.hp.com/group/softwaresupport/search-result/-/f...

23 1/27/2015 9:41 AM



Windows: 2008-x64 2012-x64

Yes DPWINBDL_00902: CORRUPTION HANG ABORT CORRUPTION QCCR2A50540CORRUPTION QCCR2A54772 CORRUPTION QCCR2A55079 HANG QCCR2A51421 HANGQCCR2A51908 HANG QCCR2A52604 HANG QCCR2A53392 HANG QCCR2A53417 HANGQCCR2A53446 HANG QCCR2A54132 HANG QCCR2A54489 HANG QCCR2A55709 HANGQCCR2A55887 ABORT QCCR2A51881 ABORT QCCR2A52780 ABORT QCCR2A53419 ABORT QCCR2A53792 ABORT QCCR2A53821 ABORT QCCR2A54260 ABORTQCCR2A54749 ABORT QCCR2A55222

Yes DPWINBDL_00902: Change Request: QCCR2A48382: Symptom: Support for restoringlibraries with custom template type in SharePoint GRE is not available in Data Protector.Resolution: Data Protector introduces support for granular recovery of lists with Custom IDvalue. However, the success of granular recovery depends on the list customization. ChangeRequest: QCCR2A50354: Symptom: Support for DB2 10.1 database and archived Log backupusing IBM DB2 database standards on SUSE Linux Enterprise Server (SLES) 11 SP3 is notavailable in Data Protector. Resolution: Data Protector now supports DB2 database and

archive logs backups using IBM DB2 "VENDOR" option for all operating systems supported byData Protector DB2 Integration. Change Request: QCCR2A52510: Symptom: The DataProtector session manager fails when StoreOnce Catalyst Stores do not have availableconnections. Resolution: The Data Protector session manager and backup media agent aremodified to queue sessions until connections are available. Change Request: QCCR2A53792:Symptom: When the user abort is initiated during the replication session, the Abort commandis not sent to the Catalyst API of the D2D box. Resolution: Data Protector introduces supportfor the user abort initiation during the replication session. The Abort command is sent to thesource and target stores through the Catalyst API. After this step, any media that is replicatedduring 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 displayingVM 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 inData Protector. Resolution: Data Protector introduces support for licence reporting for CapacityBased Licensing (CPL). Change Request: QCCR2A54899: Symptom: Support for handling theapplication database and device concurrency during backup is not available with DataProtector. Resolution: Data Protector introduces support for handling application database anddevice 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


23 1/27/2015 9:41 AM



Infrastructure) is not available with Data Protector. Resolution: Data Protector introducessupport for 3PAR integration for VMware (Virtual Infrastructure). Change Request:QCCR2A56398: Symptom: Support for backup of Resilient File System (ReFS) is not availablewith Data Protector. Resolution: Data Protector introduces support for backup of Resilient FileSystem (ReFS). Change Request: QCCR2A57443: Symptom: Support for pausing the runningbackup sessions automatically when the scheduled higher priority jobs share the same deviceis 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 samedevice. The paused jobs are resumed once the device is available. Change Request:QCCR2A57446: Symptom: Support for managing replication between Data Domain devices isnot available with Data Protector. Resolution: Data Protector introduces support for managingreplication 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 RecoveryExtension (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 itscontinuity with the old FLEX functionality. - vCenter 5.5 update 1 onwards with a new look andfeel for the GRE plugin, supporting Windows and Linux vCenter, and single vCenter communication between multiple Cell Managers. Change Request: QCCR2A57493: Symptom:Cell Manager support for Microsoft Failover Cluster on Windows Server 2012 or 2012 R2 isnot available with Data Protector. Resolution: Data Protector introduces Cell Manager supportfor Microsoft Failover Cluster on Windows Server 2012. Change Request: QCCR2A57495:Symptom: Support for VEPA Hardening including the following is not available with DataProtector: - 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 supportfor 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 inFrench 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 notavailable with Data Protector. Resolution: Data Protector introduces support for localizing theData Protector 9.00 documentation in Japanese. Change Request: QCCR2A57575: Symptom:Support for localizing the Data Protector 9.00 documentation in Simplified Chinese is notavailable with Data Protector. Resolution: Data Protector introduces support for localizing theData Protector 9.00 documentation in Simplified Chinese.

DPWINBDL_00902: Change Request: QCCR2A46153: The Data Protector "omnidbutil-show_locked_devs" command does not display locks because the "omnidbutil" commandreceive buffer size is 200 kB or 512 kB; which is too small. Change Request: QCCR2A48585:Oracle backups do not use the devfilter option (/etc/opt/omni/server/cell/devfilters) whenStoreOnce 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. Change Request:QCCR2A48627: During an object copy session, the following warning is displayed: |Warning|


23 1/27/2015 9:41 AM



From: CSM@<hostname> "" Time: <Date><Time> There are no available connections ongateway "" for the device named "". Change Request: QCCR2A48923: The Data Protector GUIdisplays incorrect values for objects during a copy session. Change Request: QCCR2A49228:The Data Protector 8.0 GUI incorrectly displays the media allocation order. Change Request:QCCR2A50000: After a successful replication session between the two B6200, the copy totape fails due to either type of 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 mediafor 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) Change Request:QCCR2A50234: Expanding objects in the Data Protector GUI restore context takes a longtime. Change Request: QCCR2A50504: After an upgrade from Data Protector 7.01 to 8.0, theMedia 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.00b596 DbgStack: DbgFcnOut() and level already 0! ExitFcn="SCTL_Write" Change Request:QCCR2A50540: During an object copy session after a failed backup session, the followingerror is displayed: |Major]|From: RMA@<hostname> "" Time: <Date><Time> |90:48| Medium iscorrupted, trying to reconstruct. Change Request: QCCR2A50778: The Data Protector "omnidb -list_changed_protection" command does not execute correctly on Windows andLinux operating systems. Change Request: QCCR2A50844: Large environments that areusing Data Protector to write on StorageTek devices like STK T10000C drives are not able tofully utilize the cartridge capacity of 5 terabytes (TB), since the current Data Protector limit is 4TB. Change Request: QCCR2A50896: The Data Protector Internal Database (IDB)consistency check fails. Change Request: QCCR2A50919: The Data Protector restore sessionwith 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 "" ChangeRequest: QCCR2A51260: After an upgrade to Data Protector 8.1, the backup session of NSSvolumes on Novell OES 11 ends abnormally with the following error message, if the folder andfilenames 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." Change Request:QCCR2A51266: The Data Protector backup session fails with the following error message:

|Critical| From: BSM@<hostname> "" Time: <Date><Time> |61:6002| Error receiving catalogdata from the BMA@<hostname> "". Ipc subsystem reports: "IPC Read Error System error:|110| Connection timed out" Change Request: QCCR2A51326: The import of media-relatedcatalog data from Media Container Format (MCF) files fail with the following error: 1241.Change Request: QCCR2A51421: The Data Protector "omnimm -delete_unprotected_media"command stops responding. Change Request: QCCR2A51551: The SNMP trap for "EndOfSession" event in the Data Protector does not display the correct parameters in theParameter String. Change Request: QCCR2A51680: The Data Protector restore session failswith 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. Change Request: QCCR2A51705: The Data Protector GUI fails with the followingerror 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 anExpression. Change Request: QCCR2A51718: The users configured in the Operator DataProtector user group are unable to browse the filesystems to easily create and save backup


23 1/27/2015 9:41 AM



specifications as it requires user impersonation. Change Request: QCCR2A51827: When theData Protector 8.1 backup specifications are assigned to groups, the "View by: Group" in theData Protector Object Operations context displays all groups twice. Change Request:QCCR2A51880: The Data Protector Internal Database (IDB) backup session fails with thefollowing error message: |Critical| From: OB2BAR_POSTGRES_BAR@<hostname> "" Time:<Date><Time> An internal error occurred. Change Request: QCCR2A51881: The DataProtector 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 "" onhost 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. ChangeRequest: QCCR2A51908: The Data Protector VMware Granular Recovery Extension (GRE)restore session stops responding when the Media Agent (MA) on the StoreOnce device isstarted. Change Request: QCCR2A51920: When executing the Data Protector "omnidb-oracle8 -detail" command, the following error message is displayed: "No query data found." Italso fails to report the data for the rest of the oracle8 objects. Change Request:QCCR2A52063: All tapes are not displayed when the Data Protector 8.1 "omnimm-list_scratch_media" command is executed. Change Request: QCCR2A52211: The DataProtector 7.03 Microsoft SQL Server Integration backup session on Windows Server 2003 failswith the following error message: |Warning| From: user@<hostname> "" Time: <Date><Time>No data for user user@<hostname> in Inet's impersonation configuration. Change Request:QCCR2A52223: When the Data Protector "omnirpt -repot dl_info" command is executed onHP-UX 11.31 IA 64 system, the output does not display Microsoft SQL, Oracle, or the file

systems. Change Request: QCCR2A52418: The Data Protector backup sessions on Linuxsystems fails with the following error message: |Major| From: BMA@<hostname> "" Time:<Date><Time> |90:65| /dev/nst11 Cannot append to medium (Invalid device block size1024KB,should be 512KB.) Change Request: QCCR2A52428: The Data Protector debug.logfile 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" Change Request: QCCR2A52442: The importing of theData Protector Network Data Management Protocol (NDMP) Server Integration media onWindows Server 2008 R2 Standard fails with the following error message: |Major| From:

MSM@<hostname> "" Time: <Date><Time> |65:99| Import failed with possible cause: thismedia 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 toprocess this command. Change Request: QCCR2A52474: The Virtual Environment Integration(VEPA) component builds slowly. Change Request: QCCR2A52479: The Data Protector objectconsolidation 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| Change Request: QCCR2A52497: The Data Protector Copy and

Consolidation Session Manager (CSM) process ends unexpectedly during large replicationsessions. Change Request: QCCR2A52578: After an upgrade from Data Protector 6.21 to 8.xin a Linux Manager-of-Managers (MoM) environment, the media consistency checks fail on theCell Manager. Change Request: QCCR2A52592: The Data Protector "omnirpt -reportobj_lastbackup" command fails with the following error message: Error creating the report


23 1/27/2015 9:41 AM



"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: '' ChangeRequest: QCCR2A52604: The Data Protector 6.21 Centralized Media Management Database(CMMDB) stops responding. Change Request: QCCR2A52660: During the execution of DataProtector "omnidbutil -purge_daily" command, the Internal Database (IDB) records "orphan"DCBF_INFO entries and their corresponding Detail Catalog Binary Files (DCBF) from disk.Change Request: QCCR2A52664: 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. ChangeRequest: QCCR2A52692: When trying to modify the Media Agent (MA) in a multipath device ineither the Manager-of-Managers (MoM) or Central Media Management Database (CMMDB),the Data Protector 8.01 GUI fails with the following error message: "The parameter isincorrect". Change Request: QCCR2A52754: During the object copy session, the DataProtector Copy and Consolidation Session Manager process (CSM) attempts to copy objectsthat are not selected in the object copy specification. Change Request: QCCR2A52780: After upgrading to Data Protector 8.11 on Windows Server 2008, the Data Protector object copysession 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> Change Request: QCCR2A52848:The Data Protector Microsoft SQL Server integration backup session with the server-sidededuplication 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 ChangeRequest: QCCR2A52972: The Data Protector backup session displays the followingmessages: |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 notuse the cartridge for further backup operations. Change Request: QCCR2A53053: The DataProtector 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 identificationsignature to disk "". Change Request: QCCR2A53122: The Data Protector backup session ona Windows server completes successfully and fails to display a warning message though theBackup Cluster Database is not backed up. Change Request: QCCR2A53142: When queryingreports using the Data Protector "omnirpt" command on Windows Server 2008 R2 up to acertain timeframe, the report gets truncated and displays (null) at the bottom of the page.Change Request: QCCR2A53146: After upgrading from Data Protector 6.21, the DataProtector Copy and Consolidation Session Manager (CSM) process locks multiple sourcedevices during an object copy session. Change Request: QCCR2A53150: The Data Protector Volume Backup Disk Agent (VBDA) ends unexpectedly during the configuration backup

session. Change Request: QCCR2A53177: The Data Protector Cell Request Server process(service) fails with the following error message: |12:1604| Cannot reach the CRS on the CellManager system. CRS on the Cell Manager host is not reachable or is not up and running.System error: |111| Connection refused Change Request: QCCR2A53228: 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. TheMedia Management daemon reports: "Medium not found." Change Request: QCCR2A53248:The backup of a Virtual Machine (VM) managed by a vCenter cannot be restored to an ESXserver not managed by a vCenter. The restore session fails with the following error message:|Major| From: VEPALIB_VMWARE@hostname "" Time: <Date><Time> Restore failed. Change

Request: QCCR2A53251: After upgrading to Data Protector 7.0 on Windows Server 2008, theCatalog protection for the filesystem backup sessions is not set correctly when the protectionis set to "Same as data protection". Change Request: QCCR2A53275: When the DataProtector "omnicheck" command is executed with the "-dns -full" option, the Data Protector "omniinet.exe" process on the Cell Manager ends unexpectedly. Change Request:


23 1/27/2015 9:41 AM



QCCR2A53282: The Data Protector restore session from a differential backup fails with thefollowing error message: |Major| From: OB2BAR_SQLBAR@<hostname> "" Time: <Date><Time> Error has occurred while executing a SQL statement. Error message: "". Use WITHMOVE to identify a valid location for the file. SQLSTATE:|42000| CODE:(1834)MESSAGE:|Microsoft||ODBC SQL Server Driver||SQL Server| The file "" cannot beoverwritten. It is being used by database "". Change Request: QCCR2A53298: When trying tobrowse for clients in the backup specification of the client Cell Manager (CM), the Data

Protector 8.11 Manager-of-Managers (MOM) GUI reports a client violation error. ChangeRequest: QCCR2A53300: 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 "" B2Ddevice! |Normal| From: MMA@<hostname> "" Time: <Date><Time> ABORTED Media Agent ""Change Request: QCCR2A53330: While copying objects from a restarted session, thefollowing 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> Change Request:QCCR2A53381: When the NSS file systems data is used for enhanced incremental backupand later for consolidation, the object consolidation session ends unexpectedly with thefollowing error: |Normal| From: CSM@<hostname> "" Time: <Date><Time> STARTING cataloganalysis of FileSystem disk_agent_client.com:"" from session <Date><Time>. ChangeRequest: QCCR2A53392: After upgrading from Data Protector 6.21 to 7.03, the VolumeBackup Disk Agent (VBDA) stops responding and displays the following error message:|Major| From: BSM@<hostname> "" Time: <Date><Time> |61:1002| The VBDA named "" onhost client.com reached its inactivity timeout of 7200 seconds. The agent on host will beshutdown. Change Request: QCCR2A53417: The Data Protector administrative command"devbra" stops responding while running on Windows Server 2003. Change Request:QCCR2A53419: The Data Protector Volume Backup Disk Agent (VBDA) ends abnormally withthe following error message: |Critical| From: VBDA@<hostname> "" Time: <Date><Time>

Connection to Media Agent broken => aborting. Change Request: QCCR2A53433: The DataProtector "omnirpt -report single_session" command does not calculate the correct objectstatus. Change Request: QCCR2A53444: The Data Protector backup session on HP-UX 11.31fails with the following error message: |Warning| From: BSM@<hostname> "" Time: <Date><Time> |61:2013| Some of the backup devices are occupied. Session is waiting for all thedevices to get free. Locknames after "autoconfigure" are not unique in case of longer serialnumbers. Change Request: QCCR2A53446: The Data Protector Backup Session Manager (BSM) on HP-UX 11.31 stops responding when the "OMNI_HOSTS" environment variable isused. Change Request: QCCR2A53449: After upgrading from Data Protector 6.20 to 8.1, theData Protector "Session per client report" does not display the correct information. Change

Request: QCCR2A53483: The Data Protector 8.0 debug.log on Windows Server 2008includes 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" Change Request: QCCR2A53584: The Data Protector 8.1Context-Sensitive Help (F1) does no longer include detail information provided as pop-ups.Change Request: QCCR2A53593: The Data Protector media import session fails with thefollowing 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 agentdisconnected. Session completed, status=5 Change Request: QCCR2A53639: ConcurrentData Protector Oracle Integration backup sessions that use same devices fail to complete

successfully. Change Request: QCCR2A53663: After upgrading from Data Protector 7.0 to8.11, changing the data or catalog protection on a single object in the Data Protector GUIchanges the protection for both the original and copy object. Change Request:QCCR2A53775: The Data Protector "omnidbutil -purge -dcbf" command takes a long time tocomplete. Change Request: QCCR2A53783: The Data Protector 8.11 Session flow report


23 1/27/2015 9:41 AM



does not mark queuing sessions and statistics reports with the Blue color. Sometimes, thequeuing statistics reports appear incorrectly. Change Request: QCCR2A53815: The DataProtector Cell Request Server (CRS) process (service) creates additional/unwanted debugs inall 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 backupsession uses an SOS device on the RedHat client. Change Request: QCCR2A53821: TheData 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> Nodevice that matches object "" with device filter "" was found. Client will be aborted. ChangeRequest: QCCR2A53827: The Data Protector 8.12 backup session on Windows Server 2012Cell Manager and VMware backup host with the Changed Blocked Tracking (CBT) option fails,while the full backup sessions complete successfully. Change Request: QCCR2A53884: Whenthe Data Protector 8.12 "omnidbutil-purge -daily" command is executed, the following error message is displayed: "Operation failed." Change Request: QCCR2A53970: The DataProtector documentation does not clearly state whether the Data Protector Cell Manager issupported on HPUX-PA RISC processors or not. Change Request: QCCR2A54030: The DataProtector Internal Database (IDB) fails after upgrading to 8.01 version. Change Request:QCCR2A54071: The email notification for the Data Protector Internal Database (IDB) backupis not readable when using the Japanese language. Change Request: QCCR2A54089: TheData Protector "omnimm -delete_unprotected_media" command fails to delete the missingmedia in the target Backup to Disk (B2D) stores, preventing the deletion of the related Internaldatabase (IDB) information, including the Detail Catalog Binary Files (DCBFs). ChangeRequest: QCCR2A54093: The Data Protector reporting command "omnirpt" fails with thefollowing error message: /opt/omni/bin/omnirpt -report session_errors -timeframe 800 800Error creating the report "Interactive": File/directory not found. System error: |2| No such file or directory. Change Request: QCCR2A54132: Multiple backups of different specifications thatuse mirroring stops responding if the first backup session is terminated. Change Request:QCCR2A54166: The Data Protector times out while enumerating virtual machines. Change

Request: QCCR2A54195: The Data Protector GUI becomes unresponsive and takes a longtime when objects in the restore context are expanded. Change Request: QCCR2A54215: TheData Protector GUI restore context fails for an incremental (Incr1) backup and displays themedia of a full backup session. Change Request: QCCR2A54228: The Data Protector VMwarerestore session on Windows Server 2008 R2 is performed on the wrong cluster. ChangeRequest: QCCR2A54250: The Data Protector Internal Database (IDB) backup session failswith 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 internalerror occurred. Change Request: QCCR2A54256: 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. Thesession will terminate. Change Request: QCCR2A54260: The Data Protector restore sessionfails with the following error message: |Normal| From: RSM@<hostname> "" <Date><Time>Restore session "" started. =========================== Session aborted!=========================== Change Request: QCCR2A54280: Several backupsessions fail simultaneously and the Backup Media Agents (BMAs) ends abnormally. |Major|From: BSM@<host name> "" <Date><Time> |61:3003| Lost connection to BMA named "" onhost <host name>. Ipc subsystem reports: "IPC Read Error System error: |10054| Connectionreset by peer Change Request: QCCR2A54302: The Data Protector object copy session ends

abnormally after installing the Data Protector 8.12_202 Cell Server and Core patches. ChangeRequest: QCCR2A54327: When reporting creates an HTML file, the Lotus Notes versions 8.5and 9.0 fails with the following error message: "MORE THAN 64 COLUMNS IN HTML TABLE"Change Request: QCCR2A54328: The restore from multiple segments using the DataProtector Volume Restore Disk Agent (VRDA) takes longer duration. Change Request:


23 1/27/2015 9:41 AM



QCCR2A54392: When running the full backup of Changed Block Tracking (CBT), the followingerror message appears: Virtual Machine 'VM': Could not gather changed blocks on diskscsi0:0... Change Request: QCCR2A54416: When running more than four backup sessions inparallel 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 availableconnections on store "" for the device named "" |GW 6768:0:107626430073417|. Change

Request: QCCR2A54476: The "Single session" and "List Sessions" reports display differentbackup success rates. Change Request: QCCR2A54489: The mirror backup to two StoreOnce software devices stops responding when the store on the original device stopsresponding. Change Request: QCCR2A54523: The Data Protector GUI does not connect tothe cell server and prompts for the Lightweight Directory Access Protocol (LDAP) logincredential. Change Request: QCCR2A54549: The Data Protector "omnib2dinfo" commandfails to execute correctly in Japanese environment. Change Request: QCCR2A54623: TheData Protector A.08.11 or SCSI-II library repository slots are sorted incorrectly. ChangeRequest: QCCR2A54656: After an upgrade to Data Protector 8.12, the "omnirpt -reportsession_statistics" command displays unrealistic high values as follows: Data Written |GB|:4473589651.61 <=== wrong value Change Request: QCCR2A54679: The Data Protector GUIends abnormally when configuring the settings for a restore of SAPDB server. ChangeRequest: QCCR2A54681: The Data Protector Daily Purge deletes sessions with objectversions that are still protected. Change Request: QCCR2A54705: The Data Protector "list_stores" command fails on any Windows Media Agent (2008 R2 and 2012 R2), where DataProtector 8.12 is installed. Regardless of a local StoreOnceSoftware B2D device or the DataProtector "-host= parameter" command being used. Change Request: QCCR2A54706: 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. Change Request: QCCR2A54749: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>. Change Request: QCCR2A54751: After an upgrade to Data Protector 8, the backup sessions report the following warningmessage: "A non-essential file cannot be found, backup continues". Change Request:QCCR2A54752: When backing up VMWare Virtual Machines through vCenter, the backup failsto resolve the vCenter by a short name. Change Request: QCCR2A54755: In Japaneseenvironment, the target object options "Logging : Same as Source" is not displayed correctly.Change Request: QCCR2A54760: The daily purge activity deletes the object versions anddetailed catalog of protected media or sessions. Change Request: QCCR2A54772: The Data

Protector "omnidbcheck" command fails with corrupted Detailed Catalog Binary Files (DCBF)error reporting different header and physical size. Change Request: QCCR2A54826: The DataProtector protected media in the Internal Database must not loose links to the Detailed CatalogBinary Files (DCBF). Change Request: QCCR2A54856: The Data Protector "omnidb -sessionSessionID -purge" command fails for replication sessions with the following error message:Internal error: DbaXXXX functions. Change Request: QCCR2A54874: 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. ChangeRequest: QCCR2A54890: 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. Change Request: QCCR2A54902: The Data Protector "omnib2dinfo" command fails to execute when one of the gateways of a Backup to Disk (B2D)device does not function. Change Request: QCCR2A54930: The Data Protector Manager of Managers (MoM) licensing distribution server fails to recognize the assigned licences. Change


23 1/27/2015 9:41 AM



Request: QCCR2A54935: Object consolidations to a Store Once Software (SOS) device failswith the following error: "Number of devices used is smaller than MIN value of load balancing."Change Request: QCCR2A54961: Tape capacity is incorrect after the format. ChangeRequest: QCCR2A54991: 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 faulttolerance benefit is defeated. Change Request: QCCR2A55011: The media with protectedobjects is not protected after an import operation. Change Request: QCCR2A55051: VEPA

considers wrong information for disk name during quiescence backup, which results in wrongdisk name after restore. Change Request: QCCR2A55068: The Data Protector RestoreSession Manager (RSM) ends abnormally when trying to restore from an incremental backupwith an expired full backup. Change Request: QCCR2A55076: When the library robotics SCSIpath is modified, the "Barcode Reader Support" and "Use barcode as medium label..." optionsare automatically disabled. Change Request: QCCR2A55077: 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 DAnamed "" on host <hostname>. Ipc subsystem reports: "IPC Read Error System error: |10054|Connection reset by peer Change Request: QCCR2A55079: The Detailed Catalog Binary Files(DCBF) are corrupted, which reports different header and physical size. Change Request:QCCR2A55127: When snapshot handling is set to "disabled" for non-CBT backups, fewsnapshots are not removed. Change Request: QCCR2A55145: The OB2BAR_DB2LIB doesnot use OB2BARHOSTNAME environment variable resulting in wrong object names duringbackup. Change Request: QCCR2A55148: The Data Protector "omnirpt -report obj_avesize"functionality reports only a single IDB backup object (ConfigurationFiles) for the IDB backup.Change Request: QCCR2A55153: The Data Protector GUI displays incorrect values for "UsedMedia (GB)" in "Devices & Media" - "Pools" context. Change Request: QCCR2A55222: TheData Protector Copy and Consolidation Session Manager binary "csm" ends abnormally after a session abort request. Change Request: QCCR2A55287: When trying to backup few virtualmachines, the following error is displayed: |Critical| From: VEPALIB_VMWARE@<hostname>

"" <date><time> No Objects found for backup... Change Request: QCCR2A55385: Whenperforming an SRD update on a Cell Manager and Data Protector Internal Database (IDB)backup on mirrored devices, the Data Protector "omnisrdupdate" utility or GUI endsabnormally. Change Request: QCCR2A55405: Restore of Data Protector VMware vAppapplication integration fails with a "cannot write to disk" error. Change Request:QCCR2A55417: The Barcode scan does not run properly with the special msm binary fromQCCR2A54706_TM2. An improved msm fix has been requested. Change Request:QCCR2A55423: The restore of a Virtual Machine (VM) as a new VM fails with the followingerror message: Error restoring item <filename>.vmx Change Request: QCCR2A55467: TheData Protector GUI does not permit the entry of more than 60 characters in the "Add Users

Name" field when the Lightweight Directory Access Protocol (LDAP) users or groups areadded. Change Request: QCCR2A55478: The output of the Data Protector "omnidb -rpt<sess_id> -detail" command displays session size that does not match the session report.Change Request: QCCR2A55619: The Data Protector reporting functionality "omnirpt -reportdl_info" fails to list the post-backup copy lists. Change Request: QCCR2A55709: During anobject copy, the "csm" consumes several gigabytes of memory and stops responding. ChangeRequest: QCCR2A55724: In Data Protector GUI, the source-side gateways are not availableafter selecting source-side deduplication at the start of backup specification creation. ChangeRequest: QCCR2A55764: The Cell Manager becomes unresponsive when multiple scheduledoperations are started (multiple running omnitrig.exe instances) and the debug.log file is

greater than 4GB. Change Request: QCCR2A55769: The media consistency check fails for amedium that apparently does not exist. root@<hostname> sbin# ./omnidbcheck-media_consistency -detail Media consistency: Failed 0501020a:53546f58:435f:0002root@<hostname> bin# ./omnimm -media_info "0501020a:53546f58:435f:0002" -detailMedium not found. Change Request: QCCR2A55793: In Direct Backup category with 1 TB


f 23 1/27/2015 9:41 AM



NDMP, the Licensing check displays incorrect values for License capacity. Change Request:QCCR2A55887: The Data Protector replication session stops responding when all gatewayconnections are used in other sessions. Change Request: QCCR2A55892: When performingan SRD update on a Cell Manager and Data Protector Internal Database (IDB) incrementalbackup on mirrored devices, the Data Protector "omnisrdupdate" utility or GUI endsabnormally. Change Request: QCCR2A55916: The Data Protector "omnirpt -reportsession_errors -timeframe 24 24" command fails when a specific hostname is specified by the

"-hosts" option. Change Request: QCCR2A55950: Upgrading Windows clients to DataProtector 8.1 fails with the following error message: |Critical| <hostname> Error 1935. An error occurred during the installation of assembly component (1A20435F-C0FC-3256-B1FD-1F3509F57CFF). HRESULT: 0x80070BC9 |Critical| <hostname> Operation failed witherror 1603: "Fatal error during installation." Change Request: QCCR2A56255: During themount process, the restore of Data Protector SharePoint 2013 application integration fails.Change Request: QCCR2A56349: The "Housekeeping" feature of StoreOnce is not workingas expected for all stores. Change Request: QCCR2A56430: When recovering files using theHP Data Protector Granular Recovery Extension with the NDMP component, the followingerror message is displayed: "Unable to present shared disks - Invalid parameters to enter share" Change Request: QCCR2A56433: The Data Protector object mirroring fails with thefollowing error message: |Major| From: BSM@<hostname> "" Time: <Date><Time> FAILED tostart mirror of object FileSystem "" "". No mirror device with suitable block size found. ChangeRequest: QCCR2A56498: When browsing the presented VM disk, the Data Protector non-staged Granular Recovery Extension (GRE) fails with the following error message:System error: |19| The media is write protected. "D:" Change Request: QCCR2A56669: TheData Protector GUI ends abnormally during the SAPDB backup configuration. ChangeRequest: QCCR2A56788: The pre-upgrade Detail Catalog Binary Files (DCBF) directory inIDB with "\ " in path name cannot be removed from Data Protector 8.0. Change Request:QCCR2A56794: The Data Protector "omnirpt" command does not display data with the TABoption: |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 Change Request: QCCR2A56980: Cannot write to aStoreOnce device. |Major| From: _BMA@<hostname>_ Time: <Date><Time> |90:51| Cannotwrite to device (StoreOnce error: The object store is not ready) Change Request:QCCR2A57227: The Data Protector documentation does not state that the object copyrequires licenses for both reading (source) and writing (target) devices, unlike restore whereno licenses are required for reading (source) devices. Change Request: QCCR2A57355: TheData Protector documentation does not state that the Data Protector GUI fails with a "bad fileformat" error message during the Data Protector 8.12 LDAP authentication. Change Request:QCCR2A57405: 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 thatreplication is also affected.


f 23 1/27/2015 9:41 AM




f 23 1/27/2015 9:41 AM



DPWINBDL_00902: Change Request: QCCR2A46153: The Data Protector "omnidbutil" binaryis modified to display locked devices correctly. Change Request: QCCR2A48585: The bsmbinary is modified to correctly handle the Oracle backup. Change Request: QCCR2A48627:The Copy Session Manager (CSM) is modified to correctly handle the connections on gatewayfor devices. Change Request: QCCR2A48923: The csm binary is modified to correctly displayobject values during a copy session in the Data Protector GUI. Change Request:QCCR2A49228: The Cell Server module is modified to correctly display the media allocation

order in the Data Protector 8.0 GUI. Change Request: QCCR2A50000: The "mma" binary ismodified to successfully complete the Data Protector object copy session to tape. ChangeRequest: QCCR2A50234: The database queries are modified to improve the performance of expanding objects in the Data Protector GUI restore context. Change Request:QCCR2A50504: The bma, cma, devbra, mma, rma, SANconf, and uma binaries are modifiedto ensure that the Data Protector debug.log file does not include the space consumingmessages. Change Request: QCCR2A50540: The bma, rma, and mma binaries are modifiedto correctly reconstruct the medium within a required time limit. Change Request:QCCR2A50778: The libfacade and facade binaries are modified to correctly execute the DataProtector "omnidb -list_changed_protection" command. Change Request: QCCR2A50844:

The Data Protector Media Agent binaries are modified to handle the large media size. ChangeRequest: QCCR2A50896: The Data Protector omnidbcheck binary is modified to not report theInternal Database (IDB) as inconsistent under low memory conditions. Change Request:QCCR2A50919: The rma and bma binaries are modified to correctly handle the Data Protector Direct Access Restore (DAR) functionality on NetApp. Change Request: QCCR2A51260: Thefacade and ormapper binaries are modified to correctly handle the Data Protector backupsession of NSS volumes. Change Request: QCCR2A51266: The Data Protector BackupSession Manager (BSM) is modified to correctly receive the catalog data from the DataProtector Backup Media Agent (BMA). Change Request: QCCR2A51326: The facade binary ismodified 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 duplicateones. Change Request: QCCR2A51421: The Data Protector Internal Database (IDB) schemais modified to improve the performance of the Data Protector "omnimm-delete_unprotected_media" command. Change Request: QCCR2A51551: The "omnirpt"binary is modified to correctly display parameters in the Parameter String. Change Request:QCCR2A51680: The Data Protector Media Session Manager is modified to successfullycomplete the restore session. Change Request: QCCR2A51705: The Data Protector InternalDatabase (IDB) schema is modified for proper functioning of the GUI when the Data Protector Network Data Management Protocol (NDMP) server integration objects are expanded. ChangeRequest: QCCR2A51718: The dbsm binary is modified to permit users configured in theOperator Data Protector user group to browse filesystems for creating and saving backup

specifications. Change Request: QCCR2A51827: The Data Protector Graphical User Interfaceis modified to display groups only once in the Object Operations context. Change Request:QCCR2A51880: The postgres_bar.exe file is modified to correctly handle the Data Protector Internal Database (IDB) backup session. Change Request: QCCR2A51881: The bsm binary is


f 23 1/27/2015 9:41 AM



modified to correctly handle the Data Protector 8.1 backup session. Change Request:QCCR2A51908: The Data Protector Backup Session Manager and the Restore SessionManager is modified to successfully complete the Data Protector VMware Granular RecoveryExtension (GRE) restore session. Change Request: QCCR2A51920: The omnidb binary ismodified to correctly handle the Data Protector "omnidb -oracle8-detail" command and reportdata for the remaining oracle8 objects. Change Request: QCCR2A52063: The InternalDatabase (IDB) module is modified to correctly display all tapes when the Data Protector 8.1

"omnimm -list_scratch_media" command is executed. Change Request: QCCR2A52211: Theomninet.exe file is modified to correctly handle the Data Protector 7.03 Microsoft SQL Server Integration backup session on Windows Server 2003 without impersonation warnings. ChangeRequest: QCCR2A52223: 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: QCCR2A52418: The Data Protector 7.03 Backup Session Manager ismodified to successfully complete the backup sessions on Linux systems. Change Request:QCCR2A52428: The "bsm" and "omnidlc" binaries are modified to avoid displaying thefollowing message: "DbgStack: DbgFcnOut() function does not match function on stack!ExitFcn="BsmOnCloseReconnect", StackFcn="brecon_checkHandle" Change Request:QCCR2A52442: The Data Protector Media Session Manager (MSM) is modified to correctlyhandle the import of the Data Protector NDMP media. Change Request: QCCR2A52474: TheVirtual Environment Integration (VEPA) component is modified to build correctly. ChangeRequest: QCCR2A52479: The rma binary is modified to successfully complete the DataProtector object consolidation session. Change Request: QCCR2A52497: The Data Protector Copy and Consolidation Session Manager (CSM) process is modified to successfully completelarge replication sessions. Change Request: QCCR2A52578: The Data Protector omnidbcheck functionality is modified to correctly return the media consistency check report.Change Request: QCCR2A52592: The dbsm binary is modified to correctly execute the DataProtector "omnirpt -report obj_lastbackup" command. Change Request: QCCR2A52604: Thefacade binary is modified to correctly handle the Data Protector Centralized Media

Management Database (CMMDB). Change Request: QCCR2A52660: The omnidbutil binary ismodified to clean up invalid Detail Catalog Binary Files (DCBF) records from Internal Database(IDB) and their corresponding files from disk. Change Request: QCCR2A52664: The DataProtector omnirc variable "OB2_RPT_VEPA_MOUNTPOINT_TO_VMPATH=1" is set tocorrectly list the Virtual Machine (VM) name in the Mountpoint field. Change Request:QCCR2A52692: The Data Protector GUI is modified to correctly handle the Media Agent (MA)in a multipath device in either the Manager-of-Managers (MoM) or Central Media ManagementDatabase (CMMDB). Change Request: QCCR2A52754: The Data Protector Copy andConsolidation Session Manager process (CSM) is modified to correctly copy only the objectsselected in the object copy specification. Change Request: QCCR2A52780: The facade binary

is modified to correctly copy objects from the file library to tape. Change Request:QCCR2A52848: The Data Protector Microsoft SQL Server integration is modified to correctlyhandle the backup session with the server-side deduplication. Change Request:QCCR2A52972: The Data Protector Media Agent binaries are modified to correctly handle thebackup session without any messages. Change Request: QCCR2A53053: The Data Protector SMIS integration is modified to function correctly when writing the disk identification signatureto disk. Change Request: QCCR2A53122: The Data Protector Volume Backup Disk Agent(VBDA) is modified to correctly display the warning message when the backup session of "/CONFIGURATION" fails. Change Request: QCCR2A53142: The facade binary is modified tocorrectly handle the Data Protector "omnirpt" command. Change Request: QCCR2A53146:

The Data Protector Copy and Consolidation Session Manager (CSM) process is modified tocorrectly handle the multiple source devices during an object copy session. Change Request:QCCR2A53150: The enhanced incremental database is modified to correctly handle entriesand identify files for backup. Change Request: QCCR2A53177: The Data Protector CellRequest Server (CRS) and Media Management Daemon (MMD) binaries are modified to


f 23 1/27/2015 9:41 AM



correctly handle the Cell Request Server process (service). Change Request: QCCR2A53228:The facade binary is modified to correctly handle the Data Protector backup session on HP-UX11.31 IA64. Change Request: QCCR2A53248: The Data Protector Virtual EnvironmentProtection Agent (VEPA) is modified to successfully complete the restore session to an ESXserver not managed by a vCenter. Change Request: QCCR2A53251: The Backup SessionManager (BSM) is modified to set the option "-keepcatalog same_as_dataprotection" correctlyto datalist when the Catalog protection is set to "Same as data protection" during the backup

configuration. Change Request: QCCR2A53275: The inet binary is modified to correctlyhandle the Data Protector 8.01 "omniinet.exe" process on the Cell Manager. Change Request:QCCR2A53282: The Data Protector SharePoint Granular Recovery Extension (GRE) ismodified to correctly handle the restore session from a differential backup. Change Request:QCCR2A53298: The Data Protector Manager-of-Managers (MOM) GUI is modified to correctlyhandle the client violation error. Change Request: QCCR2A53300: The Data Protector Media Agent module is modified to correctly handle the Data Protector replication session. ChangeRequest: QCCR2A53330: The Data Protector Copy Session Manager (CSM) is modified tocorrectly handle resumed object versions without catalog during the restore or object copy.Change Request: QCCR2A53381: The Data Protector Media Agent (MA) is modified tocorrectly handle the object consolidation session. Change Request: QCCR2A53392: The DataProtector Volume Backup Disk Agent (VBDA) is modified to correctly handle the VBDAinactivity timeout. Change Request: QCCR2A53417: The DEVBRA binary is modified tocorrectly function while running on Windows Server 2003. Change Request: QCCR2A53419: All Data Protector modules are rebuilt to correctly handle port scans. Change Request:QCCR2A53433: The facade binary is modified to correctly calculate the session object statescompleted with errors. Change Request: QCCR2A53444: The Data Protector Media SessionManager (MSM) is modified to correctly handle the Data Protector backup session. ChangeRequest: QCCR2A53446: The Data Protector "OMNI_HOSTS" variable is not added to thehost cache to ensure that the Backup Session Manager (BSM) functions correctly. ChangeRequest: QCCR2A53449: The Data Protector Database Session Manager (DBSM) is modified

to correctly handle the Data Protector "Session per client report". Change Request:QCCR2A53483: The Data Protector Media Agent (MA) is modified to correctly handle entriesin the debug.log file. Change Request: QCCR2A53584: The Data Protector Context-SensitiveHelp is modified to correctly handle popup settings, so that F1 help popups are displayedcorrectly. Change Request: QCCR2A53593: The Data Protector Media Session Manager (MSM) is modified to correctly report the media import session with relevant errors. ChangeRequest: QCCR2A53639: The Data Protector Media Management Daemon (MMD) is modifiedto correctly handle concurrent Data Protector Oracle Integration backup sessions and lockbackup devices. Change Request: QCCR2A53663: The Data Protector GUI is modified tocorrectly change data or catalog protection on the selected object only. Change Request:

QCCR2A53775: The Data Protector Internal Database (IDB) scripts are modified to correctlyhandle performance during the daily maintenance. Change Request: QCCR2A53783: Thefacade binaries are modified to correctly handle queuing sessions and statistics reports.Change Request: QCCR2A53815: The Data Protector Cell Request Server (CRS) is modifiedto function correctly and not create additional/unwanted debugs on the Store Once Software(SOS) clients. Change Request: QCCR2A53821: The Data Protector Backup SessionManager (BSM) is modified to correctly select devices that match the device filter criteria.Change Request: QCCR2A53827: A Data Protector omnirc variable"OB2_VEAGENT_VCENTER_CONNECTION_LIMIT_INCR" is added and set to 4. Thisadjusts the connection limit for incremental backups only. Change Request: QCCR2A53884:

The Data Protector omnidbutil binary is modified to correctly execute the "omnidbutil -purge-daily" command. Change Request: QCCR2A53970: The Data Protector 8.1x platform supportmatrix is modified to reflect the correct information. Change Request: QCCR2A54030: Thepostgres_bar.exe binary file is modified to successfully backup the Data Protector InternalDatabase (IDB). Change Request: QCCR2A54071: The Data Protector Internal Database


f 23 1/27/2015 9:41 AM



(IDB) backup now uses one codepage for all messages. Change Request: QCCR2A54089: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: Thelibfacade and facade binaries are modified to correctly execute the Data Protector reportingcommand "omnirpt". Change Request: QCCR2A54132: The Backup Session Manager ismodified to correctly handle multiple backups during mirroring. Change Request:QCCR2A54166: 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: The bsm, csm, rsm, asm, msm, dbsm, and facade binariesare modified to correctly handle the Data Protector GUI when objects in the restore context areexpanded. Change Request: QCCR2A54215: The Restore Session Manager (RSM) ismodified to select a media copy for restore, if the copy exists. Change Request:QCCR2A54228: The Data Protector Virtual Environment Protection Agent (VEPA) is modifiedto correctly use the cluster for the Restore session. Change Request: QCCR2A54250: Thefacade.dll file is modified to correctly handle the Data Protector Internal Database (IDB)backup session. Change Request: QCCR2A54256: The Data Protector is modified to minimizeMedia Management and Catalog database synchronization failures. Change Request:QCCR2A54260: The rsm and dbsm binaries are modified to function correctly during a restoresession. Change Request: QCCR2A54280: The bma binary is modified to function correctly.Change Request: QCCR2A54302: The Data Protector Copy and Consolidation SessionManager (CSM) is modified to function correctly during object copy sessions. ChangeRequest: QCCR2A54327: The Data Protector omnirc variable"OB2_RPT_FLOW_LOTUS_COMPATIBLE" is added to reduce the number of columns from82 to 64, and below. Change Request: QCCR2A54328: The rsm binary is modified to correctlyhandle the restore from multiple segments. Change Request: QCCR2A54392: The DataProtector Virtual Environment Protection Agent (VEPA) is modified to correctly perform the fullbackup of Changed Block Tracking (CBT) without any error messages. Change Request:QCCR2A54416: The Media Management Daemon (MMD) is modified to correctly handle the

number of free connections and successfully complete the backup session. Change Request:QCCR2A54476: The reporting functionality is modified to display consistent values in the"Single session" and "List Sessions" reports. Change Request: QCCR2A54489: The DataProtector Backup Session Manager (BSM) is modified to correctly handle the mirror backup totwo Store Once software devices when the store on the original device stops responding.Change Request: QCCR2A54523: The Data Protector GUI is modified to function correctlywhen connecting to the cell server. Change Request: QCCR2A54549: The StoreOnceInfoutility tool is modified to correctly execute the Data Protector "omnib2dinfo" command inJapanese environment. Change Request: QCCR2A54623: The facade and admin libraries aremodified to correctly sort the Data Protector SCSI-II library repository slots. Change Request:

QCCR2A54656: The reporting functionality is modified to display real values in the"session_statistics" report. Change Request: QCCR2A54679: The Data Protector GUI ismodified to function correctly when configuring settings for a restore of SAPDB server. ChangeRequest: QCCR2A54681: The Data Protector Daily Purge functionality is modified to functioncorrectly. Change Request: QCCR2A54705: The Data Protector "ObjectStoreClientCLI-list_stores" command is modified to correctly display all objects on store. Change Request:QCCR2A54706: The csm and msm binaries are modified to set all copy session objects to thedesired value. Change Request: QCCR2A54749: The Virtual Environment Protection Agent(VEPA) is modified to correctly restore a single Virtual Machine (VM) as a new VM. ChangeRequest: QCCR2A54751: 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: The Virtual Environment Protection Agent (VEPA) is modified with theaddition of Data Protector "OB2_VEAGENT_DISABLE_DNS_RESOLVE" omnirc variable toresolve vCenter and ESXi, and enable backup session to skip the DNS resolve. ChangeRequest: QCCR2A54755: The Data Protector GUI is modified to correctly display the target


f 23 1/27/2015 9:41 AM



object options "Logging : Same as Source" in Japanese environment. Change Request:QCCR2A54760: The Data Protector global option "DeleteUnprotectedMediaFreq=0" is addedto avoid the deletion of object versions and detailed catalog of protected media or sessions.Change Request: QCCR2A54772: The Data Protector "omnidbcheck" utility is modified toreport correctly the header and physical size of Detailed Catalog Binary Files (DCBF). ChangeRequest: QCCR2A54826: The Data Protector Daily Purge functionality is modified to functioncorrectly. Change Request: QCCR2A54856: The facade binary is modified to correctly handle

replication sessions. Change Request: QCCR2A54874: The bsm binary is modified tocorrectly handle the Data Protector Volume Backup Disk Agent (VBDA) timeouts. ChangeRequest: QCCR2A54890: The Data Protector Virtual Environment Protection Agent (VEPA) ismodified to correctly restore the virtual machine from the second imported disk. ChangeRequest: QCCR2A54902: The Data Protector "omnib2dinfo" utility is modified to correctly skipthe non-functional gateways. Change Request: QCCR2A54930: The "crs" binary is modified tocorrectly distribute licenses in Data Protector Manager of Managers (MoM) environment.Change Request: QCCR2A54935: The csm binary is modified to correctly handle the minimumvalue of load balancing for Disk to Disk (D2D) devices. Change Request: QCCR2A54961: TheMedia Session Manager (MSM) is modified to accept negative value and set the determinedmedium size. Change Request: QCCR2A54991: The Data Protector Backup Session Manager (BSM) is modified to correctly handle the backup operation on mirror devices. ChangeRequest: QCCR2A55011: The facade library is modified to protect media with protectedobjects after an import operation. Change Request: QCCR2A55051: The vepalib_vmware.dllfile is modified to correctly backup machines. Change Request: QCCR2A55068: The DataProtector facade library is modified to successfully restore the selected data without anyRestore Session Manager (RSM) failures. Change Request: QCCR2A55076: The DataProtector GUI is modified to correctly handle the library robotics SCSI path. Change Request:QCCR2A55077: The Data Protector Virtual Environment Protection Agent (VEPA) is modifiedto successfully allow VM restore to a non-managed ESXi 5.5 server. Change Request:QCCR2A55079: The Data Protector "omnidbcheck" command is modified to correctly handle

the Detailed Catalog Binary Files (DCBF). Change Request: QCCR2A55127: The DataProtector Virtual Environment Protection Agent (VEPA) is modified to correctly handle thedeletion of Data Protector snapshot at the end of the backup. Change Request:QCCR2A55145: The libob2db2 binary is modified to correctly handle the global variableOB2BARHOSTNAME and create correct object names during backup. Change Request:QCCR2A55148: The facade library is modified to display the real average for the IDB backupsize. Change Request: QCCR2A55153: The Data Protector GUI is modified to displayreasonable values for "Used Media (GB)" till the medium is overwritten for the first time. Bydoing so, the latter values appear correctly. Change Request: QCCR2A55222: The DataProtector Copy and Consolidation Session Manager binary "csm" is modified to correctly

handle the session abort request. Change Request: QCCR2A55287: The vepa library ismodified to correctly handle Virtual machine backup without depending on the configurationfile. Change Request: QCCR2A55385: The Data Protector "omnisrdupdate" utility or GUI ismodified to correctly handle the SRD update on a Cell Manager and Data Protector IDBbackup on mirrored devices. Change Request: QCCR2A55405: The Virtual EnvironmentProtection Agent (VEPA) is modified to successfully restore the Data Protector VMware vAppapplication integration. Change Request: QCCR2A55417: The msm binary is modified toensure that the Barcode scan executes as expected. Change Request: QCCR2A55423: TheVirtual Environment Protection Agent (VEPA) is modified to restore a Virtual Machine (VM) asa new VM. Change Request: QCCR2A55467: The Data Protector GUI is modified to permit

the entry of more than 60 characters in the "Add Users Name" field when the LightweightDirectory Access Protocol (LDAP) users or groups are added. Change Request:QCCR2A55478: The Data Protector "omnidb" utility is modified to correctly calculate thesession size information. Change Request: QCCR2A55619: The dbsm binary is modified todisplay the post-backup copy lists. Change Request: QCCR2A55709: The Data Protector


f 23 1/27/2015 9:41 AM



facade library is modified to reduce the use of memory and CPU in all types of automated copy jobs. Change Request: QCCR2A55724: The Data Protector GUI is modified to functioncorrectly and display available source-side gateways after selecting source-side deduplicationat the start of backup specification creation. Change Request: QCCR2A55764: The omnitrigbinary is modified to skip debug.log files from parsing. Change Request: QCCR2A55769: TheData Protector "omnidbcheck" utility is modified to correctly handle the media consistencycheck. Change Request: QCCR2A55793: The bsm binary is modified to display correct values

for License capacity during Licensing check. Change Request: QCCR2A55887: The csmbinary is modified to wait for all the required replication devices to become available andproceed after the required devices are locked. Change Request: QCCR2A55892: The DataProtector "omnisrdupdate" utility or GUI is modified to correctly handle the SRD update on aCell Manager, and Data Protector IDB full and incremental backup on mirrored devices.Change Request: QCCR2A55916: The Data Protector reporting functionality is modified tocorrectly handle the "-host" parameter. Change Request: QCCR2A55950: Terminate the pushinstallation, if reboot is pending on Windows system. Change Request: QCCR2A56255: TheData Protector SharePoint Granular Recovery Extension (GRE) is modified to correctly handlethe renaming of site from content database. Change Request: QCCR2A56349: TheStoreOnceSoftware utility is modified to handle "housekeeper jobs" correctly for all stores.Change Request: QCCR2A56430: The Data Protector vmwaregre-agent.exe is modified tofunction with the NDMP component. Change Request: QCCR2A56433: The bsm binary ismodified to check the maximum number of load balancing in all mirrored and original devicesand use that number to start gateway instances. Change Request: QCCR2A56498: TheVMDK mount component is modified to allow mounting on Windows Server 2012 R2 VMDKdisks in write non-persistent mode. Change Request: QCCR2A56669: The Data Protector GUIis modified to function correctly when configuring SAPDB backup configuration. ChangeRequest: QCCR2A56788: The omnidbutil is modified to handle Detail Catalog Binary Files(DCBF) directory in IDB with "\ " in path name. Change Request: QCCR2A56794: The DataProtector "omnirpt" command is modified to display correct data with the TAB option. Change

Request: QCCR2A56980: The StoreOnceSoftware utility is modified to cleanup the recyclefolder and prevent the store from stopping. Change Request: QCCR2A57227: The HP DataProtector 9.00 Installation Guide is modified to reflect a NOTE in the Traditional licensingsection. Change Request: QCCR2A57355: The following guides are modified to reflect thedetails: - HP Data Protector 9.00 Administrator's Guide - HP Data Protector 9.00 InstallationGuide Change Request: QCCR2A57405: 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 servicesby running omnisv stop 3. Start Data Protector IDB services by running omnisv start -idb_only4. 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 bestarted. Alternatively, the -check_graph can be called object by object: omnidbutil-check_graph -object <OBJECT> 5. Restart the services omnisv stop omnisv start


f 23 1/27/2015 9:41 AM




f 23 1/27/2015 9:41 AM



QCCR2A44987 QCCR2A46153 QCCR2A48382 QCCR2A48585 QCCR2A48627QCCR2A48923 QCCR2A49228 QCCR2A50000 QCCR2A50234 QCCR2A50354

QCCR2A50504 QCCR2A50540 QCCR2A50778 QCCR2A50844 QCCR2A50896QCCR2A50919 QCCR2A51260 QCCR2A51266 QCCR2A51326 QCCR2A51421QCCR2A51551 QCCR2A51680 QCCR2A51705 QCCR2A51718 QCCR2A51827QCCR2A51880 QCCR2A51881 QCCR2A51908 QCCR2A51920 QCCR2A52063QCCR2A52211 QCCR2A52223 QCCR2A52418 QCCR2A52428 QCCR2A52442QCCR2A52474 QCCR2A52479 QCCR2A52497 QCCR2A52510 QCCR2A52578QCCR2A52592 QCCR2A52604 QCCR2A52660 QCCR2A52664 QCCR2A52692QCCR2A52754 QCCR2A52780 QCCR2A52848 QCCR2A52972 QCCR2A53053QCCR2A53122 QCCR2A53142 QCCR2A53146 QCCR2A53150 QCCR2A53177QCCR2A53228 QCCR2A53248 QCCR2A53251 QCCR2A53275 QCCR2A53282

QCCR2A53298 QCCR2A53300 QCCR2A53330 QCCR2A53381 QCCR2A53392QCCR2A53417 QCCR2A53419 QCCR2A53433 QCCR2A53444 QCCR2A53446QCCR2A53449 QCCR2A53483 QCCR2A53584 QCCR2A53593 QCCR2A53639QCCR2A53663 QCCR2A53699 QCCR2A53775 QCCR2A53783 QCCR2A53792QCCR2A53815 QCCR2A53821 QCCR2A53827 QCCR2A53884 QCCR2A53970QCCR2A54030 QCCR2A54071 QCCR2A54089 QCCR2A54093 QCCR2A54132QCCR2A54166 QCCR2A54195 QCCR2A54205 QCCR2A54215 QCCR2A54228QCCR2A54250 QCCR2A54256 QCCR2A54260 QCCR2A54280 QCCR2A54302QCCR2A54327 QCCR2A54328 QCCR2A54369 QCCR2A54392 QCCR2A54416QCCR2A54476 QCCR2A54489 QCCR2A54523 QCCR2A54549 QCCR2A54623QCCR2A54633 QCCR2A54656 QCCR2A54679 QCCR2A54681 QCCR2A54705

QCCR2A54706 QCCR2A54749 QCCR2A54751 QCCR2A54752 QCCR2A54755QCCR2A54760 QCCR2A54772 QCCR2A54826 QCCR2A54856 QCCR2A54874QCCR2A54890 QCCR2A54899 QCCR2A54902 QCCR2A54930 QCCR2A54935QCCR2A54961 QCCR2A54991 QCCR2A55011 QCCR2A55051 QCCR2A55068


f 23 1/27/2015 9:41 AM



QCCR2A55076 QCCR2A55077 QCCR2A55079 QCCR2A55127 QCCR2A55145QCCR2A55148 QCCR2A55153 QCCR2A55222 QCCR2A55287 QCCR2A55385QCCR2A55398 QCCR2A55399 QCCR2A55405 QCCR2A55417 QCCR2A55423QCCR2A55467 QCCR2A55478 QCCR2A55619 QCCR2A55709 QCCR2A55724QCCR2A55764 QCCR2A55769 QCCR2A55793 QCCR2A55887 QCCR2A55892QCCR2A55916 QCCR2A55950 QCCR2A56255 QCCR2A56349 QCCR2A56398QCCR2A56430 QCCR2A56433 QCCR2A56498 QCCR2A56669 QCCR2A56788

QCCR2A56794 QCCR2A56980 QCCR2A57227 QCCR2A57355 QCCR2A57405QCCR2A57443 QCCR2A57446 QCCR2A57448 QCCR2A57481 QCCR2A57493QCCR2A57495 QCCR2A57571 QCCR2A57572 QCCR2A57575

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.Run the Patch executable: DPWINBDL_00902.EXE to install the Patch on the DataProtector system. 3.The DPWINBDL_00902 patch is created using the InstallShield 2011Premiere Edition. For silent installation, a response file (setup.iss) is required. To create theresponse file, install the patch once in normal interactive mode from the command line byusing the /r option as follows: DPWINBDL_00902.exe /r While performing a complete patchinstallation, the InstallShield will record installation choices in Setup.iss file and store it in theWindows folder. The silent installation can then be performed by using the setup.iss as input

file as follows: DPWINBDL_00902.exe /s /f1"c:\Windows\setup.iss" NOTE: Do not abort thepatch installation in between, it may leave Data Protector in an inconsistent state. The patchdocumentation is available at the HP support website at https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/DPWINBDL_00902 and containsthe latest updates. How to Remove Patch ==================== NOTE: Uninstallation of the patch will revert all the components which are part of the patch to the original productrelease. Hence any previously installed patch for this component will be erased. To uninstallindividual components delivered in this patch DPWINBDL_00902, proceed as follows: Insertthe original product media (e.g. the DVD) into the appropriate drive (for example D:\) and runthe script \bin\utilns\remove_patch.bat b902 Where is the path where the i386, ia64 and x8664

folders are located. The complete example is: C:\>cd \Program Files\omniback\bin\utilnsC:\>remove_patch.bat b902 D:\WINDOWS_OTHER The remove_patch.bat script will revert allpatched components to the DP 9.0 release version. Note that also any previously installedpatches will be erased. Any patches that were installed in your environment before theinstallation of DPWINBDL_00902 must be reinstalled. NOTE: Do not uninstall individualcomponents from the patch and do not install any previous DP 9.0 patch on top of theDPWINBDL_00902. The components contained in the patch are dependent on each other. If you uninstall individual components or reinstall previous ones, your DP installation maybecome unstable. In particular, do not solely remove the Core components when the patch isinstalled. If you do, then the other components that are part of the patch are no longer recognized on your system and cannot be removed either. If by mistake the Core componentsgets uninstalled from the system, download the remove_patch.bat file from the followinglocation to uninstall the patch completely or reinstall the patch again.


f 23 1/27/2015 9:41 AM



DPWINBDL_00902 NOTE! This patch must be installed on both, the Installation Server(IS)host and the Cell Manager(CM) host. The Data Protector client systems must be updated fromthe IS after the installation of the patch to get the fixes into effect. This patch can also beinstalled locally on a DP client. In this case, only the DP agent components that were alreadyinstalled on the client will be updated. This patch DPWINBDL_00902 contains and installs the

following Data Protector components. DPWIN-00713 - Cell Server patch DPWIN-00714 - Corepatch DPWIN-00715 - Cell Console patch DPWIN-00716 - Disk Agent patch DPWIN-00717 -Media Agent patch DPWIN-00718 - Documentation patch DPWIN-00719 - VE Agent patchDPWIN-00720 - NETAPP patch DPWIN-00721 - SMISA patch DPWIN-00722 - DB2 patchDPWIN-00723 - VMWARE-GRE patch DPWIN-00758 - SHAREPOINT-GRE DPWIN-00759 -DR patch DPWIN-00760 - EMC patch DPWIN-00762 - SOS patch DPWIN-00763 - SSEApatch DPWIN-00766 - VSS patch This patch is unable to update Japanese end-user documentation (the Data Protector Japanese Documentation Guides, Help component) wheninstalled locally. This component can only be installed remotely using a patched InstallationServer, provided an earlier version of the component is not installed on the remote client. If

installed, locally remove it first. To perform ZDB-to-disk+tape or ZDB-to-tape sessions,additionally install the "General Media Agent" Data Protector software component on thebackup system. In a Cluster environment, the patch DPWINBDL_00902 should be installed onthe active node. WARNING! The components of the patch DPWINBDL_00902 havedependencies on each other, thus the complete patch should be installed as a whole. Similarly,never uninstall an individual component from the patch. To install/uninstall the patch, pleasesee the above instructions. This patch includes the following Site Specific Patches.SSPNT900_001 SSPNT900_003


dpwinbdl 00902 wins

Documents