Readme
Release 12.1
E16566-07
December 2016
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 Oracle Secure Backup 12.1 licensing requires that the number of concurrent jobs defined for each disk pool must be licensed. The user must define the number of concurrent jobs when configuring the disk pool. The default value of for the number of concurrent jobs is 25.
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
Oracle Secure Backup 12.1 is backward compatible with Oracle Secure Backup 10.4.0.3 or 10.4.0.3.1 clients only. Oracle Secure Backup 12.1 supports Oracle Secure Backup 10.4.0.3 features and is interoperable with its functionality. All media servers must be at the Oracle Secure Backup 12.1 version level. Access to any new commands and options introduced in Oracle Secure Backup 12.1 are not supported from a 10.4.0.3 client. The new commands must be accessed from a Oracle Secure Backup 12.1 host or via the Oracle Secure Backup WebTool. A database backup to disk from an Oracle Secure Backup client 10.4.0.3 is not supported. That backup is restricted to tape.
Similarly, you can only upgrade Oracle Secure Backup 10.4.0.3 to Oracle Secure Backup 12.1. If you are using an earlier version, then you must upgrade to Oracle Secure Backup 10.4.0.3 prior to upgrading to Oracle Secure Backup 12.1.
If you are using Oracle Secure Backup 10.4.0.4, you must manually change the client version at/etc/obconfig to 10.4.0.3.0 and then run the 12.1 installer to upgrade to Oracle Secure Backup 12.1.
See Also:
Oracle Secure Backup Installation and Configuration Guide for more information on Client Backward Compatibility
Oracle Secure Backup Installation and Configuration Guide for more information on how to upgrade Oracle Secure Backup 10.4.0.3 to Oracle Secure Backup 12.1
http://docs.oracle.com/cd/E26569_01/doc.104/e21481/toc.htm#CBBJCADC for more information on upgrading to Oracle Secure Backup 10.4.0.3
This information in this section applies only to Oracle Secure Backup 12.1.0.1.
This section lists the new features in Oracle Secure Backup 12.1.0.1
This section contains the following topics:
Extended Attribute Backup and Restore for Linux and Unix System
Oracle Secure Backup provides integrated disk backup and restore capabilities. You can use disk as a backup target or a restore source for file-system, Oracle Database and MySQL backup operations. Storing backups on disk provides improved performance for Oracle Database and file-system backup and restore operations.
Disk backup provides a new copy backup image instance feature which allows you copy a backup image to tape or disk. This feature allows you to migrate a backup image instance from disk to tape. It allows you to create multiple copies of the same backup image and the capability of each copy being managed by its own distinct media family. This feature is allows you to consolidate backup image instances from an existing tape on to a new tape.
Oracle Secure Backup simplifies the process of configuring devices by providing a single command that discovers and configures devices that are attached to media servers. This includes NDMP filers and media servers that run Oracle Secure Backup software.
Oracle Secure Backup enables you to search for multiple backup entries while browsing the backup catalog. You can use Oracle Secure Backup wildcard pattern matching while providing required backup details. Wildcard pattern matching uses a set of character patterns to search for related backups without providing elaborate information.
Oracle Secure Backup enables you to restore multiple backup entries using wildcard pattern matching. Wildcard pattern matching uses a set of character patterns to search for related backups without providing elaborate information.
Oracle Secure Backup 12.1 enhances the process of importing the catalog data of a volume from another domain. In a single catalog operation you can import the catalog data of a full volume set that contains file system backups, Oracle Database backups, or NDMP filer backups.
Oracle Secure Backup 12.1 improves the security strength of Oracle Secure backup user passwords by providing password management policies that control the password's lifetime, reuse, and length.
Password lifetime determines the duration of validity of a password, in number of days. Password grace time determines the duration for which a user can continue using a password after its lifetime expires. Password reuse time specifies the duration after which a user can reuse an old Oracle Secure Backup password.
The option to force a password change has also been introduced.
Oracle Secure Backup 12.1 now supports the backup and recovery of extended attributes and access control list for file system on UNIX platforms.
In some cases, earlier Oracle Secure Backup domains cannot read backup images containing extended attributes. In such scenarios, Oracle Secure Backup gives you the option to perform the backup without saving the associated extended attributes and access control lists.
Oracle Secure Backup 12.1 supports a volume status for each individual volume. A volume's status can be usable (default), read only, or out of service. Only a volume that is marked as usable will be considered during the backup volume selection process. A volume marked as read only or out of service will not be considered for any tape write operation.
This section lists the bugs that have been fixed in Oracle Secure Backup 12.1. 0.1
Table 1-1 Oracle Secure Backup 12.1.0.1 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
19636657 |
UPGRADE ORACLE SECURE BACKUP TO LATEST VERSIONS OF APACHE AND OPENSSL |
|
19265209 |
BACKUP USING MULTIPLE PATHS IN DS CREATES MULTIPLE ENTRIES IN CATALOG |
|
19001280 |
ER: NEED TO ENABLE DEBUG_ME MACRO UNDER QTL_FIND_VOLUME_OLD |
|
18884913 |
VFYLIBS INTERMITTENTLY DETECTS TRAILING GARBAGE CHARACTERS IN THE LTO4 SAS DRIVE |
|
18748553 |
BACKUPS TO STAND ALONE DEVICES PREVENTS APPENDING |
|
18714083 |
UNLABELV DO NOT CLEAR HEADER EVEN AFTER USING FORCE OPTION |
|
18704687 |
JOB SHOULD FAIL AFTER HAVING A DEVICE BUSY ERROR |
|
18675897 |
FAILURE OF NDMP CHECKPOINT RECOVERY OR RESTARTABLE NDMP BACKUPS |
|
18644417 |
LOCATION DETAILS NOT UPDATED FOR LIBRARY WHEN CONFIGURED THROUGH MKDEV |
|
18506622 |
HOST BASED PASSPHRASE RESTORE: ENTERING PASSPHRASE CAN CAUSE RESTORE TO FAIL |
|
18489354 |
MEDIA MOVEMENT JOB ON STANADLONE TAPE DRIVE FAILS WITH "ERROR: QLM__OPEN FAILED" |
|
18432941 |
SOCKET CREATION FAILS DURING RDS/RDMA CONNECTION ESTABLISHMENT BETWEEN ADMIN/MS |
|
18401974 |
NEED OBTOOL COMMAND TO IMPORT RMAN BACKUPPIECE FROM TAPE |
|
18385954 |
HANG IN RDS/RDMA - OSB 10.4.0.3.1 RESTORE HANG |
|
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 |
|
18321680 |
IB INTERFACE PNI SELECTION HAPPENS ONLY WHEN PNI IS SET FOR MOVER AND DATASRVC |
|
18036402 |
OBNDMPD NEEDS TO BE ABLE TO PROVIDE LOW LEVEL DEBUG OUTPUT DOWN TO CDB LEVEL |
|
17957225 |
OFFLINE ATTACH POINT GETTING PICKED WHEN OPENING LIBRARY |
|
17782708 |
INCREMENTAL DATAFILE BACKUP SET RESTORE (OSB, SBT) HANGS |
|
17652407 |
STACK TRACE BACK OPTION REQUIRED ON OSB |
|
17652083 |
ORACLE PARENT JOB SHOULDN'T BE DISPATCHED TO RUN ON MEDIA SERVER |
|
17558994 |
PASS NDMP ENV VARIABLE THRU DATASET |
|
17454577 |
RMAN PIECE RESTORE FAILS WITH "ERROR: COULD NOT ATTACH TO SBT SHARED MEMORY" |
|
17361371 |
OSB NOT SEARCHING FOR ANOTHER USABLE SLOT. PICKING UP SAME MEDIA |
|
17354051 |
RDMA NOT SELECTED WHEN PNI AS IB INTERFACE IS CONFIGURED. OSB USES RDS |
|
17326952 |
JOB EXITING WITH STATUS 138, MAKING OBTAR TO CORE |
|
17252456 |
BIGBH:OSB VERSION REPORT ERROR AFTER UPGRADE TO OSB 10.4.0.3.0 |
|
17017158 |
OSB - MEDIA BARCODE AL0019, MEDIA LABEL SHOWS BARCODE AL0017 |
|
16996157 |
OSB REPORTS NDMP REMOTE TAPE WITH MULTIPLE DATASET RESTORE REACH END OF TAPE |
|
16929708 |
BACKUP KEEPS GOING IN LOOP AND NEVER COMES OUT |
|
16872289 |
BACKUP OPERATION USES VOLUME WITHOUT BARCODE EVEN IF MEDIA/BARCODESREQUIRED YES |
|
16863112 |
BARCODE LABEL (DUPLICATE BARCODE) CORRUPTION |
|
16757577 |
ALL ATTACH POINTS BEYOND THE FIRST ARE IGNORED EVEN WHEN 1ST HOST IS OUT OF SVC |
|
16689000 |
OSB ROBOT IS HANGING AND NO JOBS ARE MOVING |
|
16597934 |
VFYLIB IS IGNORING LIBRARY ARG |
|
16444130 |
REL7-ST2:SPARC:FABR: DIRECTORIES NAMED "FILES" ARE NOT BACKED UP UNDER BI |
|
16436462 |
UNABLE TO USE AN ACSLS DRIVEN CAP IN A SL8500 LIBRARY |
|
16264272 |
INCOMPLETE/BAD FILE MARKER, TAPE CLOSE CAUSING EOM GOING BACK TO BOT SILENTLY |
|
16095737 |
AUTOMOUNTER UNLOADS AND RELOADS THE SAME TAPE AFTER MOUNT FAILS |
|
14306027 |
RMVOL CONFUSION WHEN MULTIPLE VOLUMES SPECIFIED |
|
14136914 |
PROVIDE --INCLUDES FOR LSVOL BY TAPE/VOLUME ID |
|
12534836 |
POSITIONQUERYFREQUENCY SHOULD BE RENAMED |
|
9989809 |
FAILED TO CREATE SEQUENTIAL FILE A FILE NAME ALREADY EXISTS IN OSB |
|
9955877 |
SCHEDULER SHOULD IGNORE "VOLUME NOT FOUND IN LIBRARY" ERRORS FOR VAULTING JOBS |
|
9921251 |
ACSLS LOADS WRITE PROTECTED TAPES |
|
9071034 |
MORE VERBOSE OUTPUT FOR RESTORES |
|
8866305 |
OSB - NEED ABILITY TO BACKUP / RESTORE ACLS ON SOLARIS (PARTICULARLY ZFS FILES) |
|
8350968 |
OSB NT MS/CLIENT UNINSTALL SHOULD OFFER OPTION TO KEEP/DELETE DB DIRECTORY |
|
7581909 |
SHOULDN'T BE ABLE TO ENTER NON-EXISTANT CALENDAR DATES |
|
7494240 |
IMPORT AND CATALOG NDMP BACKUPS INTO ANOTHER OSB DOMAIN |
|
6486165 |
DUPLICATION AT BACKUP IMAGE LEVEL INSTEAD OF TAPE LEVEL |
This section discusses Oracle Secure Backup release 12.1.0.1 outstanding bugs and known issues.
Table 1-2 Oracle Secure Backup 12.1.0.1 Open issues
| Associated Bug Number | Issue |
|---|---|
|
18161417 |
Catalog Import of Pre-12 Tape Not Supported |
|
18095423 |
MAXBLOCKINGFACTOR Set in Policy Supersedes MBF Set on Drive |
|
18143673 |
CPINSTANCE Job Fails to Create Instance From Duplicate Volume |
|
17753203 |
Upgrade Using a Different OSB_HOME Doesn't Work |
|
18549764 |
CATALOG: Unable to Catalog Duplicated Volume in another Domain |
|
18788887 |
Instance Job Fails When Source Volume is of Higher Block Size than Target Volume |
|
18456068 |
Copy Instance Job Reports End of Tape When Using Filer Attached Device For Database Backup |
|
18966915 |
Volume Label Data Missing from Copy Job |
|
19484198 |
Win64 Uninstall Problem, Error: Can't Remove (*nix Client) Indices.cur File |
|
19375600 |
Attempt at a Post Upgrade(10.4->12.1)Restore Can't Find Tape That is in a Drive |
|
19816010 |
Backslash \ in Win64 Dataset File Not Interpreted Properly in WebTool GUI |
|
18902560 |
Oracle Secure Backup WebTool does not Support DISCOVERDEV Interactive Mode on Windows |
|
19319641 |
Discrepancy Between LSJ Output and Job Transcript Output For the Restore Job |
|
19489648 |
Backup to a Disk Pool Job is not Canceled after Replying QUIT to a Disk Full Prompt |
|
19315728 |
LSBI and LSBK Do Not Report Expiration For Instance Written To Tape Volume |
|
19834759 |
WebTool GUI - Restore Doesn't Work After Using FIND to Find a File |
|
19951942 |
ZFS Storage Appliance is not Supported as a Media Server |
|
19422017 |
Limitation on the Number of Active Jobs |
The new catalog command does not support volumes that were written by earlier versions of Oracle Secure Backup. The catalog job will improperly request assistance from the user to load another volume.
Workaround: Quit the catalog job and catalog the archives on the tape with the pre 12.1 manual method that uses obtar -tG to catalog the archives on the tape.
The max blocking factor set in global policy is given priority over the max blocking factor set on drive during volume selection for backup.
Workaround: Set the policy level max blocking factor to equal or higher than highest max blocking factor on a device.
The cpinstance command can not use a duplicate volume as the source container. The copy instance job will fail with the error that the job requires the original volume. There is no work around for this issue. The original volume must be available to be used by the copy instance job. The user can still create an duplicate of the volume by using obtool dupvol.
Upgrade from Oracle Secure Backup 10.4.0.3 to Oracle Secure Backup 12.1 can not use a different Oracle Secure Backup home location.
The new catalog command will fail to catalog a duplicated volume in a new domain. The catalog command requires the original volume.
Workaround: Use the original volume or manually catalogue the volume with obtar -tG.
This issue occurs when copying a backup image instance from a tape volume to another tape volume. If the source tape was written with a larger blocking factor than the destination tape then the copy instance job will record a block size error and the job will go into a pending for resource try-able state.
Workaround: Cancel the job and use an unlabeled volume for the copy instance job.
The copy instance job will go into a pending for resources state when the source volume is in a tape device that is attached to a NDMP filer. This issue occurs only when copying a database backup image.
Workaround: Use a tape device that is attached to an Oracle Secure Backup media server.
The job transcript for a copy instance job does not contain volume label information.
Workaround: Set copy instance copyoption debug policy. The obtool command is: setp copyinstance/copyoptions -d
A clean uninstall of Oracle Secure Backup 12.1 of an Administrative Server on the Windows platform does not remove the indices.cur files for the domains hosts. This results in a partial OSB_HOME directory remaining on the server.
Workaround: Manually delete the /OSB_HOME directory after the uninstall.
If a tape is in a device during the upgrade to Oracle Secure Backup 12.1 then that tape will not be in the Oracle Secure Backup 12.1 inventory.
Workaround: Unload all tapes before upgrading or after upgrade unload the tape and re-inventory the library.
\ in Win64 Dataset File Not Interpreted Properly in WebTool GUIThe Oracle Secure Backup WebTool can not properly use a backslash \ for Window client datasets. This issue occurs when using a non-Windows administrative server and adding or editing a dataset for a Windows client.
Workaround: Use Unix style forward slash / for pathnames, for example: include path D:/
The interactive mode for discovering devices does not function properly in the Oracle Secure Backup WebTool on a Windows administrative server.
Workaround: Use the Automatic Configure Discovered Devices option and then remove the unwanted devices.
A multi-path file system restore job will report a successful restore job but the restore job transcript will report that some restore paths have not started. These not started messages can be ignored as long as the restore job succeeded. This can also occur in a wildcard restore which resulted in multiple paths that are restored.
This issue occurs during with a backup of either a Solaris x64 or Solaris SPARC client and to a disk pool on remote media server. If the storage device that contains the disk pool becomes full during the backup the backup job may request manual intervention. Selecting quit does not automatically cancel the job.
Workaround: Enter quit and then manually cancel the job.
The lsbi and lsbk commands do not report the expiration dates of backup image instances that are contained on volume sets. The backup image instances that are written to a volume set will have the expiration date of that volume set.
Workaround: Use lsvol to determine the expiration date of the volume set that contains the backup image instance.
The Oracle Secure Backup WebTool can not be used to both search a file and then restore the file that was found by the search. The WebTool does not set the host to the host used for searching for the file.
Workaround: First browse the host to be restored then search for the file.
The ZFS Storage Appliance Software may permanently corrupt existing backups that have been created using Network Data Management Protocol (NDMP) with Oracle Secure Backup. The corruption occurs when subsequent NDMP restore operations are initiated in any configuration using the ZFS Storage Appliance as a NDMP Media Server. This problem does not exist when using an Oracle Secure Backup host as the Media Server. A patch or upgrade of the ZFS Storage Appliance NDMP software that fixes bug 19951942 is required to use the ZFS Storage Appliance as a Media Server.
See Also:
My Oracle Support note 1955089.1 for more information.
The Oracle Secure Backup job scheduler has an active job maximum limit of 1,000 jobs and any concurrent jobs over the 1,000 job threshold are not processed and must be manually canceled. If the 1,000 active (running) job limit is exceeded, the can't add read ev from new socket 1024 - bad event type error message appears in the observiced log file, which resides on the Oracle Secure Backup administrative server. If the combined total of all actively running scheduler jobs such as backup, restore and / or copy instance jobs exceeds 1,000, this situation will occur and require operator assistance to manually cancel and then restart the job(s) as appropriate.
The information in this section applies only to Oracle Secure Backup 12.1.0.2.
This section briefly describes the new functionality in Oracle Secure Backup 12.1.0.2.
Oracle Secure Backup 12.1.0.2.0 provides a method for renewing domain SSL certificates and specifying a new lifetime of the domains SSL certificates. The SSL certificates can be renewed automatically or manually for increased security.
Oracle Secure Backup 12.1.0.2.0 provides a means for setting the priority of an RMAN backup or restore job. The job priority can be set by an RMAN environment variable using the ENV parameter of the PARMS option on the CONFIGURE or ALLOCATE CHANNELcommands. The job priority can also be set in the Oracle Secure Backup Database Storage Selector.
Oracle Secure Backup 12.1.0.2.0 will support both Oracle Enterprise Linux version 7 and Microsoft Windows 10.
The following table lists all bugs fixed in Oracle Secure Backup 12.1.0.2.
Table 1-3 Oracle Secure Backup 12.1.0.2 Fixed Bugs
| Bug Number | Subject |
|---|---|
| 17753203 | UPGRADE USING A DIFFERENT OSB_HOME DOESN'T WORK |
| 17979844 | BACKUP TO VOLUMES HAVING INCOMPLETE BACKUP DATA GOES TO PENDING STATE |
| 18084509 | ADD SUPPORT FOR AN INSTALL OPTION: "SETUP -- DEBUG" |
| 18161417 | CATALOG IMPORT OF PRE 12 TAPE FAILS WITHOUT PROPER ERROR MSG |
| 18456068 | INSTANCE JOB REPORTS END OF TAPE WHEN USING FILER ATTACHED SOURCE DEVICE FOR DB COPY JOB RESULTS IN VOLUME SWAP |
| 18549764 | CATALOG : UNABLE TO CATALOG DUPLICATED VOLUME IN ANOTHER DOMAIN |
| 18807100 | SUNFILER ZFS TYPE BACKUP ON DISK COMPLETES WITH WARNINGS |
| 18826368 | INSTANCE IMAGE ON DISK IS NOT REMOVED IF INSTANCE JOB IS CANCELLED |
|
18874112 |
CATALOGING DISK POOL IMPORTS INCOMPLETE IMAGES |
|
18902560 |
Oracle Secure Backup WebTool does not Support DISCOVERDEV Interactive Mode on Windows |
| 18955070 | WEBUI: INTERACTIVE CONFIGURATION OF DEVICES AFTER REMOVAL IS NOT WORKING |
| 19152992 | OSB DOES NOT DETECT NDMP CONNECTION CLOSURE |
| 19177751 | REMOVING A DEVICE CAUSES SCHEDULES THAT HAVE IT AS A RESTRICT TO DISAPPEAR |
| 19315728 | LSBI AND LSBK DO NOT REPORT EXPIRATION FOR INSTANCE WRITTEN TO TAPE VOLUME |
| 19319641 | DISCREPANCY BETWEEN LSJ OUTPUT AND JOB TRANSCRIPT OUTPUT FOR THE RESTORE JOB |
| 19489648 | Backup to a Disk Pool Job is not Canceled after Replying QUIT to a Disk Full Prompt |
| 19563208 | OBIXD FAILED TO SEND EMAIL NOTIFICATION |
| 19600324 | RATAPE ORACLE SECURE BACKUP : 'OPERATION TIMED OUT (FSP NETWORK SERVICES MANAGER |
| 19785076 | PNI FOR TCP/TCP6 NOT HONORED AFTER MKPNI |
| 19788825 | ON ERROR, WRAPPER SHOULD PROVIDE TEXT CORRESPONDING TO ERROR CODE |
| 19816010 | BACKSLASH "\" IN WIN64 DATASET DESC FILE NOT INTERPRETED PROPERLY IN UI |
|
19833937 |
WHEN RESTORING TO AN ALT PATH IN THE UI, ORIGINAL FULL PATH SHOULD BE DISP |
| 19834759 | WEB TOOL RESTORE DOESN'T WORK AFTER USING FIND TO FIND A FILE |
|
19877451 |
WEB TOOL SEARCH DOESN'T SHOW ALL RESULTS WHEN SEARCHING MULTIPLE HOSTS |
|
19951942 |
ZFS Storage Appliance is not Supported as a Media Server |
|
20364788 |
OSB WEB UI SHOULD DISPLAY RELEVANT DATA IN ITS POPUP CALENDARS |
|
20431544 |
THE NUMBER OF CONCURRENT JOBS FOR A DISK POOL NEEDS TO BE DEFAULTED TO ONE |
|
20480211 |
LSBKUP AND LSINSTANCE DONT REPORT DATA FOR DUPLICATE VOLUMES |
|
20493388 |
PREVENT ACTIVE/NEW BACKUPS TO DISK FROM BEING MARKED AS ORPHANS |
|
20562072 |
WEBTOOL EDITING A SCHEDULE THAT CONTAINS A DIRECTORY DATASET GETS UNSELECTED |
|
20643910 |
BACKUP JOBS TO THE DISKPOOL ARE STUCK IN RETRY |
|
20675071 |
BACKUP TO TAPE WITH ENCRYPTDATAINTRANSIT GOES TO PENDING STATE WITH AIX MS |
|
20809842 |
ENCRYPTDATAINTRANSIT FEATURE NOT IMPLEMENTED FOR CPINSTANCE |
|
20975484 |
UI ISSUE WHEN ONLY 1 JOB IS LISTED ON MANAGE>JOBS (ERROR: JOBS NOT SELECTED) |
|
21102877 |
GUI RESTORE SEARCH OPTION IS NOT WORKING AS EXPECTED |
|
21122804 |
INSTALL SHOULD PROMPT USER IF .HOSTID FILE IS MISSING |
|
21137183 |
OSB ISSUE WARNINGS ON LSINSTANCE OUTPUT |
|
21137230 |
OSB CPINSTANCE USES TAPE DRIVE TO MIGRATE AN INSTANCE, INSTEAD OF DISK POOL |
|
21139473 |
RMAN CROSSCHECK FAILING WITH OSB CATALOG |
|
21185861 |
UNLABELED VOLUMES ARE NOT USED IN PASS 3 |
|
21286771 |
WHEN PROBLEM WITH CPINSTANCE MIGRATE, JOB RESTART FROM THE BEGINNING OF LIST |
|
21294597 |
ACSLS CAP SIZE REPORTED BY LSDEV IS WRONG WHEN THE CAP IS IN USE |
|
21299300 |
ISSUES WHEN MIGRATING INSTANCES FROM DISK POOL TO TAPE USING CPINSTNANCE6368 |
|
21303922 |
BACKUP JOB TO DISK POOL EXITED WITH STATUS 97 BUT INSTANCE CREATED |
|
21313646 |
BACKUP FAILING WITH MESSAGE FAILED DUE TO SIGNAL 13 |
|
21327560 |
FAILED OSB JOB GETS CATALOGED AND BACKUP IMAGE/INSTANCE ARE CREATED |
|
21349875 |
BACKUP LEVEL NOT UPDATED WHEN MIGRATING CPINSTANCE |
|
21441681 |
[RDS]LOCAL CATALOG COPY DURING BACKUP JOB ON ADMIN HOST WITH RDS INTERFACE FAILS |
|
21443526 |
APACHE NON RESPONSIVE ON HPUX SOCKET ERRORS |
|
21516534 |
[RDS] ALL BACKUPS SHOULD USE RDMA/RDS WHENEVER POSSIBLE |
|
21521019 |
LSPIECE BAD OBJECT ID |
|
21531493 |
[CPINSTANCE] CDF/RAW FILES GETS DELETED BEFORE BEING PUT ON TAPE |
|
21764519 |
FIND COMMAND PERFORMANCE NOT GOOD WHEN SEARCHING IN DIRECTORY |
|
21956975 |
CPBI MIGRATION JOB REMAINS IN RETRYABLE STATE IF IMAGE IS NOT AVAILABLE ON DISK |
| 22106604 | NETWORK CONNECTION SHOULD BE BASED ON HOST IPNAME ORDERING |
| Associated Bug Number | Issue |
|---|---|
| 18095423 | MAXBLOCKINGFACTOR Set in Policy Supersedes MBF Set on Drive |
| 18143673 | CPINSTANCE Job Fails to Create Instance from the Duplicate Volume |
| 18788887 | INSTANCE JOB FAILS WHEN SOURCE DATA IS OF HIGHER BLOCK SIZE THAN DEST VOLUME |
| 18966915 | NO VOLUME ID IN COPY JOB IN NON VERBOSE MODE |
| 19452711 | DEVICE LSBU IS INCORRECT FOR INSTANCE CREATED BY CPINS |
| 19641664 | QUITTING A CPINSTANCE JOB IN MANUAL INTERVENTION MODE SHOWS ERROR MESSAGES |
| 22110911 | ZFS SA WITH LOCALLY ATTACHED TAPE DEVICE IS LIMITED TO 512 BLOCKING FACTOR |
| 22102036 | CPINSTANCE FROM TAPE TO TAPE FAILS TO WRITE TO EXPIRED VOLUME OF LOWER BLOCK SIZE |
| 22096040 | After Domain Recertification, RMAN backups of Window Database Clients will Fail |
Workaround: Set the policy level max blocking factor to equal or higher than highest max blocking factor on the devices in the domain.
Workaround: CPINSTANCEcan only use the original volume. If only the duplicate volume is available then dupvol command can be used to create a copy if the volume.
Workaround: Ensure that Blocking Factor for the diskpool is same as the blocking factor for the tape devices in the domain.
Workaround: Set copyinstance\copyoptions policy to -d.
Workaround: Get the device information from the cpinstance job transcript.
Workaround: Cancel the job after replying quit.
Workaround: The blocking factor of the tape devices locally attached to the ZFS SA must be set to 512 or lower. Backups made with blocking factor over 512 will fail to restore.
Workaround: Unlabel the expired volume. To avoid the problem the blocking factor for all tape devices in the domain must be the same.
Workaround: Restart Oracle Secure Backup on the Window clients after recertification.
The information in this section applies only to Oracle Secure Backup 12.1.0.3.
This section contains the following topics:
This section briefly describes the new functionality in Oracle Secure Backup 12.1.0.3.
Assign ownership for backup jobs
Ownership of file-system backup jobs can be transferred to an Oracle Secure Backup user who is different from the user who created the backup.
Network interface selection for hosts
You can configure a Preferred Network Interface (PNI) for outbound connections from a host.
Secure client installation
New clients can be securely registered into the Oracle Secure Backup domain by verifying the identity of the host that initiated the request to add the new client. The user is required to supply the identity of that host during the client installation.
See Also:
Oracle Secure Backup Installation and Configuration Guide for more information on client installation
Restrict untrusted hosts in the administrative domain
You can use Oracle Secure Backup policies to control whether Oracle Secure Backup accepts jobs from an untrusted client hosts (hosts that are not the administrative server or media server).
This section lists the bugs that have been fixed in Oracle Secure Backup 12.1. 0.3.
Table 1-4 Oracle Secure Backup 12.1.0.3 Fixed Bugs
| Bug Number | Subject |
|---|---|
|
24790639 |
IDENTIFYVOL AND IMPORTVOL --IDENTIFY LEAVES ARCHIVES DATABASE IN INCORRECT STATE |
|
24744879 |
RESTORE --USER NEEDED FOR FILE SYSTEM SUPPORT IN ZDLRA |
|
24736573 |
SUPPORT A LIST OF AUTHORIZED SECURE REGISTRATION SOURCES |
|
24621686 |
INSTALLER - TEXT/CODE CHANGES TO CLARIFY USE OF "ADDING HOST INITIATOR NAME" |
|
24614464 |
DAILY CROSSCHECK JOBS ARE DETECTING THAT CU IS LOOSING BACKUPS |
|
24574534 |
CVE-2016-6290: UPGRADE PHP TO 5.6.24, 7.0.9 OR LATER |
|
24571942 |
BACKUP JOB EXITED WITH SIGNAL 11 - OBTAR SEGFAULT WHEN USEONLY PNI IS SET TO RDS |
|
24455554 |
CPINSTANCE INCORRECTLY PUTS DEVICES IN "AUTO NOT IN SERVICE" |
|
24391724 |
CATALOG UPDATE PROCESS TERMINATED WITH ERROR - OBIXD SUBPROCESS EXITED PREMATURE |
|
24377143 |
CPINSTANCE INCORRECTLY PUTS DEVICES IN "AUTO NOT IN SERVICE" |
|
24346114 |
BACKUP FAILURE WHEN REMOTE PNI (CLIENT) CONFLICTS WITH ONI FOR A HOST |
|
24332613 |
INSTALL UPGRADE: OSB VERSION NUMBER STORED IN OBCONFIG IS NOT UPDATED |
|
24298493 |
OBPROXYD SOME MESSAGES LOG LEVEL TO BE CHANGED |
|
24012031 |
UPGRADE OSB TO APACHE 2.4.23 AND PHP TO 5.6.23 |
|
24011483 |
CPINSTANCE ERROR HANDLING |
|
23733666 |
"CHHOST --ROLES ADMIN" SHOULD BE ALLOWED IF THE HOST IS ALREADY AN ADMIN |
|
23735000 |
MKPNI SEGFAULTS WITH --NETWORK OPTION |
|
23637678 |
MIGRATE OSB - ERROR: VOLUME ID ON MEDIA %S DOES NOT MATCH VOLUME ID REQUESTED |
|
23618824 |
ENHANCEMENT: "ERROR: TRUST CHECK FAILURE" SHOULD BE REPORTED BY MKHOST COMMAND |
|
23585153 |
WEB TOOL DOESN'T SET MEDIA POLICY OVERWRITE BLANK TAPE CORRECTLY |
|
23555285 |
OSB CLIENT 12.1.0.1.0, 12.1.0.2.0 AND 12.1.0.2 CANNOT BE INSTALLED ON LINUX 6.6 |
|
23526094 |
ACCEPT JOBS ONLY FROM TRUSTED HOST |
|
23484950 |
DISKPOOL FREESPACE GOAL SET TO 100% |
|
23322756 |
MKHOST AND CHHOST SHOULD DISALLOW ADDING/REMOVING ADMIN ROLE |
|
23307931 |
APACHE DAEMONS DON'T COME UP ON INITIAL INSTALL, SOLARIS SPARC & X86 |
|
23300475 |
UPGRADE APACHE, OPENSSL, AND PHP |
|
23277609 |
SV12.1.0.3.0WEBINSPECT: WEAK SSL CIPHER AND PROTOCOL IN ORACLE SECURE BACKUP |
|
23277559 |
SV12.1.0.3.0WEBINSPECT: POTENTIAL CROSS FRAME SCRIPTING IN ORACLE SECURE BACKUP |
|
23277442 |
SV12.1.0.3.0WEBINSPECT: POTENTIAL SESSION FIXATION IN ORACLE BACKUP |
|
23275414 |
ACCESSIBILITY TESTING - TEST OSB 12.1.0.3.0 AGAINST OAG 2.0 PRIOR TO RELEASE |
|
23242736 |
ALLOW PRIVILEGED USER TO CHANGE OWNERSHIP OF JOB |
|
23237092 |
OVERWRITEFOREIGNTAPE DEFAULTED TO YES |
|
23174416 |
OSB SERVICES OBSERVICED CRASHING ON ADMIN SERVER |
|
23172642 |
OSB RESTORE USER NOT ABLE TO RESTORE DATA IN GUI |
|
23139379 |
ADD SUPPORT FOR ENCRYPTION, LTO6 & IBM LTO7 DRIVES |
|
23113852 |
OBCLEANUP DOES NOT REMOVE BACKUP IMAGE AND BACKUP INSTANCE |
|
23039531 |
FULL DISK POOL NOT CLEANED UP BY SCHEDULER |
|
23000091 |
OBTOOL MANAGEDEV COMMAND NEEDS SAME DELETED IMAGES FIX AS OBPOOLMGR |
|
22980554 |
OSB 'WARNING: UNABLE TO RESET ENCRYPTION - REVERTING TO SOFTWARE ENCRYTION' |
|
22977363 |
OSB JOB STUCK WITH THE LINE "RDB: ADDING RECORD FOR OID 63925" |
|
20638950 |
UPGRADE: 10.4.0.3 TO 12.1 UPGRADE RESETS OPERATOR (AND ADMIN) CLASS RIGHTS. |
|
22891093 |
NDMP BACKUP FAILED WITH STATUS 98 INSTEAD COMPLETING PARTIALLY |
|
22695592 |
RECERTIFYDOMAIN FAILS ON 12.1.0.2 AFTER UPGRADE FROM 10.4.0.3 |
|
22876356 |
VFYLIB REPORTING STRANGE CHARACTERS FOR ULTRIUM 5-SCSI ABOUT SERIAL NUMBER |
|
13356198 |
ALL UNIX PLATFORMS SHOULD HAVE A COMMON STOP AND START COMMAND |
|
22836387 |
OBPOOLMGR CRASHES IF DELETEORPHANS IS RUN AND THERE IS NO ACTIVE DIRECTORY |
|
22836023 |
RMAN DELETEPIECE LEAVES ORPHANS IN DISK POOLS |
|
22826431 |
OSB WEBTOOL DOESN'T SHOW DIR CONTENT IF THERE IS A GREEK CHARACTER IN THE PATH |
|
22464039 |
CAN'T OPEN ACSLS CONTROLLED DRIVE. THE DEVICE IS NOT AT DEFINED TARGET |
|
22353235 |
NDMP_TAPE_CLOSE FAILED DUE TO WRITE-FILEMARK ERROR |
|
22283677 |
EXCESSIVE PERMISSIONS ON ORACLE SECURE BACKUP LOG FILES |
|
22283655 |
TCP FLOOD DOS AGAINST THE SECURE BACKUP OBPOOLMGR DAEMON |
|
22283578 |
DEFAULT KEY LENGTH FOR CERTIFICATES IS TOO SHORT IN OSB (1024 BIT) |
|
22283557 |
INSECURE INITIAL REGISTRATION OF OSB CLIENTS |
|
22274822 |
NETAPP FILER BACKUP PARTIALLY COMPLETES WITH NON ROOT OSB USER |
|
22110911 |
ZFS SA AS MEDIA SENDS EOF WHEN DATA IN BUFFER RESULTING IN RESTORE FAILURE |
|
22080000 |
REMOVE DISABLE HARDWARE ENCRYPTION FROM WEB TOOL FOR COPY BACKUP IMAGES |
|
21882426 |
POST UPGRADE OSB TO 12.1.0.1.0 BACKUP FAILS "COMMUNICATIONS FAILURE WITH CLIENT" |
|
21843834 |
LOGIN FAILED, THE OBTOOL PROGRAM IS NOT PROTECTED PROPERLY |
|
21841208 |
OBHTTPD SENDS OBSERVICED A TERMINATION SIGNAL UPON EXIT |
|
21697083 |
SOLARIS SPARC,X86 - SERVICE DAEMON IS NOT STARTED WHEN HOST IS REBOOTED |
|
20033240 |
WEBTOOL FAILS SUBMITTING PASSWORD WHEN USING CPINSTANCE AND TRANSIENT ENCRYPTION |
|
19823170 |
IMPROVE REMOVING DISKPOOL IN WEBUI |
|
19385117 |
Misc. UI ISSUES |
|
18884595 |
OBSERVICED SCRIPT UNABLE START SERVICE USING RESTART OPTION ON LINUX |
|
18082520 |
WHEN CREATING A DISK DEVICE THE --FORCE OPTION IS NOT AVAILABLE |
|
18063163 |
NO FORCE OPTION FOR REMOVING A BACKUP IMAGE INSTANCE |
|
14774218 |
WEB UI SHOULD DISPLAY A REASON WHEN LOGGING OUT A USER DUE TO A TIMEOUT |
|
13003481 |
A PIECE SPANNING MULTIPLE VOLUMES SHOWS VOL NAMES JOINED IN MANAGE>DB BU PIECES |
This section discusses Oracle Secure Backup 12.1.0.3 outstanding bugs and known issues.
Table 1-5 Oracle Secure Backup 12.1.0.3 Open issues
| Associated Bug Number | Issue |
|---|---|
|
22096715 |
BACKUP FAILS DURING CATALOG COPY IF LOCAL RDMA CONNECTION IS USED |
|
24358800 |
PNI --USEONLY FAILS TO DISTINGUISH BETWEEN RDS AND IPV4 |
|
23250387 |
COPYINSTANCE FAILS IF INSTANCES BELONG TO DIFFERENT VOLUMES IN THE SAME LIBRARY |
|
24562209 |
IMPROPER HANDLING OF ERROREOUS SYNTAX IN MKPNI NETWORK OPTION |
|
23724229 |
REMOVE PNI COMMAND DOESN'T HAVE OPTION TO REMOVE PNI CREATED BY --USEONLY OPTION |
BACKUP FAILS DURING CATALOG COPY IF LOCAL RDMA CONNECTION IS USED
Workaround: A file system backup job fails if the Administrative server is also the media server when backing up a client over a RDS/RDMA connection. The workaround is to use a separate host as the Administrative Server or to disable RDS on the Administrative/Media server.
PNI --USEONLY FAILS TO DISTINGUISH BETWEEN RDS AND IPV4
Workaround: You must use the PNI –network option to force the use of the RDS connection as the outgoing connection.
COPYINSTANCE FAILS IF INSTANCES BELONG TO DIFFERENT VOLUMES IN THE SAME LIBRARY
Workaround: The list of instances for the copy instance command must all be on the same volume set.
IMPROPER HANDLING OF ERROREOUS SYNTAX IN MKPNI NETWORK OPTION
Workaround: The list of IP address cannot contain multiple comas such as mkpni -n 10.137.32.143/24,,10.137.32.143.
REMOVE PNI COMMAND DOESN'T HAVE OPTION TO REMOVE PNI CREATED BY --USEONLY OPTION
Workaround: Use the new command option for chpni to remove the outgoing network, chpni –rmnetwork <ip address> or chpni –rmuseonly <ip address>.
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.
Access to Oracle Support
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 12.1
E16566-07
Copyright © 2006, 2016, 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.