7 Configuring DIVArchive Managers

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

• Configuration Overview

• Configuring the Local Manager

  • Basic Settings

  • Database Settings

  • Advanced Settings

  • Logging Settings

• Configuring Request Priorities

• Rerouting Destinations (restore_translations.conf)

• Controlling the Manager

• Logging Manager Activity

• Confirming System Connectivity

  • Confirming Remote Client to Manager Connectivity

  • Confirming Manager to Actors Connectivity

  • Confirming Manager to Robot Manager Connectivity

• Manager Failover Procedures

Configuration Overview

The Manager module is located in %DIVA_HOME%\Programs\Manager\bin in Windows, and in /home/diva/DIVA/Program/Manager/bin in Linux, and runs as a service. The static configuration file for the Manager is manager.conf. You can typically leave most settings in this file left at the default values. The settings that would normally require updating are highlighted in bold type.

See Appendix A for Oracle DIVArchive options and licensing information.

The following figure is the workflow for installing a DIVArchive Manager:

Configuring the Local Manager

The static configuration file in new installations is initially named manager.conf.ini. You must remove the .ini extension for it to be recognized by the DIVArchive Manager.

The configuration file is divided into five distinct groups; Basic, Database, Advanced, Logging, and Service settings. You must not modify the Service settings section, and therefore, not covered in this manual. Values defined in this section must only be altered with instruction from Oracle Support.

Each parameter section in the configuration file contains information on defining that parameter. The information lines are commented out (start with #) and ignored by the Manager. Any parameter definition that is missing the equal sign is also ignored.

Spaces in the parameter settings are significant. Do not put extra spaces before or after the parameter names or their values. If you have trouble running the Manager after configuring the manager.conf file, confirm that spaces are not present in any of the parameter values you have defined.

Restarting the Manager can disrupt a live production system. You can make most of the customizations in the configuration file effective immediately using the restart command line switch.

If you intend to update your existing DIVArchive system with a newer software release, you must use the manager.conf.ini from the new release. You must update the Basic and Database settings with the values from the old configuration file. The new release configuration file may have additional settings or updates included; this applies to all DIVArchive software modules when installing a release updated.

Basic Settings

Except for the SERVICE_NAME, these parameters are always required and must be defined for the Manager to start successfully. These settings define how other DIVArchive software components and DIVArchive API clients connect to the Manager.

Note:

These settings are not reloadable while the Manager is running. You must restart the Manager for them to take effect.

The following table describes the Basic settings in the manager.conf file:

Table 7-1 Basic Settings in manager.conf

Parameter	Parameter Type	Description	Default
SERVICE_NAME	Name	You can use this parameter to specify the name of the service. If not defined, the Service Name defaults to DIVArchive Manager.
DIVAMANAGER_NAME	Name	This is the name this Manager instance uses to identify itself to other DIVArchive Managers sharing its resources. Otherwise, this is arbitrary. It must be unique in a system running multiple Managers except for Main and Backup Managers (configured as a cold standby). In this instance, the names should be identical.	DIVA
DIVAMANAGER_PORT	TCP Port Number: unsecure connections	The TCP port other DIVArchive applications, or third party applications using the DIVArchive Client API use to connect to this Manager. If using a Sony library and running the Manager on the same computer as the PetaSite Controller (PSC) software, the PSC Server also uses TCP port 9000, which cannot be modified. In this situation, you must specify another port for the Manager.	9000
DIVAMANAGER_SECURE_PORT	TCP Port Number: secure connections	The secure TCP port used by DIVArchive Services and the DIVArchive API.	8000

Database Settings

These parameters define the location and instance of the DIVArchive Database. Except for the DIVAMANAGER_TNSNAME parameter, you must define all settings in this section for the DIVArchive Manager to launch successfully.

The following table describes the Database settings in the manager.conf file:

Table 7-2 Database Settings in manager.conf

Parameter	Parameter Type	Description	Default
DIVAMANAGER_TNSNAME	Name	The TNS Name of the DIVArchive Schema within the Oracle database. DIVArchive ignores this setting if the DIVAMANAGER_DBHOST and DIVAMANAGER_DBPORT settings are defined. This feature requires Oracle 11g or higher installed on the host running the Manager. If this setting is defined, the location of the Oracle OCI driver (for example, ocijdbc11.dll) must be added to the wrapper.java.library.path setting (located in Service settings section of the file); otherwise, the Manager will not start as a service. Example: wrapper.java.library.path=.;C:\app\oracle\product\11.1.0\BIN
DIVAMANAGER_DBHOST	IP Address or Host Name	This specifies the Host Name or IP Address of the computer containing the DIVArchive Database. If using a host name, this must be present in the hosts file on the computer where the DIVArchive Manager is installed.
DIVAMANAGER_DBPORT	TCP Port Number	The Oracle Listener port configured during the DIVArchive Database installation.	1521
DIVAMANAGER_DBSID	Name	The DIVArchive Database Instance System Identifier (SID) in Oracle where DIVArchive Manager connects. Consult your Site Configuration if you do not know this value.
DIVAMANAGER_DBUSER	Name	The user name the DIVArchive Manager uses to connect to the DIVArchive Database. This is typically diva (case sensitive).	diva
DIVAMANAGER_DBSERVICENAME	Name	Oracle ServiceName setting. Either this value or DIVAMANAGER_DBSID must be set. If both are set, this takes precedence over the SID.	No default value, but lib5.world is recommended.
DIVAMANAGER_DBSID	Name	Oracle ServiceName setting. Either this value or DIVAMANAGER_DBSERVICENAME must be set. If both are set, DIVAMANAGER_DBSERVICENAME takes precedence over SID.	No default value, but lib5.world is recommended.

Advanced Settings

You typically leave the parameters in this section are typically left at their defaults. They customize DIVArchive's default behavior for task execution, resource allocation, and the number of connections it will accept from DIVArchive Applications and DIVArchive API Clients. These parameters are normally adjusted or fine-tuned after completing the initial installation of DIVArchive.

Most (but not all) of these settings can be altered while the Manager is running by using the reload option.

The following table describes the Advanced settings in the manager.conf file:

Table 7-3 Advanced Settings in manager.conf

Parameter	Parameter Type	Description	Default
DIVAMANAGER_TO_LOWER	true or false	Sets case sensitivity for DIVArchive. If set to true, then all object names, categories and groups will be set to lowercase.	false
DIVAMANAGER_REQUEST_SCHEDULING_QUEUE_SIZE	Number of requests	The maximum number of requests that can be queued for processing by DIVAMANAGER_MAX_CONCURRENT_REQUESTS processors of the Request Scheduler.	500
DIVAMANAGER_MAX_CONNECTIONS	Number of Connections	Specifies the maximum number of simultaneous client connections the Manager will accept. This includes DIVArchive Actors, Control GUIs, API connections, and support tools.	200
DIVAMANAGER_MAX_SIMULTANEOUS_REQUESTS	Number of Requests	The maximum number of requests processed by the DIVArchive Manager. When this limit is reached, any further requests will be rejected. The maximum tested value for this setting is 2000.	500
DIVAMANAGER_API_TASK_QUEUE_SIZE	Number of tasks	The number of tasks that will be accepted to the API command processing queue. If this queue is full, subsequent commands will be rejected. The maximum tested value is 2000.
DIVAMANAGER_MAX_INACTIVE_REQUESTS	Number of Requests	Maximum number of inactive requests that cannot find resources examined by the Request Scheduler each time it is activated.	0
DIVAMANAGER_TYPICAL_OBJECT_SIZE	Percentage	During operation a DIVArchive Actor retrieves the file size of an object before an archive transfer. This value determines the best location on the tape for the file. Some servers do not indicate the file size of an object before a Direct Archive. Therefore, DIVArchive will use this value as an estimate for tape selection. You must define this setting so that most objects to be archived in the DIVArchive system are below this size.	10 (percent)
DIVAMANAGER_MAX_CONCURRENT_REQUESTS	Number of Requests	The maximum number of concurrent requests executed by the DIVArchive Manager. The maximum tested value for this setting is 16.	8
DIVAMANAGER_MAX_SPAN_SEGMENTS	Number	DIVArchive will attempt to span the file across two or more tapes if no more writable tapes with enough free space are available to archive a file. This setting defines the maximum number of tapes across which the object will be spanned.	2 (segments)
DIVAMANAGER_INITIAL_DB_CONNECTION_LIMIT	Number of Connections	The initial number of database connections available to the DIVArchive Manager.	1
DIVAMANAGER_MIN_DB_CONNECTION_LIMIT	Number of Connections	The minimum number of database connections available to the DIVArchive Manager.	1
DIVAMANAGER_MAX_DB_CONNECTION_LIMIT	Number of Connections	The maximum number of database connections available to the DIVArchive Manager.	10
DIVAMANAGER_CAPACITY_LOW_WATER_MARK	Percentage	When the percentage of the total used capacity reaches this amount, periodic warning messages are issued in the Control GUI.	90 (percent)
DIVAMANAGER_ENABLE_SPANNING_LARGE_OBJECTS	true or false	Enables spanning of large objects. This parameter overrides SPAN_SEGMENTS if any object in the system is known to be too large.	true
DIVAMANAGER_INACTIVITY_TIMEOUT	Time in Seconds	The maximum time a physical connection can remain idle in a connection cache before it is terminated (in seconds).	3600
DIVAMANAGER_MAX_OBJECTS_FOR_REPACK	Number	Repacking a tape with many objects can consume resources for a lengthy period without reclaiming a great deal of unused space in the process. This setting prevents this by limiting the selection of tapes in manual and automatic repacks based on the number of objects.	500
DIVAMANAGER_SIZE_OF_STATEMENT_CACHE	MB	The size of the database statement cache.	10
DIVAMANAGER_STOP_IMMEDIATELY_FOR_REPACK	true or false	This setting specifies whether to complete any repack requests still running or to terminate them after the Automatic Tape Repack period. If this is set to true then repack requests still in progress after the Automatic Repack period will be stopped.	true
DIVAMANAGER_DEFAULT_ROW_PREFETCH	Number of Rows	The default number of rows to prefetch from the database per query.	1000
DIVAMANAGER_DISMOUNT_AFTER	Time in Milliseconds	This specifies the time in milliseconds to automatically dismount a mounted tape no longer needed by any other request.	120000 (two minutes)
DIVAMANAGER_FAILOVER_ENABLED	Boolean	Whether to enable Fast Connection Failover. This feature introduces a slight performance penalty.	false
DIVAMANAGER_UPDATE_PRIORITIES_PERIOD	Time in Milliseconds	DIVArchive periodically examines all requests in its request queue and increments the request priority. This prevents a condition where low priority requests might be continually superseded by higher priority requests. This setting specifies the period between updates of the queue by the Manager. You set this value to 0 to disable priority updates.	60000 (one minute)
DIVAMANAGER_NUM_RS_SOLUTIONS_TO_EVALUATE	Boolean	The number of immediate solutions to evaluate per invocation of the Best Solution Finder during resource selection.Values are 0 (disabled) or 1 (enabled).	0 (disabled)
DIVAMANAGER_MAX_DELAY_BETWEEN_SCHEDULER	Time in Milliseconds	The maximum number of milliseconds between two Request Scheduler activations when the Manager is constantly busy.	5000 (five seconds)
DIVAMANAGER_SCHEDULER_AFTER_INACTIVITY	Time in Milliseconds	The number of milliseconds after which a requested Request Scheduler activation can be launched if the Manager is idle. This duration should be significantly lower than DIVAMANAGER_MAX_DELAY_BETWEEN_SCHEDULER. You should not need to modify this value.	500
DIVAMANAGER_PING_INTERVAL	Time in Milliseconds	This defines the interval in milliseconds between Manager checks to see if the connections to its clients and services are still active (Actors, SPMs, Control GUIs, and so on).	600000 (ten minutes)
DIVAMANAGER_EXPORT_ROOT_DIR	Directory Path	The Export Tapes command enables the sharing of tapes between two or more separate DIVArchive platforms. This setting defines the root folder for the exported tape's Metadata files. The folder must exist and have write permissions enabled on the host computer where the DIVArchive Manager is running.	Exported
DIVAMANAGER_MAX_RESTORE_SERVERS	Number between 2 and 200	The maximum number of servers allowed in an N-Restore request by a DIVArchive Actor.	5
TAPE_FULL_ON_SPAN_REJECTED	true or false	If true, and spanning is disabled, the Manager marks a tape full when spanning occurs.	false
DIVAMANAGER_MAX_EXPORT_TAPES	Number between 1 and 100	The maximum number of tapes allowed in an Export Tapes request.	10
DIVAMANAGER_MAX_EXPORT_ELEMENTS	Number between 1 and 10,000,000	The maximum number of elements that can be exported using the Export command.	1000000
DIVAMANAGER_MAX_FILES_IN_ARCHIVE	Number between 1 and 1,000,000	The maximum number of files allowed in an Archive request.	1000000
DIVAMANAGER_MAX_FILES_IN_PARTIAL_RESTORE	Number between 1 and 1,000,000	The maximum number of files allowed in a Partial File Restore request.	1000000
USE_IMPROVED_BEST_WORST_FIT_ALGORITHM	true or false	When a file was archived to tape in earlier DIVArchive releases, the Best/Worst Fit algorithm selected the tape with the largest remaining free size. This could result (over time) in a low number of blank tapes for tape repacking, and so on. The current algorithm selects the tape based on the smallest free space and then fills all tapes before using more free tapes.	true
DIVAMANAGER_SITE_SUPPORT_ENABLED	true or false	Resources within DIVArchive can be defined by their location. If you set this parameter to true, the Manager first tries to perform the request from the sites identified as MAIN. If unsuccessful, it retries the request with resources from all other sites. If you set this parameter to false, DIVArchive ignores site identification and all site resources are considered equally.	false
DIVAMANAGER_CACHE_QOS_USE_DISK	true or false	In earlier DIVArchive releases, a Restore request with a Quality of Service of CACHE or CACHE and DIRECT resulted in the tape instance being used as first priority, even if a disk instance existed. This setting instructs DIVArchive to use the disk instance regardless of the QOS method specified.	true
DIVAMANAGER_PRIORITY_TIER	Number between 0 and 100	DIVArchive bases the execution of requests in its request queue by the request priority number. However, there are instances where a request in the queue with lower priority uses a tape that is already mounted. Giving this request priority over others lower in the queue can save a substantial amount of time in tape mount and dismount operations, and help reduce wear and tear on the tape drives. If this setting is enabled, DIVArchive examines the request queue for lower priority requests involving a tape that is already mounted in a drive and adds the number specified here to the request priority. For example, if the request priority is 25, and the Priority Tier value is 50, the total request priority is 75. Note — This feature applies only to Restore and Copy Requests that read from tape. Archive and Copy requests that write to tape are not supported by this feature.	0 (disabled)
DIVAMANAGER_ETC_FEATURE	true or false	This parameter enables the Estimated Time to Complete feature. This function gathers statistics (over time) on the time for completion of all execution states of each DIVArchive request. Setting this value to true enables this feature.	false
DIVAMANAGER_ETC_CONFIDENCE_LEVEL	Number	The percentage of Slope Confidence Interval for the simple regression statistical function used in the Estimated Time to Complete feature. DIVArchive ignores this setting if the DIVAMANAGER_ETC_FEATURE is disabled.	50
DIVAMANAGER_OVERWRITE_POLICY	Number between 0 and 2	This value determines how DIVArchive handles files that already exist on a Destination server when executing a Restore, Partial File Restore, or N-Restore request as follows: 0 - If the file to be restored to the destination already exists no overwrite will occur. 1 - The Actor does not verify if the files with the same names exist before attempting to overwrite these files. If files with the same names do exist, a backup of the existing files is made before overwriting them. 2 - The Actor attempts to delete and then write to files with the same names.	1
DIVAMANAGER_OVERWRITE_OVERRIDE	true or false	Overrides the policy sent by the external application through a request with the policy set in DIVAMANAGER_OVERWRITE_POLICY.	false
LICENSE_EXPIRATION_NOTIFICATION_PERIOD	Number of Days	Number of days before a temporary license is to expire that a notification message will be displayed on the GUI. The range of possible values is 1 to 99.	15
LICENSE_EXPIRATION_TOD	Time of Day	The time of day the Manager will shut down if the license has expired. The Manager will stop at the designated time on the day after the license validity date. (00-23:00-59)	8:00
ATTEMPT_ACCESS_TO_OFFLINE_DISK	true or false	If a disk is offline or not visible to all available Actors, the Manager will automatically terminate a transfer request for objects residing on that disk. If this is set to true, the Manager attempts the transfer irrespective of disk status.	false
CHANGE_DISK_STATE_ON_ERROR	true or false	Defines whether the Manager will automatically vary a disk's status to Offline if a transfer error occurs.	true
MANAGER_ACTOR_DISK_RETRY_NUMBER	Number	If a disk I/O error occurs during a transfer, this sets the maximum number of transfer retry attempts with alternate Actors that also have access to the disk. Values are 0 to 7.	3
DISK_STATUS_POLLING_RATE	Number	This defines the rate in milliseconds in which each disk in the system is polled to obtain its total and remaining free space.	60000 (one minute)
DISK_BUFFER_SPACE	Number	This defines the percentage of the overall space of a disk to keep free.	0.05 (percent)
DISK_CONNECTION_STATE_RESET_DELAY	Time in Minutes	A disk connection will be reset from the Out of Order state when a successful access is completed and this amount of time has passed since the connection was set to Out of Order.	1.0 (minute)
COMPONENT_SIZE_CONVERSION_TO_KB_RULE	Number	When an element is successfully transferred to tape or disk, the Actor reports the size of the element in bytes. This value is then converted to KB before it is saved to the database. The conversion may be one of three possible values: 1 - KB = (bytes / 1024) + 1 2 - KB = bytes/1024, but if (KB < 1) then KB = 1 3 - KB = Math.ceil(bytes/1024)	3
DIVAMANAGER_MAX_EXCLUDED_INSTANCES	Number	The maximum number of instances excluded from a request that are logged as an event.	3
LOGGING_TRACE_LEVEL	DEBUG, INFO, WARN, ERROR, FATAL	Defines the level of information written to the respective log files as follows: DEBUG - All messages within the Manager are logged. Log files grow rapidly. INFO - Information, Warning, Error, and Fatal messages are logged. WARN - Warning, Error, and Fatal messages are logged. ERROR - Error and Fatal messages are logged. FATAL - No messages are logged unless the Manager stops unexpectedly.	INFO
DIVAMANAGER_MAX_SPAN_SEGMENTS	Number	DIVArchive will attempt to span the file across 2 or more tapes if no more writable tapes with enough free space are available to archive a file. This setting defines the maximum number of tapes that the object will span. This setting will completely disable spanning if set to 1 or below. If a span case arises, the Manager retries the request with a new tape using the old Worst Fit algorithm, and the first tape in the attempted span will be marked full. If the second attempt fails, the request will terminate.	0 (segments)
DIVAMANAGER_MAX_DB_CONNECTION_ATTEMPTS	Number	The maximum number of allowable attempts to connect to the database.	10000
DIVAMANAGER_MIN_DB_CONNECTION_PERIOD	Number	The minimum period (in milliseconds) between connection attempts.	1000 (milliseconds)
DIVAMANAGER_MAX_FOLDERS_IN_ARCHIVE	Number	The maximum number of folders allowed in an Archive request. Performance degradation can occur for values greater than 10000. The maximum value is 10000.	10000
DIVAMANAGER_COMPLEX_OBJECT_THRESHOLD	Number	The maximum number of files allowed before an object is classified as a complex object. The maximum value is 10000.	1000
COPY_ONLY_FROM_DISK_INSTANCE_WHEN_POSSIBLE	Boolean	Controls instance selection for Copy and CopyAs requests when the destination is tape. Copy requests always check if a disk instance can be used as the source of a copy. If the required resources for a disk to tape transfer are not available, a tape to tape transfer may be used if this parameter is set to false. When set to true the request will wait for the resources to use the disk instance as the source. This parameter is reloadable in SERVICE mode.	true
COMPONENT_SIZE_CONVERSION_TO_KB_RULE	Number	This is the Object Size Conversion Rule. Use one of the following rules to convert an object component size from Bytes to Kilobytes: 1 - KB = (bytes/1024) + 1 2 - KB = bytes/1024, but if (KB < 1) then KB = 1 3 - KB = Math.ceil(bytes/1024)	3
COPY_ONLY_FROM_DISK_INSTANCE_TIMEOUT	Time in Minutes	Tape instance is available for a Tape to Tape transfer. After this time, either a disk or tape instance may be selected as the source of a copy to tape.	15 (minutes)
DIVAMANAGER_RESTORE_QOS	CACHE_ONLY, DIRECT_ONLY, DIRECT_AND_CACHE, CACHE_AND_DIRECT, NEARLINE_ONLY, NEARLINE_AND_DIRECT	This identifies the default Quality of Service for Restore requests.	NEARLINE_AND_DIRECT
NTH_PROGRESS_MESSAGE	Number	The number of progress messages sent to GUIs. Every Nth progress message will be sent. The N=100 progress message will always be sent.	5 - implies send every fifth progress message to all GUIs.
DIVAMANAGER_TIME_TO_WAIT_FOR_GRACEFUL_SHUTDOWN	Minutes	The time to allow for a graceful shutdown to complete.	1440 (one day)
ABORT_ARCHIVES_ON_EMPTY_FILES	true or false	If true the Manager terminates an Archive request if it contains an empty file or folder.	false
TAPE_FULL_ON_SPAN_REJECTED	Boolean	If true, the Manager will mark a tape full when a span occurs but spanning is disabled.	false
DIVAMANAGER_RETRY_ON_SPAN_REJECTED_ALGORITHM	1 = Prefer empty tapes 2 = Prefer used tapes with less remaining space 3 = Prefer tapes with more remaining space	The tape selection retry algorithm to use when a span is rejected. The Manager enables configuring the retry logic when spanning is disabled, but an object is too large to fit on the selected tape. By default, the Manager retries with an empty tape, but you can alternatively retry with a used tape with most or less remaining space.	1

Logging Settings

The following table describes the Logging settings in the manager.conf file:

Table 7-4 Logging Settings in manager.conf

Parameter	Parameter Type	Description	Default
LOGGING_TRACE_LEVEL	DEBUG, INFO, WARN, ERROR, FATAL	Defines the level of information written to the respective log files as follows: DEBUG - All messages within the Manager are logged. Log files grow rapidly. INFO - Information, Warning, Error, and Fatal messages are logged. WARN - Warning, Error, and Fatal messages are logged. ERROR - Error and Fatal messages are logged. FATAL - No messages are logged unless the Manager stops unexpectedly.	INFO
LOGGING_MAXFILESIZE	Kilobytes or Megabytes	When the log file reaches this size, a new file is generated and the old one renamed with appropriate time and date stamps. Older log files are subsequently compressed automatically into zip files at one hour intervals.	10 MB
LOGGING_LIFETIME	Hours	This setting defines how long to maintain trace service and zipped log files before deleting them.	50

Configuring Request Priorities

Each request submitted to the DIVArchive Manager is placed in the Manager transfer queue. Request priorities enable DIVArchive to differentiate between important requests, such as Restore requests, over less important events. For example, tape repacks, and so on.

The request priority is a number from zero to one hundred with zero being the lowest priority and one hundred being the highest. The request priority is typically specified when you submit the request (either from the Control GUI or the DIVArchive Client API). You can also alter the priority after you submit the request using the Change Priority command.

The default request priority for each request type is preset within DIVArchive. You can override the default priorities (at your discretion) using the following procedure:

1. Navigate to the %DIVA_HOME%\Program\conf\manager folder.

2. Rename the managerpriority.conf.ini file to managerpriority.conf.

3. Edit the managerpriority.conf file using a plain text editor (for example, Notepad or Notepad++) to set the desired values for each request type.

4. You must reload the Manager configuration using the reload option or restart the Manager for the new settings to take effect.

Regardless of the configured request priority, the Manager will (by default) periodically increment the priority of every request already the request queue. This prevents a condition where a low request priority can be continually overridden by higher priority requests and never executed.

You can disable this feature by setting the DIVAMANAGER_UPDATE_PRIORITIES_PERIOD parameter in the Manager configuration file to 0. You must then reload the Manager configuration or restart the Manager.

Rerouting Destinations (restore_translations.conf)

To simplify production workflows, you can configure DIVArchive to automatically override the original destination specified in a Restore, Partial File Restore, or N-restore request based on the object category and original destination. This is called Destination Rerouting. Typically, you use this function to enable selective transcoding based on an object category.

You configure Destination Rerouting by editing the restore_translations.conf file. The file is located in the %DIVA_HOME%\Program\conf\manager folder with the Manager configuration file.

The restore_translations.conf file is delivered with a .ini extension. You must remove the .ini extension for this file to be considered by the Manager.

All re-routing entries must be in the following format:

DT_Number=Destination_1;Category_1;TranslatedDestination_1

The following list describes these parameters:

DT_Number

This must be the first string in the line and start with DT_Number. The Number can be any value unique among all entries. For example, DT_0, DT_1, DT_2, and so on. Up to three hundred entries are supported.

Destination_1

The destination in a Restore request for this rule to apply.

Category_1

If the Object Category of the request also matches the destination will be re-routed.

TranslatedDestination_1

This is the new destination for the Restore request.

The following example describes how to configure rerouting a destination:

• A video server accepts clips with Format1

• The archive contains clips with both Format1 and Format2

• Format 1 objects are in Category 1 (Cat1)

• Format 2 objects are in Category 2 (Cat2)

You configure this example as follows:

1. Define a Source (Source1) that points to the video server with no restore transcode options.

2. Define another Source (Source2) that points to the video server with options to transcode to Format1.

3. Create a restore_translations.conf file containing the following line:

   DT_0=Source1;Cat2;Source2
   

When an object with the category Cat2 is restored to destination Source1, re-route it to destination Source2 instead. In this manner, the automation can always use Source1 as the destination in the request.

Objects having a format of Format1, which are directly compatible with the video server, will be restored to Source1 without transcoding.

Objects having a format of Format2 and a category of Cat2 match the configuration line and are rerouted to Source2. Source2 has options to transcode them to Format1 when restoring.

Controlling the Manager

You perform DIVArchive Manager control and management functions from a command prompt on Windows platforms using the manager.bat batch file, and from a terminal window using the manager.sh script file on Linux platforms. The executable is located in the %DIVA_HOME%\Program\Manager\bin folder in Windows, and in the /home/diva/DIVA/Program/Manager/bin directory in Linux.

Installing and Removing the Manager Service in Windows

You must first install the DIVArchive Manager as a system service on new systems. You can accomplished this using the install (or -i) and uninstall (or -u) command line switches as follows:

manager install

This (or manager -i) installs the DIVArchive Manager service set by the SERVICE_NAME parameter defined in manager.conf. If this parameter is undefined, the service is installed as DIVArchive Manager.

manager uninstall

This (or manager -u) removes the DIVArchive Manager service set by the SERVICE_NAME parameter defined in manager.conf.

In the Windows Services applet, confirm that the DIVArchive Manager service is installed correctly. If you must change the service name, uninstall the existing service before editing the manager.conf file. Then reinstall the service after changing the service name.

The default path to the m,anager.conf file is %DIVA_HOME%\Program\conf\manager.

You can identify a specific configuration in the command line if you require using an alternate file using the -conf or -f switch as follows:

manager install -conf [configuration file]
manager uninstall -conf [configuration file]

Installing and Removing the Manager Service in Linux

The divaservice executable in the Manager /home/diva/DIVA/Program directory installs (or uninstalls) the DIVArchive Manager as a service from a Linux terminal. See Installing the DIVArchive Services for more information about using the divaservice command.

Use the following command sequence to install the Manager service:

cd/home/diva/DIVA/Program

./divaservice install manager /home/diva/DIVA/Program/conf/Manager/manager.conf

Use the following command sequence to uninstall the Manager service:

cd/home/diva/DIVA/Program

./divaservice uninstall manager /home/diva/DIVA/Program/conf/Manager/manager.conf

Managing the Manager Service

You can manage the Manager Service using the following command line switches after the service is installed:

manager start

This switch starts the Manager service (if stopped).

manager stop

This switch stops the Manager service (if running).

manager shutdown

This switch finishes currently running requests and stops accepting new requests, then it stops the DIVArchive Manager service (if running).

manager restart

This switch stops and subsequently starts the Manager service.

manager reload

Some changes in the Manager configuration files take effect after reloading the Manager. This switch reloads the manager.conf, managerpriority.conf, and restore_translations.conf files from the default path (%DIVA_HOME%\Program\conf\manager).

Use the following command to reload the Manager using a different configuration file:

manager reload -conf [configuration file]

manager status

This switch displays the current status of the Manager service (running or not running).

manager dump

This switch requests a system dump from the Manager service.

manager version

This switch (or manager -v) displays the Manager service release information and then exits.

manager help

This switch (or manager -h) display all command line options and then exits.

Logging Manager Activity

The DIVArchive Manager keeps detailed logs of its operations and stores them in the %DIVA_HOME%\Program\log\manager folder. The logs are used for troubleshooting and diagnostics purposes, and may be requested by Oracle Support.

The logging settings in manager.conf determine the level and quantity of information captured in each log file. If you must alter the settings, you can make the changes effective immediately using the manager reload command, or (in DIVArchive 7.6) change them dynamically from the Control GUI. See the Oracle DIVArchive Operations Guide in the Oracle DIVArchive Core documentation library for more details.

Class-level logging is supported through the manager.classLog.properties file. Any class set to one of the following values will log at the specified logging level:

• TRACE

• DEBUG

• INFO

• WARN

• ERROR

• FATAL

New statical data is generated every five minutes that lists various Manager performance related metrics, and collected in a statistics folder.

After logs have reached the size defined by LOGGING_MAXFILESIZE in manager.conf they are renamed with date and timestamps, compressed (zipped), and a new file is started (named manager.trace). The manager.trace file is the log file currently being written to by the Manager.

Confirming System Connectivity

After the DIVArchive Manager has been successfully configured and launched you must check that the Manager can successfully be connected to by other DIVArchive clients (for example, the Control GUI). Also, the Manager itself must be able to connect to the configured Actors and, if installed, Robot Managers.

Confirming Remote Client to Manager Connectivity

This short test establishes whether the Manager is configured correctly and accepting remote connections from clients:

1. Launch the DIVArchive Control GUI from a remote client (that is, not on the same host computer as the DIVArchive Manager).

2. Click the Menu Orb on the top left of the Control GUI.

3. Click Connect.

4. Enter the IP Address and TCP Port of the Manager in the Connect to the Manager dialog box.

5. Click Connect.

6. A successful connection will be indicated by a Connected status in the Control GUI notification area (at the bottom of the screen).

Confirming Manager to Actors Connectivity

This short test establishes whether the Manager can connect to all Actors in the system. This test assumes all Actors have been configured correctly and are online.

With the Control GUI still open, click the Actors icon in the Home tab on the icon bar to display the Actors view.

Confirm that the Manager has established a connection to all configured Actors, and troubleshoot if necessary.

Confirming Manager to Robot Manager Connectivity

This short test establishes whether the DIVArchive Manager can connected to each configured DIVArchive Robot Manager. This test assumes the following:

• All DIVArchive Robot Manager are configured correctly.

• Each DIVArchive Robot Manager is running.

• All libraries are loaded with tapes.

• Any library management software (for example, ACSLS) is running, and the library is set to Online.

• Manual operation has been confirmed successfully with the DIVArchive Robot Manager Client Tools.

Use the following procedure to confirm connectivity:

1. Click the Tapes icon on the Home tab to display the Tapes view.

2. Take note of the ACS and LSM number for each tape to test each particular library.

3. Right-click a tape for each ACS and LSM to test and click Eject Tape from the resulting menu.

4. Click the Manager icon on the Home tab to display the Manager Current Requests view.

5. Double-click the Eject Tape request entry to check if an error was encountered during request execution.

Manager Failover Procedures

Caution:

The procedures in this section are critical and sensitive. They should only be performed under the control of Oracle Support.

You use the following procedures to switch to a Backup Manager (if possible) if a Manager failure occurs.

You perform the following sequence of steps on the Main Manager:

1. Attempt to stop the DIVArchive Manager service if it is still running.

2. Execute the DIVA DB Full backup scheduled task.

3. Execute the DIVA DB Backup sync scheduled task.

4. Shutdown the DIVA Manager server as cleanly as possible.

You perform the following sequence of steps on the Backup Manager:

1. Change the IP address to the Main Manager computer's address.

2. Restart the Backup Manager computer.

3. Use the following command sequence to recover the database:

   1. Execute C:\app\oracle\admin\rman\bin\restore_lib5_from_mgr1_to_mgr2.bat.

   2. Enter 0 for Automatic Restore and wait for completion.

   3. Enter 0 for Full Backup.

   4. Enter Q to quit.

4. Start the DIVArchive services; Manager, RobotManager, Storage Plan Manager, DFM, and so on depending on your system configuration.

If all steps completed successfully, the original Backup Manager computer is now the Main Manager computer, and running the DIVArchive Manager. You can now repair or replace the original Main Manager computer.