Backup3G/DA-Oracle/RMAN 5.1 Release Notes

From Documentation

Overview and Features

DA-RMAN

DA-RMAN 5.1 facilitates the operations of tape libraries. It support loading from any slot to any drive, unloading from any drive to any slot, barcode readers, and one or more import/export (or mailbox) slots.

New features in DA-RMAN

Simpler Configuration

• Disable a backup job on a given date.
• Re-enable a backup job on a given date.
• Append a job to media based on group name.
• Schedule a secondary copy of the backup media from the backup job.
• Verify media after the backup job has completed.
• Send notification based on success status of the backup job. The backup log can be optionally attached.
• Test network communication for a given backup job, testing communications between the Master, Drive and File hosts as configured for that job.
• Method sensitive forms for backup items, making it simpler to set options.
• Folders can be browsed making it simpler to set up unstructured data backup items.
• The incremental backup methods have been renamed to differential.
• You can discover filesystems and volumes for given hosts, creating backup items for those found.
• You can filter your view of backup items by host or object.
• Various global settings can be set to change the behaviour of backup3G. These include:

• Remote access control
• Drive inactivity timeout
• Direct I/O blocksize
• Meta-data replication
• Notification.

Enhanced Operations

• The run history of a selected duty can be viewed over various date periods.
• Send notification when there are no more available media.

Improved Auditing

• The Backup3G audit trail logs the start and end and level of success of:

• backup jobs
• media copies
• re-indexing media
• media library inventory
• recovery jobs
• meta-data replication.

• The configuration audit trail logs all changes in backup3G tables.
• The operations audit trail logs all action invocations from:

• backup scheduling console
• recovery console
• media management console
• drive and media library consoles
• job monitor console.

Documentation

• A HTML or text document can be associated with a backup job, so end users can see what Policies and Procedures the backup is supporting.
• The user guide, release notes and other documentation can be viewed via your favourite browser.

Installation Requirements

Software prerequisites

To install and run backup3G 5.1 on a host, you must have:

• COSmanager 4.2.5 or newer already installed on the host (see the COSmanager User Guide for instructions)
• a backup3G distribution
• a valid license key for this host (see your COSmanager distributor if you don’t have a valid license key)
• sufficient disk space
• COSmanager Manager access, or equivalent
• the ability to open a root shell

Disk space required

Related Software

The release of backup3G 5.1 coincides with the release of stacker3G 5.1 (module), VTL3G (module), DA_Oracle 5.1 (module) and duty3G 5.1 (application).

Technical Notes: Using DA-RMAN 5.1

This section contains some technical notes, tips, and troubleshooting information to help you when installing and using DA-RMAN 5.1.

Temporary or trial licensing

Backup3G may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSmanager distributor to keep using backup3G after the expiry date.

	Note
	Backup3G won’t install if the license key is due to expire within the next 7 days. In this case you will need to obtain a new license key from your COSmanager distributor.

Building libobk.so

In order for RMAN to use backup3G as its Media Manager, a shared library called libobk.so must be provided which implements the SBT (System Backup to Tape) interface to backup3G.

Should you need to re-build the libobk.so shared library, the source code is provided in the files rman_if.c and skgfqsbt.h. Re-building may be necessary, for instance, if the version of Oracle you are using is 64 bit, but the supplied libobk.so is 32 bit.

	Note
	libobk.so should be left in this directory (da_rman_1.2/Install). A symbolic link will be created under $ORACLE_HOME/lib pointing to libobk.so in this directory.

Below are the commands needed to build the shared library on different Operating Systems:

Linux

gcc -shared -O -fPIC -D_GNU_SOURCE rman_if.c -o libobk.so

Solaris

cc -G -O -KPIC rman_if.c -o libobk.so

	Note
	On 64 bit Sparc systems, you may need to add -xarch=generic64 to force the compiler to build a 64 bit version.

AIX

cc -O -bM:SRE -bnoentry -bE:libobk.exp rman_if.c -o libobk.so

	Note
	On 64 bit systems, add -q64 -b64

HPUX

cc -O +z -c rman_if.c ld -b rman_if.o -o libobk.so

	Note
	Some OSes define flock_t, and you may get a compiler error. If this happens, edit rman_if.c and remove line 35: typedef struct flock flock_t;

Warnings

Known Problems in this Release

None known.

Hardware and OS Dependencies

AIX 4

None known.

HPUX

None known.

Linux

None known

Solaris

None known