5 Configuring DIVArchive Robot Managers

This chapter describes DIVArchive Robot Manager configuration and includes the following information:

Configuration Overview

The DIVArchive Robot Manager on Windows platforms runs as a Windows service and is launched automatically with Windows. See Appendix A for DIVArchive options and licensing information.

You configure the type of interface a specific library in a static configuration file. The file name is robotmanager.conf and is located in the DIVA_HOME\Program\conf\robot_manager folder on the computer where the DIVArchive Robot Manager is installed. In a new installation (or upgrade) the file is provided with a .ini extension. You must remove the extension for it to be acknowledged by the Robot Manager. You must copy the file, remove the .ini extension, and then edit the new file.

Since many different types of libraries and connections are supported, not all sections of the configuration file will be relevant to your particular installation. Also, some parameters are specific to the operating system where the Robot Manager is installed. Therefore, some settings in the configuration file are initially commented out (that is, they have # in front of the parameter). This indicates to the Robot Manager to ignore the setting. For the setting to be taken into account the # must be removed.

The following figure outlines the steps for configuring the robotics to be controlled by DIVArchive:

DIVArchive Robotics Configuration Flow Chart

SCSI Connected Libraries

For directly attached SCSI controlled libraries, you must configure and correctly identify the SCSI ID controlling the library, and enter this value into the RM_SCSI_DEVICE_LSM parameter in the Robot Manager configuration file. Before changing the configuration, you must understand several concepts as described in the following sections.

The robotmanager.conf configuration file includes the following main parameters:

RM_SCSI_MOVEMEDIUM_TIMEOUT

Robot SCSI uses the MOVE MEDIUM SCSI command during mount, dismount, enter, and eject requests. The value of RM_SCSI_MOVEMEDIUM_TIMEOUT is indicated in minutes, and the default timeout is fifteen minutes for the communication between the library and the robot manager.

Some libraries, like Spectra T950, may require more time to be able to complete a MOVE MEDIUM request and you should set this parameter value accordingly.

RM_SCSI_EJECT_USEGLOBALLOCK

You must set this parameter to one if you want the SCSI Robot Manager Eject calls obtain the lock number of the LSM and hold that lock until all associated tapes to be ejected have completed the ejection process. When all tape ejections are complete, the call unlocks the drive and proceeds on to the next drive. The default setting is zero.

Fibre Channel Host Bus Adapter (HBA) and SCSI Persistent Binding

Most installations use Fibre Channel (FC) rather than native SCSI to interface to the library (typically over a SAN). In these instances, the FC HBA in the DIVArchive Robot Manager host presents the World Wide Name of the library interface as a SCSI ID. By default, most HBAs automatically map these to a SCSI ID for the host operating system to access. This presents a problem if a device is added or removed on the SAN because it could alter the SCSI ID of the library by the HBA, and automatically remap the existing devices. Disable the Automap feature to avoid this issue and use Persistent Bindings instead. This feature allows the SCSI mapping of the library to remain consistent between host restarts, and from the advent of any addition or removal of devices on the SAN.

If the library controller or the HBA in the DIVArchive Robot Manager host is changed, this might alter the library's SCSI Persistent Bindings to the host operating system. This requires the Persistent Binding for the library to be reconfigured in the HBA configuration software on the DIVArchive Robot Manager computer.

Determining the SCSI Library Connection

For most SCSI interface libraries the DIVArchive Robot Manager communicates with the library directly over the SCSI hardware layer and does not require the traditional Windows driver interface. The exceptions are IBM and HP libraries.

For all other libraries it is essential that no library driver be loaded for the library interface. If a driver is loaded, the DIVArchive Robot Manager will be unable to communicate with the library. In this case, if your library does not appear in Windows Device Manager as an Unknown Medium Changer, the Robot Manager will be unable to communicate correctly with the robotics.

If you cannot locate a specific library in the Scandrive Utility (see the following), but that library is visible in your HBA, then the library has likely been disabled in the Windows Device Manager (denoted by an X over the device icon). You must re-enable the device for it to appear in the Scandrive Utility.

For Windows, you can determine the RM_SCSI_DEVICE_LSM(n) settings for the DIVArchive Robot Manager using the scandrive.exe utility. The utility is located in the %DIVA_HOME%\Actor\bin directory. The utility automatically reports all devices located in the Windows SCSI hardware tree in the registry and their corresponding Port, Bus, Target, and Logical Unit Numbers (LUN).

Scandrive Utility Output

The utility reports the SCSI Device ID of the library in the format ScsiP:B:T:L (see the previous figure), where P is the port number, B is the bus number, T is the target number, and L is the Logical Unit Number.

The Type section of the utility's output refers to that peripheral's class (HDD, CDROM, and so on). A tape library will be reported as a Medium Changer Peripheral, and the Identifier for each corresponding device reported should match the model number of the library itself (for example, SL500). You can then enter the full SCSI path reported for each library into the RM_SCSI_DEVICE_LSM(n) settings in the robotmanager.conf file.

Sony ODA Drives

DIVArchive supports Sony the new generation of ODA drives; the ODS-280F (Fibre Channel) and ODS-280U (USB). DIVArchive has only been tested with the Fibre Channel type. The drives are twice as fast as the Gen1 drives. The ODS-280U has not been qualified for use with DIVArchive.

A new cartridge type is also available for this drive, the ODC3300R. This is a WORM drive with a 3.3 TB capacity.

Gen2 drives can read content written on Gen1 media with Gen1 drives. DIVArchive does not support the READ-ONLY media-drive compatibility. Oracle recommends isolating Gen1 media from Gen2 media in the configuration (because there is no cross-generation compatibility) and there must be at least one Gen1 drive in a library containing Gen1 cartridges.

DIVArchive supports Sony ODA ODS-D55U and ODS-D77F drives only in the Windows environment. These are Blu-ray Optical Drives and the media is WORM media using a UDF format. Only AXF formatted objects can be written to the discs. The drives are controlled by the Robot Manager and the media is viewed as a Tape Cartridge.

In the Windows Device Manager these drives will be shown as Unknown Medium Changer under the Medium Changer section because there are no device drivers for them. The drive itself will also appear as an Optical SCSI Device with the make and model number under the Disk Drives section.

There are seven different types of disc media available for use with the Sony Optical Drives as follows:

SONY-ODC300R

293,265,408 KB capacity

SONY-ODC300RE

293,265,408 KB capacity

SONY-ODC600R

586,530,816 KB capacity

SONY-ODC600RE

586,530,816 KB capacity

SONY-ODC1200RE

1,173,086,208 KB capacity

SONY-ODC1500R

1,500,020,736 KB capacity

SONY-ODC3300R

3,222,717,696 KB capacity

The disc types are identified in the scsi_tape_types.ini file (described in the following section).

Note:

You must configure the drive settings before configuring DIVArchive. The recommended parity setting is PARITY ON.

You can view the drive specifics using the Optical Disc Archive Utility. This utility enables viewing of device logs, and viewing and changing drive settings.

To change the drive settings, click the Setting tab in the Optical Disc Archive Utility. Oracle recommends leaving the Default Volume Type set to PARITY ON, and to use the default settings for the remaining items.

Click the Media item under the Drive navigation tree to view information about the media in a drive.

You click the Write-protect button to write-protect a drive. Once an Optical Disc is write-protected, you can no longer write objects to the device. However they are still retrievable.

Configuration File Adjustments

You must change several parameters in the scsi_drive_types.ini configuration file to use these optical drives.

In the robotmanager.conf configuration file, under the SCSI module specific options, the serial number must be identified. You can find the serial number in the RM_SCSI_DEVICE_LSM(n) parameter line. For example, RM_SCSI_DEVICE_LSM(0)=00001003, where (0) is the LSM number, and 00001003 is the serial number. You must identify the serial number for all listed devices (LSM(0), LSM(1), LSM(2), and so on).

In the scsi_drive_types.ini file, the drive types must be uncommented (remove the #). For example, remove the # from in front of the line that reads #601 0x00 0x00 SONY-ODS-D77F 600 601 602 603 604 605 to use your D77F drive as shown. The TransportDomain and TransportType are obtained automatically and not used in the configuration, so you must leave these set to 0x00 as shown in this example.

#-------------------------------------------------------------
# If the SCSI Robot Manager is connected to a SONY ODA library
# UNCOMMENT ALL LINES IN THE FOLLOWING PART
#-----
#TypeID TransportDomain TransportType TypeName CompatibleTapeTypes
#-------------------------------------------------------------------
#600 0x00 0x00   SONY-ODS-D55U    600 601 602 603 604 605
601 0x00 0x00   SONY-ODS-D77F    600 601 602 603 604 605

Also, in the scsi_tape_types.ini file, uncomment all of the disc types listed as shown in the following example. The R or RE after the disc number indicates whether the disc is Write Once (R) or Rewritable (RE). This indicator is used because the barcode does not contain the video type as in normal tape barcodes.

#----------------------------------------------------------------
# If the SCSI Robot Manager is connected to SONY ODA library,
# UNCOMMENT ALL LINES IN THE FOLLOWING PART
#-----
#TypeID TransportDomain TransportType TypeName CompatibleDriveTypes
#----------------------------------------------------------------
600 0x00 0x00   SONY-ODC300R   600 601
601 0x00 0x00   SONY-ODC300RE  600 601
602 0x00 0x00   SONY-ODC600R   600 601
603 0x00 0x00   SONY-ODC600RE  600 601
604 0x00 0x00   SONY-ODC1200RE 600 601
605 0x00 0x00   SONY-ODC1500R  600 601

Configuration Utility Settings and Information

You must configure the following settings in the DIVArchive Configuration Utility:

Drives Tab

Set the Drive Properties to 64 KB. The serial number comes from the Robot Manager and the firmware release number comes from the drive.

Tapes Tab

The Tape Properties frame displays all of the enabled Tape Types from the scsi_tape_types.ini file.

Control GUI Settings and Information

The Optical Drives and Discs are displayed in the DIVArchive Control GUI on the Drives tab as Tape Drives and Tapes respectively.

Repack of the discs and deletion of objects is available. However, the space is not recoverable. When trying to repack the disc, the normal Repack dialog box is displayed, but there is a warning that the space is non-recoverable. Due to this limitation of the discs, auto-repack has been disabled for these drives and discs.

Additional Information

Additional information related to the use of the Optical Drives and Discs includes the following:

  • Because Write-Once media must be finalized, zero remaining space will be reported to the Manager.

  • Objects are spanned when there is 100 MB of space remaining. This is so that there is space left for the disc to be finalized. Once an object is spanned, the disc is considered full and is automatically finalized.

  • The Actor will auto-finalize the discs when there is 500 MB of space remaining unless an object was spanned. However you can manually finalize the disc through the Optical Disc Archive Utility.

  • If a drive is manually mounted and viewed in the Windows Explorer, the display will show the individual files on the disc. Each file name will begin with a numeric value at the beginning that identifies the object's location on the tape.

Configuring Direct Attached SCSI Libraries

A Direct Attached Library is directly connected to the DIVArchive Robot Manager host computer either through a native SCSI interface and SCSI HBA, or through a SCSI over Fibre Channel connection and Fibre Channel HBA (either directly or through a SAN).

In either case, the DIVArchive Robot Manager uses its own DIVArchive provided driver (SCSI_Robot.dll in Windows or libSCSI_Robot.so in Linux) to directly interface with the library without the need for intermediate library management software. For this type of SCSI attached library, you must uncomment the entries (in the following sections) and configure them in the robotmanager.conf file. Library Drive Models and Tape Types parameters are located in other configuration files.

Common Settings for SCSI-based Libraries

The following are typical settings for the SCSI-based libraries:

Robot Manager Common Options

Uncomment only the RM_MODULE=SCSI_Robot.dll in the Windows environment.

SCSI Device Parameters

The following table identifies common SCSI device parameters.

Table 5-1 SCSI Device Parameters

Parameter Parameter Type Description Default

SERVICE_NAME

Name

The display name of the Robot Manager Windows Service. You must set this variable if multiple Robot Managers are installed on the same server. If this variable is used, the Service Name will be DivaRbt-SERVICE_NAME. If this variable is not set, the Service Name will revert to just DivaRbt.

Uncommented

RM_PORT

TCP port number

The TCP port that the DIVArchive Robot Manager listens on for incoming requests. This value must be unique if there are multiple DIVArchive Robot Managers running on a single host computer. This is typically, TCP port 8500 and greater.

8500

RM_ACS

Number

The Automated Cartridge System (ACS) controlled by the DIVArchive Robot Manager module. This value will appear in the Robot Manager/ACS Association List in the Configuration Utility for this Robot Manager after database synchronization

0

SCSI Module Parameters

The following table identifies common SCSI module parameters. See Determining the SCSI Library Connection for parameter details.

Table 5-2 SCSI Module Parameters

Module Parameter Operating System Description Values

RM_SCSI_DEVICE_LSM0

Windows

This specifies the SCSI target of the library as it identified by the host operating system.

ScsiP:B:T:L

RM_SCSI_DEVICE_LSM1

Windows

This setting is specific to a StorageTek dual L1400M library with a Pass Through Port (PTP), and specifies the SCSI target of the 2nd frame (LSM).

Although this type of library configuration can be addressed using only the RM_SCSI_DEVICE_LSM0 connection, DIVArchive manages this type of library more effectively when both frames are specified. DIVArchive also manages the PTP in this case.

ScsiP:B:T:L

Additional Settings for Media Type Detection

The following table identifies an additional parameter that can be set to enable media type detection from the barcode.

Table 5-3 Additional Settings for Media Type Detection

Parameter Parameter Type Description

RM_SCSI_ENABLE_MEDIA_TYPE_DETECTION_LAYOUT

String pattern

The purpose of this parameter is to detect the type of a media from the volume tag retuned by the library. The layout is a string of 8-10 characters indicating where the label and the mediatype are. It must contain these three characters only:

L: The character at this position is part of the tape label/barcode considered into divarchive database.

T: The character at this position will be used for media type detection

X: The character at this position will be ignored

Example: for a given volume tag ABC003L6, if the layout is set to LLLLLLTT, RobotManager will detect an LTO6 tape and report ABC003 to DIVArchive.

Configuring ACSLS Attached Libraries

DIVArchive can directly interface to most Oracle StorageTek libraries using the Robot_SCSI driver. Some library configurations require the use of the Oracle StorageTek ACSLS library management software for the Robot Manager to control the library.

You can only install ACSLS (Automated Cartridge System Library Software) on Solaris platforms. The Solaris host and ACSLS are sold and supported by Oracle. See the Oracle ACSLS documentation at http://docs.oracle.com for detailed information.

Oracle does not support DIVArchive installations under the Solaris operating system.

Configuring LibAttach

LibAttach is an intermediate Windows driver providing connectivity to the ACSLS host. LibAttach runs as a Windows service and is typically installed on the same computer running the DIVArchive Robot Manager. The DIVArchive Robot Manager communicates to the ACSLS host using the LibAttach driver.

You must enter the following settings on the LibAttach Configurator dialog box (part of the ACSLS software):

Library server host name

Host name or IP address of the ACSLS server. If you use a host name, it must be resolvable by the DIVArchive Robot Manager host.

Firewall support

These settings are only required if a firewall is installed between the Robot Manager host and the ACSLS server. If no firewall is present leave these parameters set to 0.

Testing the LibAttach Connectivity to ACSLS

You can verify connectivity from the Robot Manager host to the ACSLS server with the query_server.exe utility located in the LibAttach installation directory. When you launch the utility a Windows command prompt opens. Statistics from the library will be returned if the connection is successful.

Firewall Support

You must have a TCP or UDP port open (to allow communication) if there is a network firewall between your Robot Manager host and ACSLS server. If there is a firewall, enter the open port numbers into the Firewall Support settings in the LibAttach Configurator.

Early implementation of firewall support for LibAttach did not work correctly with the DIVArchive Robot Manager, even though the query_server utility returned a successful connection. Ensure that you have the latest release of LibAttach that incorporates the patch released to address this issue. Contact Oracle Support for additional information.

robotmanager.conf Common Options

The following table identifies common robotmanager.conf options:

Table 5-4 robotmanager.conf Common Options

Parameter Parameter Type Description Default

RM_MODULE=ACSLS_Robot.dll

  

Uncomment only this line

Commented

RM_PORT

TCP Port Number

The TCP Port the Robot Manager will listen on for incoming requests. This value must be unique if there are multiple Robot Managers running on a single host. The assigned port is typically TCP Port 8500 and higher.

8500

RM_ACS

Number

ACSLS configurations ignore this value because the ACS number is supplied from ACSLS.

Ignored

SERVICE_NAME

Name

This is the display name of the Robot Manager Windows service. This variable must be set if multiple Robot Managers are installed on the same server. If this variable is used, the Service Name will be DivaRbt-SERVICE_NAME. The Service Name will revert to DivaRbtif this variable is not set.

Uncommented

The following table identifies the ACSLS parameters:

Table 5-5 ACSLS Parameters

Parameter Parameter Type Description Default

RM_ACSLS_SERVER

IP Address or Host Name

ACSLS ignores this parameter and it can be left blank.

  

RM_ACSLS_SSI_SOCKET

TCP Port Number

ACSLS SSI socket is the UNIX domain socket used by SSI. If this value is left undefined, it defaults to TCP port 50004.

50004

RM_ACSLS_TIMEOUT

Time in milliseconds

This sets the timeout period for queries to ACSLS through LibAttach. If you leave this value set to 0, the timeout period used by the Robot Manager is 10 minutes. If you must alter this timeout period, replace 0 with your own value (in milliseconds).

0

RM_ACSLS_IE_TIMEOUT

Time in milliseconds

When an Insert or Eject tape command is issued you must open the CAP and insert or eject tapes within this timeout period. If you leave this value set to 0, the timeout period used by the Robot Manager is 10 minutes. If you must alter this timeout period, replace 0 with your own value (in milliseconds).

0

RM_ACSLS_MAX_DISMOUNT_RETRIES

Number of retries

The maximum number of retries when the dismounted drive is still in use. If the setting is 5, the initial delay is five seconds and then doubled after each retry.

5

RM_ACSLS_DISMOUNT_FORCE

0 (disabled)

1 (enabled)

Under normal circumstances, you must unload a tape first (using an Actor) before issuing a dismount command to the library. A forced dismount instructs the library to issue the unload command to the drive directly. This option is not recommended because this may interfere with operations on the Actors.

0

Configuring Sony PetaServe Libraries

Control of Sony PetaServe libraries from the DIVArchive Robot Manager is directed through the Sony PSC controller over an Ethernet connection. The PSC controller parameters for the Robot Manager configuration file must match those on the PetaSite Controller.

robotmanager.conf Common Options

The following table identifies common robotmanager.conf options:

Table 5-6 robotmanager.conf Common options

Parameter Parameter Type Description Default

RM_MODULE=SONY_Robot.dll

  

Uncomment only this line

Commented

RM_PORT

TCP Port Number

The TCP Port the Robot Manager will listen on for incoming requests. This value must be unique if there are multiple Robot Managers running on a single host. The assigned port is typically TCP Port 8500 and higher.

8500

RM_ACS

Number

Automated Cartridge System (ACS) controlled by the Robot Manager module.

0

The following table identifies common Sony PetaSite options:

Table 5-7 Sony PetaSite Options

Parameter Parameter Type Description Default

RM_SONY_ENABLE_MEDIA_TYPE_TRIMMING

Number

This parameter must not be modified during production. The database may need to be patched if it is changed during production.

Some tape labels contain and additional two or three characters identifying the type of media. For example, 004452L2 is an LTO2 tape and S1000052 is a SAIT1 tape.

If this parameter is set to 1, the Sony Robot detects the tape using the label and filters out the two or three additional characters from the label.

1

RM_SONY_MEDIA_TYPE_TRIMMING_LEFT

Number

This parameter must not be modified during production. The database may need to be patched if it is changed during production.

Depending on the label, the two characters may be on the right or on the left of the label. Set this parameter to 1 if the Media Type information is on the left, otherwise set it to 0.

0

RM_SONY_PSCSERVERNAME

IP Address or Host Name

This parameter specifies the Host Name or IP Address of the Sony PetaSite controller (PSC). If you specify a Host Name, this must be defined in the operating system's hosts file.

  

RM_SONY_PSCUSERID

Number

This specifies the User ID that the Robot Manager uses when it connects to the Sony PetaSite Controller.

1

RM_SONY_PSCTIMEOUT

Time in milliseconds

Command time out to the PSC in milliseconds. This is only used for mount operations.

900000

RM_SONY_PSCDISMOUNTRETRIES

Number of retires

The maximum number of retries when the dismounted drive is still in use. If the setting is 5, the initial delay is five seconds. The delay is then doubled after each retry.

5

Configuring ADIC Libraries with SDLC

This interface is available on both Windows and Linux platforms. Refer to Appendix D for setting up the SDLC server and client components for the DIVArchive Robot Manager interface.

robotmanager.conf Common Options

The following table identifies common robotmanager.conf options:

Table 5-8 robotmanager.conf Common options

Parameter Parameter Type Description Default

RM_MODULE=ADIC_Robot.dll

  

Uncomment only this line

Commented

RM_PORT

TCP Port Number

The TCP Port the Robot Manager will listen on for incoming requests. This value must be unique if there are multiple Robot Managers running on a single host. The assigned port is typically TCP Port 8500 and higher.

8500

RM_ACS

Number

Automated Cartridge System (ACS) controlled by the Robot Manager module.

0

The following table identifies common ADIC parameters:

Table 5-9 ADIC Parameters

Parameter Parameter Type Description Default

RM_ADIC_DAS_CLIENT

Host Name

Host Name of the computer running the ADIC DAS client.

  

RM_ADIC_EJECT_AREA_NAME

Name

Symbolic name of the Cartridge Access Port.

E01

RM_ADIC_TIME_INSERT

Time in milliseconds

Number of milliseconds to wait to put away the tape after closing the CAP.

5000

RM_ADIC_MAX_DISMOUNT_RETRIES

Number of retries

Maximum number of retries when the dismounted drive is still in use. If the setting is 5, the initial delay is five seconds. The delay is then doubled after each retry.

5

Configuring Simulated Libraries (for DIVArchive Simulators)

Simulated robots are available on Windows and Linux platforms. The settings are shown here for reference only. Refer to the Oracle DIVArchive Simulator Operations Guide (available to OPN partners only) for more information on installing and configuring a DIVArchive Simulator platform.

robotmanager.conf Common Options

The following table identifies common robotmanager.conf options:

Table 5-10 robotmanager.conf Common Options

Parameter Parameter Type Description Default

RM_MODULE=SIMULATOR_Robot.dll

  

Uncomment only this line

Commented

RM_PORT

TCP Port Number

The TCP Port the Robot Manager will listen on for incoming requests. This value must be unique if there are multiple Robot Managers running on a single host. The assigned port is typically TCP Port 8500 and higher.

8500

RM_ACS

Number

Automated Cartridge System (ACS) controlled by the Robot Manager module.

0

The following table identifies the DIVArchive Simulator parameters:

Table 5-11 Simulator Parameters

Parameter Parameter Type Description Default

RM_SIMU_BASEDIR

Directory Path

The DIVArchive simulation files base directory path. This is typically C:\Diva\Simulation.

  

RM_SIMU_OPERATION_SHORT_DELAY

Time in milliseconds

This setting simulates physical delays in mount, dismount, enter, and eject operations. The recommended setting is 10000 msec.

0

RM_SIMU_OPERATION_LONG_DELAY

Time in milliseconds

You can use this setting to simulate an operation that takes more time than expected for execution. The recommended setting is 120000 msec.

0

RM_SIMU_OPERATION_LONG_DELAY_FREQUENCY

Number

This setting specifies how often a long delay should occur. The recommended setting is 50.

0

RM_SIMU_LIST_SHORT_DELAY

Time in milliseconds

This setting introduces a simulated physical delay in list operations. The recommended setting is 500.

0

RM_SIMU_LIST_LONG_DELAY

Time in milliseconds

You can use this setting to simulate a list operation that takes more time than expected for execution. The recommended setting is 60000 msec.

0

RM_SIMU_LIST_LONG_DELAY_FREQUENCY

Number

This setting specifies how often a long delay should occur in list operations. The recommended setting is 100.

0

Robot Manager Command Options

You perform DIVArchive Robot Manager control and management functions using robotmanager.exe from a command prompt. On Windows servers the executable is located in the %DIVA_HOME%\Program\Robotmanager\bin folder. On Linux servers, robotmanager.sh is located in the /home/diva/DIVA/Program/RobotManager/bin directory.

Installing and Uninstalling the Robot Manager Services in Windows

You use the following command line options to install or uninstall the DIVArchive Robot Manager from a Windows command prompt:

robotmanager -i

Installs the Robot Manager Service as set by the SERVICE_NAME parameter defined in robotmanager.conf. If this parameter is undefined, the service is installed as DIVArchive Robot Manager - host_name.

robotmanager -u

Removes the Robot Manager Service set by the SERVICE_NAME parameter in robotmanager.conf. If this parameter is undefined the service to be removed is DIVArchive Robot Manager - host_name.

These Robot Manager command options default to the robotmanager.conf file located in the %DIVA_HOME%\Program\conf\robot_manager folder to define the Service Name (if any). If you are installing multiple Robot Managers on a single host (see Appendix A for Oracle DIVArchive options and licensing information), additional Robot Manager configuration files must be created and specified to the service during installation to create unique instances for each Robot Manager.

You can create additional configuration files for each Robot Manager by copying and renaming the original robotmanager.conf file. For example, robotmanager1.conf, robotmanager2.conf, and so on. Each configuration file must contain unique SERVICE_NAME, RM_PORT, and RM_ACS entries.

For example, robotmanager1.conf might have the following parameters for a SCSI interface:

RM_MODULE=SCSI_Robot.dll
SERVICE_NAME=Robot1
RM_PORT=8500
RM_ACS=0

While robotmanager2.conf might have the following parameters for an ACSLS interface:

RM_MODULE=ACSLS_Robot.dll
SERVICE_NAME=Robot2
RM_PORT=8501
RM_ACS=1

You must specify the path to each Robot Manager configuration file for each instance when installing additional Robot Manager Services on the same host. You identify the path by adding the -conf (or -f) command switches when installing the service. For example, robotmanager -i -conf ..\..\conf\robot_manager\robotmanager2.conf installs the RObot Manager service as defined by the SERVICE_NAME parameter from the robotmanager2.conf configuration file.

If you must uninstall one or more Robot Manager Services, the configuration file path must also be specified. For example, robotmanager -u -conf ..\..\conf\robot_manager\robotmanager2.conf removes the Robot Manager Service as defined by the SERVICE_NAME parameter in robotmanager2.conf configuration file.

After installing the services check the Windows Services applet to confirm that the Robot Manager Services were installed correctly. To change the SERVICE_NAME, you must uninstall the existing service before editing the robotmanager.conf file. Then reinstall the service after changing the SERVICE_NAME parameter.

Installing and Uninstalling the Robot Manager Services in Linux

You use the following command line options to install or uninstall the DIVArchive Robot Manager from a Linux terminal.

Use the following command sequence to install the Robot Manager service:

cd /home/diva/DIVA/Program

./divaservice install robotmanager /home/diva/DIVA/Program/conf/robot_manager/robotmanager.conf

Use the following command sequence to uninstall the Robot Manager service:

cd /home/diva/DIVA/Program

./divaservice uninstall robotmanager /home/diva/DIVA/Program/conf/robot_manager/robotmanager.conf

See Installing the DIVArchive Services for information on the divaservice command.

Robot Manager Service Management Functions

The following command options are also available for the Robot Manager Service:

robotmanager debug

Starts the DIVArchive Robot Manager in console mode. Console mode displays diagnostic messages and other information from the library in the console window.

robotmanager version

Displays the DIVArchive Robot Manager software release information. You can also use -v instead of version.

robotmanager help

This displays all command line options.

Testing the Robot Manager Library Interface

After configuring the Robot Manager configuration file, launch the DIVArchive Robot Manager and confirm that the library itself can be controlled.

Library interfaces that use ACSLS, SDLC, or PSC intermediate control software must be running before launching the DIVArchive Robot Manager. ACSLS controlled libraries should also be varied online (for example, vary lsm0 online).

Starting, Stopping, and Restarting the Robot Manager

Windows DIVArchive Robot Managers start automatically with Windows. You manage (start, stop, restart, and so on) the service through the Windows Services applet.

Note:

If the library is offline when the service is started, the Robot Manager does not automatically reconnect after the library comes online. You must restart the service to connect.

You can also stop and then start (restart) a Robot Manager from a command window. The quotation marks in the commands must be used when specifying a service with spaces in the name. Use the following command sequence to stop and then start the service:

net stop "DIVArchive Robot Manager"
net start "DIVArchive RobotManager"

You use the following command sequence if the SERVICE_NAME is specified in the robotmanager.conf file:

net stop "DIVArchive Robot Manager SERVICE_NAME"
net start "DIVArchive RobotManager SERVICE_NAME"

Testing the Robot Manager Library Control

Caution:

These utilities must not be used in a live DIVArchive system. You must not send commands to a Robot Manager using either of these utilities under any circumstances when the DIVArchive Manager is running. Oracle is not responsible for any complications arising from inappropriate use of these utilities.

You can use either the Robot Manager Client (a command-line interface) or GUI to establish basic control functionality of a Robot Manager to its controlled libraries. You can use either of these utilities to send manual commands to a DIVArchive Robot Manager to initiate simple operations, for example, drive mounting, dismounting, enter or eject operations from the CAP (Cartridge Access Port). Both utilities connect to a Robot Manager through TCP/IP and can be run from a remote computer. This feature enables the Robot Manager GUI to be used from a remote computer.

If you mount a tape with either of these utilities, you must first unload the tape before it can be dismounted, unless the library supports Forced Dismount commands and they are enabled in the DIVArchive Robot Manager configuration file.

Robot Manager Client

This command-line client is typically located with the Robot Manager executable files in the %DIVA_HOME%\Program\RobotManager\bin folder.

You must specify the IP address of the Robot Manager and its TCP port when launching the client as follows:

RobotManagerClient {IP_Address} {TCP_Port}

The IP_Address is the IP address of the Robot Manager computer, and the TCP_Port is the Robot Manager listening port. You can hard-code these two parameters in the Robot Manager Client batch file if there is only a single Robot Manager requiring access.

All of the client commands are self-explanatory after you start the program.

Robot Manager Client GUI

The Robot Manager Client GUI is typically located with the Robot Manager executable files located in the %DIVA_HOME%\Program\RobotManager\bin folder. The GUI provides the same functionality as the command line client. You execute RobotManagerGUI.bat to open the GUI interface.

The GUI interface includes the following buttons and functionality:

Connect Button

Click this button to connect to the DIVArchive Robot Manager. You must enter the IP address and TCP port of the DIVArchive Robot Manager to be tested in the Connect prompt.

Tape List Button

Click this button to load the tape list from the library.

Reload Config. Button

Click this button to reload the configuration.

Exit Button

Click this button to exit the program.

Tape List

To manually mount a tape, select a Barcode ID and drag and drop it on to one of the drives displayed in the LSM list.

LSM List

This area lists all of the available drives and the tapes in the drive. You right-click a tape and select Dismount from the menu to dismount a tape.

CAP List

To manually eject a tape from the library, select a Barcode ID and drag and drop it to one of the listed CAPs.

Status Area

The Status area is at the bottom of the screen and displays status messages from the Robot Manager.

Configuring the Robot Manager at the System Level

At the system level, each instance of the DIVArchive Robot Manager must be declared to the DIVArchive Manager in the Robot Managers frame of the Robots tab in the DIVArchive Configuration Utility.

You use frame buttons to add (+), edit (Edit), or delete (-) a Robot Manager. The Update frame button refreshes the displayed Robot Manager information from the database.

Clicking the + button adds a Robot Manager to the configuration. The Add new row in Robot Managers dialog box is displayed. Enter the following information in the appropriate fields and then click OK to add a Robot Manager:

Name

The name of the DIVArchive Robot Manager attached to this DIVArchive system.

Address

The IP address of the host running the DIVArchive Robot Manager installation.

Port

The Robot Manager TCP port. This must match the RM_PORT parameter specified in robotmanager.conf.

Site

The DIVArchive Manager uses this parameter to determine optimal use of resources in resource allocation. Use the menu list to select the appropriate site for this Robot Manager. Site Selection must be enabled in the DIVArchive Manager configuration file or all sites are considered equally.

Robot Manager-ACS Association

Each DIVArchive Robot Manager is logically referred to by the DIVArchive Manager using its Automatic Cartridge System (ACS) number. This value should be unique among all DIVArchive Robot Managers. Individual libraries (or frames) are typically referred to by their Library Storage Module (LSM) number.

Use the following procedure to associate a Robot Manager with an ACS:

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize Robot Manager ACS Associations check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

  6. Confirm correct, successful, operation in the Status area at the bottom of the screen.

  7. Enter the details for each library in the Library Data Entry dialog box when prompted, and then click OK to continue.

  8. Click Close to exit the Database Synchronization dialog box.

  9. Confirm the association in the Robot Managers-ACS frame.

Logging Robot Manager Activity

During normal operation, each DIVArchive Robot Manager logs its communications with the library and stores them in the %DIVA_HOME%\log\robot_manager folder. These logs are useful for troubleshooting issues. You may be asked to provide the log files when contacting Oracle Support.

The most recent log file is named robot_manager.log or robot_manager_SERVICE_NAME.log and is located in the ..\log\robot_manager folder. Older logs are renamed with the time it was saved as its file name and moved to dated subfolders under the name of each Robot Manager.

Configuring Media and Drive Types

After you have successfully configured the DIVArchive Robot Manager for your libraries, and the appropriate details for all DIVArchive Robot Managers entered into the Robots tab section of the Configuration Utility, the Tape Media, Drive Models, and the Drive Locations currently installed in each library must be entered.

The following flowchart lists the workflow of this portion of the configuration. All of the DIVArchive Robot Managers configured must be running and successfully connected to each library before commencing this portion of the configuration.

Media and Drive Types Configuration

Tape Drives and their associated media types that are installed in a particular library are initially configured in the DIVArchive Database using static configuration files. The files are located in the %DIVA_HOME%\Program\conf\robot_manager folder. The DIVArchive Robot Manager selects the appropriate files according to the RM_MODULE setting configured in robotmanager.conf.

The following list identifies the configuration file names and use:

scsi_drive_types.ini and scsi_tape_types.ini

Used for direct attached SCSI libraries. These files are only considered if the .ini extension is removed.

acsls_drive_types.ini and acsls_tape_types.ini

Used for libraries managed by ACSLS. Normally, tape and drive types are derived from ACSLS during library synchronization with the database. However, you can use these files to override the values returned from ACSLS. These files are only considered if the .ini extension is removed.

adic_media_types.ini

Used with ADIC libraries controlled by SDLC. Drive Types for this library are directly returned from the SDLC server. These files are only considered if the .ini extension is removed.

When a hardware audit is initiated on the specific library by the Configuration Utility (through the DIVArchive Robot Managers, either directly or through intermediate library management software), hexadecimal codes are returned to identify the model and order of the tape drives currently installed, and the media types present in the library.

These library hardware codes are mapped to drive and media IDs within the DIVArchive Database using the Tape Types and Drive Types configuration files.

It is only necessary to modify these files when Drive Types or Media Types are added to the library.

SCSI_drive_types and ACSLS_drive_types

You can edit these files using any plain text editor (for example, Notepad or Notepad++). No modification of these files is required other than to remove comment fields for the appropriate library and drive types for your installation.

Remove the # at the beginning of the line in the appropriate library section for the drives to be recognized in a Synchronize Drive Types List in the Configuration Utility. You must leave drive types in libraries not installed commented out.

The Compatible Drive Types column cross-references the Tape Type ID in SCSI_Tape_Types (or ACSLS_Tape_Types if used). These values are examined in the Synchronize Media/Drive Compatibility List procedure in the Configuration Utility.

SCSI_tape_types and ACSLS_tape_types

You can edit these files using any plain text editor (for example, Notepad or Notepad++). No modification of these files is required other than to remove comment fields for the tape types for your specific library.

Remove the # at the beginning of the line in the appropriate library section for the tapes or DVDs to be recognized in a Synchronize Media Types List in the Configuration Utility. You must leave tape types (or DVDs) in libraries not installed commented out.

The Compatible Drive Types column cross-references the Drive Type ID in SCSI_Drive_Types (or ACSLS_Drive_Types if used). These values are examined in the Synchronize Media/Drive Compatibility List procedure in the Configuration Utility.

ADIC_media_types

You can edit these files using any plain text editor (for example, Notepad or Notepad++). No modification of these files is required other than to remove comment fields for the tape types for your specific library.

Remove the # at the beginning of the line in the appropriate library section for the tapes to be recognized in a Synchronize Media Types List in the Configuration Utility. You must leave tape types in libraries not installed commented out.

The Compatible Drive Types column cross-references the Drive Type ID returned from the SDLC controller. These values are examined in the Synchronize Media/Drive Compatibility List procedure in the Configuration Utility.

Defining Tape Capacity and Block Sizes

The values in the following two tables must be used when entering adding a Drive Type or Media Type in the DIVArchive Database. The values have been tuned by Oracle to avoid tape spanning, and therefore may be lower than the theoretical capacity.

The following table identifies tape capacities to use when entering a Drive Type or Media Type in the database:

Table 5-12 Tape Capacity Definitions

Media Type Drive Type Capacity

9840

STK 9840A

STK 9840B

STK 9840C

19 531 008

19 531 008

39 062 272

9940

STK T9940A

STK T9940B

58 593 536

195 312 384

T10000T1

STK T10000A

STK T10000B

488 281 008

976 562 176

T10000TS

STK T10000A

STK T10000B

STK T10000C

STK T10000D

STK T10000D (maximum capacity enabled)

117 187 072

234 374 656

5 243 000 000

7 812 500 480

8 300 781 056

DTF-2

GY-8240

195 312 448

SAIT1

S-AIT 1

488 281 088

SAIT2

S-AIT 2

781 249 536

AIT3

AIT 3

97 656 192

DLT-IV

Quantum DLT7000

34 179 648

LTO-100G

IBM, HP, Seagate LTO-1

97 656 192

LTO-200G

IBM LTO-2

195 312 128

LTO-400G
LTO-400W

IBM or HP LTO-3

390 624 768

LTO-800G
LTO-800W

IBM or HP LTO-4

781 249 536

LTO-1.5T
LTO-1.5W

IBM or HP LTO-5

1 464 843 264

LTO-2.4T
LTO-2.4W

IBM or HP LTO-6

2 441 405 952

LTO-6.4T
LTO-6.4W

IBM LTO-7

5 859 374 592

LTO-9.0T

IBM LTO-8 (M8)

8 789 062 500

LTO-12.8T
LTO-12.8W

IBM LTO-8

11 718 750 000

3592-JA
3592-JW

3592-J1A

TS1120

TS1130

292 968 750

488 281 250

625 000 000

3592-JB
3592-JX

TS1120

TS1130

TS1140

683 593 750

976 562 500

1 562 500 000

3592-JK

TS1140

TS1150

488 281 250

878 906 250

3592-JC
3592-JY

TS1140

TS1150

3 906 250 000

6 835 937 500

3592-JL

TS1150

TS1155

1 953 125 000

2 929 687 500

3592-JD
3592-JZ

TS1150

TS1155

9 765 625 000

14 648 437 500

The following table identifies tape block sizes to use when entering a Drive Type or Media Type in the database:

Table 5-13 Tape Block size Definitions

Manufacturer Tape Drive Type Block Size in Bytes

HP

LTO Ultrium 1

LTO Ultrium 2

LTO Ultrium 3

LTO Ultrium 4

65536

524288

524288

524288

IBM

LTO Ultrium 1

LTO Ultrium 2

LTO Ultrium 3

LTO Ultrium 4

LTO-5

LTO-6

LTO-7

LTO-8

65536

524288

524288

524288

524288

524288

524288

524288

Oracle StorageTek

T9840A

T9840B

T9840C

T9940A

T9940B

T10000A

T10000B

T10000C

T10000D

262144

262144

262144

262144

262144

524288

524288

524288

524288

Quantum

DLT 7000

65536

Seagate

LTO Ultrium 1

65536

Sony

GY-8240 (DTF-2)

AIT-3

S-AIT 1

S-AIT 2

65536

65536

524288

262144

Synchronizing Media Types with the Database

You must import the values that have been uncommented in the Tape_Types configuration files into the DIVArchive Database. Each DIVArchive Robot Manager to be queried must be online to complete this procedure successfully.

Use the following procedure to import and synchronize the values from the Tape_Types files in the database:

Caution:

Only perform this operation if you are adding Media Types to the library.

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize media types list check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

    The Configuration Utility will connect to the DIVArchive Robot Manager. The Robot Manager parses the SCSI_Tape_Types (or ACSLS_Tape_Types if used) configuration file.

  6. If a Tape Type is not currently in the database, you will be prompted to enter it. Click No for any Tape Types not currently in use.

    Note:

    If you report cleaning tapes in the following two steps, you must enter a Tape Size and Block Size of 1 KB for each cleaning tape added so they do not interfere with the total available size computation of all tapes in the Control GUI.

  7. Enter the Total Size for this Media Type and click OK.

  8. Enter the Block Size for this Media Type. Ensure you enter the Block Size correctly before clicking OK because you cannot change it later.

  9. Click Close to exit the Database Synchronization dialog box.

  10. Confirm the Tape Type has been correctly entered in the Tape Properties frame of the Configuration Utility Tapes tab.

Synchronizing Drive Types with the Database

You must also import the uncommented values in the Drive_Types configuration files into the DIVArchive Database. Each DIVArchive Robot Manager to be queried must be online to complete this procedure successfully.

Use the following procedure to import and synchronize the values from the Drive_Types files in the database:

Caution:

Only perform this operation if you are adding Drive Types to the library.

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize drive types list check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

    The Configuration Utility will connect to the DIVArchive Robot Manager. The Robot Manager parses the SCSI_Drive_Types (or ACSLS_Drive_Types if used) configuration file.

  6. If a Drive Type is not currently in the database, you will be prompted to enter it. Click No for any Drive Types not currently in use.

  7. Enter the Block Size for this Drive Type. Ensure you enter the Block Size correctly before clicking OK because you cannot change it later.

  8. Confirm there are no errors in the status window. If errors appear, recheck the Tape_Types and Drive_Types definition files.

  9. Click Close to exit the Database Synchronization dialog box.

  10. Confirm the Drive Type has been correctly entered in the Drive Properties frame of the Configuration Utility Drives tab.

Synchronizing Media and Drive Compatibility with the Database

This step cross-references the compatibility entries in the Tape_Types and Drive_Types definition files.

For libraries controlled by ACSLS Media and Drive Type, information is normally retrieved directly from ACSLS,. Therefore, an ACSLS software upgrade or a library firmware update may require the Media and Drive Type settings to be resynchronized.

Use the following procedure to synchronize the media and drive compatibility in the database:

Caution:

Only perform this procedure is you are adding a Media or Drive Type, or updates are made to the Tape or Drive Types definition files in a DIVArchive software update.

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize media/drive compatibility list check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

    The Configuration Utility will connect to the DIVArchive Robot Manager. The Robot Manager parses the SCSI_Tape_Types (or ACSLS_Tapes_Types if used) configuration file.

  6. Confirm there are no errors in the status window. If errors appear, recheck the Tape_Types and Drive_Types definition files.

  7. Click Close to exit the Database Synchronization dialog box.

  8. Confirm the Media Type and Drive Type associations have been correctly entered in the Media Compatibility frame of the Configuration Utility Robots tab.

Synchronizing the Library Drive List with the Database

If you add Drive Types or additional drives to a DIVArchive Managed Library, you must declare them in the DIVArchive Database. Drives that are added are initially set Offline, and therefore disabled. Before they can be used, you must set them Online and notify the Manager (if running). During DIVArchive operations, the Manager may automatically set a drive Offline if it encounters a problem with it.

When the Used field in the Drives frame is set to N, DIVArchive ignores the drive and it is not displayed in the Control GUI Drives tab. If you subsequently set a drive to Y, DIVArchive will not use it until you notify the Manager. This field restricts using drives in libraries that are shared with other backup or archive applications.

The Operations field in the Drives frame defines which operations are permitted on each drive. Operations can be one of the following:

R

The drive is dedicated to only Repack operations.

S

The drive will perform all standard operations only. That is, all operations except Repack.

A

The drive can perform all operations including Repack.

N

The drive will not be used for any operations. However, it can be enabled later without a Manager restart.

Use the following procedure to add the drives to the database:

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize drive list check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

    The Configuration Utility will connect to the DIVArchive Robot Manager. The Robot Manager obtains the current drive list and drive location for each drive from the library.

  6. Confirm there are no errors in the status window. If the drives reported from the library do not match those declared in the Drive Properties frame, an error is displayed and no drives are entered into the database.

  7. Click Close to exit the Database Synchronization dialog box.

  8. Confirm the drives have been correctly entered in the Drives frame of the Configuration Utility Drives tab.

Manually Identifying Drive Serial Numbers

When using a tape library with DIVArchive there are two logical connections to each drive in that library. The first is the Robotics Control (managed by the DIVArchive Robot Manager) for mounting and dismounting the tapes from specific drives, and the Data Interface to the drive from the Actors.

Tape libraries identify their drives by the Drive ID (typically 0, 1, 2, and so on). DIVArchive needs to know the corresponding data path to that drive from each Actor when the Robot Manager instructs the library to mount a tape to a specific Drive ID. If the Actor-Library mapping is incorrect, DIVArchive attempts to read or write to the incorrect drive, resulting in possible data loss or corruption.

The host computer operating system presents each drive to applications using their SCSI ID. The SCSI ID for a drive can vary as hardware is added or removed. This is particularly true when shared among multiple hosts in a SAN based environment. This configuration requires statically configured SCSI IDs using persistent bindings. This configuration dramatically complicates drive replacement.

To simplify configuration and streamline future drive replacements, the data path mapping to each drive (for its physical location in the library) is achieved by using its unique serial number rather than its SCSI ID. When a DIVArchive Actor is launched it interrogates each drive's serial number and compares it to the values in the database. Then the Actor establishes the correct data path to the drive, irrespective of its SCSI ID.

Each drive's serial number is automatically identified by library synchronization with the database during initial installation or drive replacement. Some cases may require you to manually determine the serial number and enter it into, or verify it against, the database.

You can manually identify the drive serial number either using the library's front panel display, or using the Scandrive Utility and the Robot Manager Client or GUI.

The latter method involves mounting a tape into a specific drive number in the tape library, establishing which drive the Actor is reporting that has that tape mounted, and then recording its serial number and entering, or verifying, it with the corresponding library Drive ID in the database. You must only complete this process one time for each drive in the library.

Caution:

The Robot Manager Client GUI utility issues direct commands to the Robot Managers and will interfere with DIVArchive operations. It interacts directly with both the Robot Managers and the Tape Drives in the libraries. You must not use it while the DIVArchive Manager is running.

You can use the Robot Manager Client GUI utility to send manual mount commands to a DIVArchive Robot Manager. See the Robot Manager Client GUI section for information.

The serial number of each drive can be discovered by using the scandrive.exe utility located in the %DIVA_HOME%\Program\Actor\bin folder. This utility automatically reports all SCSI devices installed in the host computer, and their corresponding port, bus, target and logical unit numbers. For tape devices, the utility also indicates the drive's firmware, serial number, and whether a tape is loaded into the drive.

After a tape is mounted in a drive (using the Robot Manager Client GUI), run the scandrive.exe utility on an Actor host (that will use the selected drive) to determine which drive has the tape mounted and its corresponding serial number.

See Determining the SCSI Library Connection for information on using the Scandrive utility.

In the following figure the Type section refers to that peripheral's class (HDD, CDROM and so on). Each tape drive will be reported as a TapePeripheral, and the Identifier for each corresponding device should match the model number of the drive itself (for example, IBM Ultrium TD2).

Confirm the tape barcode is the correct one loaded through the Robot Manager Client GUI. You must then enter the serial number for the appropriate drive by highlighting it in the Drives section of the Configuration Utility, and then selecting Edit. Repeat the process by mounting a tape into the next library drive.

Remember to dismount the tape after determining the drive's serial number.

Scandrive Uitlity Output Showing Tape Drives

Synchronizing the Library Tapes with the Database

Each tape inserted into a library is initially identified by its barcode label. DIVArchive keeps track of tapes currently in the library and that have been externalized in its database.

The labels and status (whether internalized or externalized) are updated in the database by Insert Tape or Eject Tape commands issued to DIVArchive. The database can become out of synch with a library's contents when tapes are added or removed directly in the library rather than through DIVArchive.

Use the following procedure to re-synchronize the tape list in the database with the library contents:

Tip:

This procedure is a quick way to populate the database with tapes from the library when tapes are initially loaded.

  1. Open the Configuration Utility and connect to the database.

  2. Select the Synchronize DB option from the Tools menu and acknowledge the warning message.

  3. Select the individual Robot Manager to synchronize from the menu list in the Database Synchronization dialog box, or select ALL to synchronize all Robot Managers.

  4. Only select the Synchronize tape list (can be very long) check box. Confirm that all other check boxes are deselected.

  5. Click Go to update the selected associations.

    The Configuration Utility will connect to the DIVArchive Robot Manager. The Robot Manager obtains the current tape list from the library.

    Tapes in the library are compared to the tape tables in the DIVArchive Database. New tapes are inserted into the table and existing tapes have their status updated (internalized or externalized).

  6. If a Tape Type is reported that does not match the types configured in the Tape Properties frame, an error is reported and no update of the database occurs. This type of error can also occur if a library cannot correctly read a tape's barcode label. You must carefully check the Robot Manager logs in this case.

  7. Click Close to exit the Database Synchronization dialog box.

  8. New tapes discovered during the audit are added to the Unused Tape Sets frame in the Sets, Groups, & Media Mapping tab of the Configuration Utility, and assigned Set ID 1. Tapes currently tracked by DIVArchive that are missing from the audit will have their status updated to externalized. You can examine the status of all tapes in the DIVArchive Control GUI.

Creating Tape Groups

You use the Sets, Groups, & Media Mapping tab of the Configuration Utility to define Tape Groups within the archive. Groups segment material within the tape library, or associate content with a particular Media Type. The default group is present in all installations and cannot be removed. However, you can specify your own Group Names and not use the default group. Generally, the Group Name is descriptive of the function or content that is being stored.

A group is associated with a Set ID defining the pool of tapes it can draw upon to store DIVArchive objects. When DIVArchive writes an object to a tape from the pool, the tape is assigned to a group. It is released from the group when all objects have been deleted or the tape has been repacked.

The group concept in combination with the Set ID enables optimal use of tape resources. Some tape drives and media are extremely fast but typically have less storage than their larger capacity (and slower) counterparts. Content that is small, or required very quickly, should be archived to this group and should use the faster drives.

For example, the 9840C tape drive is small in capacity, but it provides extremely fast access times (approximately fifteen seconds from mount to data retrieval), and is better suited to storing large numbers of relatively small data files. This is particularly true related to tape repacking.

For example, if the Commercials Group is allocated Set ID 3 and all 9840C tapes are assigned to that set. Short form commercial material written to tape will exclusively use the 9840C media. Longer (and larger) material, such as movies and interstitial programs are better suited to the larger capacity tape sets.

See Sets, Groups & Media Mapping Tab Frames for information displayed on the Groups frame.

Tape Group Encryption

Starting with the DIVArchive 7.6 release, tape drive encryption securely supports bulk tape migration between DIVArchive systems. You enable, disable, or update tape group encryption in the Configuration Utility. Tape group encryption is disabled by default.

After enabling encryption on a tape group, all additional tapes added to the group will also be encrypted. However, any existing tapes in the group remain unencrypted if encryption was previously disabled.

Enabling encryption on a tape group generates an encryption key, which is also encrypted. You can change the encryption key at any time. Use the following procedure to enable, disable, or update the encryption key:

  1. Navigate to the Groups view of the Sets, Groups & Media Mapping tab in the Configuration Utility.

  2. Double-click the tape group from the list on the Groups view to display the Edit Groups Entry screen.

  3. Select Enable, Disable, or Update from the Encryption options list.

    When you enable encryption any new tape added to the group will be encrypted. However, any tape already in the group at the time of this assignment is unaffected and remains unencrypted if encryption was previously disabled on the group. You will receive a warning that you are about to enable encryption on the group when you click OK.

    Disabling encryption (after it is already enabled) only affects additional tapes added to the group, and the existing tapes remain encrypted.

    Updating the encryption generates a new key. You will receive a warning notifying you that a new encryption key will be assigned to the group, and that any new tapes added will use the new encryption key. The existing tapes that were already encrypted will continue to use the original key. Therefore, tapes in the same tape group can have different encryption keys. You must notify the Manager of the change when updating the encryption key.

  4. Click OK to save your changes.

DIVArchive generates an encoded 256-bit encryption key. For security reasons, the encryption key is also encrypted. If you disables and re-enable encryption on a group, the same encryption key is used.

You can view the encryption status of the tape on the Home, Tapes screen in the Control GUI.

See the Oracle DIVArchive Operations Guide, and the Oracle DIVArchive Export/Import User's Guide in the Oracle DIVArchive Core documentation library for detailed information.

Creating Tape Sets

When a new tape is entered into a library, or DIVArchive clears a tape of its objects (whether all objects on that tape have been deleted, migrated to another tape, or moved to another tape after a tape repack), the tape is released back to the Unused Tapes Sets pool.

New tapes are automatically assigned a Set ID1, which is the default in all DIVArchive installations. Other Set ID numbers are typically used to distinguish between different types of media, but could be used to create restricted pools of tapes for particular applications. If this is the case in your installation, the Set ID must be updated for these tapes after they are inserted into the library.

See Sets, Groups & Media Mapping Tab Frames for information displayed on the Unused Tape Sets frame.

Remapping Media

You can put transformation rules in place for the specified groups on Archive requests on the Media Mapping frame in the Sets, Groups & Media Mapping Tab. The remapped destination media can be either a disk array, tape group, or a storage plan. This is not typically used during initial installation, but rather at a later time in the object's life cycle.

Transformation rules allow transparent redirection of objects from one media type to another without needing to alter the archive initiator. Some examples are migration of an existing group to a new drive or tape generation, or migration from tape to disk.

Note:

You must use a migration job to change a tape format from Legacy to AXF. Repacking a tape will not change the tape format. Repacking of existing Legacy format objects retains the format of the tape even if the tape group format was updated in the configuration from Legacy to AXF.

The following events appear in the request details when an object's media is remapped to another media, a storage plan, or both:

  • Media Name Translation has changed the Destination Media to media.

  • Media Name Translation has changed the Destination Media to storageplan.

  • Media Name Translation has changed the Destination Media to media & storageplan.