HP OpenView Storage Data Protector A.05.10 for the UNIX, Windows and NetWare Enterprises Software Release Notes revised on May 26, 2003 (also available on the installation CD-ROM)

Manufacturing Part Number: B6960-90085 May 2003 © Copyright Hewlett-Packard Development Company, L.P.2003.

Data Protector A.05.10 Release Notes

Chapter 1: Announcements ............................................................................... 7 1.1 Upgrades......................................................................................................................7 1.2 What Is Supported? .....................................................................................................7 1.3 Licensing .....................................................................................................................7 1.4 Discontinuance of Support ..........................................................................................7 1.5 How to Order OmniBack II .........................................................................................7 1.6 Updated Information ...................................................................................................8 Chapter 2: Product Features and Benefits ....................................................... 9 2.1 Enhanced functional capabilities for more control......................................................9 2.1.1 Easy to Use GUI for the Restore for Oracle 8/8i/9i ......................................................................... 9 2.1.2 Simplified Microsoft Exchange Single Mailbox/Mail Restore ........................................................ 9 2.1.3 Enhanced Scheduler Functionalities............................................................................................... 10 2.1.4 Encoding/Compression................................................................................................................... 10 2.1.5 Encryption and Compressing plug in ............................................................................................. 10 2.1.6 Device Autoconfiguration in a SAN Environment ........................................................................ 10 2.1.7 Automated Upgrade from Previous Versions................................................................................. 11 2.1.8 Patch Check Tool ........................................................................................................................... 11 2.1.9 DNS Connection Check Tool......................................................................................................... 11 2.1.10 Improved Debugging.................................................................................................................... 11

2.2 Increases Resilience...................................................................................................11 2.2.1 Eliminates the Impact of the Planned Downtime ........................................................................... 11 2.2.2 Eliminates the Impact of the Unplanned Downtime ...................................................................... 13

2.3 Increases Extensibility...............................................................................................14 2.3.1 Comprehensive Support for Emerging IA-64 Platforms................................................................ 15 2.3.2 Adds Support for Applications, Operating and Storage Environments ......................................... 15

Chapter 3: Limitations and Recommendations.............................................. 17 3.1 Size Limitations.........................................................................................................17 3.1.1 Internal Database Size .................................................................................................................... 3.1.2 Number of Objects in a Backup Specification ............................................................................... 3.1.3 Number of Media in One Pool ....................................................................................................... 3.1.4 Number of Sessions in the Database .............................................................................................. 3.1.5 Number of Backups Scheduled at One Time ................................................................................. 3.1.6 Concurrent Activities...................................................................................................................... 3.1.7 Number of Cells in a MoM Environment.......................................................................................

17 17 17 17 17 18 18

3.2 Internationalization....................................................................................................18

2

Data Protector A.05.10 Release Notes

3.3 Localization ...............................................................................................................18 3.4 Platform Limitations..................................................................................................18 3.4.1 UNIX Limitations........................................................................................................................... 3.4.2 Windows Limitations .................................................................................................................... 3.4.3 Novell NetWare Limitation............................................................................................................ 3.4.4 MPE/iX Limitations ....................................................................................................................... 3.4.5 OpenVMS Limitations ...................................................................................................................

18 19 20 20 21

3.5 Limitations on Disk Array Integrations.....................................................................22 3.5.1 HP StorageWorks Disk Array XP Limitations............................................................................... 3.5.2 HP StorageWorks Virtual Array Limitations................................................................................. 3.5.3 HP StorageWorks Enterprise Virtual Array Limitations............................................................... 3.5.4 HP StorageWorks Modular SAN Array 1000 Limitations............................................................

22 23 24 24

3.6 NDMP Limitations ....................................................................................................24 3.7 Limitations on Database Integrations........................................................................25 3.7.1 Oracle Limitations .......................................................................................................................... 25 3.7.2 SAP R/3 Limitations....................................................................................................................... 26 3.7.3 MC/ServiceGuard Limitations ....................................................................................................... 26

3.8 Other Limitations ......................................................................................................26 3.9 Recommendations .....................................................................................................29 3.9.1 Number of Clients in a Cell............................................................................................................ 3.9.2 Large Number of Small Files ......................................................................................................... 3.9.3 NDMP Backup Configuration........................................................................................................ 3.9.4 Support for NIS+ ............................................................................................................................ 3.9.5 Microsoft Exchange Single Mailbox Backup................................................................................. 3.9.6 Cell Manager on Windows XP/Server 2003 ..................................................................................

29 29 29 29 29 30

Chapter 4: Known Problems and Workarounds ............................................ 31 4.1 Known Data Protector Problems and Workarounds .................................................31 4.2 Known Non-Data Protector Problems and Workarounds .........................................37 Chapter 5: Installation Requirements.............................................................. 44 5.1 Cell Manager Requirements ......................................................................................44 5.1.1 On Systems Running HP-UX 11.0, 11.11 and 11.20 ..................................................................... 5.1.2 On Systems Running Solaris 7/8/9................................................................................................. 5.1.3 On Systems Running Windows NT ............................................................................................... 5.1.4 On Systems Running Windows 2000/XP....................................................................................... 5.1.5 On Systems Running Windows Server 2003-32 bit.......................................................................

44 44 44 45 45

5.2 Installation Server Requirements ..............................................................................45

3

Data Protector A.05.10 Release Notes

5.2.1 On Systems Running HP-UX ......................................................................................................... 5.2.2 On Systems Running Solaris 7/8/9................................................................................................. 5.2.3 On Systems Running Windows NT ............................................................................................... 5.2.4 On Systems Running Windows 2000/XP....................................................................................... 5.2.5 On Systems Running Windows Server 2003-32 bit.......................................................................

45 45 46 46 46

5.3 Client System Requirements .....................................................................................46 5.3.1 On Systems Running UNIX ........................................................................................................... 46 5.3.2 On Systems Running Windows...................................................................................................... 47

5.4 Java Web Reporting ..................................................................................................48 5.5 Novell NetWare.........................................................................................................48 5.6 Local UNIX Client Installation .................................................................................48 5.7 Upgrade .....................................................................................................................48 5.8 Requirements for Data Protector Services on Windows Server 2003.......................49 5.9 Files Installed in the%systemroot%\system32 Folder...............................................49 Chapter 6: Required Patches ........................................................................... 50 6.1 HP-UX 11.00 System Patches Required by Data Protector ......................................50 6.2 HP-UX 11.11 System Patches Required by Data Protector ......................................51 6.3 System Patches for the Data Protector GUI on HP-UX ............................................51 6.4 System Patches Required by MPE/iX System ..........................................................51 6.5 Solaris System Patches Required by Data Protector .................................................52 6.6 Novell NetWare Patches Required by Data Protector...............................................52 Chapter 7: Obsolete Platforms and Integrations in Data Protector A.05.10 53 7.1 Obsolete Platforms ...................................................................................................53 7.2 Obsolete Integrations.................................................................................................53 Chapter 8: Data Protector Documentation...................................................... 54 8.1 Location of Documentation .......................................................................................54 8.2 Printed Documentation..............................................................................................54 8.3 Online Help ...............................................................................................................55 8.4 Localization ...............................................................................................................55

4

Data Protector A.05.10 Release Notes

Appendix A: List of Enhancements and Defects Fixed in Data Protector A.05.10 ............................................................................................................... 57 A.1 List of Enhancements Implemented .........................................................................57 A.2 List of Defects Resolved...........................................................................................58 Appendix B: Non-ASCII Characters in Filenames Appendix ........................ 64 B.1 Non-ASCII Characters in Filenames ........................................................................64 B.1.1 Full Support for Filenames Containing Only 7-bit ASCII Characters .......................................... B.1.2 File Content.................................................................................................................................... B.1.3 Media Agent Can Run on Any Platform ....................................................................................... B.1.4 Specifying a Tree for Backup or a File for a Single File Restore.................................................. B.1.5 Standard Workaround for Trees That Cannot be Specified........................................................... B.1.6 Tables of Limitations ..................................................................................................................... B.1.9 Further Limitations ........................................................................................................................

64 64 64 64 64 65 69

Appendix C: Support Matrices......................................................................... 70

5

Data Protector A.05.10 Release Notes

Document History Version

Date

Description

1.0

May 20, 2003

Initial version

1.1

May 26, 2003

Added last minute changes

6

Data Protector A.05.10 Release Notes

Chapter 1: Announcements Data Protector A.05.10 is fully compatible with existing OmniBack II and Data Protector tapes, scripts, and procedures and includes all existing OmniBack II functionality.

1.1 Upgrades Upgrade information is available in the HP OpenView Storage Data Protector Installation and Licensing Guide. Upgrade procedures to Data Protector A.05.10 from OmniBack II versions A.03.50, A.03.51, A.04.00, A.04.10, and Data Protector A.05.00 are described.

1.2 What Is Supported? Detailed information on supported platforms, devices, and integrations is available in Appendix C of this document. For the latest platform and integration support information, refer to Appendix C or to the HP OpenView Storage Data Protector page at: http://www.openview.hp.com/products/datapro/spec_0001.html. In case of hardware failures in third-party products, please call the respective vendor directly. Supported Data Protector commands from the command-line interface (CLI) are documented in the HP OpenView Storage Data Protector Administrator’s Guide.

1.3 Licensing Data Protector A.05.10 leverages the product numbers from OmniBack II and Data Protector A.05.00. That's the reason why all OmniBack II A.03.x and A.04.x licenses and Data Protector A.05.00 licenses can be used with Data Protector A.05.10 and retain their original functionality. No license migration is required. However, standard product licenses according to the desired functionality are required and need to be installed.

1.4 Discontinuance of Support OmniBack II A.03.50 stays fully supported until August 1, 2004. OmniBack II A.04.10 stays fully supported until September 1, 2004. Data Protector A.05.00 stays fully supported until January 31, 2006. After the full support period expires, Knowledgebase Support will be provided for one more year in each case. Please be aware that you can request an individual extension of the full support at additional costs.

1.5 How to Order OmniBack II In order to extend your existing OmniBack II environment, you can acquire the OmniBack II A.04.10 version by ordering the new Data Protector A.05.10 product (to get the LTU) and the OmniBack II A.04.10 media and manual set. The Data Protector LTUs will work in your OmniBack II environment, except for the following new licenses introduced with Data Protector: On Data Protector B7022BA (Backup of NDMP servers), use B7022AA instead for OmniBack II environments. B7028AA, B7027AA, B7029AA, B7036AA, and B7037AA are licenses introduced with Data Protector releases A.05.00 and A.05.10, they will not work in an OmniBack II environment. The OmniBack II A.04.10 media and manuals (no LTUs) can be obtained by ordering one of the following product numbers: B6960BA: OmniBack II A.04.10 all media and manuals, English B6960BJ: OmniBack II A.04.10 all media and manuals, Japanese B6960BD: OmniBack II A.04.10 all media and manuals, German

7

Data Protector A.05.10 Release Notes

B6960BF: OmniBack II A.04.10 all media and manuals, French

1.6 Updated Information For the latest information, including corrections to documentation refer to the Data Protector home page: http://www.hp.com/go/dataprotector

8

Data Protector A.05.10 Release Notes

Chapter 2: Product Features and Benefits Data Protector is fully compatible with OmniBack II tapes, scripts, and procedures and includes all existing OmniBack II functionality. This chapter gives a brief description of Data Protector A.05.10 features and major changes in comparison to the previous Data Protector version.

2.1 Enhanced functional capabilities for more control Data Protector automates routine tasks to maximize the effectiveness of your data protection staff.

2.1.1 Easy to Use GUI for the Restore for Oracle 8/8i/9i Administrators can select all or individual RMAN restore options from the Graphical User Interface freeing them from dealing with the Oracle RMAN Command Line Interface. Data Protector A.05.10 offers restore of Oracle database objects using the Data Protector GUI. Earlier, Oracle restore was only possible using the Oracle RMAN command-line interface. The Data Protector GUI interacts with the Oracle database recovery tool RMAN to recover whole databases or objects within the databases. The following restore types are available in the GUI:

• Restore from incremental backups • Restore to a host other than the one used to back up the database • Restore of a datafile to a location other than the original one • Restore of a recovery catalog before the database is restored • Restore from a chain of full and incremental backups • Restore concurrency • Restore using another device 2.1.2 Simplified Microsoft Exchange Single Mailbox/Mail Restore Microsoft Exchange mailbox users can select all or individual mailboxes for single backup and restore. Data Protector A.05.10 release introduces the enhanced MS Exchange Single Mailbox backup and restore functionality. The Data Protector integration with MS Exchange Single Mailbox enables performing online backups and restores of single mailboxes located on the MS Exchange Server system. The entire mailbox content including e-mail messages, task assignments, calendar schedules, contacts, etc., can now be backed up and restored. The MS Exchange Single Mailbox integration agent communicates with MS Exchange Server through the Messaging Application Programming Interface (MAPI) thus controlling the activities between MS Exchange Server and the Data Protector backup and restore processes. You can perform the following types of online backups using the Data Protector MS Exchange Single Mailbox integration:

• Full mailbox backup • Incremental1 mailbox backup • Incremental mailbox backup The following restore options are available:

9

Data Protector A.05.10 Release Notes

• Restore into another mailbox • Restore to another MS Exchange Server • Restore mailbox from a chain of full and incremental backups • Restore only the contents from an incremental backup 2.1.3 Enhanced Scheduler Functionalities For each individual or periodic scheduled backup, Data Protector A.05.10, additionally, offers the possibility to specify the protection, and distinguish between disk and disk/tape backup. When using the value Default for protection, then the protection, defined by the backup specification is taken. The other values (until, days, weeks, permanent) overwrite the value specified inside the backup specification. These options allow scheduling the same backup specification with different protection time. For example, it is possible to schedule a full backup with permanent protection, and an incremental backup with a protection of a few weeks, with the same backup specification. With split mirror or snapshot backup, in the case of ZDB disk or ZDB disk/tape backups (instant recovery enabled), the option Split mirror/snapshot backup can be specified. For split mirror and snapshot backups, the backup type is ignored (it is set to full). Each backup specification can be scheduled multiple times with different option values. Within one backup specification, you can schedule both ZDB disk and ZDB disk/tape backups, and specify a different data protection period for each individual or periodic scheduled backup.

2.1.4 Encoding/Compression With the version Omniback II 3.5 user defined libraries, used for encoding or compressing the data, were not supported anymore. It was only possible to use the embedded Data Protector implementation. The default encoding algorithm is XOR while the default compression algorithm is Lempel-Ziv 4.3 (UNIX compress). Data Protector A.05.10 reintroduces the support of user defined encoding and compressing algorithms. This functionality allows encoding or compressing the data on that system, where the data is read and the disk agent is running with an algorithm, which is implemented by the customer. The data is send encoded and/or compressed via the network to the media agent where it is written to tape. The encode method increases the security because it pretends an unauthorized read of data.

2.1.5 Encryption and Compressing plug in If user defined algorithms are used for either encoding or compressing the data, the existing libraries (on HP-UX they are called libde.sl and libdc.sl) must be replaced. Note the name of the library differs according to the platform and can be derived from the name of the original one (libde.xx and libdc.xx). On HP-UX, the libraries can be found under /etc/opt/lib. The Data Protector A.05.10 backup session output contains information whether a user-defined algorithm was used or not. In case, the data were encoded and/or compressed by a user defined algorithm, the session output contains the name of the algorithm, specified in the DeInit() or DcInit() functionality. The libraries must contain the implementation of the functions listed below. For further information, see the whitepaper Encoding and Compression Plug-in.

2.1.6 Device Autoconfiguration in a SAN Environment Device autoconfiguration is now also available in a SAN environment, where different clients use tape drives in one library. The Data Protector autoconfiguration functionality provides automated device autoconfiguration on multiple client systems using the GUI.

10

Data Protector A.05.10 Release Notes

2.1.7 Automated Upgrade from Previous Versions Data Protector A.05.10 release offers an automated upgrade procedure from OmniBack II A.03.5x, OmniBack II A.04.x, and Data Protector A.05.00 release versions. The upgrade procedure is performed by running the omnisetup.sh command on UNIX systems and the setup.exe command on Windows systems. Note that for upgrading clients with integrations some limitations need to be considered and some additional integration-specific steps might be required. Refer to the HP OpenView Storage Data Protector Installation and Licensing Guide for instructions on performing the upgrade from earlier versions of the product as well as for the information on upgrade-related prerequisites and limitations. Automatic Merge of Global Options File Data Protector A.05.10 automatically merges the contents of the old global options file with the new global options file.

2.1.8 Patch Check Tool Data Protector A.05.10 provides a mechanism that will allow to verify which Data Protector patches are installed on a particular system.

2.1.9 DNS Connection Check Tool Data Protector requires that all client systems of the cell resolve addresses of other members consistently. Usually, DNS is responsible for that. If this is not the case then, Data Protector may encounter problems, however, a normal operation can't be guaranteed. This prerequisite can be checked with the new command line utility omnicheck. This tool verifies if:

• The Cell Manager properly resolves every other client of cell • Every client of the cell properly resolves the Cell Manager • Every system, on which the Media Agent was installed, resolves every other client • Each system resolves every other system accommodating a Media Agent If a Data Protector cell passes the above checks, it will not have any DNS-related problems during regular operation. When a DNS configuration between two hosts, A and B, is successfully checked then system A should be able to resolve the name of host B and therefore, will be able to connect to it.

2.1.10 Improved Debugging Data Protector A.05.10 offers a new debugging mode called circular debugging in which trace file sizes are limited. Other debugging improvements include a new trace file naming scheme to simplify debug trace file collection and the possibility to set the timestamp resolution.

2.2 Increases Resilience Data Protector Increases resilience with recovery from any disruption, from instant recovery to site or system disaster recovery.

2.2.1 Eliminates the Impact of the Planned Downtime Functionality related to the HP StorageWorks Modular SAN Array 1000 will be available after the release of Data Protector A.05.10 2.2.1.1 Zero Downtime Backup for HP StorageWorks EVA Array on HP-UX, Windows and Solaris Data Protector A.05.10 introduces snapshot backup support for HP StorageWorks Enterprise Virtual Array. The disk array provides snapshot functionality, a zero downtime backup solution that has already been introduced with the Data

11

Data Protector A.05.10 Release Notes

Protector HP StorageWorks Virtual Array integration. The main feature of HP StorageWorks Enterprise Virtual Array is the ability to create snapshots of data stored on the disk arrays. These snapshots can be used later to back up the data using a different server (backup system), and thus remove the backup load from the production server (application system), and allow the production applications to run uninterrupted. The largest benefit of the snapshot integration is the removal of the backup window, and the reduction of the load on the production server. Snapshot Backup and Restore

• This integration supports ZDB tape backup. It allows you to perform zero downtime backup and standard restore of filesystems, disk images and online databases, such as Oracle, SAP R/3 Microsoft Exchange, and Microsoft SQL 2000. Supported Configurations The HP StorageWorks Enterprise Virtual Array integration can be used in different backup topology scenarios, without any user interference or special configuration:

• One application system, one disk array, one backup system • One application system, multiple disk arrays, one backup system • Multiple application systems, one or multiple disk arrays, one backup system • Single system (filesystem and disk image backup only)

2.2.1.2 Online Backup of Databases and Applications Introduces the Online Backup of IBM DB2 on AIX and HP-UX Data Protector A.05.10 introduces support for the IBM DB2 Universal Database. The Data Protector integration with IBM DB2 UDB allows you to perform online and offline backups of the DB2 database objects. The DB2 part of integration provides an open interface for backing up and restoring the DB2 objects. This allows you to use Data Protector as a data transferring module for database backup and restore operations. You can perform the following types of backup using the Data Protector IBM DB2 UDB integration:

• Backup of one or several databases • Backup of one or several table spaces • Backup of several table spaces from different databases • Incremental database/table space backup • Delta database/table space backup Each backup type may be performed both online and offline. The Data Protector IBM DB2 UDB integration supports the following restore types:

• Offline database restore and roll-forward operations • Offline and online table space restore and roll-forward operations • Automatic restore from incremental or delta backups • Restore to a new database (for database-level backups only)

12

Data Protector A.05.10 Release Notes

• Restore to a different system DB2 is also supported in a MC/ServiceGuard environment. Introduces Support for Other Databases and Applications For more details about supported database and applications refer to the latest list of support matrices on the Web: http://www.openview.hp.com/products/datapro/spec_0001.html 2.2.1.3 Incorporates MS Volume Shadow Copy Service Volume Shadow Copy service is a software service introduced by Microsoft on Windows Server 2003 operating system. This service collaborates with the backup application, applications to be backed up, shadow copy providers, and the operating system kernel to implement the management of volume shadow copies and shadow copy sets. The idea of the Volume Shadow Copy service is to provide a unified communication interface that can coordinate backup and restore of any application regardless of their specific features. With this approach, a backup application does not need to handle each application to be backed up specifically. However, this approach is applicable to a backup application only in case it conforms to the VSS specification. The advantages of using Volume Shadow Copy service are the following:

• Unified backup interface is provided for all writers. • Unified backup interface is provided for all shadow copy providers. • Data integrity is provided on the application level by the writers. No interference is needed from the backup application. Data Protector supports the Microsoft Volume Shadow Copy service on two levels:

• Within the integration with the Microsoft Volume Shadow Copy service, Data Protector provides a shadow copy backup and restore of the VSS-aware writers. Data Protector integration with Microsoft Volume Shadow Copy service provides full support of the VSS-aware writers. This includes automatic detection of the supported VSS-aware writers, backup and restore functionality. Please refer to the support matrix for a list of supported writers. The consistency of data is provided on the level of a writer and is not dependent on the backup application. During the backup and restore of the VSS-aware writers, Data Protector does not communicate with each writer individually, but through the VSS interface.

• Within the Disk Agent functionality, Data Protector provides the VSS filesystem backup. During the VSS filesystem backup the consistency of data is improved in comparison with the non-VSS filesystem backup. VSS allows you to create shadow copy backups of volumes, exact point-in-time copies of files, including all open files. For example, databases that are held open exclusively and files that are open due to operator or system activity are backed up during a VSS filesystem backup. In this way, files that have changed during the backup procedure are copied correctly.

2.2.2 Eliminates the Impact of the Unplanned Downtime 2.2.2.1 Supports MS 2-8 node Cluster Server on Microsoft Windows Server 2003 Data Protector supports MS 2-8 node Cluster Server including the Network Load Balancing (NLB) to increase availability of application running on Microsoft Windows Server 2003.

13

Data Protector A.05.10 Release Notes

2.2.2.2 Supports HP MC/ServiceGuard on HP-UX 11.22 2.2.2.3 Supports Disk Agent on Veritas Cluster Server 2.0 on Solaris 7/8 2.2.2.4 Supports Netware Cluster Services 1.6 on Netware 6.0 2.2.2.5 Supports OpenVMS Cluster 2.2.2.6 Automated Media Copy for the Offsite Vaulting To increase the safety of your data, it is recommended to create additional copies of the backup media, which can then be moved to an off-site vault. Besides manually started media copying, Data Protector now offers automated media copying. There are two types of automated media copying: post-backup media copying and scheduled media copying. If you wish to have an additional copy of the media used in a backup session, you can configure post-backup media copying. The media will be copied right after the backup finishes. If you wish to copy the media at a later time, you can schedule the media copying to take place at any time that suits you. 2.2.2.7 Media Vaulting Enhancements Data Protector media vaulting functionality is now enhanced with a new report type, Extended List of Media. This report provides information about medium ID, medium label, medium location, medium condition, medium protection, used and total space (MB), the time when the medium was last accessed, media pool, media type, and the backup specifications that have used the specified media for backup. 2.2.2.8 Incorporates Support for MS's Automated System Recovery for Microsoft Windows Server 2003 Data Protector A.05.10 offers Automated Disaster Recovery (ASR) - a new, effective and highly automated method for disaster recovery of Windows XP and Windows Server 2003 systems (i386 and IA64 based systems). ASR is an automated system, which reconfigures a disk to its original state in the case of a disaster. This includes disk partitioning and logical volume configuration. ASR thus enables the Data Protector drstart.exe command to install the active DR OS which provides Data Protector disk, network, tape and filesystem access. Data Protector then recovers the target system to the original system configuration and finally restores all user data. We have tested ASR successfully with a local floppy drive. Your system might also support ASR via a USB floppy drive, please check with your vendor. In the future Microsoft might also allow to store ASR information on the installation CD or on a network location. If your system is able to read this information from those locations the ASR process will work. 2.2.2.9 Support for Multi-pathing Software Improves the availability of data through support of multi-pathing software (HP StorageWorks SecurePath, HP StorageWorks AutoPath, EMC PowerPath), to eliminate single point of failure of SAN components. 2.2.2.10 Disk-Image Delivery recovery approach for AIX and Tru64 environments

2.3 Increases Extensibility Data Protector extends its level of protection services to new operating systems, databases and disk arrays.

14

Data Protector A.05.10 Release Notes

2.3.1 Comprehensive Support for Emerging IA-64 Platforms 2.3.1.1 Microsoft Windows XP on IA-64 Data Protector A.05.10 introduces support for Disk Agent, Media Agent (with and without robotics), NDMP, User Interface, MS Volume Shadow Copy service, Microsoft SQL Server 8.0 for 64-bit Windows Server 2003, Oracle9i, and Automatic Disaster Recovery components on Windows Server 2003 64-bit operating system. All Windows XP features and limitations described in the Data Protector documentation, also apply to Windows Server 2003 64-bit, unless stated otherwise. Detailed information on supported platforms and integrations is available in Appendix C of this document. 2.3.1.2 Microsoft Windows Server 2003 on IA-64 Data Protector A.05.10 introduces support for Media Agent (with and without robotics, NDMP), User Interface and Installation Server on the Windows XP 64-bit operating system. All Windows XP 32-bit features and limitations described in the Data Protector documentation, also apply to Windows XP 64-bit, unless stated otherwise. The 64-bit components can be installed locally using a setup.exe located in the ia64 directory on the Windows installation CD-ROM or remotely from the Installation Server. Detailed information on supported platforms and integrations is available in Appendix C of this document. 2.3.1.3 HP-UX on IA-64 Data Protector A.05.10 introduces native support for Disk Agent, Media Agent, Oracle9 (64-bit) and User Interface (command line only) components on HP-UX 11.22 (IA64 based systems). All HP-UX features and limitations pertaining to these components for HP-UX systems described in Data Protector documentation, also apply to HP-UX 11.22 IA64 based systems, unless stated otherwise. 2.3.1.4 Linux on IA-64 Data Protector A.05.10 introduces native support for Disk Agent on Red Hat 7.2, Suse 7.3 and Debian 3.0 IA64 based systems. All Linux Disk Agent features and limitations described in the Data Protector documentation, also apply to 64-bit Linux Disk Agent, unless stated otherwise.

2.3.2 Adds Support for Applications, Operating and Storage Environments 2.3.2.1 Windows Server 2003 32-bit Data Protector A.05.10 introduces support for Cell Manager, Installation Server, Disk Agent, Media Agent (with and without robotics), NDMP, User Interface, MS Volume Shadow Copy service, Microsoft SQL Server 8.0, Oracle9i, and Automatic Disaster Recovery components on Windows Server 2003 32-bit operating system. All Windows XP features and limitations described in the Data Protector documentation, also apply to Windows Server 2003, unless stated otherwise. Detailed information on supported platforms and integrations is available in Appendix C of this document. 2.3.2.2 OpenVMS Data Protector A.05.10 introduces support for Media and Disk Agent on OpenVMS systems. For more details please refer to the latest support matrices on the Web: http://www.openview.hp.com/products/datapro/spec_0001.html

15

Data Protector A.05.10 Release Notes

2.3.2.3 Tru64 64-bit Data Protector A.05.10 introduces support for User Interface and Media Agent with robotics on Tru64 5.x 64-bit systems. Autoconfiguration of backup devices is also supported. 2.3.2.4 Other Extensions

• Cell Manager on Solaris 9 • AIX Media Agent in a SAN environment • Novell Netware 6

16

Data Protector A.05.10 Release Notes

Chapter 3: Limitations and Recommendations 3.1 Size Limitations 3.1.1 Internal Database Size Data Protector A.05.10 Number of filenames1

32GB or approx. 700 million (UNIX systems) 450 million (Windows systems)

Number of file versions

10xNo of filenames

Maximum number of DCBF2 directories

50

Maximum size per DCBF directory

4 GB

Maximum number of files per DCBF directory

10,000

Maximum number of concurrent drives (DLT7000 and lower performing)

100

Maximum number of concurrent drives (DLT8000/SDLT/LTO)

50

Notes 1

The maximum size of the filename database is 32 GB for the Cell Manager. The number of filenames is an estimate for an average Data Protector environment. 2

DCBF = Detail Catalog Binary Files

3.1.2 Number of Objects in a Backup Specification There can be up to 500 Filesystem objects in the backup specification.

3.1.3 Number of Media in One Pool There can be up to 40,000 media in one pool. In total, there can be 500,000 media in the Data Protector media management database.

3.1.4 Number of Sessions in the Database There can be up to 1,000,000 sessions in the database. At the most, 2,000 backup sessions can be run in one day.

3.1.5 Number of Backups Scheduled at One Time The maximum total number of backup sessions running in parallel is 100 on UNIX systems and 60 on Windows systems. The default value is set to 5. This can be increased using the MaxBSessions global option. When the number of parallel sessions is larger than 50 (recommended maximum) the probability of hitting one of the system limits on the Cell Manager increases significantly (number of file descriptors, TCP/IP limitations, memory limitations).

17

Data Protector A.05.10 Release Notes

3.1.6 Concurrent Activities • Each backup session can by default use up to five devices at the same time. This number can be increased up to 32. The upper limit for this parameter is controlled by the MaxMAperSM global option (default = 32).

• By default, up to five Disk Agents (depending on the concurrency of a device) can write to the same device at the same time. This number can be increased up to maximum 32 using the MaxDAperMA global option.

• Up to ten media can be imported in the IDB at the same time. 3.1.7 Number of Cells in a MoM Environment There can be up 50 cells in a MoM environment.

3.2 Internationalization For a list of restrictions when using non-ASCII characters in filenames, refer to Appendix B.

3.3 Localization Data Protector A.05.10 is localized to the Japanese and French languages on Windows, HP-UX and Solaris operating systems. However, the installation procedure is not localized.

3.4 Platform Limitations 3.4.1 UNIX Limitations • LOFS filesystems are fully supported. However, Data Protector might not recognize directories that are lofs-mounted, if they are mounted within the same filesystem. This will result in additional data being backed up.

• The maximum size of files and disk images you can back up depends on operating system and filesystem limitations. Data Protector has no file size limitations on the following UNIX systems: HP-UX, Solaris, AIX, IRIX, Linux, Tru64. On other UNIX systems Data Protector backs up files and disk images of up to 2 GB. HP-UX Limitation

• Restore of a single file from a disk image is no longer supported.

18

Data Protector A.05.10 Release Notes

Solaris Limitations

• If a csh script is used for pre- or post-exec, the -b option must be specified in the interpreter specification line: #!/bin/csh -b

• /tmp does not exist as a normal filesystem. It is a virtual filesystem in the swap area. If the /tmp directory is included in a backup specification, and empty /tmp directory will be backed up. If the backup is subsequently restored, a swap area must therefore be configured on the client concerned, or the /tmp directory cannot be re-created.

• The auto device discovery functionality is not provided for Media Agents running on Solaris clients. • The Solaris installation CD-ROM is in the pkg stream format, which is not recognized by the standard tar utility. That's why the HP-UX, and not the Solaris installation CD-ROM must be used for the local installation/upgrade of Solaris clients.

• Backup of ACL is not supported. Tru64 Limitations

• Raw device backup is not supported. 3.4.2 Windows Limitations • Data Protector restores a shared folder without the share attribute. Shared folders properties are kept in registry file and are backed up only if you select the CONFIGURATION backup.

• Only one CONFIGURATION backup can run on a Windows client at a time. • Data Protector requires the same name for both, the computer name and resolving the hostname. • Microsoft Installer 2.0 is required to install Data Protector A.05.10. If an older MSI version is installed on the target system, installation will upgrade it to version 2.0. However, the system must be rebooted for the changes to take effect. This applies to remote installation procedure as well (the MSI on the client will be updated, but the client must be rebooted by user). After the computer is rebooted, restart the installation.

• To run the Microsoft Volume Shadow Copy Service (VSS) filesystem or VSS integration backups using Windows system provider of shadow copies, your system must have at least one NTFS filesystem.

• Backing up network shared volumes using the VSS functionality is not supported. • All available VSS writers listed in the GUI are currently not supported. Data Protector A.05.10 supports a specific subset of VSS writers. Please refer to the support matrix for a list of supported writers. Windows NT Limitations

• On Windows NT, the native tape robotics driver has to be disabled in order to configure the robotics with Data Protector (JAGad35429).

• To perform a disaster recovery, boot and system partition on Windows NT 4.0 must be together smaller than 7.8 GB due to the operating system limitations.

• On Windows NT 4.0, a name of a backup specification containing non-US characters is not displayed correctly when viewing an event under Event Log in the Reporting context. Windows 2000/XP/Server 2003 Limitation

• On Windows 2000/XP/Server 2003 the native robotics driver (Removable Storage Manager) is automatically loaded to enable tape 19

Data Protector A.05.10 Release Notes

libraries. To use the library robotics with Data Protector on a Windows 2000/XP/Server 2003 systems, disable the Windows medium changer (robotics) driver before you configure the system with the Data Protector Media Agent (JAGad35429). Windows XP/Server 2003 64-bit Limitations

• Data Protector A.05.10 does not support Web Reporting on the 64-bit versions of Windows XP/Server 2003, as Microsoft does not provide a JVM on the 64-bit versions of Windows XP/Server 2003. The 32-bit version of Internet Explorer needs to be installed on such a client. It is also shipped with Windows XP/Server 2003.

• The glossary is not available in online help on 64-bit versions of Windows XP/Server 2003. • Only the native Microsoft Windows installation CD, is supported for Automated System Recovery (ASR). The Windows XP 64-bit Edition Recovery DVD that comes with Itanium systems cannot be used for ASR.

• It is not possible to integrate the Data Protector GUI with the Microsoft Management Console (MMC) using the Data Protector OB2_Snap snap-in.

3.4.3 Novell NetWare Limitation • Cross-platform restore is not supported. • On Novell NetWare systems, Data Protector backs up files and disk images of up to 4 GB. 3.4.4 MPE/iX Limitations • The maximum number of MPE/iX Disk Agents that can be running at the same time is limited to 15. • The backup of MPE/iX configuration files or operating system is not possible. If you need to recover the MPE/iX configuration files or operating system, you should create a System Load Tape (SLT).

• The TurboStore/iX 7x24 True-Online product musts be installed on the system in order to use the online and true-online backup options (option ONLINE and ONLINE = START).

• True-online backup with the ONLINE = END option is not supported. • Cross-platform restore is not supported. • The maximal path of arguments (trees and directories) for Data Protector -tree and -exclude DA options is 210 characters. It is recommended to back up whole accounts and groups on MPE/iX filesystem, instead of backing up individual files in one backup session.

• Preview backup with option -exclude uses POSIX wildcards (*, ?). Backup with option -exclude uses specific MPE/iX wildcards @ (replace zero or more alphanumeric characters) and ? (replace one alphanumeric character).

• Maximum Media Agent communication buffer is 32 KB. • On MPE/iX clients, only the omnib CLI command is supported. • The following TurboStore/iX options are not supported and must not be used: FCRANGE, FCRANGE, FILES, LOGVOLSET, MAXTAPEBUF, NOTIFY, ONERROR, PURGE, RENAME, SPLITVS, STOREDIRECTORY, STORESET and TRANSPORT.

• The following TurboStore/iX options are not supported by the TurboStore/iX API (which is used by Data Protector A.05.10 for backup and restore): COMPRESS, FCRANGE, FILES, FULLDB, INTER, LOGVOLSET , MAXTAPEBUF, NOTIFY, ONERROR, ONLINE=END, PARALLEL, PARTIALDB, PURGE, RENAME, SPLITVS, STOREDIRECTORY , STORESET and TRANSPORT.

• Tape statistics functionality is not supported on Media Agents running on MPE.

20

Data Protector A.05.10 Release Notes

3.4.5 OpenVMS Limitations • The OpenVMS client must be installed locally on the OpenVMS system. There is no support for a remote installation from an Installation Server.

• The product can only be installed on the system disk in SYS$COMMON:[OMNI]. • Any file specifications that are passed to the CLI must be in UNIX style syntax: /disk/directory1/directory2/filename.ext.n

— The string should begin with a slash, followed by the disk, directories, and filename, separated by slashes. — Do not place a colon after the disk name. — A period should be used before the version number instead of a semi-colon. — File specifications for OpenVMS files are case insensitive. For example: An OpenVMS file specification of: $1$DGA100:[USERS.DOE]LOGIN.COM;1

must be specified in the form: /$1$DGA100/Users/Doe/Login.Com.1

• There is no implicit version number. You always have to specify a version number. Only file versions selected for the backup will be backed up. If you wish to include all versions of the file, select them all in the GUI window, or, using the CLI, include the file specifications under the Only (-only) option, including wildcards for the version number, as follows /DKA1/dir1/filename.txt.*

• If the Do not preserve access time attributes (-touch) option is enabled during a backup, the last accessed date will be updated with the current date and time on ODS-5 disks. On ODS-2 disks, this option has no effect, and all the dates remain unchanged.

• Rawdisk backups are not available on OpenVMS. There is no equivalent to a “BACKUP/IMAGE” or “BACKUP/PHYSICAL”. • The Backup POSIX hard links as files (-hlink), Software compression (-compress), and Encode (-encode) options are not available on OpenVMS.

Files with multiple directory entries are only backed up once using the primary path name. The secondary path entries are saved as soft links. During a restore, these extra path entries will also be restored. For example, system specific roots on an OpenVMS system disk will have the SYSCOMMON.DIR;1 path stored as a soft link. The data for this path will be saved under [VMS$COMMON...].

• Files being backed up or restored are always locked regardless of whether the Lock files during backup (-lock) option is enabled or disabled. With the -lock option enabled any file opened for write is not backed up. With the -lock option disabled any open file is backed up as well. No message is issued when an open file is saved.

• The default device and directory for pre- and post-exec command procedures is /omni$root/bin. To place the command procedure anywhere else the file specification must contain the device and directory path in UNIX style format: For example:/SYS$MANAGER/DP_SAVE1.COM

• When specifying wildcards for Skip (-skip) or Only (-only) filters, use ‘*’ for multiple characters and ‘?’ for single characters.

21

Data Protector A.05.10 Release Notes

• If you restore to a location other that the original location, only the disk device and starting directory are changed. The original directory path is added to the destination path to form the new restore location.

• If the Restore Time Attributes (-notouch) option is disabled during a restore, the last accessed date will be updated with the current date and time on ODS-5 disks. On ODS-2 disks, the original dates will be set on the files.

• The Move Busy Files (-move) and Restore Sparse Files (-sparse) options are not available on OpenVMS. • Files backed up from an ODS-5 disk on an OpenVMS system that have extended filesystem names (for example upper and lower case letters, Unicode characters, etc) may not be restored to an ODS-2 disk.

• If the Restore Protection Attributes (-no_protection) option is disabled, the files are created with the default owner, protection and ACL.

• Software compression and software encryption is not supported by the OpenVMS Disk Agent. • Files with multiple directory entries (soft links) will be saved once using the primary path/filename. There is no support for a BACKUP/IMAGE equivalence. To make a restored copy of an OpenVMS system disk bootable the OpenVMS WRITEBOOT utility has to be used to write a boot block onto the restored disk.

• 16-bit unicode filenames on an ODS-5 disk volume will be displayed in 8-bit format on the cell server in the form of "^Uxxyy" for a unicode character where "xx" and "yy" are the hexcodes for this character. Other valid characters for files on ODS-5 volumes can be specified using the OpenVMS guidelines for extended file specification syntax.

• If you restore OpenVMS files to a non-OpenVMS platform you will lose the OpenVMS specific file attributes (for example record format, backup date, ACL).

• Files that have been saved on non-OpenVMS platforms and are to be restored to an OpenVMS system may lose some file attributes. No ACL will be restored in this case.

• For a backup, if you select the "Do not preserve time attributes" or on a restore you turn off the "Restore time attributes" options (touch option), the volume where the files reside must be an ODS-5 disk with the access_dates volume_characteristic set. If the volume is an ODS-2 volume or that attribute is not set, the last accessed, attributes, and modified dates will not be used. To create an ODS-5 volume with that characteristic, use the command: $ SET VOLUME/STRUCTURE_LEVEL=ODS-5 - /VOLUME_CHARACTERISTICS=ACCESS_DATES

• No qualification is done for tape drives which are not supported by OpenVMS. See the OpenVMS Software Product Description (SPD) for a complete list of tape drives.

• HSJ connected tape libraries cannot be autoconfigured. Use manual configuration methods to add these devices to Data Protector. • Maximum block size on tape is 63.5 kB for all tape devices. • All tape media initialized by the media agent starts with an ANSI VOL1 label having a non-blank Volume Accessibility character. To mount such a tape volume under OpenVMS use the /OVERRIDE=ACCESSIBILITY qualifier. However, the tape volume does not comply with ANSI tape labeling and can therefore not be used with OpenVMS utilities like DCL-COPY.

3.5 Limitations on Disk Array Integrations 3.5.1 HP StorageWorks Disk Array XP Limitations • Asynchronous CA configuration is not supported. • Split mirror restore (restore to a secondary volume and synchronizing to the primary volume) is only supported for the filesystems and disk images in the BC configuration. Database/application split-mirror restore is not supported.

22

Data Protector A.05.10 Release Notes

• In case the MS Exchange 2000/5.x Server is installed on the backup system, its Information Store (MDB) and Directory Store have to be installed on the HP StorageWorks Disk Array XP LDEVs that are different than the mirrored LDEVs used for the integration. The drive letters assigned to these LDEVs have to be different from those assigned to the LDEVs that are used for the integration.

• Dynamic disks are not supported on Windows 2000. • Instant recovery from a split mirror session (ZDB disk/tape backup) is not possible after exporting the backup medium. Workaround: Do not export the backup medium while backup copies of mirror disks are still valid. In case the medium is exported during this time and you need to perform instant recovery, import the medium and then perform instant recovery.

• Campus Cluster configurations cannot be run on HP-UX if the backup server has any of the following patches installed: PHCO_25814, PHCO_25390, or PHCO_24809. These patches will cause the vgimport of a partial quorum volume group to core dump. PHCO_23333 does not demonstrate this behavior.

• Split mirror (ZDB disk/tape) and tapeless (ZDB disk) backups cannot be started or previewed before the backup specification has been saved.

• During a Data Protector session, when the HP StorageWorks AutoPath Shortest Queue Length load balance policy is set, and if the failover to an alternate path occurs, the Data Protector will fail the session.

• Routine maintenance, including (and not limited to) hot-swapping any field replaceable components like, disk array controllers, FC switches, and/or online firmware upgrades during backups are not supported. Backups are a high-IO activity and should not be done at the same time as routine maintenance.

3.5.2 HP StorageWorks Virtual Array Limitations • Only the HP Business Copy VA snapshot configuration is supported. • Dynamic disks are not supported on Windows 2000. • Only one logical volume can reside on one HP StorageWorks Virtual Array LUN in case LVM Mirroring is used. • Limit the size of LUN0 to 10 MB and do not use it for storing data, as LUN0 is used as a command device and is accessed by all hosts connected to the disk array.

• ZDB disk and ZDB disk/tape backups cannot be started or previewed before the backup specification has been saved. • Instant recovery from the ZDB disk/tape session is not possible after exporting the backup medium. Workaround: Do not export the backup medium while backup copies of snapshots are still valid. In case the medium is exported during this time and you need to perform instant recovery, import the medium and then perform instant recovery.

• Due to a hardware limitation, it is not possible to perform instant recovery if extra snapshots, associated with the same parent LUNs as those to be restored are existing on the HP StorageWorks Virtual Array. Workaround: It is necessary to delete (using omnidbva or manually remove) these extra snapshots before the instant recovery can be performed. Snapshots created by Data Protector can be identified using the omnidbva -lun command.

• If instant recovery is performed, all snapshots for the parent LUNs involved in the instant recovery session will be deleted automatically before the restore takes place.

• Routine maintenance, including (and not limited to) hot-swapping HBAs/SCSI controllers, disk array controllers, FC switches, and/or online firmware upgrades during backups are not supported. Backups are a high-IO activity and should not be done at the same time as routine maintenance.

23

Data Protector A.05.10 Release Notes

3.5.3 HP StorageWorks Enterprise Virtual Array Limitations • Dynamic disks are not supported on Windows 2000. • The creation of snapclones using Data Protector is not supported. • If a snapclone process (triggered by an application other than Data Protector) of a virtual disk is running on a disk array, the Data Protector backup of this virtual disk is not possible. Workaround: Wait until the snapclone creation process is finished, before initiating the backup.

• A maximum of 7 snapshots can be created of each virtual disk and all of them need to be of the same type (either standard snapshots or vsnaps). This limitation applies to the Virtual Controller Software Package V2.0 only.

• A vsnap of a virtual disk cannot be created if standard snapshots of this virtual disk already exist and vice versa. • Instant recovery is not supported. • Replica storage rotation is not supported. • ZDB disk and ZDB disk/tape backups are not supported. • On all supported platforms (Solaris, HP-UX, and Windows 2000), HP StorageWorks Enterprise Virtual Array supports systems with multiple FC HBA cards only when they are running Secure Path.

• Virtual Controller Software Package V1.0 is not supported. • Continuous Access software appliance (DRM) is not supported. • Routine maintenance, including (and not limited to) hot-swapping HBAs/SCSI controllers, disk array controllers, FC switches, and/or online firmware upgrades during backups are not supported. Backups are a high-IO activity and should not be done at the same time as routine maintenance.

3.5.4 HP StorageWorks Modular SAN Array 1000 Limitations • This disk array is not supported with Data Protector A.05.10.

3.6 NDMP Limitations • Only filesystem backup and restore is possible. • The operations media copy and media verify are not supported. • Device cleaning is not supported. • Load balancing is not supported. • Only Full and Incr1 backup levels are supported. • Maximum device concurrency is 1. • Device selection as well as filesystem browsing is not possible. • Device block size is limited to 64 KB. • NDMP devices must use dedicated media pools.

24

Data Protector A.05.10 Release Notes

• Localization for the NetApp specific messages is not possible. • Remote NDMP backup and restore is not supported. Only the devices locally attached to the NetApp Filer can be used to backup and restore that Filer.

• It is not possible to deselect a subtree of the selected tree to be restored. NetApp Filer

• Direct access restore (DAR) is not supported for directories, instead a standard restore will be performed. This has performance implications only.

• On NetApp filers running ONTAB 6.4 or higher, the authentication must be set to options ndmpd.authtype plaintext on the filer. Celerra

• If you select directory restore using the Direct Access Restore functionality, only the selected directory will be restored without its contents. To restore an entire directory tree, set DIRECT=N.

3.7 Limitations on Database Integrations 3.7.1 Oracle Limitations • For Oracle8/9 RMAN options supported in the GUI, refer to the HP OpenView Storage Data Protector Integration Guide. • When using RMAN scripts in Oracle8/9 backup specifications, double quotes (") must not be used and single quotes (‘) must be used instead.

• On Oracle8/9, when editing an RMAN script the term “backup”, which is a reserved word, must be written in capital letters when it is used in the sql command. In all other RMAN commands, do not use capital letters for the reserved word “backup” (JAGae26626).

• Data Protector does not check whether database objects to be restored were backed up and exist in the Data Protector internal database. The restore procedure simply starts.

• When restoring tablespaces to point in time the RMAN interface has to be used. • Only the Oracle Restore GUI and Oracle8/9 RMAN can be used to recover the Oracle8/9 recovery catalog database. • When using the Data Protector Restore GUI, the user will not be able to edit RMAN scripts before they are executed when performing a restore operation.

• When restoring a database using the Data Protector Restore GUI for Oracle to a host other than the one where the database originally resided, the instance name chosen on the new host must be the same as that of the original instance name.

• When editing RMAN scripts, a maximum of two backup commands can be used, otherwise the specification cannot be browsed in the GUI. The first backup command is used for backing up any of the database objects (or the whole database), while the second is reserved for backing up only the archive logs. SQL commands can be used.

• A proxy copy backup of an Oracle8i/9i database is not possible if the database is on raw disks. The backup seems to be completed without any problems reported, but restore from the session is not possible (HSLco41566).

25

Data Protector A.05.10 Release Notes

3.7.1.1 Windows Oracle Limitation

• Maximum 15 RMAN channels can be allocated to run Oracle8/9 backup and restore sessions on Windows platforms. 3.7.2 SAP R/3 Limitations • The length of the full pathnames of all files in a backup specification should not exceed 100 000 characters on UNIX clients, 50 000 characters on Windows clients if you are using manual balancing.

• When backing up a tablespace in a ZDB environment on Windows, the controlfile has to be on the mirrored disk/in the snapshot that will be backed up in order for the backup to be successful (HSLco41567).

3.7.3 MC/ServiceGuard Limitations • You can verify the installation only on the active node. • When adding components on MC/ServiceGuard, add the component(s) on the active node. Then start the package on the other node, and add the component(s) on this node too.

3.8 Other Limitations • The STK - Horizon Library manager is not supported. • You cannot select different condition factors for pools sharing the same free pool. All media pools using a free pool inherit the condition from the free pool.

• Device files for the spt driver cannot be created automatically by Data Protector. The device file needs to be created manually using the mknod command (NSMbb46057).

• Media pools with magazine support cannot use free pools. • Data and catalog protection can only be set until the year 2037. Workaround: set protection period to 2037 or less and extend it with one of the future Data Protector releases that will support time settings past the year 2037.

• The network connections from a Cell Manager to DA clients must respond within 10 seconds or the backup will be aborted. (JAGad29261).

• To view online Help on UNIX platforms, you need to have a Web browser installed. You also have to set the Help Mode to default HTML browser in the Preferences options from the File menu in the GUI.

• If the Inet default port (5555) is changed, Web reporting does not work on the Cell Manager where the port is changed. The following error is reported: Cannot login to Cell Manager.

• Data Protector does not support the user@domain notation. The required form for entering the account information is domain\user (NSMbb48734).

• When installing a Data Protector Cell Manager on a Windows NT system that is configured as the Backup Domain Controller (BDC), setup fails to enable the Log on as a service user right to the account that you specify to be used as the service account for the Data Protector CRS service. You must set this user right manually. You must wait approximately 5 to 15 minutes before this change is propagated to the Backup Domain Controllers or you must force the domain synchronization.

• When installing Data Protector on Windows, you cannot run multiple instances of the setup.exe program.

26

Data Protector A.05.10 Release Notes

• Cross-platform restore of files with the Euro symbol (€) in the filename is not supported. The symbol is displayed only on Windows clients using the GUI (HSLco26804).

• The name of a backup specification should not exceed 64 characters. • The maximum length of text strings to identify or describe the properties of media and devices (for example, the media label applied to a medium when being initialized) is 80 characters.

• Session level restore is not available for the online database integrations. • Data Protector does not support appendable backups for devices of type QIC. • The - (minus) symbol must not be used as the first character in any Data Protector labels or descriptions. • The word DEFAULT is a reserved keyword and must not be used in device names, backup specification names, and pool names. • All media with barcode labels starting with the CLN prefix are treated as cleaning tapes. Labels with this prefix should only be used on cleaning tapes.

• Software data compression for online database backups, such as Oracle, Sybase, SAP R/3, Informix, and Microsoft SQL, is not supported.

• The name used during the installation of the Data Protector Cluster Integration on Windows must not be "omniback". See also the HP OpenView Storage Data Protector Installation and Licensing Guide.

• Backup and restore of sockets and FIFOs is not supported on Tru 64 UNIX. • The configuration of SNMP traps using the Data Protector Manager depends on the platform of the Cell Manager: On HP-UX Cell Managers, the recipient system for the trap that is configured in the GUI, receives the traps. On Windows Cell Managers, the content of the recipient field in the GUI is ignored. The recipient must be configured on the Cell Manager in the Control Panel under Network->Services->SNMP Services.

• The eject/enter functionality for ATL 2640 and ATL 6/176 devices is not supported using the fast access port. • Media of different format types are not compatible: — Data Protector (written by devices under direct Data Protector MA control) — NDMP NetApp (written by devices connected to NetApp filers) — NDMP Celerra Media from these different format categories cannot reside in the same pool. A media from one format category cannot be recognized when subjected to one of the other environments using a different format category. In such a case, the media will be viewed as foreign and depending on the policy, unexpected overwrites might occur.

• On Solaris, detection of media types other than Data Protector media is not reliable, due to the use of a number of different block sizes. Do not rely on Data Protector to recognize foreign media. Workaround: To prevent Data Protector from automatically initializing a medium it does not recognize correctly, set INITONLOOSEPOLICY=0 in the global options file. All media then have to be initialized manually.

• The Restore Sparse Files option, which can be selected when setting options for the Restore Session, is not supported on SCO UNIX.

• From one backup object, only 1,024 files and/or directories can be selected, otherwise select the entire object. For details about backup objects, refer to the HP OpenView Storage Data Protector Administrator’s Guide.

• If an object is deleted from the RMAN Recovery Catalog database, these changes will not be propagated automatically to the IDB

27

Data Protector A.05.10 Release Notes

and vice versa.

• When browsing with the backup specification editor, the Windows user interface lists both online and offline Informix dbspaces. To check for databases, use the onstat -d command. Available databases are marked with the PO flag.

• Some filesystems allow creation of deep directory structures (deeper than 100). Data Protector can only back up down to a depth of 100.

• When changing the omnirc file, it is required to restart the Data Protector services/daemons on the system. This is mandatory for the crs daemon on UNIX and recommended for Data Protector Inet and CRS services on Windows. On Windows, restarting is not required when adding or changing entries, it is required only when removing entries.

• If you use quotes ("") to specify a pathname, do not use the combination of a backslash and quotes (\"). If you need to use trailing backslash at the end of the pathname, use double backslash (\\).

• Tape quality statistics functionality is not currently supported if the Media Agent runs on: MPE, SCO, NetWare, Linux, Sinix, Aix. • Tape sanity check is not supported on NDMP, DAS and ACS Media Agents. • Automatic drive cleaning for library definitions with a shared cleaning tape is not supported. Each library definition needs to have its own cleaning tape configured.

• Cleaning tape recognition in DDS libraries does not work on Solaris. • The path of DR image file is limited to 250 characters, if it is saved on the Cell Manager during backup. • When recreating volumes during the Phase 1 of automated disaster recovery (EADR or OBDR), the original volume-compression flag is not restored (always saved to non-compressed). Workaround: Restore the volume compression flag manually after restore.

• The Data Protector GUI can display a limited number of backup specifications. The number of backup specifications depends on the size of their parameters (name, group, ownership information and information if the backup specification is dynamic or not). This size should not exceed 80 Kb.

• Browsing more than 64,000 objects has a performance impact on the GUI. • On the HP-UX GUI, the user/group information IDs is in numeric format only. • After the transition from the ext2 to the ext3 filesystem on Linux systems, the journal will be visible as the .journal file in the root directory of the filesystem. If the filesystem is not mounted, the journal will be hidden and will not appear in the filesystem.

Due to the Linux operating system limitations, do not delete this .journal file, do not back it up, and do not restore it from backup.

• Data Protector A.05.10 cannot make use of the cartridge memory functionality available in the IBM ULT3580-TD1 and ULTRIUM-TD1 LTO drives due to a difference in the "Media Auxiliary Memory (MAM) attribute data" scsi command implementation compared to the HP Ultrium drive. The cartridge memory support should be disabled for the IBM LTO (HSLco39158).

• Cartridge Memory does not work on QLogic QLA12160 SCSI adapters on Windows Clients with Itanium processors. (HSLco37542)

• On Unix clients, the ksh shell must be installed. Note that on Linux the Public Domain Korn Shell (pdksh) can also be used.

28

Data Protector A.05.10 Release Notes

3.9 Recommendations 3.9.1 Number of Clients in a Cell In typical environments, 100 clients per cell is a reasonable number. In some customer environments it is possible to have many hundred clients in one cell, depending on factors like:

• IDB load: types of objects backed up, filesystem log level, image, online database, split mirror backup/zero downtime backup, NDMP...

• Network and system load: local versus network backup, level of concurrent backup activities. • Maintenance tasks: user management, configuration of backup specifications, upgrade, patches. The maximum number of clients per cell should not exceed 1000.

3.9.2 Large Number of Small Files Backup of a client with a large number (>100,000) of small files puts a high stress on system resources. If such a system needs to be backed up, the following steps (in the suggested sequence) can be performed to improve the situation: 1.

Avoid any other activity on the system where the Media Agent runs during backup.

2.

Set the log level option for such filesystems to directory. This way, individual filenames and file versions will not increase the size of the database.

3.

Consider disk image backup.

4.

Increase the system resources (Memory, CPU) on the system where the Media Agent runs first and then on the Cell Manager system.

3.9.3 NDMP Backup Configuration The recommended maximum number of filenames per NDMP backup object should not exceed 6 million.

3.9.4 Support for NIS+ NIS+ cannot be used as the primary name resolution for hosts when using Data Protector. However, you can run Data Protector on the hosts where NIS+ is configured if one of the following alternatives for name resolution with Data Protector is chosen:

• Using DNS. In this case, change the line starting with hosts in the /etc/nsswitch.conf file as follows: hosts: dns [NOTFOUND=continue] nisplus

• Using hosts file. In this case, change the line starting with hosts in the /etc/nsswitch.conf file as follows: hosts: files [NOTFOUND=continue] nisplus

In both cases, the Cell Manager must have full qualified name registered in DNS or hosts file.

3.9.5 Microsoft Exchange Single Mailbox Backup Microsoft Exchange Single Mailbox backup is not as space- and CPU-efficient as Microsoft Exchange 2000 backup. It is recommended to use this only for a small number of mailboxes. If you are backing up large numbers of mailboxes, please use the Microsoft Exchange 2000 Server integration instead.

29

Data Protector A.05.10 Release Notes

3.9.6 Cell Manager on Windows XP/Server 2003 As Windows XP/Server 2003 features Remote Desktop connection, Data Protector by default uses the TCP/IP protocol when communicating with the IDB. This is slower than local transport used on Windows systems not equipped with Terminal Services technology. If you do not use the Remote Desktop feature, you may switch the transport mechanism to local transport, using the following procedure: 1.

Stop Data Protector services: omnisv -stop

2.

Edit the \db40\datafiles\catalog\velocis.ini file. Change the following lines: [TCP Configuration] ;Enabled=no ;Required=no Port=1530 [NT NP Configuration] Enabled=no Required=no [Local Configuration] Enabled=no Required=no

to: [TCP Configuration] Enabled=no Required=no Port=1530 [NT NP Configuration] Enabled=no Required=no [Local Configuration] ;Enabled=no ;Required=no

3.

Save the file and restart Data Protector services: omnisv -start

30

Data Protector A.05.10 Release Notes

Chapter 4: Known Problems and Workarounds This section lists known Data Protector and non-Data Protector problems and workarounds.

4.1 Known Data Protector Problems and Workarounds Integrations Related Problems

• SAP backup fails, when '-u' option is specified in the command line when using brbackup or brarchive commands. Workaround: If you specified '-u' in the command line of brbackup or brarchive, it should be followed by /.

• A split mirror restore of the SAP R/3 integration using the Data Protector GUI on the backup system is done as a regular filesystem restore, during which split mirror agents (SYMA, SSEA) mount disks on /var/opt/omni/tmp (by default). Since this is a restore of an application integration, VRDA restores files to the original mount points. Therefore, the restore is not done to EMC disks, but to the root partition. (HSLco36051) Workaround: Set the following omnirc variable in the/opt/omni directory on the backup system: SYMA_PRESERVE_MOUNPOINTS=1, for the EMC Symmetrix integration SSEA_PRESERVE_MOUNTPOINTS=1, for the StorageWorks XP integration

• Restore of Oracle9 database on Linux fails with the error message Binary util_orarest failed (HSLco40718). Workaround: Replace the util_orarest.exe file with the util_orarest9.exe file (both located in the /usr/omni/bin directory on Linux). To do so, rename the util_orarest.exe to util_orarest.exe.orig and util_orarest9.exe to util_orarest.exe.

• When reconfiguring Sybase or Informix integration using the Data Protector GUI, the configuration data already known to Data Protector is not displayed in the GUI. Workaround: Enter the configuration data manually.

• In split mirror backup environment on Solaris 7 (Sun SPARC) with Oracle 8.0, where different configuration files exist both on backup host and application host, it is possible that check configuration passes but the actual backup fails because the check configuration process reads the configuration for the backup host while the backup process reads the configuration for the application host. Workaround: In order to force the configuration process and backup process to read from the same configuration file, the /opt/omni/lbin/ob2rman.exe file on the backup host needs to be replaced with the file UNIX-CD:/MISC/Solaris7_Oracle8/ob2rman.exe located on any of the UNIX Data Protector CDs. Caution: save the original file and ensure that the permissions of the replaced files are like they were on the original file.

• Data Protector A.05.10 creates an RMAN script with the include current controlfile option. Oracle sends the request for the controlfile backup at the beginning of the backup session, which means that the running backup will not be registered in the controlfile that has been backed up. Therefore it is not possible to restore the latest backup if that controlfile has been restored first (disaster recovery). The problem is also documented in the Oracle documentation. (HSLco37323) Workaround: When creating a backup specification, select the database and the archivelogs to be backed up. You can use one of the templates: Database_Switch_Archive or Database_Switch_ArchiveDel. Save the backup specification and manually add a third backup command for the controlfile backup to the RMAN script. Note that the Source tab will now be frozen and you cannot browse the list.

• In split mirror backup environment with huge SAP databases, the size of the message buffer used by Data Protector may be too small for the complete list of SAP files to be backed up. The backup session will fail with the following error: [Critical] From: [email protected] "TOR" Time: 07/24/02 10:42:16

31

Data Protector A.05.10 Release Notes

[131:108] The list of files specified for backup or restore is too long. [Major] From: [email protected] "TOR" Time: 07/24/02 10:42:16 Resolving to disk level failed (error=-4) BR278E Command output of '/opt/omni/lbin/ob2smbsplit /big_sap_baza/TOR/malo_da_podaljsamo_dir/sapbackup/.bdimmklf.lst': [Major] From: [email protected] "TOR" Time: 07/24/02 10:42:16 Aborting connection to BSM. Abort code -2

Workaround: To increase the buffer size, set the environment variable OB2IPCBUFSIZE in the .omnirc file on Cell Manager, R1 and R2 hosts and specify the desired amount of memory to be used for the buffer before starting the backup: OB2IPCBUFSIZE=. How to determine the buffer size? N_obj

number of objects (files)

N_fs

number of file systems

N_lvmvg

number of volume groups

N_dg

number of disk groups

N_rdsk

number of rawdisks

Obj

Object Name

ObjBack

Object Backup Name

MntPathLen

Path name on backup site (example: /var/opt/omni/tmp/App_host)

fsmnt

File System Mount Point

fsdev

File System Device File (example: /dev/dsk/c0t1d1 or /dev/vg01/lvol1)

vg

Volume group (example: /dev/vg01)

dg

Disk group (VxVM) - dependence on mapfile which is required for creating disk group (example: /dev/vx/dsk/dg01)

rdsk

Raw disk file name (example: /dev/rdsk/c1t1d1)

AvgLen_

average length of

There are two different buffers used: BSM R1 and R1 R2 Calculating the BSM R1 buffer size MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen) Calculating the R1 R2 buffer size MsgSize_R1_R2 = N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) + N_fs * (AvgLen_fsmnt * 2 + MntPathLen + AvgLen_fsdev * 2) + N_lvmvg * (AvgLen_vg * 2)+ N_dg*(AvgLen dg*2)+ N_rdsk * (AvgLen_rdsk * 2) Calculating the OB2IPCBUFSIZE value OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)

Example N_obj = 3000 N_fs =3 N_lvmvg = 3 N_rdsk = 8 AvgLen: Obj = 80

32

Data Protector A.05.10 Release Notes

MntPathLen = 20 fsmnt = 30 fsdev = 12 vg =7 rdsk = 12 MsgSize_BSM_R1 = 303000 MsgSize_R1_R2 = 402 This means: OB2IPCBUFSIZE=310000

• Zero downtime backup of Exchange 2000 Server (which was upgraded to SP3) fails with the following error: [Normal] From: [email protected] "" Time: 7/24/2002 10:26:52 AM Executing the split pre-exec script. (omniex2000.exe -dismount -storage_group 'Accept' -appsrv vaexchg.ipr.com) [Critical] From: [email protected] "" Time: 7/24/2002 10:26:53 AM [224:501] Split links pre-exec command failed with exit code -1.

Workaround: When Exchange 2000 Server is upgraded to SP3, omniex2000.dll must be unregistered and registered again. From /bin directory on Exchange 2000 Server, run the regsrv32.exe command: to unregister: regsvr32 /u omniex2000.dll to register: regsvr32 omniex2000.dll

• Restore of an Informix database cannot be started from the CLI with the omnir command. Workaround: The restore can be started with ob2onbar.exe or with the Informix command onbar.exe. (HSLco41629) Media and Disk Agent Related Problems

• When you have a cell set up where the Cell Manager is installed outside the cluster and the devices are connected to cluster nodes and a failover during backup activity occurs, the Media Agent may not be able to properly abort the session, which results in the medium no longer being appendable (NSMex03642).

• When attempting a parallel restore which has more Disk Agents than the Media Agent concurrency, some Disk Agents may fail with the following error: Cannot handshake with Media Agent (Details unknown.) => aborting. Workaround: Restart the restore objects of the failed Disk Agents (JAGab76083).

• During restore, the restore Disk Agent (VRDA) displays the mount points of the application host in the monitor. For example, instead of the restore target mount point /var/opt/omni/tmp//BC/fs/LVM/VXFS it actually displays the corresponding application source mount point /BC/fs/LVM/VXFS.

• Cleaning tape drive functionality works correctly when there is a cleaning tape present either in the library slot or in the repository slot. If the cleaning tape is not present, the mount request for the cleaning tape will not work properly.

• When importing a range of tapes, Data Protector normally skips all invalid tapes (such as tar tapes, blank tapes, etc.) and continues with the next slot. If importing a range of tapes on a NetApp Filer (Celerra), and a NetApp tape is detected, Data Protector reports a major error and aborts.

• If during backup/restore to ACS xMA library mount request occurs (in case that library run out of usable media) do not format or scan additional tapes with the tape device used by the backup/restore session. Use the different tape device in library to perform this operation and confirm the mount request.

• When restoring files to a different host via a UNC share, the restore fails with the following message in the session log: 33

Data Protector A.05.10 Release Notes

Can not open: ([112] There is not enough space on the disk. ) => not restored. [Warning] From: [email protected] "host2.test.com [/H]" Nothing restored

Time: 27/09/00

16:58:40

Workaround: OmniInet logon user must have the access to log on to the remote host, which is specified in the UNC path. You should also be the owner or have write permission to the files you want to restore via UNC share.

• Data Protector UNIX session manager sometimes fails to start restore media agents in parallel on Novell NetWare clients with an error message like, for example, Could not connect to inet or Connection reset by peer. It is possible that some parallel restore sessions are completed without errors, while other restore sessions are not even started (HSLco40874). Workaround: Set the SmMaxAgentStartupRetries global variable in the Data Protector global options file (located in /etc/opt/omni/options/global) to 2 or more (max. 50). This variable specifies the maximum number of retries for the session manager to restart the failed agent before it fails. For more information on the Data Protector global options file, refer to the online Help index keyword “global options file”.

• After upgrading to Data Protector A.05.10, you cannot use devices that were configured as different device types in previous releases. For example, you cannot use 9940 devices that were configured as 9840 devices, or SuperDLT devices that were configured as DLT devices. The following error occurs (HSLco35667; HSLco40390): [Critical] From: [email protected] "SDLT" [90:43] /dev/rmt/1m Invalid physical device type => aborting

Time: 2/22/2003 5:12:34 PM

Workaround: Manually reconfigure these devices using the mchange command, located on the Cell Manager in the following directories:

— On HP-UX: /opt/omni/sbin/utilns/HPUX — On Solaris: /opt/omni/sbin/utilns/SOL — On Windows: \bin\utilns\NT The syntax of the mchange command is: mchange -pool PoolName -newtype NewMediaClass where: PoolName is the name of the media pool with devices that are currently configured and should be reconfigured (for example, Default DLT or Default T9840). NewMediaClass is the new media type of the devices, for example, T9940 for 9940 devices and SuperDLT for SuperDLT device. This command changes media types for all media, drives and libraries that use the defined media pool. After you have executed this command for each device you changed, move the media associated with the reconfigured devices from the current media pool to the media pool corresponding to these media. For example, move the media associated with the reconfigured 9940 devices to the Default T9940 media pool, and the media associated with the reconfigured SuperDLT devices to the Default SuperDLT media pool. For related procedures, refer to the online Help. GUI Related Problems

• If several backup schedules are added in the Data Protector GUI in succession, it is possible that the Date/Time dialog box will lock up. Workaround: Press the ESC key.

• In the Data Protector GUI on HP-UX, when using the default roman8 encoding, unreadable characters may appear. Workaround: Set your locale to an iso88591 encoding. For example, set an iso88591 compatible locale: $ export LANG=C.iso88591 There are usually other iso88591 locales too, such as en_US.iso88591, de_DE.iso88591, etc. You can check available

34

Data Protector A.05.10 Release Notes

locales on your system using the locale -a command. If this command isn't available on your system, browse the following directories to determine which locales are supported: /usr/lib/nls /usr/lib/locales /usr/lib/X11/nls

• Copying a selection of a session message text to clipboard by right clicking the selected text and selecting Copy to clipboard does not work on UNIX systems. A workaround for UNIX systems is to make a selection in the session message text and paste it in a text editor (for example vi editor). You can then save the contents of the text editor in a new file. Installation and Upgrading Related Problems

• After upgrading from an OmniBack II A.03.5x installation, it may not be possible to browse into the structure of previous IDB backup objects in the Restore Context. Workaround: List details from media, then this structure can be browsed.

• After upgrading Data Protector from a versions earlier than A.04.10, you may get the following warning during the first backup, if the Resynchronize links before backup option is selected: [Warning] From: [email protected]""

Time: 10/24/2001 11:33:06 AM

Internal error: Unknown option -disable_bs.

Workaround: In the existing backup specification click Apply and the warning will disappear in the next backup.

• In case there is not enough free disk space on the destination partition, the push installation of the User Interface fails and reports: [Warning] Installation of User Interface FAILED! Data Protector Software package installation failed Check the log file /var/tmp/cc.pkgadd-log

Workaround: The disk space on the destination partition has to be at least 40MB even if the package is installed on the linked partition.

• Installation CD-ROM cannot be ejected after installing the Cell Manager on Solaris systems. Workaround: Stop and start Data Protector services: /opt/omni/sbin/omnisv stop /opt/omni/sbin/omnisv start

• If the cluster client is configured under several virtual names, then Data Protector Cell Manager will will only update configuration information for cluster virtual node (HSLco41388 ). Workaround: This has no effect on the actual state of the Data Protector client - only configuration data is not upgraded. To finish the upgrade, log to the Cell Manager system and run the command omnicc -update_host for every virtual name (other than cluster name). Other Known Problems

• If you have different logical devices for the same physical device and you use a different logical device for backup every day, the lock name concept prevents collisions between different logical devices assigned to the same physical device. When trying to perform a restore, where several logical devices but only one physical device was used for different backups (full, inc1, inc2, inc3...), Data Protector does not check the lock name, and therefore does not recognize that the same physical device was used for all backups. An error message that the restore session is waiting for the next device to get free is displayed. Workaround: Remap all logical devices to the same physical device by following the steps below:

35

Data Protector A.05.10 Release Notes

1.

In the Context List, click Restore.

2.

In the Scoping Pane, expand the appropriate data type and desired client system and object for restore.

3.

When the Restore Properties window opens, select the files that you would like to restore.

4.

In the Devices tab, select the original device and click Change.

5.

When the Select New Device window opens, select the physical device name and click OK.

• Command omnistat -session [session ID] -detail sometimes displays Restore started and Backup started incorrectly. This can result in both parameters appearing to be identical

• The following applications are not recommended to be installed together with Data Protector on the same system: WebQoS, CyberSitter 2000, NEC E-border AUTOSOCKS. Coexistence of Data Protector Media Agent and Storage Allocator may cause unexpected results. For most recent patch information, refer to the HP Web page: http://support.openview.hp.com/support.jsp

• After failover on the secondary Application System (application is in MC/ ServiceGuard) instant recovery may fail with the following error message, if the Check data configuration consistency option is selected: [Critical] From: [email protected]""

Time: 11/8/2001 11:43:09 AM

Data consistency check failed! Configuration of volume group /dev/vg_sap has changed since the last backup session!

Two workarounds are possible:

— Make sure that the vg configuration on the system is not changed, deselect the Check data configuration consistency option and restart the instant recovery.

— When setting up the cluster, make sure that all disk device files are identical by use of the ioinit command. • If you export a physical node from the MC/ServiceGuard cluster, you cannot import it back, as the cell_server file will be deleted. This file is shared among all nodes of a cluster, so you need to recreate it. Workaround: Run /opt/omni/sbin/install/omniforsg.ksh -primary -upgrade.

• If backup server is in a cluster environment and the backup is performed using the actual hostname, the instant recovery fails if you try to recover using the secondary host. Workaround: In order to avoid this, use a virtual hostname.

• Data Protector instant recovery fails when the filesystem is busy. Workaround: List processes which occupy filesystem by using the fuser command. For example, if the filesystem /oracle/P01 is busy, run: fuser -kc /oracle/P01.

• If a backup is performed on one node and then instant recovery attempted to another node with the Check data configuration consistency option selected, the following error message is displayed: Volume group configuration has changed. This message is displayed because the vgdisplay command detects that the LUN configuration on one client is different than that of the other client.

Workaround: If the ext_bus instance is the same, this message is not displayed. Alternatively, it is not displayed if the Check data configuration consistency option is not enabled. (NSMbb46150)

• A backup may fail, if the snapshot backup specification contains an invalid rdsk object in the first place. Workaround: Change the order of the rdsk objects so that a valid rdsk is in the first place.

• Data Protector services my not be running after EADR/OBDR. 36

Data Protector A.05.10 Release Notes

Workaround: In the Control Panel, go to Services (Windows NT) or Administrative Tools, Services (Windows 2000) and change the startup type for Data Protector services from Manual to Automatic. Start the services after you have changed the startup type.

• If more than one omnidbutil -purge session is started, omnidbutil reports that it cannot communicate with the Cell Manager. To avoid this, do not start more than one session.

4.2 Known Non-Data Protector Problems and Workarounds Non-Data Protector Problems Related with Integrations

• If a Microsoft Exchange backup fails with an error message like "...cannot wait for synchronization event", the reason could be that the backup was run concurrently with a defragmentation process. Consult the Microsoft support article ID: Q183675.

• For the purpose of remote administration, to be able to run the omniex2000SM.bat script from a Windows client that does not have the MS Exchange 2000 Integration software component installed, you must copy the omniex2000SM.bat to such a client.

• Due to Microsoft SQL Server 7.0 bug 53787 in cluster support with VDI, set the _VIRTUAL_SERVER_NAME_ environment variable in the omnirc file prior to invoking IClientVirtualDeviceSet::Create(). (HSLco23526)

• In the Data Protector GUI, the tape device you want to use for an MS Exchange or MS SQL restore cannot be changed from the device originally used by backup. Workaround: To change the device for restore, in the Data Protector GUI, click the Change button. You cannot change the device just unselecting the default device and selecting the desired device.

• If installed as a cluster-aware application, Microsoft SQL 7.0 needs the Microsoft SQL 7.0 Service Pack 1. • SAP R/3 brtools version 4.6C has problems backing up datafiles on Solaris platform. Database backup and tablespace backups however work fine.

• Backing up the SAP R/3 database using the zero down time backup functionality and Oracle8 Recovery Manager together fails. During the SAP R/3 (Oracle 8i) integration backup the following error may occur: BR002I BRARCHIVE 4.6D (17) BR252E Function fopen() failed for '/oracle/YP1/817_64/saparch/adhjhzoc.cpd' at location main-4 BR253E errno 2: No such file or directory BR121E Processing log file /oracle/YP1/817_64/saparch/adhjhzoc.cpd failed sh: 12312 Memory fault [Warning] From: OB2BAR@sv005 "OMNISAP" Time: 02/20/02 10:54:03 BRARCHIVE /usr/sap/YP1/SYS/exe/run/brarchive -d util_file -scd -c returned 35584 Workaround: Add the Oracle8 NLS_LANG environmental variable into the SAP R/3 configuration file: NLS_LANG=AMERICAN_AMERICA.WE8DEC SAPDATA_HOME=/oracle/YP1

• When performing a split mirror backup of Oracle, and tablespaces can neither be put in nor out of the backup mode, Data Protector finishes the backup with an error: ORA-12532: TNS: invalid argument alter tablespace IDX end backup ORA-03114: not connected to ORACLE

Workaround: Ensure that the newest 'ksh' patches are installed on the system.

37

Data Protector A.05.10 Release Notes

• Tablespace names must not be RMAN reserved names on the Oracle8 integration for Windows platforms. In such case the backup fails when Oracle8 RMAN parses the command script. Also, a tablespace called LEVEL cannot be created due to the Oracle8 internal error (HSLco11582).

• An Oracle8/9 backup session on the Windows platform waits for 20 sec. before it ends. This waiting time occurs because Oracle8/9 does not notify that the API session is complete. If you run a backup from RMAN and use the Data Protector library ( orasbt.dll) to perform that task, you must wait at least 20 sec. between two backups with the same backup specification name. If not so, all the backup objects will be within one backup session.

• In case the backup system is low on resources (CPU, memory, etc.), the following error is reported by the Oracle Server Manager in the Data Protector Monitor context for the Oracle8 HP StorageWorks XP integration: ORA-12532: TNS: invalid argument. Workaround: Configure the backup system in such a way that it has sufficient resources to run the Oracle Instance and perform a backup at the same time.

• If an Informix Logical Log backup on the Informix Dynamic Server version 7.30 is aborted or fails, the Onbar hangs. Workaround: Contact Informix Support for an appropriate patch (PTS 102449).

• Due to an Informix bug, the point in time restore for Informix 7.31 TC8 on Windows 2000 does not work. Workaround: Contact Informix support for an appropriate patch (HSLco25099).

• On Informix 7.3x 64-bit, the $INFORMIXDIR/bin/onbar binary does not work properly. Workaround: Copy the $INFORMIXDIR/bin/onbar shell-script from 32-bit version of Informix 7.3x. If you do not have this script, contact Informix Support.

• When you start more than a single restore session of the Informix Dynamic Server version 9.21.TC1 on Windows 2000, the session might hang. Workaround: Reboot the Windows 2000 system and restart the restore (HSLco26988).

• When you perform a recovery and then a restore in Informix, Data Protector always reports that the ON-Bar process exits with the return code 0. Workaround: Check the Informix log file /tmp/bar_act.log, for the real return code value.

• Restore of a whole backup chain on Informix 9.20 FC1 64 bit on HP-UX does not work. Workaround: Check for availability of an Informix patch that should solve this problem.

• When performing a backup on Informix Enterprise Decision Server version 8.3, the logical logs are not backed up automatically. This is an Informix PTS bug 147170 (HSLco25521). Workaround: Install the Informix patch 8.30.FC3D9.

• Due to an Informix bug, you cannot perform an Informix restore by a logical log number on Windows NT/2000 with the Informix version 7.31.TC2.

• If you are using a version of Informix that is older than 8.3x version, it can happen that the Informix log files cannot be backed up. (NSMbb41591) Workaround: Edit the /opt/omni/lbin/ob2onbar.exe script so that every option "-b -l" is replaced with "-l".

• When the Restore complete database option for the Informix integration is selected in the Restore Context of the GUI, only several databases are shown as selected for restore. However, the complete database is restored. This problem occurs when ReflectionX is used (HSLco24390). Workaround: To avoid this problem, use the ReflectionX version 9.0.

38

Data Protector A.05.10 Release Notes

• Aborting a Sybase backup session on Solaris, Windows NT and Windows 2000 hangs the system. Workaround: Kill the $SYBASE_HOME_DIR/bin/sybmultbuf process from the command-line interface to abort the backup session.

• When performing a Sybase backup on Windows NT 4.0, the following message appears in the Monitor window during backup (HSLco17012): Data Protector, Library Version=1, Message=Error in reading configuration file ?????fError in reading configuration file %s.

Workaround: This is a Sybase error message. Contact Sybase support for the latest patch information.

• Data Protector currently does not support ZDB backups if the backup system has Windows 2000 with SP3 installed due to the Windows 2000 SP3 problem. When Windows 2000 SP3 is installed on the backup system, a ZDB backup may fail occasionally (HSLco38015). Description: The drive scan operation fails when a new snapshot is created and presented to the system. It shows the missing volume/partition. The disk can be seen on the system, but there is no volume device available. All existing volumes appear in output of the mountvol Windows command. Workaround: The backup system must have Windows 2000 with SP2 installed for all ZDB integrations. For updated information on the issue, refer to http://support.openview.hp.com/support.jsp

• When performing a ZDB backup on Windows, Data Protector does not clean up devnodes from the Registry, which can cause a reboot of the backup system. The problem occurs on snapshot disk arrays (HP StorageWorks VA and HP StorageWorks EVA). Workaround: Install the “Scrubber” utility and run it. It will remove obsolete storage nodes from the Registry. Note that a reboot of the backup system is required afterwards. For more information on the “Scrubber” utility, refer to the Microsoft support.

• If performing a snapshot backup on HP StorageWorks EVA (Windows systems), the following message may occurs: [Normal] Starting drive discovery routine. [Major] Resolving of filesystem has failed. Details unknown.

Workaround: Install Secure Path version 4.0A and patch v4.0A-3. The patch is available on http://www.openview.hp.com/products/datapro/spec_0001.html. Patch v4.0B-3 for Secure Path version 4.0B will be available on the above mentioned site. Additionally, set the following omnirc variables to minimize the probability of the problem to occur: EVA_EMAPI_MAX_RETRY EVA_EMAPI_RETRY_DELAY

Predefined values of these variables should fit most of your configurations. However, if the specified settings do not solve the problem, you should enlarge the values as needed. Other Non-Data Protector Problems

• When using the Data Protector GUI on UNIX platforms the color codes used in menu trees can be unreadable because the menu entries are highlighted in black. There are two workarounds: 1.

Modify the .Xdefaults file in the home directory by adding the following line: *enableEtchedInMenu: False

Log off and log on so that the change takes effect.

39

Data Protector A.05.10 Release Notes

2.

Start the GUI with the -cde command line option. This forces the GUI to use system colors. You can also export the system colors before running the GUI using the following command: export OMNI_CDE_COLORS=1

• Due to a Microsoft Windows 2000 bug the backup of the Active Directory can fail, especially if there are several backup runs within a short period of time. Workaround: Install the Microsoft Windows 2000 Service Pack 2. For more information refer to the Microsoft Knowledge Base on http://support.microsoft.com/support/kb/articles/Q282/5/22.ASP.

• When using an LTO or Super DLT device with Fibre Channel, do not change the block size from the default value, which is 64 KB. • Cannot import media or omnimlist using a DLT8000 (StorageWorks_E DLT Library). Getting errors... [Major] From: MMA@hkgbkup3 [90:182]

"HKGBKUP3_1m"

Cannot forward segment. ([5] I/O error)

[Major] From: MMA@hkgbkup3 "HKGBKUP3_1m" [90:53]

Time: 10/31/01 19:52:35

/dev/rmt/1m

Time: 10/31/01 19:52:35

Cannot seek to requested position ([5] I/O error)

Resolution: Quantum has confirmed that there is a problem with the controller firmware. There is a cumulative slip occurring in the tach relative to the tape. This coupled with seeing the BOT marker causes the drive to reconstruct its internal directory. This happens only on tapes with LOTS of data. Please consult with your HP Support representative before you perform any of the following: The DLT8000 drive FW must be upgraded to V51. This can be done by accessing the FW Upgrade page and following the directions: http://www.hp.com/cposupport/swindexes/hpsurestor18551_swen.html More details of the fix in Service Note A5597A-27

• If an HP StorageWorks Disk Array XP split mirror backup session is started on a Solaris system with the GUI Leave the backup system enabled option or CLI leave_enabled_bs option set, and the .omnirc file SSEA_MOUNT_PATH variable is changed after the session is finished, the next split mirror backup or split mirror restore session for the same mount point will fail.

Workaround: To avoid the failure, manually unmount the old backup system mount point and (re)start the session.

• Breece Hill's Saguaro libraries use the stack mode for entering and ejecting cartridges. One mail slot has two SCSI addresses, one for the enter operation and the other for the eject operation. For Data Protector to work in this mode, the following omnirc command variables must be set:

• OB2LIB_STACKEXP must contain the SCSI address of the export slot • OB2LIB_STACKIMP must contain the SCSI address of the import slot • Backup on UNIX systems may fail because of the shared memory shortage with the following error (HSLco40194): Cannot allocate shared memory pool (IPC Cannot Create Shared Memory Segment System error: [22] Invalid argument ) => aborting

Workaround: The actions are different for different operating systems. After you have applied the changes, you need to reboot the system. On HP-UX Set the OB2SHMEM_IPCGLOBAL variable to 1 in the global options file: /opt/omni/.omnirc.

40

Data Protector A.05.10 Release Notes

On Solaris Set the kernel parameters in the /etc/system file as follows: set set set set set set set set set

shmsys:shminfo_shmmax=4294967295 shmsys:shminfo_shmmin=1 shmsys:shminfo_shmmni=100 shmsys:shminfo_shmseg=10 semsys:seminfo_semmni=100 semsys:seminfo_semmsl=100 semsys:seminfo_semmns=200 semsys:seminfo_semopm=100 semsys:seminfo_semvmx=32767

If the problem persists, the parameters can be increased. On SCO UnixWare Increase the value of the SHMMAX kernel variable using the scoadmin command. The minimum value required by Data Protector can be calculated using the following equation: minimum value for SHMMAX = (Disk Agent buffers * Block size in KB* 1024) + 16 You can get the values of Disk Agent buffers and Block size from the Advanced Options dialog box for the target backup device. It is recommended that the SHMMAX value is set to larger number.

• Data Protector Media Agent cannot coexist with CA ArcServe installed on the same Windows client system, as this can lead to data loss.

• Data Protector does not support NDMP v4 on NetApp ONTAP version 6.1.2. Workaround: Either upgrade to NetApp ONTAP version 6.2R3 or enforce the usage of NDMP v3 by setting the following omnirc variable on the NDMP Media Agent client: OB2NDMPDEFVERSION=3.

• If an IRIX 6.5 disk is connected to the second SCSI controller, there might be a problem detecting if the disk is mounted. Workaround: Ensure that the disk is not mounted before you perform disk image (rawdisk) restore.

• When starting online Help from the GUI on UNIX systems using Netscape Navigator, only the Netscape browser is started. Workaround: Verify that the correct pathname to the Netscape Navigator installation is specified in the Data Protector GUI: 1.

Click File -> Preferences -> Settings.

2.

In the Location of executable script or binary file text box, enter the correct pathname to Netscape Navigator.

• When using Outlook XP with the latest security patch installed, the following problem appears: when you add a report to a report group specifying email as a send method, and then try to start a report group, the GUI hangs (HSLco35048). The same happens if you configure a notification and select the email send method. This problem also occurs if you install the latest security update for Outlook 2000 or Outlook 98 (Microsoft Knowledge Base article IDs: Q262617, Q267319, Q262700). The cause of the problem is that Outlook requires user interaction before sending an email notification. This feature cannot be disabled since it is a part of the Outlook security policy. Workaround: Start a report from the CLI. When a warning appears, click Yes to receive a notification. For information on how to customize security settings, refer to Administrator Information About the Outlook Email Security Update (Microsoft Knowledge Base article ID: Q263296).

• When viewing Web Reporting using Netscape Navigator, after resizing the browser window, the applet does not adjust its size to fit within the new dimension.

41

Data Protector A.05.10 Release Notes

Workaround: Start the Netscape Navigator manually, resize the window to the desired size and then open the WebReporting.html file (NSMbb40457).

• When using web reporting on HP-UX 11.00 together with Netscape 7.0 (only in Japanese language), the tree in the Scoping Pane is not properly displayed.

• When you are backing up Data Protector clients not configured for Data Protector report, the report lists all clients from a specified network range. In case you specify a C-class network that is in another subnet, then the report can take quite a lot of time before it is created. (HSLco26168).

• When sending an HTML report on a Windows Cell Manager using the email send method, the report will be displayed in the ASCII format (HTML plain text) when opened. (NSMbb41120). Workaround: To display the report correctly, open it in an HTML browser.

• If you use Data Protector reporting and the output format is HTML, a UNICODE file is produced. Some earlier browsers (such as Internet Explorer 3.x) do not support local viewing of UNICODE files. However, if you view the same file through a Web server using the same browser, it is displayed correctly.

• Data Protector uses host name resolution to communicate between hosts. This is done either via DNS servers or via /etc/hosts or /etc/lmhosts file. If the DNS service is not available or correctly configured on the Windows clients, you can edit the hosts (lmhosts) file, which are located in the \WINNT\System32\drivers\etc directory. Use the hosts file if you want to map IP addresses to hostnames and lmhosts file if you want to map IP addresses to computer (NetBIOS) names. Additional information on how you can edit these files is found in the beginning of these two files. After you have done editing, terminate the Data Protector GUI and restart it for changes to take effect. You must ensure that the name resolution is consistent throughout the Data Protector cell.

• When connecting a Windows 2000 GUI client to a Cell Manager, the following error may occur: You do not have access to any Data Protector functionality ...

The issue can be that the system name (including the domain suffix) is set at two places on Windows 2000 systems. You have to ensure that the fully qualified hostnames in the ( system properties->Network-Tab->properties->more->Primary DNS suffix…) and (local area connection properties->TCP/IP->Advanced->DNS-Tab->DNS-suffix…) settings on the Windows 2000 GUI client are identical and are the same as the system name (including the DNS suffix) defined in the Data Protector User Context.

• Data Protector Cell Manager is not supported on Windows NT 4.0 Terminal Server (NSMBB45909). • If you have Data Protector Cell Manager installed on computer running Windows 2000 Terminal Services, you may experience a performance drop of the IDB. You can solve this by configuring the IDB to use local transport (shared memory) to communicate with the rest of the Cell Manager. However, if you configure to use (faster) local transport, then Data Protector cannot be accessed over Terminal Services client. Data Protector Cell Manager can also be accessed using the Data Protector GUI. Before you begin, you should always make a backup of all initialization files. Perform the following steps on the Cell Manager in order to change the configuration to use local transport: 1. Modify the velocis.ini file, which is located in the \db40\datafiles\catalog directory: [TCP Configuration] Enabled=no

;Enable transport (default yes)

Required=no

;Require transport to start (default yes)

PacketSize=8192 Port=1530

;Set send/recv packet size (default 4096) ;Port to bind to (default services entry for server name)

2. Modify the connect.ini file, which is located in the \db40\datafiles\catalog

42

Data Protector A.05.10 Release Notes

directory and remove [ob2_40] section: [ob2_40] Protocol=TCP Host= Port=1530 Encryption=0 3. Restart Data Protector services. If you would like to revert to the old configuration which uses TCP/IP protocol, simply replace these two initialization files with the original copies and restart Data Protector services again.

• When using the Data Protector GUI on UNIX platforms, the following action may cause the hang of the GUI: If you use the drop-down arrow in the Data Drive drop-down list (Devices & Media context, Devices -> Drives -> drive property page ->Drive tab) to get a list of available devices, and then try to change the width of columns in the list, the GUI may hang.

• Erase operation on magneto-optical drive connected to HP-UX fails with the following error: [Major] From: [email protected] "MO-lada" Time: 5/6/2002 3:52:37 PM [90:90] /dev/rdsk/c2t0d1 Cannot erase disk surface ([22] Invalid argument) => aborting

• If Physical Address Expansion (PAE) is specified for Windows 2000, Data Protector is not able to perform correctly with devices such as Ultrium. Device operations fail with the following error: error 87 cannot write to device the parameter is incorrect This happens if the tape that is being restored was created while running Windows 2000 without the Physical Address Extensions (PAE) option enabled. Workaround: Set the registry key value MaximumSGList to 17. MaximumSGList should be located in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\\Parameters where represents the ID of a SCSI interface used for controlling the device (e.g. aic78u2 for Adaptec).

• After installation or upgrade to Data Protector A.05.10, Windows may report that some application is not installed or that or a reinstall is required. The reason is an error in Microsoft Installer upgrade procedure. Please read the Microsoft Knowledge Base article Q324906 to solve the problem.

• Secure path on HP-UX external device filename may change after reboot. This changes the mapping to volume managers. Raw device backups can fail due to a different device file being specified in the backup specification.

• The (de)installation of Data Protector version A.05.10 may run into a fatal error 1723. This is a Windows Installer Package problem caused by a running IDriver.exe or Setup.exe process while you try to (de)install Data Protector version A.05.10. Workaround: To resolve this situation, use the Task manager to end any running setup.exe or IDriver.exe processes and then retry the (de)installation of Data Protector.

43

Data Protector A.05.10 Release Notes

Chapter 5: Installation Requirements This chapter gives a description of Cell Manager, Installation Server, and client installation requirements. It also provides a list of upgrade requirements. The following are general installation requirements:

• Free TCP/IP port: 5555 by default • The TCP/IP protocol must be installed and running. The protocol must be able to resolve all hostnames in the Data Protector Cell.

5.1 Cell Manager Requirements The Data Protector Session Manager does not support the IDB on a filesystem that is mounted as NFS type.

5.1.1 On Systems Running HP-UX 11.0, 11.11 and 11.20 The Cell Manager must meet the following minimum requirements:

• The Soft File Limit per Process on the Cell Manager should be at least 1024. • 256 MB RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB for data segments are needed.

• 240 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB). • It is recommended, that the kernel parameter maxdsiz (Max Data Segment Size) is set to at least 131072000 Bytes (128 MBytes). After this the kernel should be recompiled and the machine rebooted.

5.1.2 On Systems Running Solaris 7/8/9 The Cell Manager must meet the following minimum requirements:

• 256 MB RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB of data segmenta are needed.

• 220 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) • The following values of kernel parameters are recommended: SEMMNI (maximum number of semaphore sets in the entire system) = 100 SEMMNS (maximum semaphores on the system) = 256 A system restart is necessary for kernel changes to take effect.

5.1.3 On Systems Running Windows NT The Cell Manager must meet the following minimum requirements:

• 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM are needed.

• 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB)

44

Data Protector A.05.10 Release Notes

• Windows NT 4.0, Service Pack 6 or later, TCP/IP protocol from Microsoft • 16 MB of disk space needed on system drive • Microsoft Internet Explorer 5.x or later 5.1.4 On Systems Running Windows 2000/XP The Cell Manager must meet the following minimum requirements:

• 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM are needed.

• Windows 2000, Service Pack 3 or later • Windows XP Professional, Service Pack 1 or later • 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) • 16 MB of disk space needed on system drive • Microsoft Internet Explorer 5.x or later 5.1.5 On Systems Running Windows Server 2003-32 bit The Cell Manager must meet the following minimum requirements:

• 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM are needed.

• 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) • 16 MB of disk space needed on system drive • Microsoft Internet Explorer 5.x or later

5.2 Installation Server Requirements 5.2.1 On Systems Running HP-UX The Installation Server must meet the following minimum requirements:

• 64 MB RAM • 340 MB of disk space 5.2.2 On Systems Running Solaris 7/8/9 The Installation Server must meet the following minimum requirements:

• 64 MB RAM • 380 MB of disk space

45

Data Protector A.05.10 Release Notes

5.2.3 On Systems Running Windows NT The Installation Server must meet the following minimum requirements:

• 64 MB RAM • 250 MB of disk space • Microsoft Windows NT 4.0 with Service Pack 6 • Microsoft Internet Explorer 5.x or later 5.2.4 On Systems Running Windows 2000/XP The Installation Server must meet the following minimum requirements:

• 64 MB RAM (Windows 2000 Professional) • 250 MB of disk space • Microsoft Windows 2000 Service Pack 3 or later • Windows XP Professional, Service Pack 1 or later • Microsoft Internet Explorer 5.x or later 5.2.5 On Systems Running Windows Server 2003-32 bit The Installation Server must meet the following minimum requirements:

• 64 MB RAM • 250 MB of disk space • Microsoft Internet Explorer 5.x or later

5.3 Client System Requirements 5.3.1 On Systems Running UNIX The prerequisites for UNIX user interface installation and remote installation on the client are:

• Netscape Navigator 4.7.x or Netscape Navigator 7.0 for Data Protector online help on UNIX • The inetd daemon must be up and running. The Web browser must be able to run under the same account as Data Protector. Disk space and RAM requirements of Data Protector UNIX clients The following table shows the minimum disk space and RAM requirements for the various Data Protector clients: Client System

RAM (MB)

Disk Space (MB)

User Interfacea

256b

150c

46

Data Protector A.05.10 Release Notes

Client System

RAM (MB)

Disk Space (MB)

Disk Agent

64 (recommended 128)

10

Media Agent

64 (recommended 128)

20

Integration Modules

64 (recommended 128)

15

a. The documentation ( .pdf files, 60MB) is included. b. The memory requirements for the GUI system vary significantly with the number of elements that need to be displayed at a time. This consideration applies to the worst case actual display which you want to view (like expanding a single directory). You do not need to consider the total of directories and file names on a client, unless you want to expand all directories while viewing.It has been shown that 2 MBytes memory are required per 1000 elements (directories or file names) to display plus a base need for about 50 MBytes. So the 256 MBytes of RAM are good to display about 100 000 file names. However, if you need to browse 400 000 different file names in a single directory (before restore) then you should have a GUI system with >850 MB. c. With regard to the disk space, keep in mind, the page file alone should be able to grow to about 3 times the physical memory. The figures indicate requirements from the agent only. For example the "disk space" figure does not include space allocation for the OS, page file or other applications. The Data Protector A.05.10 HP-UX and Solaris GUI are based on Windows emulation software and therefore require higher graphical processing power. It is recommended to use midrange (or higher) workstation system with considerable graphics power. Usage over dial-up line is not feasible. HP-UX Systems When installing or upgrading remotely, the available disk space in the folder /tmp should be at least the size of the biggest package being installed (HSLco40379). Solaris Systems When installing a Media Agent, make sure that the following entry is in the file /etc/system: set semsys:seminfo semmni=100 When installing or upgrading remotely, the available disk space in folders /tmp and /var/tmp should be at least the size of the biggest package being installed (HSLco40379). The Solaris installation CD-ROM is in the pkg stream format,which is not recognized by the standard tar utility. That is why the HP-UX, and not the Solaris installation CD-ROM must be used for the local installation/upgrade of Solaris clients.

5.3.2 On Systems Running Windows The prerequisites for Windows user interface installation and remote installation on the client are:

• Microsoft Windows NT 4.0 with Service Pack 6 • Microsoft Windows 2000 with Service Pack 2 • Windows XP Professional, Service Pack 1 or later • Have Microsoft Internet Explorer 5.0 or higher installed on the system.

47

Data Protector A.05.10 Release Notes

The following table shows the disk space and RAM requirements of Data Protector Windows clients: Client System

RAM (MB)

Disk Space (MB)

User Interfacea

256b

100c

Disk Agent

64 (recommended 128)

10

Media Agent

64 (recommended 128)

20

Integration Modules

64 (recommended 128)

15

a. the documentation (.pdf files) is always included. b. The memory requirements for the GUI system vary significantly with the number of elements that need to be displayed at a time. This consideration applies to the worst case actual display which you want to view (like expanding a single directory). You do not need to consider the total of directories and file names on a client, unless you want to expand all directories while viewing. It has been shown that 2 MBytes memory are required per 1000 elements (directories or file names) to display plus a base need for about 50 MBytes. So the 256 MBytes of RAM are good to display about 100 000 file names. However, if you need to browse 400 000 different file names in a single directory (before restore) then you should have a GUI system with >850 MB. c. With regard to the disk space, keep in mind, the page file alone should be able to grow to about 3 times the physical memory. The figures indicate requirements from the agent only. For example the "disk space" figure does not include space allocation for the OS, page file or other applications.

5.4 Java Web Reporting Java VM version 1.1 is required, and supported browsers are Netscape Navigator 4.7.x and Microsoft Internet Explorer 5.0 with Service Pack 1, or later. On the following web page you can obtain a plug-in that will update your previous Internet Explorer and Netscape Navigator browsers with Java VM with version 1.1 http://java.sun.com/products/plugin/.

5.5 Novell NetWare • Any Novell system that is part of a Data Protector cell must have TCP/IP version 3.1 or later installed. • Novell NetWare 4.2 must have the Support pack 9 or later installed. Novell NetWare 5.1 must have the Support pack 5or later installed. Novell NetWare 6.0 must have the Support pack 2 or later installed.

5.6 Local UNIX Client Installation UNIX clients are installed locally using the installation script omnisetup.sh. You can install the client locally from the HP-UX installation CD-ROM and import it to the Cell Manager using automated procedure. For the installation procedure refer to the HP OpenView Storage Data Protector Installation and Licensing Guide.

5.7 Upgrade The upgrade procedure to Data Protector A.05.10 from the its predecessor OmniBack II releases A.03.5x and A.04.x and from Data Protector A.05.00 is documented in the HP OpenView Storage Data Protector Installation and Licensing Guide. Upgrade from OmniBack II version A.03.10 or earlier is not supported. Please upgrade earlier releases of OmniBack II to OmniBack II A.03.50 and

48

Data Protector A.05.10 Release Notes

then upgrade to Data Protector A.05.10 following the procedure in the HP OpenView Storage Data Protector Installation and Licensing Guide. On Solaris, you can perform one-step upgrade from OmniBack II A.03.50 client, OmniBack II A.03.51 Cell Manager and Data Protector A.05.00 to Data Protector A.05.10. When upgrading both, HP-UX from 10.x to 11.x and from OmniBack II to Data Protector, you need first to remove OmniBack II, upgrade the operating system and then install Data Protector A.05.10.

5.8 Requirements for Data Protector Services on Windows Server 2003 Data Protector uses three services: OmniInet - Client backup service, CRS - Cell Server Service, and RDS - Cell Server Database Service. By default, OmniInet and RDS services are running under the Local System account, and CRS service is running under the Administrator's account. You can change the account information for any of these services. However, the following are minimum requirements that must be met by the new accounts: Service

Resource

Minimum resource permission required by service

RDS

\db40 HKLM\SOFTWARE\Hewlett-Packard\OpenView\OmnibackII

Full access Read

CRS

HKLM\SOFTWARE\Hewlett-Packard\OpenView\OmnibackII

Full access Full access

OmniInet

Backup and Restore Take Ownership

-

5.9 Files Installed in the%systemroot%\system32 Folder The following files are placed (depending on the components selected) into system32 folder on Windows systems: BrandChgUni.dll

This is a resource library. It is used only internally; however, it also contains the path to registry settings, so it must be located in a well-known location where it can be accessed by integration libraries.

libarm32.dll

This is a NULL shared library for ARM instrumentation. It will be replaced by third-party monitoring software.

ob2informix.dll

This library is used to integrate with the Informix database.

orasbt.dll

This library is used to integrate with the Oracle database.

snmpOB2.dll

This library is used to implement system SNMP traps.

49

Data Protector A.05.10 Release Notes

Chapter 6: Required Patches For Data Protector patches, please consult http://support.openview.hp.com/support.jsp for the latest information. For systems running Windows, contact the Microsoft Corporation for the latest Microsoft Windows Service Pack. For patches on systems running the HP-UX operating systems please consult http://www.software.hp.com/SUPPORT_PLUS/qpk.html for the latest information or check with the Response Center to get the current patch numbers. Install the latest patches before calling support. The Patches listed can be replaced with newer patches. We recommend that you regularly install the Extension Software Package delivered for HP-UX. This is a collection of recommended patches, some of which are listed below. Contact HP Support for the current version of the HP-UX Extension Software Package.

6.1 HP-UX 11.00 System Patches Required by Data Protector The following HP-UX 11.00 patch bundles are required by Data Protector: Service Pack

Bundle Name

Description

SP58-11.00 (or later)

QPK1100

Current patch bundle for HP-UX 11.00

The following HP-UX 11.00 individual patches are recommended by Data Protector in addition to the patch bundle from the table above: Patch Name

Hardware Platform

Description

PHCO_24645

s700_800

LVM commands cumulative patch

PHCO_25707

s700_800

libc cumulative patch

PHKL_22170

s700_800

JFS 3.3 fix mount(2), umount & fs_size probs

PHKL_25613

s700_800

IDS/9000; syscalls related to file/socket

PHKL_27178

s700_800

LVM Cumulative Patch w/Performance Upgrades

PHNE_26551

s700_800

HyperFabric B.11.00.0[0-12] cumulative patch

PHSS_14982

s700_800

PDCINFO patch Version A.02.24

PHSS_17496

s700_800

Predictive C.11.0[0,a-m] cumulative patch

PHSS_26262

s700_800

ld(1) and linker tools cumulative patch

PHSS_26270

s700_800

MC/SG & SG-OPS Edition A.11.12

PHSS_26338

s700_800

MC/SG & SG-OPS Edition A.11.09

50

Data Protector A.05.10 Release Notes

6.2 HP-UX 11.11 System Patches Required by Data Protector The following HP-UX 11.11 patch bundles are required by Data Protector: Service Pack

Bundle Name

Description

SP0206-11.11 (or later)

GOLDQPK11i

Current patch bundle for HP-UX 11.11

SP0206-11.11 (or later)

HWEnable11i

Required hardware enablement patches

The following HP-UX 11.11 individual patches are recommended are recommended to be installed on any Data Protector system. Patch Name

Hardware Platform

Description

use latest

s700_800

LVM commands cumulative patch (successor of PHCO_27913)

PHKL_26743

s700_800

LVM Cumulative Patch

PHKL_26785

s700_800

SCSI Tape (stape) cumulative

PHSS_26946

s700_800

HP aC++-AA runtime libraries (aCC A.03.33)

PHSS_27858

s700_800

V EMANATE14.2 Agent Consolidated Patch

use latest

s700_800

MC/Service Guard patches for the version you use

6.3 System Patches for the Data Protector GUI on HP-UX The following HP-UX individual patches are highly recommended for Data Protector GUI clients: Patch Name

Hardware Platform

Operating System

Description

PHCO_25707

s700_800

11.00

libc cumulative patch

PHKL_27351

s700_800

11.00

creat(2) ENOENT, syscall, signal, umask

PHKL_27364

s700_800

11.00

Probe,IDDS,PM,VM,PA-8700,asyncio,T600,Hang

PHNE_26387

s700_800

11.00

ONC/NFS General Release/Performance Patch

PHSS_26262

s700_800

11.00

ld(1) and linker tools cumulative patch

6.4 System Patches Required by MPE/iX System Operating System

Description

MPE/iX 6.0 system

PowerPatch II, TurboStore/iX's patch MPELXC2C (C.60.23)

MPE/iX 6.5 system

PowerPatch I, TurboStore/iX's patch MPELXG2A (C.65.13)

51

Data Protector A.05.10 Release Notes

Operating System

Description

MPE/iX 7.0 system

PowerPatch I

6.5 Solaris System Patches Required by Data Protector Solaris 7 Recommended Patch Cluster is required by Data Protector GUI on Solaris. Operating System Patch: Use the latest kernel patch from Sun Microsystems. Sun provides patch information at: http://sunsolve.sun.com.

6.6 Novell NetWare Patches Required by Data Protector Use the latest recommended patches on Novell NetWare clients:

• the latest filesystem patch (NSS) • TSAx.NLM patches • the latest Support Pack See patch information at Novell NetWare Web page: http://support.novell.com.

52

Data Protector A.05.10 Release Notes

Chapter 7: Obsolete Platforms and Integrations in Data Protector A.05.10 The relevant version information regarding supported platforms is in the support matrices (see Appendix C). The information in this chapter is provided for your convenience but may be not exhaustive.

7.1 Obsolete Platforms The following operating systems are no longer supported in the Data Protector A.05.10:

• HP-UX 10.20 Data Protector Disk Agent is no longer supported on the following systems:

• Windows 95 • NCR • Dynix

7.2 Obsolete Integrations The following integrations are no longer supported in the Data Protector A.05.10

• Data Protector integration with Oracle 7.x • Data Protector integration with Fastrax • Data Protector integration with Sybase Replication Server versions 11.5 and 11.5.1 • Data Protector integration with Sybase Adaptive Server Enterprise version 11.9.2

53

Data Protector A.05.10 Release Notes

Chapter 8: Data Protector Documentation 8.1 Location of Documentation Data Protector manuals are available in printed format and in PDF format. Install the PDF files during the Data Protector setup procedure by selecting the User Interface component on Windows or the OB2-DOCS component on UNIX. Once installed, the manuals reside in the \docs directory on Windows and in the /opt/omni/doc/C/ directory on UNIX. You can also find the manuals in PDF format at http://ovweb.external.hp.com/lpe/doc_serv/ Additional the following file is provided:

• A spreadsheet to estimate the size of the IDB, IDB_capacity_planning.xls The support matrices can be found at the mentioned locations in the sub-directory support_matrices. Adobe Acrobat Readers for Windows (English) and for HP-UX (English) are available at Windows®-CD:\Adobe. For any other version please refer to http://www.adobe.com.

8.2 Printed Documentation The Data Protector printed documentation set consists of the following manuals: HP OpenView Storage Data Protector Administrator’s Guide This manual describes typical configuration and administration tasks performed by a backup administrator, such as device configuration, media management, configuring a backup, and restoring data. HP OpenView Storage Data Protector Installation and Licensing Guide This manual describes how to install the Data Protector software, taking into account the operating system and architecture of your environment. This manual also gives details on how to upgrade Data Protector, as well as how to obtain the proper licenses for your environment. HP OpenView Storage Data Protector Integration Guide This manual describes how to configure and use Data Protector to back up and restore various databases and applications. There are two versions of this manual:

• HP OpenView Storage Data Protector Windows Integration Guide This manual describes integrations running the Windows operating systems, such as Microsoft Exchange, Microsoft SQL, Oracle, SAP R/3, Informix, Sybase, NetApp Filer, HP OpenView Network Node Manager, and Lotus Domino R5 Server.

• HP OpenView Storage Data Protector UNIX Integration Guide This manual describes integrations running on the UNIX operating system, such as Oracle, SAP R/3, Informix, Sybase, NetApp Filer, IBM DB2 UDB, HP OpenView Network Node Manager, and Lotus Domino R5 Server. HP OpenView Storage Data Protector Concepts Guide This manual describes Data Protector concepts and provides background information on how Data Protector works. It is intended to be used with the task-oriented HP OpenView Storage Data Protector Administrator’s Guide. HP OpenView Storage Data Protector EMC Symmetrix Integration Guide This manual describes how to install, configure, and use the EMC Symmetrix integration. It is intended for backup administrators or operators.

54

Data Protector A.05.10 Release Notes

It describes the integration of Data Protector with the EMC Symmetrix Remote Data Facility and TimeFinder features for Symmetrix Integrated Cached Disk Arrays. It covers the backup and restore of file systems and disk images, as well as online databases, such as Oracle and SAP R/3. HP OpenView Storage Data Protector HP StorageWorks Disk Array XP Integration Guide This manual describes how to install, configure, and use the integration of Data Protector with HP StorageWorks Disk Array XP. It is intended for backup administrators or operators. It covers the backup and restore of Oracle, SAP R/3, Microsoft Exchange, and Microsoft SQL. HP OpenView Storage Data Protector EVA/VA/MSA Integration Guide This manual describes how to install, configure, and use the integration of Data Protector with HP StorageWorks Virtual Array, HP StorageWorks Enterprise Virtual Array or HP StorageWorks Modular SAN Array 1000. It is intended for backup administrators or operators. It covers the backup and restore of Oracle, SAP R/3, Microsoft Exchange, and Microsoft SQL. HP OpenView Storage Data Protector Integration Guide for HP OpenView This manual describes how to install, configure, and use the integration of Data Protector with HP OpenView Service Information Portal, HP OpenView Service Desk, and HP OpenView Reporter. It is intended for backup administrators. It discusses how to use the OpenView applications for Data Protector service management. HP OpenView Storage Data Protector MPE/iX System User Guide This manual describes how to install and configure MPE/iX clients, and how to back up and restore MPE/iX data. HP OpenView Storage Data Protector Integration Guide for HP OpenView Operations This manual describes how to monitor and manage the health and performance of the Data Protector environment with HP OpenView Operations (OVO), HP OpenView Service Navigator, and HP OpenView Performance (OVP). HP OpenView Storage Data Protector Software Release Notes This manual gives a description of new features of HP OpenView Storage Data Protector A.05.10. It also provides information on supported configurations (devices, platforms and online database integrations, SAN, and ZDB), required patches, and limitations, as well as known problems and workarounds. An updated version of the supported configurations is available at http://www.openview.hp.com/products/datapro/spec_0001.html.

8.3 Online Help Data Protector provides context-sensitive (F1) help and Help Topics for Windows and UNIX platforms.

8.4 Localization Data Protector provides the localization to the Japanese and French languages for the online Help. The following manuals are localized into Japanese:

• HP OpenView Storage Data Protector Installation and Licensing Guide • HP OpenView Storage Data Protector Concepts Guide • HP OpenView Storage Data Protector Administrator’s Guide • HP OpenView Storage Data Protector Windows Integration Guide • HP OpenView Storage Data Protector UNIX Integration Guide 55

Data Protector A.05.10 Release Notes

• HP OpenView Storage Data Protector Software Release Notes The following manuals are localized into French:

• HP OpenView Storage Data Protector Installation and Licensing Guide • HP OpenView Storage Data Protector Concepts Guide

56

Data Protector A.05.10 Release Notes

Appendix A: List of Enhancements and Defects Fixed in Data Protector A.05.10 A.1 List of Enhancements Implemented SR ID

Headline

ID

H555006925

Duplicate tapes in database, same barcode same location

HSLco31867

8606112602

Cannot specify different media for restore w/ NT GUI

JAGab84945

8606135270

Warning msg when attempt "restore as" of file to an existing directory

JAGad04404

8606171785

cannot make disaster recovery with RAID-5

JAGad41049

8606181579

remote connect to CS via NT-GUI is not showing the installed Patch-Level

JAGad50795

8606182014

request for a better controlled software compression

JAGad51230

8606203550

Backup of very big files in other platforms like (SGI, NT, Novell. etc)

JAGad72723

8606223084

All disks are visible on all nodes in Windows 2000Cluster with Veritas VM

JAGad92187

8606223669

Please implement backup of files >2GB on Linux 6.x and 7.x platform

JAGad92765

8606223709

Link to Online Support and Services requested

JAGad92805

8606224760

omnisv cannot be started by non-root user

JAGad93848

8606225773

OB limitation in Solaris doing raw backups.

JAGad94846

8606230896

Sync messages of SSEA fills up the session report/OBII database

JAGae00134

8606234312

require omnimcopy protection to work as documented

JAGae03532

8606245285

cu wants OB RMAN integration interface to be used without RMAN knowledge

JAGae11758

8606248339

Please add "CopyDeleteSave" template on SAP integration.

JAGae14739

8606249379

Additional information requested for Omniback error messages

JAGae15771

8606250282

CU needs special omnirc parameter for Solaris BC

JAGae16657

8606252833

mbxcopy doesn't work multi threaded.

JAGae17900

8606260363

some Environment Variables not usable for objects

JAGae24686

57

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

8606268255

Add option to set protection with omnimcopy

JAGae32494

8606276784

Filesystem objects do not back up in the specified order Dynamically

JAGae40859

A.2 List of Defects Resolved SR ID

Headline

ID

H555006782

Omniback does not detect failure of brbackup

HSLco31227

H555006990

Catalog dump failing after appending data segment

HSLco32238

H555007123

Exchange 2000 does not go through hard recovery

HSLco32626

H555007210

rman core dumps due to missing OmniBack objects

HSLco32861

H555007500

Restored MAC files displayed incorrectly in GUI

HSLco33547

H555007501

Customer needs Netware patch with all fixes

HSLco33551

H555007901

OB2PORTRANGE not working after applying latest OB2 patches

HSLco34427

H555008105

Number of devices specified is smaller than MIN

HSLco34785

H555008141

Pre-exec split launched under shell or sh -c type

HSLco34841

H555008377

Calculated volume of data backed up is inconsistent in 4.10

HSLco35273

H555008403

[Warning] From: VRDA@.... File cannot be replaced!

HSLco35346

H555008410

Device locking not working properly

HSLco35364

H555008425

Unable to restore SQL database with large number of .ldf files

HSLco35430

H555008436

SNAPA-R1 agent core dumps and BSM finally shuts down 7200 seconds later

HSLco35468

H555008452

BSM does not terminate after SmDaIdleTimeout when DA failover.

HSLco35515

H555008466

Media header sanity check lost in OMNIBACK_00056

HSLco35557

H555008478

Unable to run two Oracle backups together

HSLco35615

H555008483

Omniback starts second session after backup aborted

HSLco35646

H555008493

Logical devices are not locked

HSLco35664

H555008496

Urgent request to change false message for header check

HSLco35670

58

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

H555008504

fails to eject tape in mailslot

HSLco35704

H555008533

Informix backups hang.

HSLco35783

H555008538

VA (snapa) integration not working when PVG are configured

HSLco35801

H555008559

Oracle8 barlist corrupt after adding line

HSLco35943

H555008565

problem with util_sap.exe

HSLco35966

H555008573

SSEA reports (Raid Manager LIB Error: [2]

HSLco35984

H555008577

[223:327] SYMA-R2 Could not mount filesystem ...

HSLco36009

H555008599

Command "/usr/bin/pairresync -g" failed with exit code 242

HSLco36105

H555008604

VA Integration: Resolve takes too long on backup host

HSLco36130

H555008606

[61:1002] The Snapshot Agent reached its inactivity timeout of 7200s

HSLco36132

H555008610

How should we see the EW EOM on Solaris?

HSLco36147

H555008634

Omniback does not unload the tape at end of backup

HSLco36329

H555008639

The Kanji "month" sign not displayed in OB 4.XX

HSLco36395

H555008641

Update of client results in drWatson

HSLco36403

H555008642

BR247E No Backup utility ID or ID longer than 16 characters

HSLco36404

H555008644

Need correct binary for ssea agent for 4.10

HSLco36407

H555008648

Devbra fails detecting tape devices in san setup

HSLco36419

H555008649

change backupset 1156 delete fails to complete

HSLco36422

H555008651

When other job running and upgrading NT client CRS dies on HPUX

HSLco36460

H555008655

File device with FileMediaCapacity=4000 fails at 2Giga

HSLco36472

H555008656

Search for backup logical volume failed

HSLco36476

H555008658

HOST backup does not send magic packet to wake client

HSLco36489

H555008662

Backup of Net App filer with NDMP integration hangs

HSLco36532

H555008665

backint does not find latest version of file

HSLco36560

H555008667

Expecting new option when parsing string "20".

HSLco36565

H555008680

MSM goes into a loop when Cartridge Memory Support is enabled

HSLco36656

59

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

H555008685

resolve of BC copy on Backup Host takes a long time - ScsiInquiryXp loop

HSLco36669

H555008686

Scheduled Exchange backups do not start

HSLco36696

H555008691

Unable to backup Lotus Notes file with strange characters.

HSLco36730

H555008704

tape which is a copy to retain permanent protection in the DCBF

HSLco36772

H555008729

NDMP limitation checkup list

HSLco36902

H555008730

xomnimm error/abort when loading large device or pool content

HSLco36904

H555008740

problems using tapes on second backup no error message

HSLco36934

H555008743

ssea hangs launching post-exec script

HSLco36942

H555008776

XP lvm_mirror +BC backup failing when one of the XP does not have BC license

HSLco37090

H555008778

Could not activate volume group /dev/vgBWP_bwpd2.

HSLco37092

H555008779

Notifications run script anywhere with ExternalMode=1

HSLco37094

H555008812

saprest reports "Error: Cannot open object" for raw restore

HSLco37210

H555008825

Lost connection to VBDA named

HSLco37252

H555008826

RMA doesn't position tape to the correct location

HSLco37256

H555008870

PATH not set in /opt/omni/acs/ssi.sh

HSLco37582

H555008873

Restore of MAC files results in namespace LONG

HSLco37601

H555008887

SSEA-R1/R2 connection times out while SSEA-R1 in SmbEventLoop()

HSLco37704

H555008908

Need fix for defect ID JAGad76196

HSLco37783

H555008950

cdbsync started on MOM clients deletes the CDB

HSLco37977

H555008958

Lost connection to Monitor named "noname"

HSLco37991

H555008977

Need a rm -f /var/opt/omni/tmp/smb.$$ added to smb_common.sh

HSLco38032

H555009008

Host backup restore from nested directories

HSLco38099

H555009017

Mount request causes second object to start first

HSLco38123

H555009030

License not available "ZD Backup Extension for ONE HP Surestore XP

HSLco38197

H555009095

"Invalid slot specified.

HSLco38412

H555009096

Auditing information lost

HSLco38414

60

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

H555009101

Read capacity command failing although OK in HP-UX

HSLco38420

H555009116

sapback.exe generates Exception number: c0000005 (access violation)

HSLco38454

H555009141

Cannot read ACLs: ([13] Permission denied).

HSLco38494

H555009153

Restore over NDMP says 3 Gb restored with actually 36 Gb was restored

HSLco38516

H555009158

Split pre-/post-exec exit -1: SystemErr: [109] The pipe has been ended.

HSLco38536

H555009194

Use/total blocks reported as large negative integer for LTO tapes

HSLco38751

H555009209

device locking broken

HSLco38804

H555009216

RMAN-00558: error encountered while parsing input commands

HSLco38855

H555009249

Internal error in ("da/rda/alpha.c /main/r41/1":236) => process aborted

HSLco39001

H555009253

Multiple Media Agent Related problems

HSLco39011

H555009263

writedb is creating corrupted ascii files

HSLco39036

H555009270

ABORTED SSEA-Backup Agent on ucps0101.ussb.astrazeneca.net.

HSLco39063

H555009273

bulk eject on netware not supported

HSLco39082

H555009274

DP does not abort the MA if scsi bridge is set to off

HSLco39083

H555009288

[SseXPairVolStat] pairvolstat failed! No such LDEV in the RAID.

HSLco39133

H555009291

OMNI_HOSTS causes Oracle8(64bits) backup to fail

HSLco39136

H555009298

SQL Backups Hang during large Transaction Loads

HSLco39173

H555009315

SAN+PHSS_27459 MA drops off with EBUSY when heavy SAN activity

HSLco39232

H555009322

SystemErr: [10054] Connection reset by peer

HSLco39260

H555009404

Debug mode is breaking Informix restore GUI

HSLco39486

H555009414

81:80 "cannot preserve time attributes

HSLco39503

H555009415

OB2BAR appears to die during Oracle 8 restore

HSLco39504

H555009424

Media copy aborting when any Console on cell manager is closed.

HSLco39523

H555009425

File corrupted on restore

HSLco39524

H555009450

MPE restore to different volumeset does not seem to work.

HSLco39571

H555009456

[SseReportBCPairs] SseXPairVolStat failed!

HSLco39583

61

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

H555009548

NDMP: Command aborted

HSLco39850

H555009567

Database corrupted but unable to find corruption

HSLco39885

H555009570

GUI does not allow blank hostname for local exec script - CLOSED

HSLco39892

H555009573

OB4.1 XP512 Instant Recovery fail - incorrect reporting ldev as simplex

HSLco39896

H555009600

SM/DA protocol error => aborting

HSLco39994

H555009621

/etc/hosts entry showing up from util_cmd command

HSLco40059

H555009625

Resolve on R2 failing with PHSS_27597; also line limit in vgimport

HSLco40093

H555009630

During Restore: Cannot open device (The medium is Write Protected.)

HSLco40131

H555009675

cmmdb merge does not work

HSLco40228

H555009678

Customer can not configure, use sanconf for a MSL5026

HSLco40232

H555009718

Cannot get VxFS filesystem options ([25] Not a typewriter)

HSLco40333

H555009779

bsm from SSPUX410_056 never completes with omniabort

HSLco40396

H555009806

ADIC SCALAR library fails mode sense command

HSLco40423

H555009833

'Unable to read a page in ReadPage' error in RDS.log; RDS aborts

HSLco40471

H555009859

OB2ACS_VOLUMEDRIVE_POOR=1 does not mark ACS tapes "Poor

HSLco40523

H555009863

OB2IPCBUFSIZE variable needs to be implemented for SSEA

HSLco40537

H555009880

Magstar 3590 is not supported in the OB GUI

HSLco40563

H555009895

omnidbutil -cdbsync fails on non-MoM environment

HSLco40594

H555009900

BC backup of VA7410 fails with unknown internal error

HSLco40601

H555009911

[Major] From: BMA-DAS...Cannot unload drive ..[d_errno=31] things don't

HSLco40624

H555009941

[61:1002] OB2BAR restore DA ... reached its inactivity timeout of 7200 s

HSLco40709

H555009973

ON-Bar restore failed with exit status 141

HSLco40768

H555010030

unable to solve SIBF corruptions

HSLco40877

H555010233

Not possible to browse MS Cluster shared disk nested mountpoints

HSLco41262

H555010278

Error has occurred while executing a SQL statement

HSLco41398

62

Data Protector A.05.10 Release Notes

SR ID

Headline

ID

8606228982

xomni is NOT a well-behaved X window client

JAGad98036

8606245960

OB4.10GUI doesn't display exclude statements for filesystem backup

JAGae12418

8606261787

search interval displayed by gui

JAGae26106

8606262839

Error in GUI configuring a report of type "lookup_sch".

JAGae27169

8606271949

Add option to list exchange 2000 objects in omnidb -MSESE

JAGae36127

8606280024

The report "extended report on used media" is not working.

JAGae43999

8606284961

/opt/omni/lbin/.util defect doing swlist OMNIBACK-II

JAGae48903

8606293108

SuperDLT Quantum 320 is reported as supported but is missing on scsitab

JAGae56858

B555014057

Customer can not restore data in a single session.

NSMbb45777

63

Data Protector A.05.10 Release Notes

Appendix B: Non-ASCII Characters in Filenames Appendix B.1 Non-ASCII Characters in Filenames B.1.1 Full Support for Filenames Containing Only 7-bit ASCII Characters Filenames consisting of 7 bit ASCII characters only are fully supported for all combinations of platforms for all components involved (Cell Manager, Client, GUI). If filenames contain one or more characters other than plain 7 bit ASCII, certain limitations apply.

B.1.2 File Content The content of the files is not affected or processed in any way. This is completely independent from how the filenames are processed. When a file is backed up and restored, the byte sequence of the file body is retained.

B.1.3 Media Agent Can Run on Any Platform Handling of the filenames is not affected by the Media Agent platform.

B.1.4 Specifying a Tree for Backup or a File for a Single File Restore When Data Protector conveys the information about selected trees (or files), this information is transferred between Data Protector components, for example at restore time from the GUI to the Cell Manager and from the Cell Manager to the Client. When these components are on different platforms, some information can be lost or altered because of the conversions from Unicode to SBCS or DBCS, or vice versa. When this happens, the Disk Agent is not able to match the specified tree with the directory name or filename on the tape (or on the disk in case of a backup). The same restrictions apply also for exclude, skip and only specifications. Whether or not a filename is displayed correctly is not in direct correlation with the ability to successfully specify it for a backup or a restore. Refer to “Further Limitations” on page 69 for problematic situations and corresponding workarounds. For restores, when in doubt, you are encouraged to restore one tree/file per restore session. A message "Nothing restored" will give you a clear indication that the tree was not restored. There are other possible reasons, for example if default File Conflict Handling is used (Keep most recent) this message may also indicate that the files are already on the disk and were not overwritten, however Restore Into would restore the files into the specified path. When only few files are restored you may also use the List restored data option. B.1.4.1 All Files Within a Successfully Specified Tree are Backed Up Regardless of what type of characters filenames contain, they are always backed up and restored, provided that they are within a tree that is successfully specified for a backup or a restore. For example, if you back up or restore an entire disk, all files will be backed up or restored.

B.1.5 Standard Workaround for Trees That Cannot be Specified The standard workaround is to select a tree above the desired tree, assuming that this parent tree is one that can be successfully specified (for example, its name consists of ASCII characters only). For backups, this means that more data will be backed up. This is usually not an issue since typically entire disks or at least major trees are backed up (for example /home or \My Documents).

64

Data Protector A.05.10 Release Notes

For restores, you can choose to restore the parent tree to a new location, using the restore as or restore into option, to prevent any damage by restoring more than just the desired file or directory.

B.1.6 Tables of Limitations The following tables deal primarily with how filenames with non-ASCII characters are handled in Data Protector GUI. Refer also to the “Further Limitations” on page 69 at the end of this appendix. B.1.6.1 How to Read the Tables First, determine the platform on which your Cell Manager is running. This leaves you with two tables, one for limitations when having the GUI on UNIX and one for limitations when having the GUI on Windows NT, Windows 2000, or Windows XP. There are separate code page groups as columns for various language settings. You should only observe one group at a time. If all systems in a cell have the same language settings, then only one group applies and you can disregard the others. A check mark (3) indicates that no problems are expected for that particular operation on clients of that platform. If there is a remark beside the check mark, it means that problems may occur in some situations. Check the table footnotes for description of that problem. A cross mark (7 ) indicates that operation will most likely fail on clients of that platform. Check the table footnotes for workarounds. The language setting itself does not mean that operation will fail. A failure (cannot see filename properly or cannot restore a single file) only occurs for filenames that actually contain characters from that code page. The language setting of the Cell Manager system itself (for example, the account under which the Data Protector CRS process is running) is not relevant in this context. B.1.6.2 Code Page Groups

• Latin 1 (Western Europe): CP1252 on Windows, CP850 on Netware, ISO 8859 1 (Latin 1) on UNIX

• Latin 2, Hebrew, EUC-JP, ... Other code pages, for example: CP1250 on Windows, CP852 on Netware, ISO 8859 2 (Latin 2) on UNIX, or CP1255 on Windows, CP862 on Netware, ISO 8859 8 (Hebrew) on UNIX EUC code pages on UNIX (See table footnotes for specifics regarding correct display of the filenames when using Windows GUI.)

• Shift-JIS (Japanese) Code page 932 on all platforms B.1.6.3 Mixed Language Environments If not all systems in the cell have the same language settings, then the respective portion of the table will only be valid if the language settings on the GUI client are the same as the language settings of the client system that is being configured for backup or restore. On Netware and Windows 98/ME systems, language setting is a property of the system. On UNIX clients, consider the "system's language setting" to be the language setting used to create the filenames.

65

Data Protector A.05.10 Release Notes

B.1.6.4 Cell Manager on Windows, GUI on Windows NT, Windows 2000 or Windows XP Code page group 4

Latin 1

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

Shift-JIS (Japanese)

UNIX

Client (Disk Agent) platform

Latin 2, Hebrew, EUC-JP,...

Files within a tree are backed up

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

Filenames are displayed correctly in backup pane

✓5

✓5

✓

✓

✓5

✓5

✗2

✓

✓7

✓7

✗2

✓

Tree/File can be specified for backup

✓

✓

✓

✓

✓

✓

✓

✓

✓7

✓7

✓7

✓

Filenames are displayed correctly in restore pane

✓5

✓5

✓

✓

✓5

✓5

✓

✓

✓7

✓7

✓7

✓

Tree/File can be specified for restore

✓

✓

✓

✓

✓

✓

✗3

✓

✓7

✓7

✗3

✓

B.1.6.5 Cell Manager on Windows, GUI on UNIX Code page group 4

Latin 1

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

Shift-JIS (Japanese)

UNIX

Client (Disk Agent) platform

Latin 2, Hebrew, EUC-JP,...

Files within a tree are backed up

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

Filenames are displayed correctly in backup pane

✓

✗6

✓

✓

✓

✗6

✓

✗1

✓7

✓7

✓7

✗1

Tree/File can be specified for backup

✓

✓

✓

✓

✓

✓

✓

✗1

✓7

✓7

✓7

✗1

Filenames are displayed correctly in restore pane

✓

✗6

✓

✓

✓

✗1

✗1

✗

✓7

✓7

✗1

✗1

Tree/File can be specified for restore

✓

✓

✓

✓

✓

✓

✗1

✗1

✓7

✓7

✗1

✗1

66

1

Data Protector A.05.10 Release Notes

2.1.7. Cell Manager on UNIX, GUI on Windows NT, Windows 2000 or Windows XP Code page group 4

Latin 1

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

Shift-JIS (Japanese)

UNIX

Client (Disk Agent) platform

Latin 2, Hebrew, EUC-JP,...

Files within a tree are backed up

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

Filenames are displayed correctly in backup pane

✓5

✓5

✓

✓

✓5

✓5

✗2

✗1

✓7

✓7

✗2

✗1

Tree/File can be specified for backup

✓

✓

✓

✓

✓

✓

✓

✗1

✓7

✓7

✓7

✗1

Filenames are displayed correctly in restore pane

✓5

✓5

✓

✓

✓5

✓5

✗1

✗1

✓7

✓7

✗1

✗1

Tree/File can be specified for restore

✓

✓

✓

✓

✓

✓

✗1

✗1

✓7

✓7

✗1

✗1

2.1.8. Cell Manager on UNIX, GUI on UNIX Code page group 4

Latin 1

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

UNIX

Netware

Windows 98 Windows ME

Windows NT Windows 2000 Windows XP

Shift-JIS (Japanese)

UNIX

Client (Disk Agent) platform

Latin 2, Hebrew, EUC-JP,...

Files within a tree are backed up

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

Filenames are displayed correctly in backup pane

✓

✗6

✓

✓

✓

✗6

✓

✗1

✓7

✓7

✓7

✗1

Tree/File can be specified for backup

✓

✓

✓

✓

✓

✓

✓

✗1

✓7

✓7

✓7

✗1

Filenames are displayed correctly in restore pane

✓

✗6

✓

✓

✓

✗6

✗1

✗1

✓7

✓7

✗

✗1

Tree/File can be specified for restore

✓

✓

✓

✓

✓

✓

✗1

✗1

✓7

✓7

✗1

67

1

✗1

Data Protector A.05.10 Release Notes

Legend 1.

Non-ASCII characters other than those from the Latin 1 code page are displayed as underscores if the GUI and/or the Cell Manager is on UNIX. When any character in a filename is replaced with an underscore, it is not possible to successfully specify that filename for a backup or a restore. Workaround: Standard workaround only, see “Standard Workaround for Trees That Cannot be Specified” on page 64. Standard workaround for trees that cannot be specified for more information.

2.

Non-ASCII characters in filenames of Windows 98/ME clients are not displayed correctly in the backup context of Windows GUI, except for clients configured for Latin 1 code page. Workaround: For simple backup specifications this is usually not an issue, because entire disks are usually backed up, or trees that are backed up have names containing only ASCII characters. Alternatively you can use GUI on a UNIX client or on a Windows 98/ME client to configure backups of such clients.

3.

Although all filenames are displayed correctly for Windows 98/ME clients in the restore context of Windows GUI, it is not possible to specify them for restore, except for clients configured for Latin 1 code page. Workaround 1: For standard workaround see “Standard Workaround for Trees That Cannot be Specified” on page 64 for more information. Workaround 2: Restore the desired file/directory to a Windows NT, Windows 2000, or Windows XP client and then copy the files to the Windows 98/ME system.

4.

It is assumed that the GUI client and the client for which you are configuring backup or restore are using the same language (code page) settings. Check the “Mixed Language Environments” on page 65 for details.

5.

In the Windows GUI, files on UNIX clients will only be displayed correctly if an appropriate ISO code page is used. Further problems arise from the differences between ISO and Windows code pages. See Appendix B.1.9.3, “ISO vs. Windows Code Pages,” on page 69. Files on NetWare clients will typically not be displayed correctly since NetWare clients use DOS code pages. In this situation the incorrect display does not mean that the files/directories cannot be successfully specified for a backup or a restore. If only some of the characters in the filenames are not displayed correctly, you may be able to determine the desired file. To change the encoding that is used to display the filenames in the tree view, use the View->Encoding menu. Use Default OEM to use the DOS code page that corresponds to your language settings. Use No Conversion for Windows clients. The six predefined code pages can be customized in registry at the following location: HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\OpenView\OmniBack II\GUI\Core Note, that for some code pages an appropriate language pack needs to be installed. Otherwise, the Menu item for that code page will be disabled.

6.

Assuming ISO code pages are used on UNIX systems, filenames of NetWare clients are not displayed correctly since Netware clients use DOS code pages. In this case this does not mean that the files/directories cannot be successfully specified for a backup or a restore. If only some of the characters in the filenames are not displayed correctly, you may be able to determine the desired file. However, for certain languages (Hebrew for example), you will probably need to use the workaround. Workaround: Use GUI on a Windows NT, Windows 2000, or Windows XP client.

7.

Japanese characters where the second byte of a double byte character is a backslash (\) are NOT handled properly. Filenames containing these characters are not displayed correctly and also cannot be successfully specified for a backup or a restore. Workaround: Standard workaround only, see “Standard Workaround for Trees That Cannot be Specified” on page 64 for more information.

68

Data Protector A.05.10 Release Notes

B.1.9 Further Limitations B.1.9.1 Filenames in Restore by Query In Windows GUI, Data Protector adjusts the display of filenames depending on user's language settings and the target system platform. Internal representation of the filenames can differ significantly. The search for a filename may fail because of this. The workaround is to specify wildcards ('?') for any non-ASCII character in the filename you are searching for. This limitation does not apply to files backed up from Windows NT, Windows 2000, and Windows XP clients. B.1.9.2 Filenames in Windows CLI When using Data Protector CLI on a Windows client to manage backups of other platforms, the filenames will only be displayed correctly for code page 1252. Characters from other code pages will appear corrupted. Even though a filename appears corrupted in the CLI it will be backed up or restored properly. Data Protector II CLI expects such "corrupted" filenames as input parameters. Workaround 1: Use copy-paste to exchange the "corrupted" filename from one command to another. Workaround 2: Use the CLI on UNIX where you can adjust the display of the filenames using the locale settings. B.1.9.3 ISO vs. Windows Code Pages There are some minor differences between implementations of code pages in Windows and in UNIX operating systems. This can result in some characters not being mapped correctly if the GUI is not run on the same platform as the client being configured. In most cases, only a few characters will be displayed incorrectly and this should not prevent the user from successfully specifying those filenames for a backup or a restore. There are noticeable differences in Latin 2 code pages (Central Europe), while in other code pages the differences occur mostly for characters that are not commonly used in filenames. B.1.9.4 Restoring to Another System When files backed up on one system are restored to another system, filenames are guaranteed to remain unchanged only if both systems are of the same platform family and have the same language settings. Some combinations of systems are less vulnerable to this type of problems. For example, Windows NT, Windows 2000, and Windows XP systems use Unicode and therefore the language settings are not relevant when only those systems are involved. Also, restoring files backed up on a Windows 98/ME system can always be restored to a Windows NT, Windows 2000, or Windows XP client and the filenames will restore properly. B.1.9.5 Filenames With Non-ASCII Characters After Upgrade This note only applies if you are upgrading to Data Protector release from OmniBack II releases prior to OmniBack II A.04.00. Filenames (containing non-ASCII character) in UNIX and Netware objects are affected. When backups of these objects are performed after the upgrade, the problematic filenames will be stored to the database in the new format and will appear next to the old filenames when browsing filenames. The old filenames may appear corrupted, or will be displayed correctly and will look like duplicates. Check the properties and determine the file/directory you wish to restore by examining the backup version. In most cases it is not possible to specify the files from the old versions for a restore and only the standard workaround can be used.

69

Data Protector A.05.10 Release Notes

Appendix C: Support Matrices The support matrices can also be found on any Data Protector CD in the \DOCS directory. The following support matrices are available in the Adobe Acrobat format: HP OpenView Storage Data Protector A.05.10 Supported Platforms and Integrations HP OpenView Storage Data Protector A.05.10 Supported Devices HP OpenView Storage Data Protector A.05.10 Split-mirror Backup for HP StorageWorks Disk Array HP OpenView Storage Data Protector A.05.10 Zero Downtime Backup for HP Virtual Array HP OpenView Storage Data Protector A.05.10 Zero Downtime Backup for HP Enterprise Virtual Array HP OpenView Storage Data Protector A.05.10 EMC Split-mirror Backup Integration HP OpenView Storage Data Protector A.05.10 Disaster Recovery Support Matrix HP OpenView Storage Data Protector A.05.10 Supported Devices and SAN Solutions HP OpenView Storage Data Protector A.05.10 Fibre Channel SAN Support Matrix For the latest list of support matrices on the Web, please refer to: http://www.openview.hp.com/products/datapro/spec_0001.html

70