Configuring Oracle Secure Backup for PTT

1. Install OSB software on the hosts requiring protection.
2. From the OSB console, assign the appropriate host role.
   Administratrive Server

   The administrative server houses the OSB catalog and scheduling information. There can be only one administrative server per backup domain.

   Note: You can also assign the media server role to the Administrative Server, as needed.

   Media Server

   The media server attaches directly to the tape devices.

   Client

   The client contains the data to back up.

   Note: All hosts have a minimum of client role.

1. From the obtool command line interface (CLI), create an OSB device object for each PTL and assign it a user-defined name.
2. Attach each PTL to the device special file using the following command:

   ob> <device_object> --type library --attach <device_special_file>

3. For each tape drive attached to the PTLs, create an OSB device object and assign in a user-defined name.
4. Attach each drive on the PTL to the device special file using the following command, as needed:

   ob> <PTL_device_object> --type tape --library <type> --<drive_device_object> --attach <device_special_file>

5. Verify the configuration using the following command:

   ob> lsdev

   Example

   You attach the following PTL drives to device special files:

   ob> mkdev --type tape --library i500 --dte 1 --attach svtest0030:/dev/obt0 IBMLTO3A

   ob> mkdev --type tape --library i500 --dte 2 --attach svtest0030:/dev/obt1 IBMLTO3B

   ob> mkdev --type tape --library i500 --dte 3 --attach svtest0030:/dev/obt2 IBMLTO3C

   You run the following command to verify the configuration:

   ob> lsdev

   OSB displays the following output:

   library i500 in service

   drive 1 IBMLTO3Ain service

   drive 2 IBMLTO3B in service

   drive 3 IBMLTO3C in service

An NDMP copy-enabled VTL, such as a Quantum DXi, has an embedded NDMP server and multiple access paths. This format offloads the volume duplication I/O from the application running on the media server to the VTL.

You must configure the NDMP copy-enabled VTL as a group of tape devices with multiple attach specifications. This representation ensures that the inventory data coming through the multiple access paths is identical.

Note: The following task provides basic configuration steps. For detailed instructions, see Oracle Secure Backup Administrator's Guide.

Configure an NDMP copy-enabled VTL

1. In the obtool CLI, create two OSB host objects to represent the VTL.

   1. Associate the first object with the media server to which the VTL is attached.

   2. Associate the second object with the VTL's embedded NDMP server.
2. Assign the media server role to both of these host objects.
3. Create one OSB library device object with two attach specifications for the VTL.

   1. Assign the first access path through the media server to which the VTL is attached.

   2. Assign the second access path through the embedded NDMP server.
4. Create an OSB tape device object with two access paths for each drive contained within the VTL.

   1. Assign the first access path through the media server.

   2. Assign the second access path through the embedded NDMP server.
5. Create one OSB library device object with a single attach specification for the PTL.

   Assign the access path through the VTL's embedded NDMP server.

6. Create an OSB tape device object with a single attach specification for each drive contained within the PTL.

   Assign the access path through the VTL's embedded NDMP server.

   Note: Multiple media servers can access the PTL and its drives if the PTL is connected to a shared storage area network. In this case, create the OSB device objects for the PTL and its drives with multiple attach points.

Example

Following is an example of the obtool commands used to configure an NDMP copy-enabled VTL. Many of the options specified in a real environment have been omitted for clarity. The device names shown are simply placeholders that may differ from the actual names in a real environment.

1. Create the OSB host object associated with the media server to which the VTL is attached.

   mkhost --access ob --ip ipname osb_media_server

2. Create the OSB host object associated with the embedded NDMP server contained within the VTL.

   mkhost --access ndmp --ip ipname ndmp_server

3. Configure an OSB device object that is associated with the VTL vlib.

   mkdev --type library --class vtl

   -attach osb_media_server:/dev/obl0,ndmp_media_server:/dev/sg0 vlib

   Note: Access to this library and its drives is through the OSB media server and the embedded NDMP server.

4. Configure an OSB device object for drive vdrive1, which is contained in the VTL vlib.

   mkdev --type tape --library vlib --dte 1

   -attach osb_media_server:/dev/obt0,ndmp_media_server:/dev/nst0 vdrive1

5. Repeat this command for each tape drive in the VTL.

   mkdev --type tape --library vlib --dte 2

   -attach osb_media_server:/dev/obt1,ndmp_media_server:/dev/nst1 vdrive2

   mkdev --type tape --library vlib --dte 3

   -attach osb_media_server:/dev/obt2,ndmp_media_server:/dev/nst2 vdrive3

6. After configuring your devices, review the attached configured devices on the Configure Devices tab.