This chapter describes a general overview of the DIVArchive configuration and includes the following information:
Each DIVArchive software module has its own static configuration text file with parameters needed to launch that particular application. The files are typically denoted with the .conf file name extension. There are some DIVArchive modules that use an XML based file rather than a text file for their configuration and those will be noted where applicable.
Unlike older releases of DIVArchive that stored these configuration files in the same folder as the application itself, DIVArchive 7.6 centralizes them to a dedicated conf subfolder under the DIVArchive Program Group.
The configuration files are typically updated with additional or changed settings in newer releases of the software. A new or patch release of DIVArchive will have the new releases of the .conf files appended with a .ini extension. For example, the new release of the DIVArchive Manager Configuration file will be named manager.conf.ini. You must remove the .ini extension after the installation is complete and the new configuration file updated.
Each configuration file can be opened and edited with any plain text editor (for example, Windows Notepad).
Any changes made to the configuration file of a DIVArchive software component requires that the component be shut down and then restarted for the changes to take effect. The exceptions to this are the Manager and Access Gateway options, both of which allow configuration changes to be reloaded while they are still running. There are codependencies between some applications in the DIVArchive platform, so other components may also need to be restarted for changes to take effect.
At the system level, settings that relate to the overall operation of each DIVArchive component and their interaction are configured and retained by an Oracle Database. This is commonly known (and will be referred to in this document) as the DIVArchive Database (or just simply as the database).
User modification of this database is performed through the DIVArchive Configuration Utility.
The DIVArchive Configuration Utility connects only to the database and does not necessarily require the DIVArchive Manager to be running. It is only intended for experienced users and caution should be exercised when altering settings using the utility. An incorrect setting can impede DIVArchive operations or prevent the DIVArchive Manager from starting successfully. Contact Oracle Support for assistance if you are unsure about making a particular change.
When launched, the DIVArchive Manager obtains the DIVArchive system configuration from the database. However, it does not poll the database for changes made through the Configuration Utility. Therefore, the database must be notified of any changes made. This is performed using the Notify Manager menu item in the Configuration Utility.
You can accomplish most changes to the configuration while the DIVArchive Manager is running. There are a small number of configuration changes that require a restart of the DIVArchive Manager to become effective. A full list of changes that can be made to the system configuration dynamically while the Manager is running is listed in Appendix B.
The Configuration Utility also does not dynamically poll the database for changes that are made when the Manager is running. In such cases, you click the Update button in the utility to refresh the information displayed from the database.
You can install the Configuration Utility on any computer that has TCP/IP connectivity to the database and a supported Java Runtime Environment installed. DIVArchive release 7.6 requires the Java Runtime Environment 64-bit (build 1.8.0_45-b14), to be installed to launch the Configuration Utility successfully.
In some cases, a network firewall between the two can prevent a connection. For complete operation and functionality of the Configuration Utility, the Oracle Listener Port (typically 1521) and the DIVArchive Robot Manager Ports (typically 8500 and higher) must be opened in the firewall. Full functionality of the Control GUI also requires that the DIVArchive Manager Port (typically 9000) is open.
The DIVArchive Metadata Database has very high performance and almost unlimited scalability. The Metadata Database should be treated with the same caution as the Oracle Database. It should be backed up at regular intervals through the DIVArchive Backup Service.
Oracle highly recommends that the Metadata Database files are stored on a RAID disk array. The Metadata Database should not be on a standard disk due to decreased performance and the real-time backup functionality that a RAID array offers the system.
Metadata Database files stored on a standard disk are vulnerable to data loss if a single disk failure until the information is replicated through the DIVArchive Backup Service. Storing the Metadata Database files on a RAID array isolates the data from this type of failure.
The information stored in the Oracle Database is already stored on a RAID-1 array and is not subject to data loss if a single disk fails.
The following formula can be used as a rough guide to determine the minimum amount of disk space required to support the Complex Object Metadata Database:
(100+average_path_filename_size)*1.15*avg_num_component_files*num_objs
The following is a general example using the equation:
average_path_filename_size = 60For example, this/nested/subdir01/As_The_World_Turns_24fps_scenes1-10.avi
avg_num_component_files = 200,000The Average Number of Files and Folders within the complex object.
num_objs = 50,000The number of complex objects to be archived.
In this example, minimum budgeting for a Metadata Database size of approximately 1.67 TB would be recommended.
When planning the system, you must allocate enough Metadata Database disk space to ensure for expected, or unexpected, growth of the environment. The same amount of disk space must also be allocated for the Metadata Database in all of the backup systems.
Some DIVArchive software components may require defining one or more Windows operating system environment variables for those components to launch successfully.
An environmental variable allows the configured variable to be available to all programs rather than requiring it to be configured from the application each time it is executed. This makes the variable independent of the application and therefore you do not need to manually insert or update the value when the application software is updated or modified.
A User Environmental Variable only applies to an individual Windows User Profile. A System Environmental Variable is applicable to all Windows User Profiles.
The following example illustrates how to configure the DIVA_JAVA_HOME environment variable on a Windows system.
Note:
This is simply an example and NOT required for DIVA_JAVA_HOME as it is already pointing to a valid JRE after installation.This variable defines the path of the Java Runtime Environment for DIVArchive applications on the Windows host. This particular parameter is required on any Windows computer that will run either the DIVArchive Configuration Utility or the DIVArchive Control GUI.
Use the following procedure to configure an environment variable:
Open the Windows Control Panel.
Double-click the System icon.
Click the Advanced tab.
Click the Environment Variables button.
Click the New button.
Enter the variable name in the Variable name field. In this example the name is DIVA_JAVA_HOME.
Enter the variable value in the Variable value field. This is the path (or other value) to use for the named variable. In this example the value is C:\DIVA\java.
Click OK to complete the process.
You have now defined the variable and it is displayed in the System variables list. The DIVA_JAVA_HOME environment variable is now accessible to all users (and applications) on the system and does not need to be defined each time an applications is executed.
DIVArchive 7.6 introduces SSL Certificate Authentication for authentication of services, and securing the internal and API communications in DIVArchive. Certificate authentication provides unique identification and secure communications for each DIVArchive service in a network.
Certificate authentication functions similar to identification cards like passports and drivers licenses. For example, passports and drivers licenses are issued by recognized government authorities. SSL (Secure Sockets Layer) certificates are signed by a recognized CA (Certificate Authority). An SSL certificate verifies the identity of its owner. When the SSL certificate is presented to others, it helps verify the identity of its owner based on the quality of the contents of the certificate.
DIVArchive it comes with Default Root Certificate Authority called DIVA_CA. The DIVA_CA is a self signed CA created for this purpose, and signs all SSL certificates for the DIVArchive services. Every DIVArchive service now has its own password protected private keys and an SSL certificate which will be signed by the DIVA_CA.
See SSL (Secure Sockets Layer) and Authentication for configuration information.
You can use external third party CAs (for example, VeriSign, Comodo, and so on) with DIVArchive. The external CA must create a CSR (Certificate Signing Request) for DIVA_CA, signed by the third party CA, and the third party certificate must be added to the Trust Store to satisfy the certificate chain.
See SSL (Secure Sockets Layer) and Authentication for instructions to create the CSR, and installing the thirty party CA in your DIVArchive installation.
Caution:
The Configuration Utility is intended only for experienced users. Incorrect or incomplete changes in the Configuration Utility can adversely affect DIVArchive operations (and possibly even delete data from the archive), or prevent the DIVArchive Manager from running. Contact Oracle Support for assistance if you are unsure about making desired changes.The DIVArchive Configuration Utility primarily connects to the DIVArchive Database, and for some tasks, directly to the DIVArchive Robot Managers (if installed). After launching the utility you must first connect to the database to edit the DIVArchive system configuration. The Oracle user name and password for DIVArchive is arbitrary and can vary between installations. These details are documented in the DIVArchive Site Configuration for your site.
The utility can be installed and run on any computer with TCP/IP connectivity to the DIVArchive Database, Manager, and Robot Managers. Because it is a Java-based utility, a valid Java Runtime Environment (JRE) must also be installed on the host. For the Configuration Utility to launch, the DIVA_JAVA_HOME environmental variable in the host operating system must also be defined (see the previous section). This variable should match the absolute directory path to the JRE bin folder. For example DIVA_HOME\Java (where DIVA_HOME is the chosen DIVArchive installation directory). The required release of Java is delivered with DIVArchive, and installed during the DIVArchive installation process.
Use the following procedure to connect the Configuration Utility to the DIVArchive database:
Open the DIVArchive Configuration Utility.
Click File, and then Connect.
Alternatively click the Connect icon just under the File menu.
Enter the following information in the fields on the DB Connection dialog box:
The database user name (typically diva).
The Oracle password associated with the entered user name.
The Oracle System Identifier (typically lib5).
The IP address of the computer where the DIVArchive Database is installed.
The Oracle Listener Port (typically 1521).
Click OK to connect to the database.
The connection status is displayed in the notification area at the bottom of the screen. If the connection fails an error message is generated, including an error code, and displayed in this area. Contact Oracle Support if you still cannot connect after attempting to resolve the error.
Disconnect the Configuration Utility from the database when not in use. Use the following procedure to disconnect from the database:
Click File, and then Disconnect.
Alternatively click the Disconnect icon just under the File menu.
Click Yes in the displayed Confirm dialog box.
Click OK in the displayed Disconnected dialog box.
The notification area at the bottom of the screen will display the Not Connected message.
Each frame in the Configuration Utility includes a set of buttons that perform various functions as follows:
This button is a plus sign (+). Clicking the button launches a dialog box to add an entry to the frame.
Highlighting a frame entry and clicking this button enables editing of the entry's properties.
This button is a minus sign (-). Highlighting a frame entry and clicking this button will remove the entry from the frame. Entries with child dependencies cannot be removed.
Clicking this button refreshes the associated frame content listing from the database.
The DIVArchive Control GUI provides four fixed user profiles (Administrator, Operator, Advanced Operator, and User) to provide varying levels of access. The Administrator, Operator, and Advanced Operator profiles require a password that you can change using the Configuration Utility.
The difference between the Operator and Advanced Operator profiles are the Insert and Eject commands, which are only accessible from the Advanced Operator profile. You use the Operator profile during normal operations unless you are inserting or ejecting a tape.
There is no default password to log in to the Control GUI as an Administrator or Operator. You must assign an Administrator and Operator password in the Configuration Utility after DIVArchive installation is complete. Without an assigned password you are not permitted to switch to the respective profile in the Control GUI. If you attempt to switch to Administrator or Operator mode without first assigning a password to the profile, an error message is displayed notifying you that you must set a password. After you set the profile password in the Configuration Utility the first time, it no longer matters what you use for the old password when changing passwords.
Use the following procedure to set the Administrator password:
Open the Configuration Utility.
Connect to the DIVArchive Database.
Click the Tools menu item.
Click the Change GUI Administrator Password menu item (or use Control+G).
This option is only available when the Configuration Utility is connected to the database.
Enter the following information in the appropriate fields on the Change GUI Administrator Password dialog box:
Enter the old Administrator password in the Old Administrator Password field. You must leave this field blank the first time you set the Administrator password.
You enter the new password in the New Password field.
You enter the new password again in the Confirm Password field.
Click OK to save the password.
Use the following procedure to set the Operator password:
Open the Configuration Utility.
Connect to the DIVArchive Database.
Click the Tools menu item.
Click the Change GUI Operator Password menu item (or use Control+G).
This option is only available when the Configuration Utility is connected to the database.
Enter the following information in the appropriate fields on the Change GUI Administrator Password dialog box:
Enter the Administrator password in the Administrator Password field.
You enter the new password in the New Operator Password field.
You enter the new password again in the Confirm Password field.
Click OK to save the password.
Use the following procedure to change the Database Logging Level:
Open the Configuration Utility.
Connect to the DIVArchive Database.
Click the Tools menu item.
Click the Change DB Logging Levels menu item (or use F12).
This option is only available when the Configuration Utility is connected to the database.
Use the menu lists to select the desired logging level for each package listed in the Change DB Logging Levels dialog box. Available levels are:
When selected, this level displays very severe errors that may cause DIVArchive to terminate.
When selected, this level displays errors that still allow DIVArchive to operate.
When selected, this level displays warning messages that are potentially harmful to operations.
When selected, this level displays informational messages about the progress of the operations.
When selected, this level displays messages used to help debug the system.
Click OK to save your changes.
The following sections describe a general overview of each tab in the Configuration Utility. Each tab includes multiple frames where you configure different aspects of the system.
To notify the Actors of any changes in the Actor configuration, click the Notification menu item, and then Notify Actors while connected to the Manager. The Actors must be running and connected to the Manager to receive the notifications.
The System tab defines key parameters for your DIVArchive installation and is the starting point for creating your DIVArchive configuration.
You should create a drawing of the system components before entering details into the Configuration Utility. The drawing includes the data and control paths between components, how they interact with each other, established naming conventions for resources such as disks and tapes, and the workflow of the platform. Some parameters are difficult to change once they have dependencies from other configuration parameters in the database.
The System tab includes the following frames:
All DIVArchive installations have at least one production system. Additional production systems allow dedication of a particular Actor for specific destinations.
All installations have at least one site. Additional sites are optional and may be considered by the DIVArchive Manager for optimal resource allocation.
Note:
Site Support must be enabled in the DIVArchive Manager configuration, otherwise all sites will be considered equally.These define where DIVArchive archives from (Sources) and restores to (Destinations).
These define Actor host definitions and logical functions. All installations have at least one Actor. See Appendix A for Oracle DIVArchive options and licensing information.
These define DIVArchive transcoders and analyzers. DIVArchive automatically selects the Actors either attached to a Bitstream Flip Factory Transcoder installation or integrated with the DIVAnalyze Harris QuiC compressed file analysis software. DIVArchive allows a single transcoder to perform multiple transcodings. DIVArchive assigns additional ports as needed from the base port specified in the configuration. Therefore, a gap of one hundred between individual transcoder port settings is recommended to avoid port conflicts.
Except for the Service Name and Port, all Actor configuration settings are located in the Configuration Utility under the Actor Advanced and Partial Restore Settings tabs of the Actor frame of the Systems tab. Some settings are only available In Engineering Mode and are labeled with an X in the Engineering Mode column of the following tables.
Table 3-1 Advanced Actor Parameters
| Name | Type | Min. | Max. | Engineering Mode | Default |
|---|---|---|---|---|---|
|
DISABLE_DISK_PREALLOCATION |
Boolean |
X |
Yes |
||
|
TAPE_TEST_UNIT_READY_TIMEOUT (S) |
Integer |
60 |
1200 |
|
|
|
DO_NOT_CHECK_OBJECT_NAME |
Boolean |
No |
|||
|
DO_NOT_CHECK_CATEGORY |
Boolean |
No |
|||
|
SIMULATION |
String |
X |
|||
|
SIMULATION_READING_ERROR_RATE (%) |
Integer |
0 |
100 |
X |
|
|
SIMULATION_WRITING_ERROR_RATE (%) |
Integer |
0 |
100 |
X |
|
|
SIMULATION_TAPE_SIZE (MB) |
Integer |
20 |
500000 |
X |
|
|
SEACHANGE_CHECK_DELAY (MS) |
Integer |
0 |
10000 |
X |
|
|
PROFILE_READ_BLOCK_SIZE (B) |
Integer |
1500 |
262144 |
|
|
|
PROFILE_WRITE_BLOCK_SIZE (B) |
Integer |
1500 |
262144 |
|
|
|
QUANTEL_RENAME_CLIPS |
Boolean |
No |
|||
|
QT_SELF-CONTAINED_THRESHOLD (MB) |
Integer |
10 |
100 |
|
|
|
RENAME_TRANSCODED_CLIPS |
Boolean |
X |
|||
|
DIRECTORY_SERVER_ENABLED |
Boolean |
X |
Yes |
||
|
DISK_FTP_PASSIVE_MODE |
Boolean |
No |
|||
|
DISK_FTP_BLOCK_SIZE |
Integer |
1024 |
524288 |
|
|
|
DISK_FTP_SOCKET_WINDOW_SIZE (B) |
Integer |
65536 |
10485760 |
|
Table 3-2 Partial File Restore Parameters
| Name | Type | Min. | Max. | Engineering Mode | Default |
|---|---|---|---|---|---|
|
QT_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
QT_OMNEON_FIRST_FRAME_HANDLING |
String |
Reset |
|||
|
AVI_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
EVS_MXF_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
GXF_TIMECODE_REFERENCE |
Integer |
0 |
2 |
|
|
|
GXF_PROGRESSIVE_TIMECODE_TRANSLATION |
Boolean |
No |
|||
|
LXF_IGNORE_START_TIMECODE |
String |
No |
|||
|
MXF_PARTIAL_RESTORE_DICTIONARY_FILE |
String |
||||
|
MXF_TIMECODE_FROM_SOURCE_PACKAGE |
Boolean |
No |
|||
|
MXF_TIMECODE_VALUE_TO_SWITCH_PACKAGE |
String |
|
|||
|
MXF_ENFORCE_CLOSED_HEADER |
String |
Yes |
|||
|
MXF_RUN_IN_PROCESSOR |
String |
||||
|
MXF_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
MXF_USE_BMX_LIBRARY |
Boolean |
No |
|||
|
MXF_USE_OMNEON_DARK_METADATA |
Boolean |
No |
|||
|
MXF_SERIALIZE_DEPTH_FIRST |
Boolean |
No |
|||
|
MXF_GENERATE_RANDOM_INDEX_PACK |
Boolean |
Yes |
|||
|
MXF_NUMBER_FRAMES_PER_BODY_PARTITION |
Integer |
50 |
500 |
|
|
|
MXF_UPDATE_TCTRACK_ORIGIN |
Boolean |
No |
|||
|
MXF_TOLERANCE_ON_TCOUT |
Integer |
0 |
250 |
|
|
|
MXF_DURATION_FROM_FOOTER |
Boolean |
Yes |
|||
|
MXF_MAX_QUEUE_SIZE |
Integer |
100 |
1000 |
|
|
|
SEACHANGE_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
MPEG2_TRANSPORT_STREAM_IGNORE_START_TIMECODE |
Boolean |
No |
|||
|
MPEG2_PROGRAM_STREAM_IGNORE_START_TIMECODE |
Boolean |
No |
All DIVArchive installations include the Robots tab, although not every installation necessarily has a library. This tab defines basic associations with the robotics software and hardware components.
The Robots tab includes the following frames:
This frame defines to DIVArchive the connection parameters to each host running a DIVArchive Robot Manager Instance. See Appendix A for Oracle DIVArchive options and licensing information.
Displays the tape or DVD libraries currently configured through one or more DIVArchive Robot Managers and their online status.
This frame maps the Tape Media Type defined in the Tapes tab, to the Drive Types defined in the Drives tab. Although you can manually remove entries in this frame, they can only be added or updated during a database synchronization with a Robot Manager.
This frame associates each Robot Manager with an Automated Cartridge System (ACS) number. Although you can manually remove entries in this frame, they can only be added by performing a database synchronization with the specific Robot Manager.
The Disks tab defines the physical disks that are to be used by DIVArchive, how they are grouped together for either permanent or cache storage, and how each disk is logically accessed by the Actors.
The Disks tab includes the following frames:
An Array defines a logical association of disks in which one or more physical disks are assigned for use by DIVArchive. The Array Name is equivalent to the Group Name for tapes.
The symbolic name and location for each disk in your system, whether confined to a single host or shared between hosts. These disks are then assigned to Arrays.
Configures how each disk is logically connected to each DIVArchive Actor, and how it is to be used. For shared disks accessible by more than one Actor, the disk connection must be declared for all Actors. See Appendix A for Oracle DIVArchive options and licensing information.
Configures how each object storage account is logically connected to each DIVArchive Actor, and how it is to be used. See Appendix A for Oracle DIVArchive options and licensing information.
The Drives tab is where the drives in your tape libraries are identified and configured for use with DIVArchive and its Actors. In some installations, a tape library and its drives may be shared with other applications. The configuration options enable you to disable any of the identified drives from DIVArchive use. See Appendix A for Oracle DIVArchive options and licensing information.
The Drives tab includes the following frames:
Displays the drives currently identified to DIVArchive in a database synchronization and their current status.
The Drive Edit dialog box enables editing the Serial Number, Status (online or offline), Enabled Operations (Archive, Restore, and so on), and Used (yes or no), information for a drive. This is useful if this information was not retrieved, or was entered improperly, during a SyncDB process. The firmware release for the drive is also displayed in a non-editable field. The firmware information is obtained from the Actors when they scan for tape drive devices. Other additional non-editable information is also displayed in this dialog box, and all of the information is displayed in the Drives frame.
This displays the drive models currently configured for use with DIVArchive. Although you can manually remove entries in this frame, they can only be added by performing a database synchronization with a Robot Manager. See Appendix A for Oracle DIVArchive options and licensing information.
Indicates to DIVArchive which Actors have access to the drives configured in the Drives frame. In this area associations can be added, edited, or deleted.
Clicking the + button adds an existing Actor-Drive association. The Add New Row in Actors-Drives dialog box is displayed. Use the menu list to select the Actor, and then use the check boxes next to each drive to associate with the selected Actor.
Clicking the Edit button enables edit of an existing Actors-Drives association. The Edit Drives Entry dialog box is displayed. Make the required or desired updates and click OK to save the changes.
See Appendix A for Oracle DIVArchive options and licensing information.
The Tapes tab defines each Tape Media Type capacity in DIVArchive, and each individual tape's write, repack or to be cleared status. Tapes that do not contain any DIVArchive objects (that is, they are empty or are from another archive application in a shared library environment) and have been ejected from a DIVArchive managed library can also be deleted from the DIVArchive database from this tab.
The Tapes tab includes the following frames:
Displays the Tape Media Types and configuration parameters currently configured in DIVArchive after a library database synchronization.
In the Tape Properties frame, you can highlight an existing tape and click Edit to open the Tape Properties dialog box.
Displays the tapes that no longer have any DIVArchive content and have been ejected from an attached library. Clicking the - button permanently removes the selected tape from the DIVArchive Database.
When a tape is externalized, it is set to Protected Mode by DIVArchive. You must manually remove this state after reinsertion into the library if the tape is to have content written to it.
A tape will appear in this frame if either the Enable for Writing or the Enable for Repack states is set to N. The Enable for Writing state can be automatically disabled by DIVArchive if it encounters an error during a read, write, or repack operation.
Click the + button in the Tape States frame to add a tape to the Tape States. Select the tape to add from the list in the displayed dialog box, and then click OK to add the tape.
The Tape States frame gives an overall indication of the reliability of your tape drives. Tapes appearing in this frame (if not manually inserted) indicates that either a read or write error occurred on that tape during DIVArchive operations. If you have many tapes present here this may indicate an issue with one or more of your tape drives and should be promptly investigated.
You use the Sets, Groups & Media Mapping tab to allocate tapes into pools for use by DIVArchive. The Set ID represents each media pool. The Set ID is typically used to distinguish different types of tape media. However, it may also be used to dedicate a specific set of tapes to specific groups.
A Group is a logical name for the storage of DIVArchive objects. Each group is assigned a Set ID of tapes to draw upon. Each group can only be assigned one Set ID. Several groups can share the same Set ID.
You can use the Configuration Utility to define the format of an array or group. The format is configured in the Disks and Sets, Groups & Media Mapping tabs for arrays and groups respectively. Alternatively, you can use the addGroup API call define a group or array and its format. The default format is AXF. This can also be achieved by selecting Legacy in the Configuration Utility, or specify the corresponding value for the format using the API call.
Changing the format of an array is performed through the Edit Array Entry dialog box. Changing the format of a group is performed through the Edit Groups Entry dialog box. In either case, highlight the desired array or group and then click Edit to open the associated dialog box. Use the menu list to select the format (Legacy or AXF). Use the following procedure to change the format of an array or group:
Navigate to either the Disks (for arrays) or the Sets, Groups & Media Mapping (for groups) tab.
Highlight the desired array or group in the displayed list.
Click the Edit button at the top of the frame.
Use the Tape Format menu list to select the format for the selected array or group.
Click OK to complete the change.
The Sets, Groups & Media Mapping tab includes the following frames:
Displays empty tapes that are recognized by DIVArchive and the library module where they are located. The Set ID of each tape can also be defined in this frame.
You can highlight an existing tape and click Edit to display the Edit Unused Tapes Sets Entry dialog box. When done editing the Tape Set click the Refresh button to refresh the list.
The Unused Tape Sets frame includes the following columns:
These are tapes not currently in use by a group.
The ACS number is the specific library where the tape is located.
The LSM number is the specific library where the tape is located.
This is the set's Media Type.
This is the tape's Set ID. Click the desired tape to edit and then click the Edit button.
You can select multiple tapes by holding the CTRL key and clicking each tape. You select a range of tapes by holding the SHIFT key, click the first tape in the range, and then click the last tape in the range. Click Edit to open the Edit Multiple Rows dialog box.
Select the Set ID for the tape from the Set ID list. Only Set IDs that have already been created in the Groups window will be listed.
Setting the Set ID to 99 indicates that the DIVArchive is not to use the tape. This particularly applies to cleaning tapes installed in the library if they are reported to DIVArchive after a library audit. For example, a cleaning tape's typical barcode is CLNnnnn.
This also applies to some installations where DIVArchive shares its libraries with other applications. Tapes in use by other applications should also have their Set ID set to 99 to prevent DIVArchive from using them.
Adds, removes, or edits existing groups and each group's association with the tape pools defined in the Unused Tapes Sets frame. A group can only be removed when it no longer contains any DIVArchive objects.
Additional Set IDs for the Unused Tape Sets frame are only available after they are first created in a group. Tapes that should not be used by DIVArchive (for example, cleaning tapes) must be configured with a Set ID of 99.
The Groups frame includes the following columns:
This is the library ID the group belongs to. This is automatically generated by the system and not editable.
The name assigned to the group. These names will appear in the MEDIA list of an Archive request in the Control GUI.
Default Set ID of each group is 1. You cannot assign tapes to additional Set IDs until after they are included in a group.
This is an arbitrary description of the group.
This is the tape Media Types currently in use by this group. This is updated automatically when a tape is assigned to the groups Set ID in the Unused Tapes Sets frame.
This is the format of the tape (Legacy or AXF).
Identifies whether tape group encryption is enabled or disabled.
Identifies whether tape group compression is enabled or disabled.
By default, DIVArchive attempts to fill any tapes already assigned to a group before assigning an unused tape. The Worst Fit option attempts to span objects on as many tapes as possible.
This only applies if the Worst Fit option is enabled. It sets the number of unused tapes in the pool to reserve for tape repacking. All other groups that also use this group's Set ID must also have identical values.
This column identifies whether Verify Write is on or off for the group.
Media Mapping enables DIVArchive to automatically alter the specified media in an Archive request to another Disk Array, Tape Group or Storage Plan. In this way, you can alter the storage for Archive requests without requiring any changes in the archive initiator (automation or MAM system).
To edit an existing Media Map, highlight the desired mapping and then click Edit to edit the entry. Click OK to save your changes.
Click the + button in the Media Mapping frame to add a Media Mapping entry. Enter the Name for the mapping in the Name field. Use the menu lists to select the From (source), Media to Map to and Storage Plan to Map to, and then click OK to save the entry.
The DIVAprotect settings are identified in the Configuration Utility's DIVAprotect tab as described in the following sections.
You set the main parameters in the Configuration frame as follows:
Enter the number of months to retain DIVAprotect event history.
Enter the maximum number of DIVAprotect Metrics stored in the system. DIVAprotect will remove the oldest entries after this number is exceeded. This is completed through an automated database job that executes once per day, every day.
Enter the number of events collected in memory before saving them to the database.
Enter the maximum interval for saving events to the database. If this interval is reached before the size triggering parameter is reached, the events will be saved to the database regardless of how many have been collected.
The Event Definitions panel displays the list of Event Definitions available for use in the metrics. Double-clicking an Event Definition or clicking Open will display a dialog box listing its associated parameters
Event Definitions are factory set and cannot be modified. Built-in metrics (DIVAPROTECT* metrics) cannot be edited and therefore do not appear in the Metric Definitions frame.
You double-click a Metric Definition to display an editing dialog box where the metric can be examined or modified. This has the same effect as selecting a metric in the list and clicking the Edit button.
The + and - buttons at the top of the frame enable adding or deleting a metric.
When adding a metric definition or editing an existing one, the Metric Definitions Properties dialog box is displayed. You can now enter or edit the following information as necessary:
This is the name of the Metric Definition.
This field enables you to enter a description of the Metric Definition that is displayed next to the Metric Name in the Metric Definitions panel. This description also appears in the Control GUI when pausing your mouse over an entry of the Metric Definition list.
Select this check box to enable the metric. Deselect it to disable the metric.
The Collection Type fields specify which event parameter (for example, Transfer Size) is collected as the data and the statistical computation performed on it (for example, Sum). Available statistics are as follows:
Average
Count
Maximum
Minimum
Sum
Weight-based Average
The Weighted By field specifies the divider parameter for Weight-Based Average collection (for example, Duration).
The Collected Event list specifies the events from which the collected event parameter is retrieved. The list will only display event types suitable for the parameter specified in the Collection Type second field. Event types that have no such parameter attached are absent from the listing.
The Resource Type field specifies which resource breaks down the data. For example, if you select Drive Serial Number, separate metrics will be generated for each drive. Use the menu list to select the resource type for the metric.
The Interval specifies the interval for metric calculation. For example, selecting 1 Day will generate a metric each day (if corresponding data is available). The metric calculation is based on the associated events that occurred in the last 24 hours. Use the menu list to select the desired interval.
The following table identifies the default events and metrics that are internal to DIVArchive:
Table 3-3 Default Event and Metric Definitions
| Event Field ID | Displayed Name | Is Aggregatable? Is Resource? | Is Collectable? | Date or Number | Quantifier |
|---|---|---|---|---|---|
|
1 |
Event ID |
No |
Yes |
Number |
|
|
2 |
Event Type |
Yes |
No |
||
|
3 |
Tape Type |
Yes |
No |
||
|
4 |
Tape Barcode |
Yes |
No |
||
|
5 |
Drive Type |
Yes |
No |
||
|
6 |
Drive Name |
Yes |
No |
||
|
7 |
Drive Serial Number |
Yes |
No |
||
|
8 |
Actor Name |
Yes |
No |
||
|
9 |
Object Name |
Yes |
No |
||
|
10 |
Object Category |
Yes |
No |
||
|
11 |
Object Instance |
No |
No |
||
|
12 |
Media |
Yes |
No |
||
|
13 |
Request ID |
No |
No |
||
|
14 |
Event End Time |
No |
No |
||
|
15 |
Event Duration |
No |
Yes |
Number |
Seconds |
|
16 |
Transfer Size |
No |
Yes |
Number |
Bytes |
|
17 |
Transfer Rate |
No |
Yes |
Number |
MB/Second |
|
18 |
Transfer Error Rate |
No |
Yes |
Number |
Errors/GB |
|
19 |
Error Code |
Yes |
No |
||
|
20 |
Error Message |
No |
No |
||
|
21 |
Disk Name |
Yes |
No |
||
|
22 |
Library Serial Number |
Yes |
No |
||
|
23 |
SD Name |
Yes |
No |
||
|
24 |
Transcoder Name / Analyzer Name |
Yes |
No |
||
|
25 |
Local DIVArchive System |
Yes |
No |
||
|
26 |
Number of Operations |
No |
Yes |
Number |
The following is a sample use case scenario:
You want to create your own metric for average duration of read and write operations on a tape in a DIVArchive system. You use the following procedure to create this metric:
Open the Configuration Utility.
Click the DIVAprotect tab.
Click the + button on the Metrics Definitions frame to open the Metric Definition dialog box.
Enter a unique name for the metric in the Name field.
Enter a description in the Description field.
Select the Enabled check box to enable the metric.
Set the Collection Type and Weighted By fields as appropriate using the menu lists.
For example, if you select Weight-Based Average as the Collection Type, the Weighted By field is enabled. Because the Weighted By field is active, you are required to select a value to use to weigh the metric definition. In this case, the values for the Weighted By field are identical to the second Collection Type field.
Use the check boxes in the Collected Event area to select the events for collection.
Use the menu list to select the aggregation Resource Type.
Use the menu list to select the aggregation Interval.
Click OK to save your metric definition and complete the process.
The Media tab displays information (properties) of the media identified in the DIVArchive system. The display is for informational purposes and read only. You click the Refresh button to refresh the displayed list.
The Source Media Priority determines which source instance is preferred during the instance selection process of a Restore, Partial Restore, and Copy To Group request, by the media on which the instance resides. Instances on media with a higher priority are preferred. If two instances reside on media with the same priority, DIVArchive will select an instance based on its internal algorithm (same algorithm used in earlier versions of DIVArchive).
Note:
Cloud instances are only copied or restored if all local instances are offline or no local instances exist. In other words, this condition is an absolute condition independent of the Source Media Priority.Caution:
Misconfiguration of the Oracle DIVArchive Storage Plan Manager (SPM) may lead to unexpected and disastrous results! Minor changes can lead to catastrophic consequences. For example, the deletion of hundreds of thousands of instances on tape or database corruption. Without special training and familiarity with the product, it is recommended to contact Oracle Support before making any changes to SPM. Failure to do so may result in severe damage to the DIVArchive system or even permanent data loss.The Storage Plans tab enables creation of simple and advanced rules for automated management and movement of content within the archive.
For detailed configuration information, see the Oracle DIVArchive Storage Plan Manager (SPM) User's Guide in the Oracle DIVArchive Additional Features documentation library. See Appendix A for Oracle DIVArchive options and licensing information.
The Storage Plans tab includes the following frames:
Displays the Storage Plan names and definitions.
You click the + button in the Storage Plans frame to add a Storage Plan. Enter the Storage Plan name in the Storage Plan Name field. Use the menu lists to select whether to Allow Last Instance Deletion, Please Specify Origin (Internal/External) (this is typically Internal), and the Group/Array Name to associate with the Storage Plan. Click OK to save the changes.
You highlight a desired Storage Plan, and then click Edit to edit the selected Storage Plan. Click OK to save your changes.
Defines the tape groups or disk arrays to be allocated to slots, and if content deletion will be managed by the Storage Plan Manager.
You click the + button in the Media Groups frame to add a Media Group. Enter the Medium Name and Storage Name in the designated fields. Use the menu lists to select the Group/Array Name, Watermarked, and the Disk Cleaning Strategy. Click OK to save the changes.
You highlight a desired Media Group, and then click Edit to edit the selected Media Group.
Displays the Storage Plan names and definitions.
You click the + button in the Storage Plans frame to add a Storage Plan. Enter the Storage Plan name in the Storage Plan Name field. Use the menu lists to select whether to Allow Last Instance Deletion, Please Specify Origin (Internal/External) (this is typically Internal), and the Group/Array Name to associate with the Storage Plan. Click OK to save the changes.
You highlight a desired Storage Plan, and then click Edit to edit the selected Storage Plan. Click OK to save your changes.
After you click OK, A warning dialog box appears asking whether you want to continue saving the changes. Click Yes to save the changes, or No to cancel.
This frame displays filter definitions related to the Storage Plan Objects. It enables performing actions on all or specific objects (based on object filters).
This tab defines the Slots associated with the Storage Plans for the Storage Plan Manager. Slots define which tape groups or disk arrays are related to each storage plan, and the parameters for storage plan execution.
For detailed configuration information, see the Oracle DIVArchive Storage Plan Manager (SPM) User's Guide in the Oracle DIVArchive Additional Features documentation library.
The Slots tab includes only one frame named Slots.
You click the + button in the Slots frame to add a Slot. Configure the Slot's parameters by entering the information desired for this slot, or using the menu lists to select the options. Click OK to save the changes.
You highlight a desired Slot, and then click Edit to edit the selected Slot. Click OK to save your changes.
The Slot Configuration screen serves two purposes; new slot configuration and editing an existing slot configuration. Both functions use the same dialog box. However, the information displayed in the dialog box is determined by whether a slot is being added, or an existing slot is being edited.
You use the Manager Setting tab to set several parameters related to the Media and the Metadata Database in the system.
There are two settings to configure for the Media in the Manager Setting tab:
The object is assigned to a specific Storage Plan and saved to the specified media. The Media Name and the SP Name must be separated by the & delimiter.
DP_OPERATIONS TableThe maximum number of records maintained in the DP_OPERATIONS table in the database.
You must configure the following three parameters in the Manager Settings tab to enable complex objects processing:
Enter the full path to the Metadata Database files in this field.
Select the check box to enable the Metadata Database backup notifications, or deselect the check box to disable notifications.
Notifications must be enabled to receive DIVArchive Backup Service messages to the Control GUI. If this parameter remains disabled, there will be no notification of errors or warnings displayed in the Control GUI. The default is enabled (selected).
Select the check box to enable the Metadata Database Backup feature. The default is disabled (deselected).
The Keystore password is set in the Configuration Utility in the Manager Configuration view. You enter the Keystore password in the Export: Tape Encryption Keystore Password field. The password must be at least eight characters and contain at least one digit, at least one lowercase alphabetic character, at least one upper case alphabetic character, and at least one special character within a set of special chars (!@#%$^).
You enable exporting encryption keys by selecting the Export: Enable Export of Encryption Keys check box. Exporting encryption keys is disabled by default. You must be in Engineering mode to view or edit both settings.
You can verify the integrity of the Keystore file using the Java keytool. See https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html for details on Java's keytool.