| Oracle® Secure Backup Readme Release 10.1 Part Number B25050-07 |
|
| View PDF |
| Oracle® Secure Backup Readme Release 10.1 Part Number B25050-07 |
|
| View PDF |
Readme
Release 10.1
B25050-07
May 2007
Purpose of this Readme
This Readme file is relevant only to Oracle Secure Backup release 10.1. This Readme documents supported platforms and devices as well as known issues.
Documentation
For documentation, use your Web browser to access the Oracle Secure Backup documentation library. The library home page is named index.htm and is located in the doc directory of your CD-ROM image. You can also access the library online at the following URL:
http://www.oracle.com/technology/documentation/
Contents
Section 1, "CD-ROM Image Contents"
Section 2, "Release Components"
Section 3, "Licensing Information"
Section 4, "Bugs and Known Issues"
Section 5, "Supported Tape Devices and Platforms"
Section 6, "AIX Device Identification"
Section 7, "Documentation Correction and Addition"
Section 8, "Documentation Accessibility"
The CD-ROM image contains all necessary tools, documentation, and software to install and operate Oracle Secure Backup on the supported platforms. You can access the image from a physical CD-ROM or through a Zip file downloaded from the following product site:
http://www.oracle.com/technology/products/secure-backup/
The images in the CD-ROM and Zip file are identical.
The only product in this release is Oracle Secure Backup.
Refer to Oracle Secure Backup Licensing Information for licensing terms.
The following sections describe bugs and known issues with Oracle Secure Backup.
On a Linux host running Enterprise Manager Database Control or Enterprise Manager Grid Control, support for managing Oracle Secure Backup is not included until you apply the first Oracle Database 10g release 2 patch set.
Also, in releases 10.2.0.1 and 10.2.0.2 of Enterprise Manager Grid Control and release 10.2.0.2 of Enterprise Manager Database Control, the Oracle Secure Backup section of the Maintenance page is not displayed by default.
Follow the steps in the section "Using Enterprise Manager" in the "Getting Started" chapter of Oracle Secure Backup Administrator's Guide to configure Enterprise Manager to include the Oracle Secure Backup section in the Maintenance page.
The clocks on the administrative server, the clients and the media servers must be synchronized to within 60 minutes of each other. If the time skew among hosts in the administrative domain is more that 60 minutes, then you might encounter problems when attempting to issue the mkhost command to configure new hosts. The error that appears in the observiced log file on the client or media server is "failed to validate certificate".
The solution is to synchronize the clocks on all hosts in the administrative domain to match the clock on the administrative server and then retry the failed operation.
You cannot edit the RMAN-DEFAULT media family when using Enterprise Manager 10.2.0.2 or earlier. Use the Oracle Secure Backup Web tool or obtool to edit the RMAN-DEFAULT media family.
Tape device-related debug logging should be enabled only under the direction of Oracle Support. Enabling tape device-related debug logging outside the instructions of a support representative can cause backup failures.
Configuring a Linux host for the Oracle Secure Backup media server role requires that the SCSI Generic driver be installed on that host. The host must also be configured to automatically reload the driver after a restart.
Kernel modules are usually loaded directly by the facility that requires them, if the correct settings are present in the /etc/modprobe.conf file. However, it is sometimes necessary to explicitly force the loading of a module at start time.
For example, on RedHat Enterprise Linux, the module for the SCSI Generic driver is named sg. Red Hat Enterprise Linux checks for the existence of the /etc/rc.modules file at start time, which contains various commands to load modules.
Note:
Therc.modules should be used, and not rc.local, because rc.modules runs earlier in the start process.You can use the following commands to add the sg module to the list of modules configured to load as root at start time:
# echo modprobe sg >> /etc/rc.modules # chmod +x /etc/rc.modules
On Windows platforms, if the securecomms security policy is enabled (the default setting), then you must be logged in as Administrator (or your logged-in account must belong to the Administrators group) in order to run the Oracle Secure Backup obtool command line tool.
Oracle Secure Backup clients and media servers running on Windows platforms are not automatically updated when changes are made to certain policy parameters. The parameters affected are:
rmanresourcewaittime
rmanrestorestartdelay
securecomms
After making changes to any of these parameters, you must stop and restart the observiced service on each Windows client and media server in Services. (To access Services, click Start, and then select Programs > Administrative Tools > Services.)
If there are no media devices attached to a Windows 2000 host, then do not configure that host for the media server role.
If you configure the media server role on a Windows 2000 host with no attached media devices, then the operating system tries continuously to load the Oracle Secure Backup driver. Continuously trying to load the driver uses most of the available CPU cycles on that system and renders the system unusable.
If you use a Windows host as an Oracle Secure Backup administrative server, then there is a resource limitation that determines the maximum number of hosts and tape drives that you can include in the administrative domain. The limitation is as follows, where H is the number of hosts in your administrative domain and T is the number of tape drives (standalone or in tape libraries):
H + (4 * T) < 40
If you configure an Oracle Secure Backup administrative domain on Windows that exceeds this limit and run multiple simultaneous backup or restore jobs, then in some cases jobs might hang waiting for resources. When this condition arises, you see the following error message in the observiced log file:
reached maximum Windows event limit (FSP event manager)
To resolve the problem, stop the hung backup or restore jobs and let the others run to completion. Then restart the hung jobs and allow them to run.
The default configuration of the Windows Firewall in Windows XP can block ports used by Windows hosts running Oracle Secure Backup. This can prevent Windows hosts from connecting to other hosts in the administrative domain.
Instructions for configuring the Windows Firewall to not interfere with Oracle Secure Backup are contained in the Oracle Secure Backup Installation Guide.
If you use a Windows host as an Oracle Secure Backup administrative server, then host names cannot contain upper-case characters. An invalid name error results when upper-case letters are used in host names with Windows as the administrative server. This limitation does not apply with Linux or Solaris as the administrative server.
Supported platforms, Web browsers and NAS are listed on Certify on OracleMetalink at the following URL:
Tape device matrixes are available at the following URL:
Before you configure devices within Oracle Secure Backup, you must obtain the following identifying information about how they are attached to the host (media server):
SCSI bus number
Target ID
Logical Unit Number (LUN)
If the devices are directly attached to an AIX host, then this information might not be readily available for all SCSI attached devices using standard operating system commands. To assist with gathering device information in AIX environments, a standalone tool (obscan) has been included on the CD. The obscan executable can be found in the cdtools directory of the CD or CD image.
You must have operating system privilege to access devices, which is often root access, to run obscan. The syntax for obscan is as follows, where device_filename is the special device file name of the SCSI adapter you want to scan:
obscan device_filename
Run obscan for each SCSI adapter with tape devices to be used by Oracle Secure Backup. In the following example, obscan gathers information about the tape devices connected to the SCSI bus (adapter) identified by the special device file /dev/scsi2:
obscan /dev/scsi2 obscan version 10.0.0.0 (AIX) Copyright (c) 2007, Oracle. All rights reserved. DEVICE information for /dev/scsi2 Target-id : 1, Lun : 0 Vendor : ADIC Product : FastStor 2 Target-id : 2, Lun : 0 Vendor : HP Product : Ultrium 2-SCSI Total count of Media Changers and/or Tape devices found : 2
Note:
Theobscan tool is not included as part of the Oracle Secure Backup installation. It is provided as an optional tool for device identification in AIX environments.This section contains additions to the Oracle Secure Backup Administrator's Guide.
If your administrative host runs HP-UX PA-RISC (64-Bit), then the nobody user and group might not be able to access shared memory. To avoid this issue, complete the following steps:
In the apache/conf/httpd.conf file, edit the User and Group sections for the Web server.
Change user nobody to user john where john is an alternate username and nogroup to svrtech where svrtech is an alternate user group.
Start obhttpd.
Check apache/logs/error_log for errors.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Secure Backup Readme, Release 10.1
B25050-07
Copyright © 2007, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
