Readme
Release 10.4
E21481-07
May 2015
This Readme applies only to Oracle Secure Backup release 10.4 (10.4.0.1.0, 10.4.0.2.0, 10.4.0.3.0, and 10.4.0.4.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/database-technologies/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, "Supported Tape Devices and Platforms"
Section 5, "ReadMe Information for Oracle Secure Backup 10.4.0.4.0"
Section 6, "ReadMe Information for Oracle Secure Backup 10.4.0.3.0"
Section 7, "ReadMe Information for Oracle Secure Backup 10.4.0.2.0"
Section 8, "ReadMe Information for Oracle Secure Backup 10.4.0.1.0"
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:
The only product in this release is Oracle Secure Backup.
Refer to Oracle Secure Backup Licensing Information for licensing terms.
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/database-technologies/secure-backup/learnmore/index.html
See Also:
"Deprecated Platforms for Oracle Secure Backup 10.4.0.4.0" for more information on platform support updates for Oracle Secure Backup 10.4.0.4.0The information in this section of the ReadMe applies only to Oracle Secure Backup release 10.4.0.4.0.
This section contains the following topics:
Section 5.1, "Upgrading to Oracle Secure Backup 10.4.0.4.0"
Section 5.2, "Bugs Fixed in Oracle Secure Backup 10.4.0.4.0"
Section 5.3, "Deprecated Platforms for Oracle Secure Backup 10.4.0.4.0"
The process of upgrading to Oracle Secure Backup 10.4.0.4.0 is the same as that of upgrading to Oracle Secure Backup 10.4.0.2.0.
During an upgrade, Oracle Secure Backup uses the installation parameters specified in the obparameters file. If you had modified the values of certain parameters in the configuration file obconfig, then ensure that you modify these parameters in the obparameters file also.
See Section 7.2, "Upgrading to Oracle Secure Backup Release 10.4.0.2.0".
Table 1 lists the bugs fixed in Oracle Secure Backup 10.4.0.4.0
Table 1 Oracle Secure Backup 10.4.0.4.0 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
17454577 |
RMAN PIECE RESTORE FAILS WITH "ERROR: COULD NOT ATTACH TO SBT SHARED MEMORY" |
|
17782708 |
INCREMENTAL DATAFILE BACKUP SET RESTORE (OSB, SBT) HANGS |
|
18965178 |
OSB TIMESOUT EARLIER THAN ACSLS TIMESOUT ON LIBRARY MOVE OPERATION |
|
18349417 |
JOB UNABLE TO USE DEVICE - TOO MANY OPEN HANDLES ERROR IN SCHEDULER LOG |
|
18335104 |
PREVENTIVE FIX FOR NOT OVERWRITE FROM BOT IF RW MODE IS QDV__OVERWRITE_HERE_M (SR# 3-8522553451) |
|
19600324 |
RATAPE-ORACLE SECURE BACKUP: 'OPERATION TIMED OUT (FSP NETWORK SERVICES MANAGER) |
|
19630317 |
BACKPORT OF HANG IN RDS/RDMA - OSB 10.4.0.3.1 RESTORE HANG |
|
19842492 |
SSL V3.0 POODLE DISABLE SSL V3 |
|
20017150 |
ENCRYPTION ISSUE WHILE DOING A SPANNING H/W TRANSIENT BACKUP FOR FILERS |
|
17256146 |
OSB BACKUP FAILS WITH ERROR RDS/RDMA SOCKET CREATION ERROR IN OBNDMPDMS.LOG |
|
16833624 |
UNABLE TO RESTORE A 'TRANSIENT + HW' ENCRYPTED BACKUP |
|
16863112 |
BARCODE LABEL (DUPLICATE BARCODE) CORRUPTION |
|
16929708 |
BACKUP KEEPS GOING IN LOOP AND NEVER COMES OUT |
|
16994838 |
BACKUP WITH PASSPHRASE CAN'T BE RESTORED ACROSS OSB DOMAINS |
|
17282897 |
OBTOOL COREDUMPS WHEN ACCESSING THE LIBRARY WITH LSDEV |
|
17353339 |
OSB SHOULD WORK WITH FILE SYSTEM THAT DOES NOT SUPPORT HARDLINKS |
|
17354051 |
RDMA NOT SELECTED WHEN PNI AS IB INTERFACE IS CONFIGURED. OSB USES RDS |
|
17605335 |
OSB HA OPTION TO SUPRESS IP CHECK DURING TRUST CHECK |
|
17620025 |
LSJOB -A DOES NOT COMPLETE WHEN SYSTEM MEMORY IS LOW |
|
17252456 |
BIGBH:OSB VERSION REPORT ERROR AFTER UPGRADE TO OSB 10.4.0.3.0 |
Oracle Secure Backup 10.4.0.4.0 does not support Linux 32-bit platforms, Windows 32-bit platforms, Windows XP 64-bit, and Windows 2003 64-bit platforms.
Although Oracle Secure Backup 10.4.0.4.0 does not support the mentioned platforms, it is backward compatible to clients using earlier Oracle Secure Backup 10.4 versions on these platforms.
The information in this section of the ReadMe applies only to Oracle Secure Backup release 10.4.0.3.0.
This section contains the following topics:
Section 6.1, "New in Oracle Secure Backup 10.4.0.3.0"
Section 6.2, "Upgrading to Oracle Secure Backup Release 10.4.0.3.0"
Section 6.3, "Bugs Fixed in Oracle Secure Backup 10.4.0.3.0"
Section 6.4, "Outstanding Bugs and Known Issues in Oracle Secure Backup 10.4.0.3.0"
This section briefly describes the new functionality in Oracle Secure Backup 10.4.0.3.0 and provides links to the books that contain detailed information about these features.
When multiple network connections exist between a media server and client, if you configure a PNI, then Oracle Secure Backup uses the network interface specified in the PNI to transmit data between the media server and other hosts. If no PNI is configured, Oracle Secure Backup chooses a network interface based on a predefined order of precedence.
The process of upgrading to Oracle Secure Backup 10.4.0.3.0 is the same as that of upgrading to Oracle Secure Backup 10.4.0.2.0.
During an upgrade, Oracle Secure Backup uses the installation parameters specified in the obparameters file. If you had modified the values of certain parameters in the configuration file obconfig, then ensure that you modify these parameters in the obparameters file also.
See Section 7.2, "Upgrading to Oracle Secure Backup Release 10.4.0.2.0".
Table 2 lists the bugs that have been fixed in Oracle Secure Backup 10.4.0.3.0.
Table 2 Oracle Secure Backup 10.4.0.3.0 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
12628683 |
OBACSLIBD HUNG WHILE CONSUMING LARGE AMOUNT OF CPU TIME |
|
13828501 |
OSB WEBTOOL SHOWING INCORRECT SIZE |
|
14054363 |
PNI TO TAKE PRECEDENCE OVER TYPE OF CONNECTION |
|
14108975 |
AFTER UNINSTALL, OBCONFIG FILE SHOULD BE RETAINED |
|
14191502 |
AIX MEDIA SERVER FAILS WITH BLOCKINGFACTOR GREATER THAN 1024 |
|
14366759 |
RESTORING WITH BLOCKINGFACTOR SET TO NOT MATCH RECORDED BLOCKINGFACTOR FAILS |
|
14366777 |
RESTORES FAIL WHEN BACKUPS ARE DONE WITH MULTIPLE BLOCKINGFACTORS |
|
14514220 |
ACSLS RESTRICTS TAPE DEVICES TO 20 AND CAPS TO 2 |
|
14587517 |
MORE THEN 6 CONCURRENT RESTORES FAILING ON ACSLS/OBACSLIBD CONTROLLED HARDWARE |
|
14799563 |
OBACSLIBD SHOWS HIGH CPU USAGE |
|
15843540 |
AIF IS NOT IMPORTED IF CATALOG SIZE EXCEEDS 128 GB |
|
15923162 |
ADD SUPPORT FOR HP ESL G3 LIBRARY |
|
16167707 |
NDMP_TAPE_CLOSE FAILURE THEN NEXT BACKUP ON TAPE VOLUME OVERWRITES VALID DATA |
|
16192092 |
CORE DUMP DURING MKDEV OF IBM LTO6 IN SL3000 - MM_FREE WITH WST_ENCR/CDC TAG |
|
16270470 |
AVOID OVERWRITING VOLUMES EVEN IF EOM IS NOT PRESENT OR RETURNS TO BOT |
|
16278738 |
SUPPORT FOR HP MSL 6480 AND HP ESL G3 LIBRARIES |
|
16459119 |
SBT__RPC_CREATEJOB: BACKUP JOB COULD NOT BE CREATED ('DUPLICATE JOB ID' ) |
|
16469638 |
UPGRADE APACHE, OPENSSL AND PHP FOR OSB WEB TOOL |
|
16477594 |
EMAIL TO BE SENT WHEN NOUPDATE FILE IS PRESENT AND IMPORT FAILS |
|
16477623 |
VOLUMES IN STANDALONE DRIVES CAN'T BE PRELABELED WITH BARCODES |
|
16477641 |
DATABASE BACKUP JOB WITH BF SET TO > 4096 GOES IN LOOP |
|
16477657 |
INCORRECT TAPECAPACITY REPORTED IN HUMAN READABLE FORMAT |
|
16569323 |
DIRECTORIES NAMED "FILES" ARE NOT BACKED UP UNDER BI |
|
16569596 |
DUPLICATION COMPLETES SUCCESSFULLY BUT LEAVES A MINIMALLY LABELED VOLUME |
|
16665462 |
OBCLEANUP IS SEG FAULTING |
Table 3 discusses the outstanding bugs and known issues in Oracle Secure Backup 10.4.0.3.0.
Table 3 Oracle Secure Backup 10.4.0.3.0 Open Issues
| Associated Bug Number | Issue |
|---|---|
|
9773754 |
Volume Duplication Policy Requiring Multiple Duplicates Will Fail |
|
10018505 |
|
|
10367517 |
|
|
14123834 |
|
|
14185327 |
NDMP Filer Restore Failure When Multiple Paths Are Specified for RESTORE |
|
14200659 |
Windows 2003/XP IPv6 Media Server Does not Connect to an IPv4 Client |
A volume duplication policy that requires multiple duplicates fails to create more than one duplicate volume. The first duplication job completes successfully but the subsequent duplication jobs go into a pending state waiting for resources.
Workaround: Restrict the duplication to two tape devices.
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.
A volume that has not been written to, but was pre-labeled with a media family (using the labelvol command), will be selected for vaulting by a vaulting scan.
Workaround: To prevent a volume from being selected during a vaulting scan, do not use the lastwrite event in the rotation rule that is defined for the media family.
A backup job fails with I/O errors when the blocking factor is set above 1024 and Direct I/O is enabled.
Workaround: Change the blocking factor to be less than or equal to 1024 or disable Direct I/O on the media server. For more information, see "Additional Information On Blocking Factors".
The restore operation of an NDMP filer fails when multiple path names are specified in the RESTORE command.
Workaround: Specify one path name for a RESTORE command.
A Windows 2003 or Windows XP media server that is configured to support both an IPv6 and an IPv4 connection does not connect to a client that supports only an IPv4 connection.
Workaround: Add an IPv6 connection to the client or backup the client to a media server of a different platform such as Windows 2008 or Linux.
If the blocking factor is changed from the Oracle Secure Backup default setting, the best practice is to test that backup and restore operations function properly with the new blocking factor setting. RMAN backups, NDMP filer backups, and file-system backups have different blocking factor requirements that must be validated with the new blocking factor.
The media server platform, operating system, and the tape device may also have specific blocking factor limitations or requirements which you must review. Each media server in the Oracle Secure Backup domain needs to be tested with the new blocking factor. The testing must be done using typical backup loads that are specific to your environment. Both backup and restore operations must be completed without warnings or errors from either Oracle Secure Backup or RMAN. The restored data must also be examined to verify success. In particular, Oracle Secure Backup-issued warnings regarding the blocking factor during a backup operation must not be ignored. If you receive such warnings, adjust the blocking factor and rerun the backup operation.
The best practice is to have consistency by using only one blocking factor across the Oracle Secure Backup domain. More specifically, all backups written to a tape must be created with the same blocking factor. If you have a separate disaster recovery site, test and confirm that the new blocking factor setting is supported by the site's infrastructure.
This information in this section of the Readme applies only to Oracle Secure Backup release 10.4.0.2.0.
This section contains the following topics:
Section 7.1, "New in Oracle Secure Backup 10.4.0.2.0"
Section 7.2, "Upgrading to Oracle Secure Backup Release 10.4.0.2.0"
Section 7.3, "Bugs Fixed in Oracle Secure Backup 10.4.0.2.0"
This section briefly describes the new functionality in Oracle Secure Backup 10.4.0.2.0 and provides links to the books that contain detailed information about the functionality.
Starting with Oracle Secure Backup 10.4.0.2.0, you can choose to improve the write throughput of your tape devices by using asynchronous I/O. Asynchronous I/O implements write command queuing for SCSI channel operations. In this release, the LT05 and T10000C tape drives take advantage of the performance benefits provided by asynchronous I/O. This functionality is supported on Linux platforms only.
To enable asynchronous I/O, direct I/O must be enabled on the Linux media server. Perform the following steps to enable direct I/O:
# touch enable_dio in $OSB_HOME/device # echo 1 >/proc/scsi/sg/allow_dio
Ensure that the environment variable OSB_HOME is set to the location of Oracle Secure Backup home directory.
Note:
Support for asynchronous I/O is available only on Linux.Starting with Oracle Secure Backup 10.4.0.2.0, the StorageTek Automated Cartridge System Library Software (ACSLS) is supported on a Linux 64-bit media server.
You can use the lsvol command to list volumes that can be recycled in a tape library or a volumes catalog. The new value "recyclable" of --attribute lists the time-managed and content-managed volumes that can be recycled. This functionality is available only with the Oracle Secure Backup command-line client, obtool, not with the Oracle Secure Backup Web tool or Oracle Enterprise Manager.
See Also:
Oracle Secure Backup ReferenceStarting with Oracle Secure Backup 10.4.0.2.0, Reliable Datagram Socket (RDS) over Infiniband, with Remote Direct Memory Access (RDMA), is supported on Solaris SPARC 11 platforms.
You can import cleaning tapes using the clean option of the importvol command. This functionality is available only with the Oracle Secure Backup command-line client, obtool, not with the Oracle Secure Backup Web tool or Oracle Enterprise Manager.
See Also:
Oracle Secure Backup ReferenceOracle Secure Backup release 10.4.0.2.0 is not backward compatible with Oracle Secure Backup release 10.1 or release 10.2. To upgrade to Oracle Secure Backup release 10.4.0.2.0, all hosts within the administrative domain must be utilizing Oracle Secure Backup release 10.3.0.1.0 or higher.
Note:
Backups created using previous releases of Oracle Secure Backup can be restored using Oracle Secure Backup 10.4.0.2.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:
It is recommended that you back up the administrative server before you perform an upgrade.Before Upgrading an Administrative Domain to Oracle Secure Backup 10.4.0.2.0
Perform the following steps before you upgrade your existing administrative domain to Oracle Secure Backup release 10.4.0.2.2:
Shut down drivers and background processes related to Oracle Secure Backup on all hosts
Stop the daemons and services related to Oracle Secure Backup on all hosts in the administrative domain
Upgrade the administrative server host first, and then the other hosts in the domain.
See Also:
Oracle Secure Backup Reference for operating system-specific startup and shutdown commandsBrief instructions on upgrading Oracle Secure Backup on different platforms are described in the following sections.
To upgrade to 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 10.4.0.2.0, you must first uninstall the existing software. You then run the Oracle Secure Backup 10.4.0.2.0 installer to install the new software on all your hosts.
While uninstalling software from your administrative server, you must select the Keep option to retain your administrative server configuration.
For more information about the steps to upgrade to Oracle Secure Backup 10.4.0.2.0 on Windows, see Oracle Secure Backup Installation and Configuration Guide.
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 release 10.4.0.2.0 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.
Table 4 lists the bugs that have been fixed in Oracle Secure Backup 10.4.0.2.0.
Table 4 Oracle Secure Backup 10.4.0.2.0 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
9277316 |
OSB:10302: VFYLIBS REPORTS TRUNCATED SERIAL NUMBER FOR THE DRIVE |
|
9916444 |
TAPE DRIVE SHOULD NOT BE TAKEN OUT OF SERVICE |
|
10629160 |
VFYLIBS IS FAILING WITH 'WRONG ID REPORTED BY DRIVE' |
|
11774370 |
DUPLICATE VOLUME NOT USED WHEN ORIGINAL VOLUME IS MISSING |
|
11784757 |
DRIVE CHANNEL LATENCY - WRITE - LINUX AND SOLARIS |
|
12574582 |
BOGUS DUPLICATION ERROR: "OUTPUT MEDIA SMALLER THAN DATA SIZE OF INPUT MEDIA" |
|
12578717 |
FAILED DUPLICATION REMOVES ON-TAPE LABEL |
|
12579854 |
OSB IGNORES PRELABELED TAPES, USES UNLABELED |
|
12668367 |
IMPORTVOL LEAVES THE VOLUME IN THE DRIVE AND REPORTS ERROR "SOURCE IS EMPTY" |
|
12775775 |
AIX 10.4 LIB DIR CONTENTS NEED TO BE REMOVED BEFORE UPGRADE OR AFTER UNINSTALL |
|
12786273 |
OBROBOTD SEG FAULTS DURING MULTIPLE VIRTUAL DEVICE CREATION |
|
12794762 |
OBROBOTD EXITED WITH CODE 0X20008F06, VALUE 26 |
|
12840740 |
USE LISTS CAN BECOME TOO LONG TO SUPPORT |
|
12874518 |
OBTOOL – LSSSEL CRASHES WHEN SELECTOR HOSTNAME IS LONGER THAN 37 CHARACTERS |
|
12951078 |
DUPLICATION JOB GOES TO PENDING WHEN LARGE NUMBER OF DEVICES ARE PRESENT |
|
12969272 |
INCREASE BLOCK SIZE LIMIT FROM 1MB TO 2MB ON THE LINUX PLATFORM |
|
12986708 |
ERROR: COULD NOT CREATE SYMLINK /ARCSIGHT/ARCARCHIVE4/TEST/USR/BIN/RPMDB: PERMIS |
|
13023406 |
FOR T10K DEVICE REMTAPE LOCATION WRONGLY DEFINED IN WST_DRIVES.H |
|
13035935 |
ACC: DATA TABLE SUPPORT OF ROW HEADERS IS MISSING |
|
13056050 |
RMAN FAILED WITH ORA-19511 |
|
13083531 |
ENCRYPTION WARNINGS ON T10000B AND C DRIVES |
|
13088096 |
CAN'T CHANGE A USER PASSWORD IN THE UI IN WINDOWS32 OR 64 |
|
13241877 |
FAILED DUPLICATION UPDATED UNFINISHED DUPLICATE TO VOLUME DB |
|
13262666 |
OBSCHEDULED LOG HAS ERRONEOUS WARNING ABOUT HAVING 2 DEVICE RESERVATIONS ON DUP |
|
13391793 |
OSB UNABLE TO RESOLVE IPV6 ADDRESSES WHEN SPECIFIED AS :: |
|
13474350 |
RESTORE FAILS WITH ERROR: CAN'T QUEUE JOBS - CONNECTION RESET BY PEER |
|
13475037 |
NDMP_DATA_CONNECT FAILURE: COUDN'T CONNECT TO MOVER |
|
13476158 |
"OBJECT NOT FOUND" WHEN ATTEMPTING RESTORE |
|
13501265 |
EDITING HOST ON WINDOWS CREATES ERROR: CAN'T FETCH HOST - NAME NOT FOUND |
|
13504602 |
WEBTOOL FAILS TO ADD PREAUTHORIZED ACCESS |
|
13520013 |
DEVICE GETTING LOCKED AFTER DUPLICATION |
|
13592144 |
BACKUP OF ORACLE FAILS WITH NDMP ERROR |
|
13604237 |
CHANGE DEFAULT FOR NETWORK LOAD BALANCING TO DISABLE |
|
13610839 |
DATASET DIRECTIVE CAUSES FILES TO BE INVISIBLE DURING CATALOG BROWSE FOR RESTORE |
|
13623433 |
REDUCE SCHEDULER DEPENDENCE ON OBROBOTD |
|
13651198 |
UPGRADE TO LATEST VERSION OF APACHE (v2.2.22), PHP (v5.3.13), AND OPENSSL (v0.9.8x) |
|
13694304 |
NETAPP BACKUP FAILS BAD FILE DESCRIPTOR WHEN FILES IN DIR > 1.5MILLION |
|
13771142 |
OSB RMAN BACKUP 'LSVOL'DOESN'T INDICATE WHEN NO BACKUP PIECES REMAIN ON TAPE |
|
13813168 |
"EXCLUDE ORACLE DATABASE FILES" - DOESN'T EXCLUDE DB FILES |
|
13899880 |
INVALID CHAR IN KEYSTORE PASSWORD CAUSES "FATAL: LIBNDMPCOMMON.SO: OPEN FAILED" |
This information in this section of the Readme applies only to Oracle Secure Backup release 10.4.0.1.0.
This section contains the following topics:
Section 8.1, "New in Oracle Secure Backup 10.4.0.1.0"
Section 8.2, "Upgrading to Oracle Secure Backup Release 10.4.0.1.0"
Section 8.3, "Bugs Fixed in Oracle Secure Backup 10.4.0.1.0"
This section briefly describes the new features in Oracle Secure Backup 10.4.0.1.0 and provides links to the books that contain detailed information about these features.
Oracle Secure Backup enables you to use the Reliable Datagram Socket (RDS) protocol over Infiniband for data transfer between a client and media server. You can also use Remote Direct Memory Access (RDMA) with RDS to maximize the benefits of using RDS over Infiniband.
Oracle Secure Backup supports network load balancing for both file-system and Oracle Database backup and restore operations. Network load balancing ensures optimal utilization of multiple network connections on a client by distributing backup and restore jobs across the available network connections.
See Also:
Oracle Secure Backup Installation and Configuration Guide for more information about network load balancingOracle Secure Backup provides support for Non-Uniform Memory Access (NUMA) architecture. In a NUMA architecture, processors are grouped into smaller systems called nodes or regions and all processors within a node share a common memory. This provides improved scalability and performance because accessing this local memory is faster.
Oracle Secure Backup 10.4.0.1.0 supports character special files while backing up and restoring raw file-systems.
See Also:
Oracle Secure Backup Reference for more information about backing up and restoring character special filesStarting with Oracle Secure Backup 10.4.0.1.0, the role of Oracle Secure Backup administrative server, media server, and client is supported on the following platforms:
Microsoft Windows 7 64-bit
Solaris SPARC v11 Express
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 that you back up the administrative server before you perform an upgrade.Before upgrading an existing administrative domain to Oracle Secure Backup release 10.4.0.1.0, you must shut down drivers and background processes related to Oracle Secure Backup on all hosts. You must stop the daemons and services related to Oracle Secure Backup on all hosts in the administrative domain. Upgrade the administrative server host first, and then the other hosts in the domain.
See Also:
Oracle Secure Backup Reference for operating system-specific startup and shutdown commandsBrief instructions on each step are described in the following sections.
Oracle Secure Backup release 10.4.0.1.0 is not backward compatible with Oracle Secure Backup release 10.1 or release 10.2. To upgrade to Oracle Secure Backup release 10.4.0.1.0, all hosts within the administrative domain must be utilizing Oracle Secure Backup release 10.3.0.1.0 or higher.
Note:
Backups created using previous releases of Oracle Secure Backup can be restored using Oracle Secure Backup 10.4.0.1.0.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.4.0.1.0 by running the Oracle Secure Backup release 10.4.0.1.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.4.0.1.0, the uninstaller displays 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.
For the admin directory files, select the Keep option. Selecting the Delete option causes 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.3 or 10.2 and select the Delete option. After you uninstall Oracle Secure Backup release 10.3 or 10.2, you can install Oracle Secure Backup release 10.4.0.1.0 by running the Oracle Secure Backup release 10.4.0.1.0 installer.
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 release 10.4.0.1.0 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.
Table 5 lists the bugs that have been fixed in Oracle Secure Backup 10.4.0.1.0.
Table 5 Oracle Secure Backup 10.4.0.1.0 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
12965340 |
SUPPRESS CAPACITY CHECK FOR DUPLICATION |
|
12926877 |
CWALLET.SSO IS SKIPPED DURING HARDWARE ENCRYPTION |
|
12875157 |
DEVICE OBJECT USE LIST CORRUPTION CAUSING RESTORE FAILURE |
|
12822296 |
BROWSING CATALOG GETS EXTREMELY SLOW AT TIMES |
|
12652278 |
NON ACSLS MACHINES SHOULD ONLY HAVE 3 PASSES IN AUTOMOUNTER |
|
12575036 |
OBROBOTD CONNECTION RESET BY PEER |
|
12543183 |
OBTOOL SEGFAULTS DURING CATALOG LISTING OF 1023 CHARACTER LENGTH DIRECTORY PATH |
|
12322773 |
USERNAME INPUT VALIDATION BYPASS OF VALIDATE_LOGIN FUNCTION ON LOGIN.PHP PAGE |
|
12315104 |
OSB WEB TOOL ONLY DISPLAYS THE 1ST 25 BACKUP SECTIONS |
|
12313425 |
VOLUME MISMATCH |
|
12312668 |
DATA FIELDS OVERFLOW WHEN DEALING WITH TAPE VOLUMES LARGER THAN 2TB |
|
11907554 |
MODIFY IO RATE REPORT IN JOB TRANSCRIPTS TO BE MORE ACCURATE AND DESCRIPTIVE |
|
11817669 |
NULL STRING FOR CLIENT IN PNI COMMAND CAUSES SEG FAULT |
|
11797678 |
SCHEDULER CRASH WHEN DUPLICATION JOB SUMITTED WITH STANDALONE DRIVE |
|
11779486 |
UI CATALOG RESTORE BROWSE 'PREVIOUS' ISN'T WORKING "ERROR: CAN'T CD" IS THROWN |
|
11662645 |
OSB MEDIA SERVER CAN'T HANDLE DAR RESTORES WHEN POSITION > 0X7FFFFF |
|
11076873 |
LSJ AND CATXCR UNRESPONSIVE WHEN OBACSLIBD HAS ANY DEVICE RESERVED |
|
11071973 |
OBACSLIBD SEG FAULTS WHEN NO TAPE DRIVES ARE CONFIGURED |
|
10314282 |
WEB SERVER STARTUP FAILS - OBPASS.BAT CAN'T EXECUTE OBTOOL |
|
10302944 |
CHPNI COMMAND |
|
10283082 |
UPDATER CHECKED OUT - STAT RECORD NOT FOUND (OB INDEX DB MGR) |
|
10273086 |
DATASERVICE FAILED TO CONNECT TO MOVER SERVICE. |
|
10259321 |
IBM LTO 5 DRIVE REPORTS "MEDIAINFO NOT HW ENCRYPTABLE" WHEN IT SHOULD BE |
|
10231332 |
CLEANING NOT WORKING PROPERLY-- "ERROR: CAN'T EXECUTE COMMAND - SOURCE IS EMPTY" |
|
10218725 |
OSB JOB START IS SLOW |
|
10199325 |
WEBTOOL REMOVE HOST DOESN'T SUPRESS COMMUNICATION EVEN WHEN CHECKED |
|
10191788 |
OBTOOL INVENTORY FAILED WITH "CAN'T EXECUTE COMMAND - OBJECT NOT FOUND" |
|
10162402 |
OSB CH/RM/MKDEV CMD TO ACSLS INVALIDATES DRIVE DB, AFFECTING QUEUED REQUESTS |
|
10158637 |
DIRECT ATTACHED SCSI DEVICE FILES(SGEN) HAVE UNRECOGNIZED FORM |
|
10154601 |
IN GUI, QUOTED BACKSLASHES IN ALTERNATE PATH BREAKS RESTORE AND RESTORE PREVIEW |
|
10134939 |
CORE DUMPS FROM ACSLS LIBRARY |
|
10126431 |
SOLARIS V11 INSTALL REPORTS ERRORS DURING PROTECTION STEP |
|
10080006 |
MULTIPLE ATTACH POINTS POSES RISKS OF DEVICE HANGS |
|
10071088 |
NDMP INCREMENTALS FAIL IF USING A BACKUP TYPE THAT DOESN'T SUPPORT BASE_DATE |
|
10054576 |
REFERENCING MH AND DRIVE STRUCTURES INTERCHANGEABLY LEADS TO CORE DUMPS |
|
10045771 |
OSB MULTI-LINKED DIRECTORY ERRORS BACKING UP ON AIX |
|
9958811 |
SENSE RANGE COMMAND BEING ATTEMPTED ON LIBRARY THAT DOESN'T SUPPORT RANGES |
|
9857394 |
TRYING TO ADD MORE THAN 35 CLIENTS FOR A PNI JUST GETS AN ERROR |
|
9828170 |
OBACSLIBD APPEARS TO HANG WITH 20 TAPES DRIVES IN ACSLS LIBRARY |
|
9387688 |
OSB WEBTOOL FAILS TO PING DEVICE WITH WWN ATTACHMENT |
|
9371317 |
INCREMENTAL BACKUPS BEHAVES DIFFERENTLY IF TZ VARIABLE IS SET |
|
9302454 |
AUTOMOUNT FAILS TO OVERWRITE VOLUME THAT ONLY HAS AN INCOMPLETE SECTION |
|
9245324 |
CANNOT SET DEVICE RESTRICTION FOR OSB-CATALOG-SCHED SCHEDULE IN WEB TOOL |
|
9194101 |
CAN NOT SET WRITE WINDOW OF FOREVER |
|
9170790 |
RENAME OF A HOST WITH THE '--NOCOMM' OPTION FAILS IN UI |
|
9170779 |
IF ONLY ONE JOB IS DISPLAYED ON THE MANAGE:JOBS PAGE, TRANSCRIPT ISN'T VIEWABLE |
|
9082393 |
HOST NAME: ERROR STATUS: OPERATION ROLES: [UNABLE] IN OSB WEB |
|
8994552 |
ABILITY TO BACKUP RAW DEVICES /DEV/RDSK/DEVICE |
|
8617627 |
REPLACE GETENV() OS CALLS WITH POSIX_UNAME |
|
8495214 |
CONFIG:DEVICES:BLOCKING FACTOR NEEDS A CHECKBOX FOR DEFAULT |
|
8491199 |
OSB BACKUP SCHEDULE--PREVIEW TRIGGER MISSING 'LEVEL' INFO |
|
8491189 |
SETTING AN IP INTERFACE NAME FOR AN NDMP HOST IN THE UI THROWS AN ERROR |
|
8422984 |
OPTIONS 'IDENTIFYVOL' & 'IMPORT' SHOULD ONLY BE OFFERED FOR A DRIVE/NOT LIBRARY |
|
8390931 |
MANAGE->VOLUMES PAGE DOES NOT RETAIN THE SELECTED VOLUME ATTRIBUTES |
|
8256070 |
RAW RESTORE APPENDING THE 'FILE NUMBER' TO THE VOLUME ID SPECIFIED |
|
7704721 |
INV OF LIMITED RANGE OF SE'S IS SAMPLING ALL ELEMENTS ON SOME LIBRARIES |
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Secure Backup Readme, Release 10.4
E21481-07
Copyright © 2006, 2015, 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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.