asigra - rman interface_description

Asigra Cloud Backup™ - ORACLE-SBT Generated on: 10/11/2012 v12.0 [Revision Date: May 31, 2012] Page: 1 of 28. © Asigra Inc. All Rights Reserved. Confidential.

ASIGRA DS-Client ORACLE-SBT (System Backup to Tape)

Interface

Data is sent to DS-System instead of Tape.

AUDIENCE This document assumes the audience has read the following documents and can apply all their knowledge about RMAN when using the ASIGRA DS-Client ORACLE-SBT functionality:

Oracle® Database Backup and Recovery User's Guide 11g Release 2 (11.2) E10642-01.

Oracle® Database Backup and Recovery Reference 11g Release 2 (11.2) E10643-01 (for RMAN Commands and Syntax)

This document contains a set of exercises and examples on how to apply RMAN functionality and usability with the ASIGRA ORACLE-SBT Library. It is intended for Oracle database administrators (DBAs) who perform the following tasks:

Back up, restore, and recover Oracle databases.

Perform maintenance on backups of database files. VERY IMPORTANT NOTE To use this document, you must know the following:

Relational database concepts.

Database administration skills as described in Oracle Database Administrator's Guide.

Operating system environment on which you are running the Oracle database.


CONTENTS Introduction to Backup and Restore/Recovery using ASIGRA ORACLE-SBT ............................................................3

How it works .........................................................................................................................................................3

Overview Diagram ................................................................................................................................................4

Getting Started with ASIGRA ORACLE-SBT backup using RMAN ..........................................................................5

Step-by-step instructions how to configure ASIGRA ORACLE-SBT ...........................................................................6

1. Configuration of DS-Client Server .....................................................................................................................6

1.1 Create the Backup Set on the DS-Client side ..............................................................................................6

1.2 Configure the DS-Client for API access .......................................................................................................8

2. Configuration on the ORACLE Server ...............................................................................................................9

2.1 Configure the ORACLE-SBT Library .............................................................................................................9

2.2 Copy the ORACLE-SBT Libraries (for the corresponding Operating System) to the ORACLE SERVER ..... 12

2.3 Create ASIGRA BACKUP USERS on the Oracle Server .............................................................................. 15

3. Run a test backup from the Oracle Server using RMAN Command Line ...................................................... 16

4. Asigra Oracle-SBT Advanced Usage Topics .................................................................................................... 17

5. Restoring as pure files from DS-System (or from Disc/Tape or from BLM)................................................... 19

6. Troubleshooting ............................................................................................................................................ 20

7. Configuring the Oracle Enterprise Manager to backup using Asigra Oracle-SBT .......................................... 21

8. Known Issues ................................................................................................................................................. 22

8.1 Error message on restore ........................................................................................................................ 22

8.2 Retention ................................................................................................................................................. 22

8.3 HPUX 11.31 patch updates ...................................................................................................................... 22

8.4 Multiple sessions (backup / restore) ....................................................................................................... 23

8.5 Parameter File ......................................................................................................................................... 23

8.6 Backup Set name length .......................................................................................................................... 23

8.7 DS-Client functionality (un)available to Oracle-SBT backup sets. ........................................................... 24

8.8 Workaround to quickly catalog multiple backup pieces ......................................................................... 24

8.9 Alternate or Disaster Restore requires manual creation of the data directory ...................................... 28

8.10 Upgrading from v11 to v11.2 (IMPORTANT READ THIS NOTE) ............................................................. 28


Introduction to Backup and Restore/Recovery using ASIGRA ORACLE-SBT

How it works

The DS-Client Oracle-SBT interface allows the Oracle RMAN to interact with the DS-Client through the ORACLE-SBT protocol. This protocol allows RMAN to send backup data to the DS-Client, restore data from the DS-Client, as well as catalog and delete items. When using the Oracle-SBT protocol, the DS-System just acts as a data repository (via DS-Client) and all actual operations (backup/restore) are controlled through RMAN. NOTES:

If you are using the controlfile as RMAN Repository, you may need to increase the CONTROL_FILE_RECORD_KEEP_TIME=integer to keep the maximum ORACLE backups records in the controlfile.

It is recommended to setup CONFIGURE CONTROLFILE AUTOBACKUP to ON, to include a backup of the controlfile and the spfile. This will allow you to restore them and mount the database in case of Disaster Recovery. Otherwise, you must configure Recovery Catalog to keep track of all the ORACLE backup records.


Overview Diagram


Getting Started with ASIGRA ORACLE-SBT backup using RMAN

This type of backup is recommended to be used for incremental backups. The following are the main benefits:

Reduce the amount of data saved in the DS-System.

Reduce the backup window.

Reduce the amount of data transmitted over the network.


Step-by-step instructions how to configure ASIGRA ORACLE-SBT

1. Configuration of DS-Client Server

In order to use the ASIGRA ORACLE-SBT library, the Oracle Server must be told which DS-Client to connect to, and where to store the data (in what backup set). This is done in the steps outlined below.

1.1 Create the Backup Set on the DS-Client side

1) The backup set is created on the DS-Client side as an “ORACLE-SBT” backup set:

2) The backup set itself is not tied to any computer. The New Backup Set Wizard will display a

computer placeholder as well as a “share” placeholder when creating the backup set.


3) In order to control access, the New Backup Set Wizard will also prompt for an access username/password. This information is required by the Oracle RMAN client.

IMPORTANT NOTE:

The username and password are not related to the operating system or the oracle database. These credentials are only used to access the backup set. These credentials will be used on the Oracle server when you configure the “params.txt” file.

4) The backup set can be created as normal (through the Asigra DS-User interface).

IMPORTANT NOTES:

Backup and Restore is controlled through RMAN. As such, 'on-demand' and ‘scheduled’ backups do not apply to it. You can schedule retention or validation; however backup must not be scheduled for this backup set.

You should take into account that DS-Client activities (like scheduled retention or validation) may conflict with RMAN requested operations. As such, it may be a good policy not to schedule any DS-Client operations on this backup set at all.


1.2 Configure the DS-Client for API access

The ORACLE-SBT library will need to connect to the DS-Client using the Asigra Hessian API. By default, the DS-Client will only listen on the local loopback (127.0.0.1) address. To allow remote connections, you must configure the advanced DS-Client parameters to listen for the specific Oracle IP address, or for all remote connections (0.0.0.0).

1) Add the Oracle IP to the DS-Client:

2) Click “OK” or “Apply” to save the settings.

NOTE:

This is a Global Setting. It will affect all the API Connections to the DS-Client. It is recommended that you use “0.0.0.0” to listen to for all connections.


2. Configuration on the ORACLE Server

2.1 Configure the ORACLE-SBT Library

1) Create the Asigra ORACLE-SBT parameter file The ORACLE-SBT Library will know how to connect to the DS-Client by the use of a text file. The file format is:

“key/value” pairs, separated by a colon (:)

'#' starts a comment and the '\' character is used as an escape for special characters (e.g. '#' or space in values).

This text file will contain the following information:

DS-Client : specifies the DS-Client IP address/DNS name

User : specifies the username used to access the backup set. This

username does not have any relation to the DS-Client server or

the Oracle server. It is only a set of credentials that you add

to access the backup set.

Password : specifies the password associated with this user name. This can

be entered in plain text or with an encrypted key.

Backup Set : must be provided if the same username/password provides access

to several backup sets on same DS-Client. Contains the backup set

name that is going to be accessed.

Disk Source : This is used when you are trying to restore from pure files. It

should be used by itself in the “params.txt” file. It must point

to the location of the pure file(s).

IMPORTANT NOTE: The parameter “DS-Client” and the parameter “Disk Source” cannot be set at the same time on the params.txt file, otherwise you will get an error. Make sure the “params*.txt” file belongs to the Oracle user and group permissions. Example: ‘/Asigra/params_enc.txt’ – make sure there are no spelling mistakes.

DS-CLIENT : 10.20.10.10

User : test1

Password : ds1

Backup Set : ORACLE_SBT - data_dumps - orcl

2) Encrypt the Backup Set Passwords that will be used in the ASIGRA ORACLE-SBT Parameter File. To use the “asigraenc” application to encrypt the “password” in the params.txt file, do the following:

Go to the DS-Client server in the path: /opt/CloudBackup/DS-Client/Tools/

Export LD_LIBRARY_PATH=`pwd`

Run ./asigraenc on the password. For example:

[root@RH5U4DSCi7 Tools]# export LD_LIBRARY_PATH=`pwd`

[root@RH5U4DSCi7 Tools]# ./asigraenc mypassword

aes-128-cbc$8C4FEC0C140A04D005E9BD08B9A75796EC2B2F0CF1E993A8CF867D859CAC945A

[root@RH5U4DSCi7 Tools]#

Copy the encrypted password in to the “params_enc.txt” file. NOTE: Every time the “params.txt” file is modified, you must restart the dsclient service.


3) Encrypt the connection between the DS-Client and the Oracle Server using SSL.

To encrypt the connection, do the following:

Example of the Asigra ORACLE-SBT parameter file params_enc.txt using encryption between DS-Client and the Oracle server (located in ‘/Asigra/params_enc.txt’):

DS-CLIENT : 10.20.10.10

User : test1

Password : aes-128-cbc$45B3250504B60BC3ED5901C7749C13A786303C87011B0EE35FF65E27547BDEC7

Backup Set : ORACLE_SBT - data_dumps - orcl

From the DS-User GUI on the DS-Client server, the Asigra “API Key File” parameter is configured under (DS-User > Setup > Configuration > Advanced: “API Connectivity” category). The default location is “/opt/CloudBackup/DS-Client /etc/api.pem”.

On the DS-Client server, verify that the “API Key File” parameter in the “/opt/CloudBackup/DS-Client/etc/dsclient.cfg” file has been added:

API IP : 0.0.0.0

API Key File : /opt/CloudBackup/DS-Client/etc/api.pem

API Key Password : aes-128-cbc$20B0B277242385286418F89CEC1B98F23AE1D7DB82BF57369CFAFD647DE80D72

API Log File : apiserver.log

API Log Level : warning

API Port : 4411


4) UN-ENCRYPTED DATA TRANSMISSION IF YOU DO NOT NEED TO ENCRYPT THE CONNECTION BETWEEN THE DS-CLIENT AND THE ORACLE SERVER BECAUSE THE SERVERS ARE IN YOUR OWN LAN USING SSL, DO THE FOLLOWING. (The main benefit is the backup speed will be faster because it is not encrypted.) By default, the DS-Client will accept only SSL encrypted API calls and the SBT library will transmit data using SSL encryption. Faster backup speeds may be achieved by disabling SSL encryption through the following steps:

In the SBT configuration file, use the format “http://<client_ip_or_dns>:4411” to force the SBT library to connect without using SSL to the DS-Client

Example of the Asigra ORACLE-SBT parameter file params_unenc.txt not using encryption between DS-Client and the Oracle server (located in ‘/Asigra/params_unenc.txt’):

DS-CLIENT : http://10.20.10.10:4411

User : test2

Password : aes-128-cbc$45B3250504B60BC3ED5901C7749C13A786303C87011B0EE35FF65E27547BDEC7

Backup Set : ORACLE_SBT - data_dumps – orcl

From the DS-User GUI on the DS-Client server, the Asigra “API Key File” parameter is configured under (DS-User > Setup > Configuration > Advanced: “API Connectivity” category). The default location is “/opt/CloudBackup/DS-Client/etc/api.pem”. Clear this field in order to skip encryption.

On the DS-Client server, verify the “API Key File” parameter in the “/opt/CloudBackup/DS-Client/etc/dsclient.cfg” is empty.

API IP : 0.0.0.0

API Key File :

API Key Password : aes-128-cbc$4711DDE8127DF79B8968EC037CA0A624FE0074A0942BBB0338A41F2DDEC50AE8

API Log File : apiserver.log

API Log Level : warning

API Port : 4411


2.2 Copy the ORACLE-SBT Libraries (for the corresponding Operating System) to the ORACLE SERVER

These files can be found on the installation DVD in the path /Software/Tools/Oracle_SBT_Library. NOTE: Make sure the ASIGRA ORACLE-SBT library belongs to the Oracle user/group “permissions” as well as has “executable” rights.

Windows x64: dsc_ora_sbt_Windows_64.dll, libeay32.dll, ssleay32.dll, vcredist_x64.exe o Run “vcredist_x64.exe” o Copy “libeay32.dll” and “ssleay32.dll” to “$ORACLE_HOME\bin” o Copy “dsc_ora_sbt_Windows_64.dll” to “C:\asigra” folder

Windows x86: dsc_ora_sbt_Windows_32.dll, libeay32.dll, ssleay32.dll, vcredist_x86.exe o Run “vcredist_x86.exe” o Copy “libeay32.dll and ssleay32.dll” to “$ORACLE_HOME\bin” o Copy “dsc_ora_sbt_Windows_32.dll” to “C:\asigra” folder

Linux x64: libdsc_ora_sbt_Linux_x86_64.so, libssl.so.0.9.8, libcrypto.so.0.9.8 o Copy “libdsc_ora_sbt_Linux_x86_64.so” to “/asigra” folder o Copy “libcrypto.so.0.9.8” to “$ORACLE_HOME/lib” folder o Copy “libssl.so.0.9.8” to “$ORACLE_HOME/lib” folder

Linux x86: libdsc_ora_sbt_Linux_i686.so , libssl.so.0.9.8, libcrypto.so.0.9.8 o Copy “libdsc_ora_sbt_Linux_i686.so” to “/asigra” folder o Copy “libcrypto.so.0.9.8” to “$ORACLE_HOME/lib” folder o Copy “libssl.so.0.9.8” to “$ORACLE_HOME/lib” folder

Solaris SPARC: libdsc_ora_sbt_Sunos_sun4u_64.so, libstlport.so.1 o Copy libstlport.so.1 to “$ORACLE_HOME/lib” o Copy “libdsc_ora_sbt_Sunos_sun4u_64.so” to “/asigra” folder

Solaris x86: libdsc_ora_sbt_Sunos_i86pc_64.so, libstlport.so.1 o Copy “libstlport.so.1” to “$ORACLE_HOME/lib” o Copy “libdsc_ora_sbt_Sunos_i86pc_64.so” to “/asigra” folder

HPUX Itanium: libdsc_ora_sbt_hpux_ia64_64.sl o Copy “libdsc_ora_sbt_hpux_ia64_64.sl” to “/asigra”

AIX Power: libdsc_ora_sbt_AIX_powerpc.so o Copy “libdsc_ora_sbt_AIX_powerpc.so” to “/asigra” o Copy “libssl.a” to “$ORACLE_HOME/lib” o Copy “libcrypto.a” to “$ORACLE_HOME/lib”

NOTE: Asigra Oracle-SBT Libraries Pre-installation Requirements.


Packages for Oracle Enterprise Linux 5, and Red Hat Enterprise Linux 5, the following packages (or later versions) must be installed:

libstdc++-4.1.2

libgcc-4.1.2

glibc-2.5 Packages for Oracle Enterprise Linux 4, and Red Hat Enterprise Linux 4, the following packages (or later versions) must be installed:

glibc-2.3.4

libstdc++-3.4.6

libgcc-3.4.6 Packages for SUSE Linux Enterprise Server 11, the following packages (or later versions) must be installed:

glibc-2.9

libstdc++43-4.3.3

libgcc43-4.3.3

zlib-1.2.3 Packages for SUSE Linux Enterprise Server 10, the following packages (or later versions) must be installed:

glibc-2.4

libstdc++-4.1.2

libgcc-4.1.2 Packages for SUSE Linux Enterprise Server 9 SP4, the following packages (or later versions) must be installed:

glibc-2.3.3

compat-libstdc++-lsb-4.0.2

libgcc-3.3.3


2.2.1 Oracle-SBT Support Matrix

Version PlatformRed Hat Enterprise

Linux 4

Red Hat Enterprise

Linux 5

Red Hat Enterprise

Linux 6

SUSE Enterprise

Linux 10

SUSE Enterprise

Linux 11

Windows XP, 2003, 2003 R2 (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows VISTA Business, Enterprise, Ultimate (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows 2008 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Windows 2008 R2 (x64) Active Support Active Support Active Support Active Support Active Support

Windows 7 Professional, Enterprise, Ultimate (x86/x64) Active Support Active Support Active Support Active Support Active Support

Solaris 10 (SPARC 64-bit) Passive Support Active Support Passive Support Active Support Active Support

Solaris 10 Update 6 (x86_64) Passive Support Active Support Passive Support Active Support Active Support

Oracle Enterprise Linux 4 / 5 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Oracle Linux 6 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Red Hat Enterprise Linux 4 Update 7 (x86/x64) Active Support Active Support Active Support Active Support Passive Support

Red Hat Enterprise Linux 5 Update 2 (x86/x64) Active Support Active Support Active Support Passive Support Active Support

Red Hat Enterprise Linux 6 (x86/x64) Passive Support Active Support Active Support Passive Support Active Support

Suse Linux Enterprise Server 10 (x86/x64) Passive Support Passive Support Active Support Active Support Active Support

Suse Linux Enterprise Server 11 (x86/x64) Passive Support Active Support Active Support Active Support Active Support

AIX 6.1 (PowerPC 64-bit) Active Support Active Support Passive Support Active Support Active Support

AIX 7.1 (PowerPC 64-bit) Passive Support Active Support Active Support Passive Support Active Support

HPUX 11.31 (Itanium) Passive Support Active Support Active Support Active Support Active Support

Solaris 9 Update 7 (SPARC 64-bit) Passive Support Passive Support Passive Support Passive Support Passive Support

Solaris 10 (SPARC 64-bit) Active Support Active Support Passive Support Active Support Active Support

Solaris 10 (x86_64) Active Support Active Support Passive Support Active Support Active Support

Solaris 9 Update 7 (x86_64) Active Support Active Support Passive Support Active Support Active Support

Oracle Enterprise Linux 4 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Oracle Enterprise Linux 5 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Windows XP, 2003 (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows Vista Ultimate (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows Vista Enterprise (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows 2008 (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Red Hat Enterprise Linux 4 (x86/x64) Active Support Active Support Active Support Active Support Passive Support

Red Hat Enterprise Linux 5 (x86/x64) Active Support Active Support Active Support Passive Support Active Support

Suse Linux Enterprise Server 10 (x86/x64) Active Support Passive Support Active Support Active Support Active Support

Suse Linux Enterprise Server 11 (x86/x64) Passive Support Active Support Active Support Active Support Active Support

HPUX 11.31 (Itanium) Passive Support Active Support Active Support Active Support Active Support

Solaris 9 Update 6 (SPARC 64-bit) Passive Support Passive Support Passive Support Passive Support Passive Support

Solaris 10 (SPARC 64-bit) Active Support Active Support Active Support Active Support Active Support

Solaris 10 (x86_64) Passive Support Active Support Passive Support Passive Support Active Support

Windows XP Professional, 2003 (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows Vista Ultimate / Ent. (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Windows 2008 (x64) Active Support Active Support Active Support Active Support Active Support

Red Hat ES/AS Linux 3 (x86/x64) Passive Support Passive Support Passive Support Passive Support Passive Support

Red Hat ES/AS Linux 4 (x86/x64) Active Support Passive Support Active Support Active Support Passive Support

Red Hat ES/AS Linux 5 (x86/x64) Passive Support Active Support Active Support Passive Support Active Support

Suse Linux Enterprise Server 9 (x86/x64) Passive Support Passive Support Passive Support Passive Support Passive Support

Suse Linux Enterprise Server 10 (x86/x64) Active Support Active Support Active Support Active Support Active Support

Suse Linux Enterprise Server 11 (x86/x64) Active Support Active Support Active Support Active Support Active Support

HPUX 11.23 (Itanium) Active Support Active Support Active Support Active Support Active Support

Solaris 9 (SPARC 64-bit) Passive Support Passive Support Passive Support Passive Support Passive Support

Solaris 9 (x86) Passive Support Passive Support Passive Support Passive Support Passive Support

Windows XP Professional (x86/x64) Passive Support Passive Support Passive Support Passive Support Passive Support

Windows 2003 (x86/x64) Active Support Active Support Passive Support Active Support Active Support

Red Hat Enterprise Linux 3 (x86/x64) Passive Support Passive Support Passive Support Passive Support Passive Support

Red Hat Enterprise Linux 4 (x86/x64) Active Support Passive Support Passive Support Active Support Passive Support

Suse Linux Enterprise Server 9 (x86/x64) Active Support Passive Support Passive Support Passive Support Passive Support

HPUX 11.23 (Itanium) Active Support Active Support Passive Support Active Support Active Support

Solaris 8, 9 (SPARC 64-bit) Passive Support Passive Support Passive Support Passive Support Passive Support



Suse Linux Enterprise Server 9 (x86/x64) Active Support Active Support Passive Support Active Support Passive Support

HPUX 11.0 (Itanium) Passive Support Passive Support Passive Support Passive Support Passive Support

9i R2

Oracle Server Linux DS-Client

11g R2

11g R1

10g R2

10g R1

Active Support: DS-Client supports backup / restore of Oracle server. Tests were done on


the latest update/service pack version of these operating systems.

Passive Support: Asigra did not perform backup / restore tests on these platforms, but there should not be any technical limitations.

Not Supported: Oracle server backup / restore is not supported.

2.3 Create ASIGRA BACKUP USERS on the Oracle Server

It is recommended that a specific user be created only for this backup solution.

2.3.1 On the target Oracle Server

Create a user to do the backups: Example:

SQL> create user backup identified by asigra DEFAULT TABLESPACE users

temporary tablespace TEMP;

User created.

SQL> alter user backup account unlock;

User altered.

SQL> grant sysdba to backup;

Grant succeeded.

SQL> exit

2.3.2 On the recovery catalog server

If you configured the recovery catalog, create a user to keep the records of the backups. Example:

SQL> create user backup identified by asigra DEFAULT TABLESPACE users

temporary tablespace TEMP;

User created.

SQL> alter user backup account unlock;

User altered.

SQL> grant sysdba to backup;

Grant succeeded.

SQL> grant connect,resource,recovery_catalog_owner to backup;

Grant succeeded.

SQL> exit


3. Run a test backup from the Oracle Server using RMAN Command Line

Once the Asigra Oracle-SBT parameter file is created, Oracle can be configured to use the ASIGRA-provided SBT library by passing the parameter file using the 'CONNECT_INFO' environment variable. The following are basic examples of using the ASIGRA ORACLE-SBT Library: 1) To manually allocate channel(s) to backup:

Create an rman script called “backup.rman” make sure the script belongs to Oracle and it has executable permissions.

To run the script, use the command “rman @/Asigra/backup.rman”.

Make sure there are no spelling mistakes in the script. Example script:

Connect target /

Run {

ALLOCATE CHANNEL ch_sbt

DEVICE TYPE sbt

PARMS="SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/

asigra/params.txt)"

;

BACKUP DATABASE

CHANNEL ch_sbt

;

}

2) To automatically allocate a channel to backup: Example:

Connect target /

CONFIGURE CHANNEL

DEVICE TYPE 'SBT_TAPE' PARMS

'SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/

asigra/params.txt)';

BACKUP DATABASE;


4. Asigra Oracle-SBT Advanced Usage Topics

Backup of Oracle using multi-channel backups. (The main benefit of using multi-channel backups is increasing the backup speed.)

The ASIGRA SBT Library supports multi-channeling during backup (not during on-line restore). To take advantage of multi-channeling: 1) Make sure that the DS-Client “/opt/CloudBackup/DS-Client/etc/dsclient.cfg” file specifies an appropriate “MaxThread Number” value. This parameter specifies the maximum number of files the DS-Client can send in parallel to the DS-System. For Oracle-SBT backups, the maximum recommended amount is 16. You must restart the DS-Client after reconfiguring this parameter.

Example 1: Editing via DS-User GUI.

OR - Example 2: On the DS-Client server, edit the following line in the file

“/opt/CloudBackup/DS-Client/etc/dsclient.cfg”.

MaxThread Number : 16

2) Allocate several channels inside a “run” block, with the same parameter file.

Example using a run block with the maximum of 16 channels: connect target /

run {

ALLOCATE CHANNEL ch1 DEVICE TYPE SBT

PARMS="SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/asigra/param_unenc_orcl.txt)" ;
































BACKUP DATABASE;

}

3) Preconfigure RMAN to use multi-channel over SBT connections with a specific FORMAT:

Example: RMAN> show all;

using target database control file instead of recovery catalog

RMAN configuration parameters for database with db_unique_name ORCL are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'CONTROLFILE_%F';

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'CONTROLFILE_%F';

CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 16 BACKUP TYPE TO COMPRESSED BACKUPSET;

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/asigra/param_unenc_orcl.txt)' FORMAT

'DB_ACTIVATION_ID_%a_COPYNUMBS_%c_DB_NAME_%d_DBID_%I_BACKUPPIECENUM_%p_BSNUM_%s_BSTIMESTAMP_%t_DATE_%T';

CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' PARMS

'SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/asigra/param_unenc_orcl.txt)' FORMAT









































CONFIGURE MAXSETSIZE TO UNLIMITED; # default


CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl.f'; # default

RMAN>

5. Restoring as pure files from DS-System (or from Disc/Tape or from BLM)

Direct RMAN-controlled restore is only possible when restoring from on-line (the DS-System). When restoring from Disc/Tape or BLM, files must be restored as “pure files” to the Oracle server. IMPORTANT NOTE: “Pure files” that are restored are not directly visible as 'disk dumps' by Oracle since the dump to disk and the dump to SBT are different. As a result, you still need to use the ASIGRA ORACLE-SBT Library to access the pure files. 1) In order to access the pure files, define a parameter text file containing the 'Disk Source' parameter, whose value is the directory where you restored the pure files:

NOTE: Make sure the “Disk Source” parameter is by itself (alone) in the file “disk_params.txt”.

Example of the folder structure required for UNIX and Linux “disk_params.txt”: Disk Source: /Restore_as_pure_file/dumps

Example of the folder structure required for Windows “disk_params.txt”: Disk Source: D:/Restore_as_pure_file/dumps

The format should be changed from “D:\Restore_as_pure_file\dumps” to “D:/Restore_as_pure_file/dumps” or “D:\\Restore_as_pure_file\\dumps”.

Important: Make sure that the Oracle user has access to this directory’s “PERMISSIONS”. The ORACLE-SBT Library will run under the Oracle context when performing cataloging/restore. Once the parameter file is created, you can re-configure Oracle to use the new parameter file.

2) You must re-catalog any restored files. It will take the folder location from the disk_params.txt file and the “dump file name” from the “CATALOG DEVICE TYPE SBT BACKUPPIECE 'restored_file_name.dmp’;” For example:

Connect target /

CONFIGURE CHANNEL


'SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/asigra

/disk_params.txt)'

;

CATALOG DEVICE TYPE SBT BACKUPPIECE 'restored_file_name.dmp';


6. Troubleshooting

The ASIGRA SBT Library supports trace levels 0, 1 and 2 as required by the ORACLE-SBT specifications. Default tracing level is 0 (higher levels increase verbosity and will make backup/restore operations slower and may fill up the disk). The trace output will, by default be located in the file 'sbtio.log', together with the rest of the Oracle trace files. Example of the configuration of a channel using “TRACE” to get logs to investigate any kind of problem that you may have. The logs will be located in the Oracle trace and alert log file folder on the Oracle server.

Connect target /

CONFIGURE CHANNEL



/params.txt)' TRACE 2;

CROSSCHECK BACKUP;


7. Configuring the Oracle Enterprise Manager to backup using Asigra Oracle-SBT

1) Log in to the Oracle Enterprise Manager > Availability > Setup “Backup Settings”. 2) Enter the amount of channels: up to 16. 3) Enter the following line for the media management vendor library parameters:

SBT_LIBRARY=/asigra/libdsc_ora_sbt_Linux_x86_64.so,ENV=(CONNECT_INFO=/asigra/param.txt)

4) Enter the Host Credentials. 5) Test if the Tape Backup is ready to use. 6) All functionality of the ORACLE Enterprise Manager is enabled for backup. (Scheduled Backups, Customized backups, Tape settings [Copies of datafile backups and Archive log backups], Backup Policy, Retention Policy, Archive Log Deletion Policy: please refer to the relevant Oracle documentation for more information).


8. Known Issues

This section contains a list of known issues you might encounter:

8.1 Error message on restore

During restore, the DS-Client event log might show the error "Remote side cancelled restore". This is because RMAN has read all data from the backup pieces and then closed the restore session because RMAN does not need it any more. This leads to a much quicker restore.

8.2 Retention

Retention should not be assigned on the DS-Client side (i.e. on the Oracle-SBT backup set). Retention rules should be managed by RMAN itself. Even if you enforce retention from DS-Client on an Oracle-SBT backup set, DS-Client will not delete any files because all files only have a single generation. Retention always keeps the latest generation of every file.

8.3 HPUX 11.31 patch updates

HPUX may have issues with transferring encrypted files via SSL to DS-Client. For HPUX 11.31, you should install all the latest HPUX 11.31 Patch bundles. This will cause a rebuild of the HPUX kernel. You can obtain these patch bundles from HP website. Refer to the "Oracle Database Quick installation Guide for HP-UX Itanium” document for a description of the required patches. Without them, encryption through SSL on HPUX 11.31 is not supported. Here is the list required Patches for HP-UX 11i V3 (11.31):

PHCO_40381 11.31 Disk Owner Patch

PHKL_38038 VM patch - hot patching/Core file creation directory

PHKL_38938 11.31 SCSI cumulative I/O patch

PHKL_39351 Scheduler patch : post wait hang

PHSS_36354 11.31 assembler patch

PHSS_37042 11.31 hppac (packed decimal)

PHSS_37959 Libcl patch for alternate stack issue fix (QXCR1000818011)

PHSS_39094 11.31 linker + fdp cumulative patch

PHSS_39100 11.31 Math Library Cumulative Patch

PHSS_39102 11.31 Integrity Unwind Library

PHSS_38141 11.31 aC++ Runtime

PHSS_39824 - 11.31 HP C/aC++ Compiler (A.06.23) patch

===========================================================


8.4 Multiple sessions (backup / restore)

A queue was added to the DS-Client functionality for ORACLE SBT Sessions. There are rules that apply for RMAN multi-sessions to the same “Oracle database” target via the same backup set from the same DS-Client:

1. RMAN Backup sessions can be done in parallel.

2. If one RMAN Backup session has already begun backing up and another RMAN Restore session tries to restore, the RMAN Restore session will not start until the RMAN Backup Session is finished.

3. RMAN Restore sessions and RMAN Delete sessions cannot be done in parallel. Therefore the

queue is available and those can be done one by one, depending on the queue order.

4. If one RMAN Restore session already begun restoring, all other RMAN Restore sessions must wait in the queue until the previous RMAN Restore Session has finished.

8.5 Parameter File

1. In the parameter file for Asigra ORACLE SBT library, the backup set password can be encrypted or plain text. Asigra recommends using an encrypted password.

2. When using the 'Disk Source' parameter for Windows platforms, such as 'D:\data\restore', it

written in the parameter file either as 'D:/data/restore' or 'D:\\data\\restore'.

3. If you encounter any problems, enable the ‘trace’ feature on RMAN environment. For example:

CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE'

PARMS

'SBT_LIBRARY=/asigra/libdsc_ora_sbt_hpux_ia64_64.sl,ENV=(CONNECT_INFO=/asigra

/param.txt)' TRACE 2;

8.6 Backup Set name length

RMAN has a limitation about label length. When creating backup set, please don't use any name beyond 64 characters.


8.7 DS-Client functionality (un)available to Oracle-SBT backup sets.

1. The following features are not available for ORACLE SBT backup sets on the DS-Client side:

DS-Client buffer

Local Cache

Backup schedules

2. The following functionality / feature should be performed from the Oracle Enterprise Manager:

Scheduled backups

Customized backups

Tape settings (Copies of datafile backup, and Archive log backups)

Backup policy

Retention Policy

Archive log deletion policy

Etc.

3. DS-Client Local-Only Functionality is supported for Asigra ORACLE SBT Backup sets.

8.8 Workaround to quickly catalog multiple backup pieces

If you need to catalog multiple pure files to the control file / catalog, you can use a python script to generate the ‘catalog backup pieces’ script automatically. This is an example of how to catalog multiple backup pieces as fast as possible.

1. Restore all the backup pieces as pure files to a folder. This example uses '/restore_as_pure_files_oracle/DT/files/' as the target path:

[oracle@dsclrh5u2 files]$ cd /restore_as_pure_files_oracle/DT/files/

[oracle@dsclrh5u2 files]$

[oracle@dsclrh5u2 files]$ ls

3vl7nd86_1_1 4al7ndbk_1_1 4ml7nlgn_1_1 52l7nn7s_1_1 5el7nsfg_1_1

5pl7nt5p_1_1 65l7nu3n_1_1 40l7nd8b_1_1 4bl7nddf_1_1 4nl7nlh4_1_1

53l7nn8p_1_1 5fl7nsfn_1_1 5rl7nu28_1_1 66l7nu3r_1_1 CONTROLFILE_c-

1215762398-20100304-00 41l7nd8f_1_1 4cl7nde2_1_1 4ol7nlj1_1_1 54l7nn96_1_1

5gl7nsft_1_1 5sl7nu2c_1_1 67l7nu3v_1_1 CONTROLFILE_c-1215762398-20100304-

01

42l7nd8k_1_1 4el7nldr_1_1 4pl7nlpo_1_1 55l7nn9k_1_1 5hl7nsg9_1_1

5tl7nu2h_1_1 68l7nu44_1_1 CONTROLFILE_c-1215762398-20100304-02 43l7nd8s_1_1

4fl7nldv_1_1 4ql7nlt7_1_1 56l7nn9v_1_1 5il7nsgi_1_1 5ul7nu2l_1_1

69l7nu48_1_1 CONTROLFILE_c-1215762398-20100304-03

44l7nd93_1_1 4gl7nle5_1_1 4rl7nlv7_1_1 57l7nnac_1_1 5jl7nsgv_1_1

5vl7nu2q_1_1 6al7nu4c_1_1 CONTROLFILE_c-1215762398-20100304-04 45l7nd9d_1_1

4hl7nled_1_1 4tl7nn6q_1_1 58l7nnas_1_1 5kl7nshc_1_1 60l7nu30_1_1

6bl7nu4g_1_1 CONTROLFILE_c-1215762398-20100304-05 46l7nd9k_1_1 4il7nlen_1_1

4ul7nn6u_1_1 59l7nnbd_1_1 5ll7nshp_1_1 61l7nu35_1_1 6cl7nu4l_1_1


47l7nda2_1_1 4jl7nlf6_1_1 4vl7nn74_1_1 5al7nnbo_1_1 5ml7nsi6_1_1

62l7nu39_1_1 6dl7nu4q_1_1 48l7ndab_1_1 4kl7nlfv_1_1 50l7nn7b_1_1

5cl7nsf7_1_1 5nl7nsil_1_1 63l7nu3e_1_1 6el7nu4u_1_1 49l7ndas_1_1

4ll7nlga_1_1 51l7nn7l_1_1 5dl7nsfc_1_1 5ol7nt3p_1_1 64l7nu3j_1_1

6gl7nv23_1_1

[oracle@dsclrh5u2 files]$ pwd

/restore_as_pure_files_oracle/DT/files

[oracle@dsclrh5u2 files]$

2. The following is a python script used to read the name of the files in a folder and add them to

a file (catalog_backuppieces.rman) with the command "CATALOG DEVICE TYPE SBT BACKUPPIECE" in front of the file name.

[oracle@dsclrh5u2 catalog_script]$ cd

/SCRIPTS/restore_from_pure_files_dt/catalog_script

[oracle@dsclrh5u2 catalog_script]$

[oracle@dsclrh5u2 catalog_script]$ cat rman_sbt_catalog.py

#!/usr/bin/python

import os

import sys

if (len(sys.argv) < 3):

print 'Usage: %s sbt_file_directory catalog_filename' % sys.argv[0]

sys.exit()

else:

dname = sys.argv[1]

fname = sys.argv[2]

names = os.listdir(dname)

f = open(fname, 'wb')

for i in names:

f.write('CATALOG DEVICE TYPE SBT BACKUPPIECE \'')

f.write(i)

f.write('\';\n')

f.close()


3. Example of how to run the python script.

First, specify the script name (./rman_sbt_catalog.py).

Then specify the folder where the backuppieces are located (/restore_as_pure_files_oracle/DT/files).

Then add a name to the output file (catalog_backuppieces.rman).

For Example:

[oracle@dsclrh5u2 catalog_script]$ ls

rman_sbt_catalog.py

[oracle@dsclrh5u2 catalog_script]$ ./rman_sbt_catalog.py

/restore_as_pure_files_oracle/DT/files catalog_backuppieces.rman

[oracle@dsclrh5u2 catalog_script]$ cat catalog_backuppieces.rman


CATALOG DEVICE TYPE SBT BACKUPPIECE '49l7ndas_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5jl7nsgv_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '64l7nu3j_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5ul7nu2l_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '46l7nd9k_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4fl7nldv_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '52l7nn7s_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '67l7nu3v_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4gl7nle5_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE 'CONTROLFILE_c-1215762398-20100304-02';

CATALOG DEVICE TYPE SBT BACKUPPIECE '59l7nnbd_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '40l7nd8b_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4tl7nn6q_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '6dl7nu4q_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5pl7nt5p_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '6bl7nu4g_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '6cl7nu4l_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '68l7nu44_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '6gl7nv23_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '45l7nd9d_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '6el7nu4u_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5hl7nsg9_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4il7nlen_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4pl7nlpo_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '4rl7nlv7_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4ul7nn6u_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '65l7nu3n_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '6al7nu4c_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4ol7nlj1_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5kl7nshc_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '56l7nn9v_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4el7nldr_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5rl7nu28_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '54l7nn96_1_1';



CATALOG DEVICE TYPE SBT BACKUPPIECE '5gl7nsft_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '44l7nd93_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '57l7nnac_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5cl7nsf7_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '58l7nnas_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5vl7nu2q_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '43l7nd8s_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5sl7nu2c_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4hl7nled_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5al7nnbo_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4vl7nn74_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '53l7nn8p_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5ol7nt3p_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5dl7nsfc_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4jl7nlf6_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4nl7nlh4_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5el7nsfg_1_1';



CATALOG DEVICE TYPE SBT BACKUPPIECE '5nl7nsil_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '3vl7nd86_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5ll7nshp_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '66l7nu3r_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5il7nsgi_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4ql7nlt7_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '48l7ndab_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '50l7nn7b_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '47l7nda2_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '42l7nd8k_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4ml7nlgn_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5fl7nsfn_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '5tl7nu2h_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4al7ndbk_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '41l7nd8f_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '4bl7nddf_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4kl7nlfv_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4cl7nde2_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '4ll7nlga_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '63l7nu3e_1_1';


CATALOG DEVICE TYPE SBT BACKUPPIECE '5ml7nsi6_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '55l7nn9k_1_1';

CATALOG DEVICE TYPE SBT BACKUPPIECE '51l7nn7l_1_1';


4. How to use this catalog_backuppieces.rman on rman. First make sure the database is on mount state.

[oracle@dsclrh5u2 catalog_script]$ rman target sys/sys@orcl

Recovery Manager: Release 11.1.0.6.0 - Production on Tue Mar 16 09:54:29 2010

Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: ORCL (DBID=1215762398)

RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS


/param_rp_dt.txt)';

using target database control file instead of recovery catalog

old RMAN configuration parameters:

CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS


/param.txt)' TRACE 2;

new RMAN configuration parameters:

CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS


/param_rp_dt.txt)';

new RMAN configuration parameters are successfully stored

RMAN>

@/SCRIPTS/restore_from_pure_files_dt/catalog_script/catalog_backuppieces.rman

.


.

RMAN> CATALOG DEVICE TYPE SBT BACKUPPIECE '4ll7nlga_1_1';

released channel: ORA_SBT_TAPE_1

allocated channel: ORA_SBT_TAPE_1

channel ORA_SBT_TAPE_1: SID=150 device type=SBT_TAPE

channel ORA_SBT_TAPE_1: DS-Client SBT Library

cataloged backup piece

backup piece handle=4ll7nlga_1_1 RECID=1208 STAMP=713788344

RMAN> CATALOG DEVICE TYPE SBT BACKUPPIECE '63l7nu3e_1_1';

.

.

8.9 Alternate or Disaster Restore requires manual creation of the data directory

During a disaster recovery or if restoring the database to an alternate location, the folder structure must be created and the corresponding permissions must be added to the target Oracle database prior to restore. If the database is managed by ASM, you still need to manually create the folder structure using ASMCMD.

8.10 Upgrading from v11 to v11.2 (IMPORTANT READ THIS NOTE)

The Asigra Oracle SBT library has been updated with fixes and has been rebuilt with Visual C++ 2010. Due to these changes, if you are upgrading from an earlier version, you must make sure you copy the latest library (from the v11.2 DVD) to the Oracle Server. You must also run the Microsoft Visual C++ 2010 Redistributable Setup on the Oracle Server in order for the new library to function. If you perform all the installation steps from section “2. Configuration on the ORACLE Server” using files from the v11.2 DVD, the configuration should work. Otherwise, verify the following:

1. You are using the v11.2 Asigra Oracle_SBT library (located on v11.2 DVD under the directory '\Software\Tools\Oracle_SBT_Library'):

\Windows_x86\dsc_ora_sbt_Windows_32.dll (32-bit) \Windows_x64\dsc_ora_sbt_Windows_64.dll (64-bit)

Note: The Oracle Tool ‘sbttest’ can be used to verify the version is 11.2.0.0 (output value for ‘Media manager is version’). This tool can be found in the directory ‘$ORACLE_HOME\BIN’.

2. You must run the Visual C++ 2010 redistributable setup package on the Oracle Server. Select the 32-bit or 64-bit version, depending on the platform used. These files can be found on the Asigra v11.2 DVD in the following folders:

\Software\Tools\Oracle_SBT_Library\Windows_x86\vcredist_x86.exe (32-bit) \Software\Tools\Oracle_SBT_Library\Windows_x64\vcredist_x64.exe (64-bit)

asigra - rman interface_description

Documents