Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Sample of the interface-specific configuration file

&pagelevel(5)&pagelevel

The sample configuration file /etc/robar/abba.conf.d/templates/template.txt below is supplied for the ABBA interface.

The file contains notes in English and German. Only the English comments are shown in this manual.

The notes on the various sections of the file are contained at the end of the section concerned; they are arranged according to the order of their occurrence.

Unable to render {include} The included page could not be found.

Notes on the section Internal environment variables

Information field %INFO%
Additional archive system information. In the ROBAR-SV Manager this is displayed in the archive system’s status information.

CLOSE_DISPLAY configuration parameter
The MANUAL and/or DISPLAY menus can remain open during the ROBAR start procedure. If the relevant ROBAR server indicates a low level of performance, a data bottleneck may have occurred between the ROBAR processes and the display processes that leads to a timeout during initialization of the start procedure. If the CLOSE_DISPLAY shell variable is defined and the variable value is set to YES, the two accessed menus are closed automatically during the ROBAR-SV start procedure. Default value: CLOSE_DISPLAY=NO

MANCHECK configuration parameter
MANCHECK allows you to restrict the range of volumes that can be processed using the menu MANUAL. In a multisystem configuration, for instance, you can stop volumes from being processed using the MANUAL menu (access protection for volumes).

If MANCHECK=YES, then the commands entered via the menu MANUAL are subject to the same checks as the commands from a BS2000 system. All parameters contained in the command are checked for plausibility and reliability.

The following checks are carried out:

  • VSN specifications are compared with the configuration parameter ROBAR_ARCHIV. If the configuration parameter is present and has been supplied with values, the VSN specifications of all commands are compared with the values in the configuration parameter.

  • If the check was positive, the values contained in the Host VSN definitions section of the configuration file may also be included in the check.

If MANCHECK=NO, the commands from the menu MANUAL are not checked.

The section Host VSN definitions in the configuration file must contain a server with the host name MAN and with a VSN list for this function to be available.
If the configuration file does not contain a host called MAN, the following error message is issued: RSV1332 HOST NOT AUTH. HOST: MAN.

Default value: MANCHECK=NO

ROBAR_ARCHIV configuration parameter
ROBAR_ARCHIV shows the archive numbers (VSNs) which may be processed by this ROBAR-SV instance. If this variable is not set, all VSNs are accepted for processing. In entries made during installation, lowercase letters are automatically converted into uppercase. Maximum length: 1024 characters.

Note the following guidelines for entering VSNs:

  • The VSN consists of six of the following characters: A..Z, a..z, 0..9, $, @, #.

  • When specifying VSN ranges (e.g. ARCHxx-ARCHyy), xx and yy must be numbers. The letters in the number range must correspond as they are used to define the start and end of the number range.

  • The first VSN may not be greater than the last VSN.

  • The first and last VSNs in the VSN range are separated by a hyphen (-).

  • The first and last VSNs in the VSN range have the same length.

  • VSNs and VSN ranges in a list must be separated by commas.

  • There must be no blanks.

  • Any number of hyphens ("-") or commas (",") are permitted at the end of the list.

A possible entry might be: A00001-A00030,B00003,B00005,B00010-B00015,---

ROBAR_INFO_MSG configuration parameter
If ROBAR_INFO_MSG=YES the ROBNxxx messages are output to the BS2000 console. The messages are suppressed if this configuration parameter is NO or not defined. ROBNxxx messages are always output as a reaction to Nxxx error messages that originate in the archive system. It is not however practical to output ROBNxxx messages in BS2000 systems as generally measures to eliminate the relevant error are initiated at the same time as the archive system error messages and more serious errors are displayed directly on the screen using the relevant ROBAR messages.

ROBOT_OFF_MSG configuration parameter
As soon as the robot switches to OFF mode, an appropriate message is sent to the BS2000 systems. This message is always a PAUSE message unless the configuration parameter ROBOT_OFF_MSG exists and has the value TYPE.
Default value: PAUSE

INIT_RESTART_OPTION configuration parameter
INIT_RESTART_OPTION defines whether the automatic restart is enabled (YES) or not (NO) for the instance when a ROBAR-SV instance is started for the first time. See section "Automatic restart of ROBAR-SV instances" in chapter "Automating the behavior of ROBAR-SV".
Default value: NO

MSG_LOG_LEVEL configuration parameter
MSG_LOG_LEVEL specifies ROBAR message output verbosity. NONE suppresses some warning messages non-critical for operation. VERBOSE value or omitting this parameter means the default verbosity.
Default value: VERBOSE

IGNORE_DEV_STATUS configuration parameter
IGNORE_DEV_STATUS defines whether ROBAR-SV ignores (YES) or not (NO) internal device status tracking when processing mount/unmount requests. See also the notes in chapter "High Availability (HA)".
Default value: NO

Unable to render {include} The included page could not be found.

Notes on the section Global definitions

archive_type configuration parameter
Defines the type of archive system.
Default value: CentricStor (must not be changed).

robots_count configuration parameter
Number of robots (ETERNUS CS is supported only as a single-robot system).
Default value: 1 (must not be changed).

location configuration parameter
A storage location name is required for the MTC devices administered by ROBAR.
A separate storage location name must be defined for each ROBAR-SV instance in accordance with the MTC devices administered and the archive system.

archive_serial_number configuration parameter
This configuration parameter is only described for reasons of compatibility.
Specification of a value <1 .. 4> is required to create default names for local CMX names. A different value should be defined for each ROBAR-SV instance if the default names are used for local CMX names.

robot_devid configuration parameter (mnemonic device names)
To simplify device configuration, archive systems support device names in mnemonic format (00..ZZ). The configuration parameter robot_devid can be used to stipulate that the device mnemonics will be used in the ROBAR configuration to address the devices operated by the robot in the commands intended for the robot.

The mode of address to be used is selected in the configuration parameter robot_devid. If the value EXPLICIT is defined for robot_devid, the mnemonic format is used. If the value IMPLICIT is defined for robot_devid (not recommended), the “numbered topologic form” is used.

Further explanations are provided in "Notes on the section Device definitions (ABBA interface)".

robot_address1 configuration parameter
The address of the archive system in the specified format (IP or FQDN, and a port number). See also the notes in chapter "Connections at the ABBA interface".

repetition_count configuration parameter
When ROBAR-SV is started, a connection to the archive system is established. The response from the archive system is expected within 20 seconds. If there is no response from the archive system, the connection is closed down and all processes of the ROBAR-SV instance are terminated.
The number of connection establishment attempts can be defined using the repetition_count configuration parameter. ROBAR-SV waits 15 seconds between each connection attempt.
The value of 0 means unlimited connection attempts. In this case the instance is started in background to avoid possible blocking for a long time.
Default value: repetition_count=1.

Unable to render {include} The included page could not be found.

Unable to render {include} The included page could not be found.

Notes on the section Device definitions

Names / addresses of the MTC devices

MTC devices can be assigned a 4-character device name (4-byte MN). However, at the interface to the archive systems ROBAR-SV still only uses a 2-character field for the device name (<DevName>).

robot_devid=EXPLICIT and 4-byte MNs in BS200

The use of 4-byte MNs and device names means that the device names used in the server and archive system are disjunctive. When multiple large ETERNUS CS systems are used, for example, it may also be necessary to assign identical device names. This increases the diagnostic effort when a fault occurs. You are therefore recommended to convert operation to 4-byte MNs only if the set of values for the 2-byte MNs is no longer adequate for the entire device configuration.

If 4-byte MNs are used in a BS2000 system, ROBAR-SV must convert the 4-byte MN into the 2-byte device name of the archive system. The devname = <DevName> operand is provided for this purpose in the device definitions. The two-byte device identifier (set of values: 0..9, A..Z) which must be specified there corresponds to the device name definition in the device configuration of the archive system (e.g. DevName in the ETERNUS CS configuration tool GXCC). The device names must be unique within an archive system.

Example

Unable to render {include} The included page could not be found.

It is advisable to use either 2-byte MNs or 4-byte MNs for the (virtual) tape devices of an archive system.

A mixture of 2-byte MNs and 4-byte MNs can also occur in the device definition. In this case you must ensure that a 2-byte MN is not used as <DevName> in one of the devname = <DevName> operands. ROBAR-SV also uses a 2-byte MN automatically as a 2-byte device name.

Example

Unable to render {include} The included page could not be found.

robot_devid=IMPLICIT and 4-byte MNs in BS2000

You are recommended not to use IMPLICIT addressing mode any longer.
However, ROBAR-SV still supports this mode and accepts the specification of 2-byte and 4-byte MNs in the device definitions section for up to 99 devices.
The devname operand may not be specified in IMPLICIT addressing mode.

Unable to render {include} The included page could not be found.

Unable to render {include} The included page could not be found.

Notes on the section Host VSN definitions

You can define VSN number ranges in two ways in ROBAR-SV:

  • Definition of global VSN number ranges via the configuration parameter ROBAR_ARCHIV (see "ROBAR_ARCHIV configuration parameter"). This means, however, that the VSNs entered there can be used by all BS2000 systems which communicate with ROBAR-SV.

  • Definition of server-related VSN number ranges in the ROBAR-SV configuration file. This enables you to assign VSN-dependent actions to selected servers (multiclient capability).

    In the Host VSN definition section you can define lists in the form

    <Hostname> <vsnbeg>-<vsnend>;

    (specification of range)

    and / or
    <Hostname> <vsn>; ....; <vsn>;(specification of single VSN)

    <vsnbeg> and <vsnend> specify the first and last elements in a range of MTC VSNs. When a range is specified, the letters in <vsnbeg> and <vsnend> must match; the range is defined by the number part. The number in <vsnbeg> must be less than that in <vsnend>. Example: D00100-D00800.

    For compatibility reasons, all VSNs defined in the gen_hosts_vsn section must also be contained in the set of values of the ROBAR_ARCHIV configuration parameter. Otherwise the definitions in the gen_hosts_vsn section will be meaningless. The lines in the gen_hosts_vsn lines must be terminated by a semicolon.

    Example

    gen_env_vars
ROBAR_ARCHIV=A00100-A01200,B11111,C10000-C11000,D00100-D00800,D02222, 
D03333,E00500-E01000
end_env_vars

gen_hosts
S200 partner=PAD1EDXX local=PAD1ED
SANDRA partner=PAD3EDXX local=PAD3ED
end_hosts

gen_hosts_vsn
PAD1EDXX A00100-A01200;B11111;C10000-C11000;
PAD3EDXX D00100-D00800;D02222;D03333;E00500-E01000;
end_hosts_vsn
Powered by Atlassian Confluence and Scroll Viewport.