Readme
Release 10.3
E14817-06
September 2010
This Readme applies only to Oracle Secure Backup release 10.3.0.3.0. This Readme documents licensing, supported platforms and devices, and known and fixed issues.
For documentation, use your Web browser to access the Oracle Secure Backup documentation library. The library home page is named welcome.html and is located at the top level of your CD-ROM image.
The most current Oracle Secure Backup documentation can be found at http://www.oracle.com/technetwork/database/secure-backup/documentation/index.html. The documentation is updated periodically, and Oracle recommends that you check this site for the current documentation and information on how to best use Oracle Secure Backup.
Section 1, "CD-ROM Image Contents"
Section 2, "Release Components"
Section 3, "Licensing Information"
Section 4, "Upgrading Oracle Secure Backup Releases 10.1 and 10.2 to Release 10.3.0.3.0"
Section 5, "Supported Tape Devices and Platforms"
Section 6, "Outstanding Bugs and Known Issues"
Section 7, "Bugs Fixed in Oracle Secure Backup 10.3.0.3.0"
Section 8, "Documentation Addendum"
Section 9, "Documentation Accessibility"
The CD-ROM image for each platform contains all necessary tools, documentation, and software to install and operate Oracle Secure Backup on the selected platform.
Note:
Each supported platform requires its own separate CD-ROM or installation Zip file.You can access the installation files from a physical CD-ROM or through a Zip file downloaded from the following product site:
http://www.oracle.com/technetwork/database/secure-backup/downloads/index.html
The only product in this release is Oracle Secure Backup.
Refer to Oracle Secure Backup Licensing Information for licensing terms.
Oracle Secure Backup Release 10.3 is not backward compatible to Oracle Secure Backup release 10.1 or release 10.2. To upgrade to Oracle Secure Backup release 10.3, all hosts within the administrative domain must be utilizing Oracle Secure Backup release 10.3.0.1.0, release 10.3.0.2.0, or release 10.3.0.3.0.
In an upgrade installation, the Oracle Secure Backup catalogs (contained in the admin directory) are preserved, retaining configuration information and backup metadata for your administrative domain. This state information for your administrative domain, such as the backup catalog, host, user and device configuration information, and any scheduled backup jobs, is stored in the admin directory under the Oracle Secure Backup home on your administrative server.
Note:
Oracle recommends backing up the administrative server before upgrading.Before upgrading an existing administrative domain to Oracle Secure Backup release 10.3.0.3.0, you must shut down drivers and background processes related to Oracle Secure Backup on all hosts. Upgrade the administrative server host first, and then the other hosts in the domain.
Brief instructions on each step are described in the following sections.
Before performing an upgrade installation, you must stop the daemons and services related to Oracle Secure Backup on all hosts in the administrative domain. See Oracle Secure Backup Reference for operating system-specific startup and shutdown commands.
You can upgrade your Windows 32-bit or Windows 64-bit administrative server, media servers, and clients from any earlier version of Oracle Secure Backup to Oracle Secure Backup release 10.3.0.3.0 simply by running the Oracle Secure Backup release 10.3.0.3.0 installer. This is called an upgrade installation. The installer detects the existing installation of Oracle Secure Backup and runs the uninstaller for the previous version automatically before beginning the new installation.
When you upgrade your administrative server from any earlier version of Oracle Secure Backup to Oracle Secure Backup release 10.3.0.3.0, the uninstaller will display the following prompt:
This system was configured as an Oracle Secure Backup Administrative Server. Oracle Secure Backup creates files specific to this administrative domain in the "admin" directory. Would you like to keep these files in case you reinstall Oracle Secure Backup? If you choose "Delete" all files related to Oracle Secure Backup will be removed from this system. If you choose "Keep" the files specific to this administrative domain will be retained.
You must choose the Keep option for the admin directory files. Selecting the Delete option will cause the installation to be incomplete, and then you must uninstall and reinstall Oracle Secure Backup to complete the installation. If you do not want to save the existing admin directory files, then you must exit the installation, uninstall Oracle Secure Backup release 10.2.0.1 or 10.2.0.2, and select the Delete option. After you have uninstalled Oracle Secure Backup release 10.2.0.1 or 10.2.0.2, you can install Oracle Secure Backup release 10.3.0.3.0 by running the Oracle Secure Backup release 10.3.0.3.0 installer.
When you upgrade your administrative server from Oracle Secure Backup release 10.1 to Oracle Secure Backup release 10.3.0.3.0, you should select the Keep option to keep the existing configuration of your administrative domain. If you select the Delete option, then the Oracle Secure Backup release 10.3.0.3.0 installation will succeed, but you will have to re-enter all of your Oracle Secure Backup configuration settings.
To upgrade a Linux or UNIX installation of Oracle Secure Backup, follow the setup and installation process described in Oracle Secure Backup Installation and Configuration Guide.
During the upgrade, the installer displays the following prompt:
Oracle Secure Backup is already installed on this machine (myhostname-sun2). Would you like to re-install it preserving current configuration data[no]?
Enter yes to perform the upgrade installation, retaining your previous configuration.
Oracle Secure Backup 10.3.0.3.0 changed the method by which library and tape devices that are attached to a Solaris media sever are supported. Oracle Secure Backup 10.3.0.3.0 now uses the Solaris standard generic (sgen) driver to support attached devices.
For more information about configuring the Solaris sgen driver to provide Oracle Secure Backup attach points, see Oracle Secure Backup Installation and Configuration Guide.
Supported platforms, web browsers and NAS devices are listed on Certify on My Oracle Support (formerly OracleMetaLink), at the following URL:
Tape drive and library matrixes are available at the following URL:
http://www.oracle.com/technetwork/database/secure-backup/learnmore/index.html
This section discusses Oracle Secure Backup release 10.3.0.3.0 outstanding bugs and known issues.
Table 1 Oracle Secure Backup Open issues
| Associated Bug Number | Issue |
|---|---|
|
9302454 |
Automount Fails to Overwrite Volume that Contains only an Incomplete Section |
|
9350364 |
Unable to Perform Catalog Backup After Renaming Administrative Host |
|
9773754 |
Volume Duplication Policy Requiring Multiple Duplicates Will Fail |
|
9857394 |
Trying to Add More than 35 Clients for a PNI Will Produce an Error |
|
10018505 |
During an auto swap, Oracle Secure Backup will not select an unexpired volume that contains only incomplete backup sections.
The workaround is to unlabel the volume that contains only incomplete backup sections.
The Oracle Secure Backup Catalog Backup job will fail if the Administrative Server is renamed.
The workaround is to stop and restart the Service Daemon on the Administrative Server after you rename the server. Refer to the Startup and Shutdown of Oracle Secure Backup services section in Oracle Secure Backup Reference for more information.
A volume duplication policy that requires multiple duplicates will fail to create more than one duplicate volume. The first duplication job will complete successfully but the subsequent duplication jobs will go into a pending state waiting for resources.
Workaround: Restrict the duplication to two tape devices.
Oracle Secure Backup cannot support an unlimited number of clients for a single PNI for a server host. There is a limit of 35 clients for a single PNI.
The Oracle Secure Backup Web tool can fail to start on the Windows platform, if the Oracle Secure Backup Service Logon account is not the System Account.
Workaround: Run Oracle Secure Backup Configuration and select the default System Account for the service logon.
This section lists the bugs that have been fixed in Oracle Secure Backup 10.3.0.3.0.
Table 2 Oracle Secure Backup Fixed Bugs
| Bug Number | Subject |
|---|---|
|
5378584 |
SOLARIS 10 BREAKS SUPPORT FOR GENERIC SCSI DEVICES |
|
8490434 |
UPGRADE IN PLACE FROM 10.2.0.3.0 TO 10.3.0.1.0 DOESN'T ALLOW DEVICE CONFIG ON NT |
|
9189432 |
LOAD-IF-REQUIRED OPERATION FOUND FAULTY |
|
9198603 |
RESTORE FAILURE ON ACSLS LIBRARY |
|
9211189 |
OSB DEVICES LOST AFTER REBOOT |
|
9270232 |
ACS - DRIVES DB CREATING USE LISTS |
|
9305860 |
OBACSLIBD CRASHES WHEN DRIVES VIA OBTOOL MKDEV |
|
9313317 |
UNLABLE TO UNLOAD TAPES IN 8 DRIVE 2 MEDIA SERVER ACSLS SETUP |
|
9317213 |
CANCELLATION OF DATABASE RESTORE JOB HANGS WHEN SBT ALLOCATED BUFFER NOT USED |
|
9346275 |
NETAPP BACKUP ABORTS WITH ILLEGAL ARGUMENTS IF PATH NOT FOUND |
|
9346882 |
WINDOWS 2008 64BIT SYSTEM FAILS TO BACKUP |
|
9363431 |
NO IP ADDR INFO WHEN OBACSLIBD IS UNABLE TO BIND TO A SOCKET |
|
9400190 |
SELECTIVE RESTORE FAILS FOR SOME PATHS WHEN PATHS ARE GIVEN IN CERTAIN ORDER |
|
9404563 |
OBNDMPD MOVER FAILS ON BIND WHEN A PORT RANGE IS SPECIFIED FOR OSB DAEMONS |
|
9430916 |
INVENTORY FINDS AN OBJECT NOT MATCHING THE VOL DB THROWS 'OBJECT NOT FOUND' ERR |
|
9482631 |
AIF IMPORTS ARE FAILING IN 10.3.0.2 IN NETAPP FILERS |
|
9504573 |
DRIVE OR VOLUME ON WHICH MOUNT ATTEMPTED IS UNUSABLE |
|
9532621 |
NEED SUPPORT FOR IBM TS1130/3592 TAPE DRIVE |
|
9557350 |
OBROBOTD IS NOT RECOGNIZING THAT FAILURES HAVE OCCURED IN TAPE/DRIVE |
|
9579962 |
PINGD OF ACSLS BASED TAPE DRIVES LOADED WITH TAPES RETURNS ILLEGAL SEEK |
|
9580442 |
PNI MECHANISM DOES NOT WORK IN IPV6 ENVIRONMENT |
|
9720418 |
OBSERVICED DOES NOT SUPPORT 31-CHARACTER VOLUME IDS IN CERTAIN FIND_OBJ REQUESTS |
|
9721615 |
KILLING A PROCESS WITH AN OPEN DEVICE LEAVES DEVICE OPEN |
|
9753828 |
OBIXD FAILS TO CATALOG A NDMP BACKUP WHEN FILE HISTORY IS OFF OR UNAVAILABLE |
|
9768359 |
MISCONFIGURED DRIVES WITH THE SAME DTE WILL CAUSE OBROBOTD TO SEGV IN SOLARIS |
|
9806366 |
INVENTORY REPORTS ERROR WHEN LAST DRIVE IS NOT CONFIGURED |
|
9919700 |
NETAPP FILER ASCII IMPORT FAILS IF DATA SET HAS NON-EXISTING INCLUDEPATH |
|
10013883 |
ACSLS FAILS TO DISMOUNT THE TAPE |
|
10009773 |
DURING FILEYSTEM BACKUP OF DB, SEEING STRANGE CHARS IN TRANSCRIPT |
This section describes changes to Chapter 9, Vaulting, in the Oracle Secure Backup Administrator's Guide.
The following statement must be removed from the description of the expiration event in Step 6b of the section "Adding Rotation Policies":
This event is applicable only to volumes with a time-managed expiration policy.
The following information must be added to the subsection "Location Report" of the section "Reports".
For content-managed volumes associated with an expiration event rotation policy, a specific Move Date cannot be provided until the volume expires. Until the volume expires, the location report will display the following text in the Move Date column: Volume not expired, not eligible to be moved.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Oracle Secure Backup Readme, Release 10.3
E14817-06
Copyright © 2006, 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.