Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Automating the behavior of ROBAR-SV

&pagelevel(4)&pagelevel

The following measures automate the behavior of ROBAR-SV.

Configuration parameters

The repetition_count configuration parameter in the interface-specific ROBAR-SV configuration file (see "Interface-specific ROBAR-SV configuration files") determines how often ROBAR-SV attempts to set up the connection to the archive system during the start of a ROBAR-SV instance (default value: 1).

ROBAR-SV waits 15 seconds between each connection attempt. Setting this configuration parameter to a value > 1 makes particular sense when the archive system is controlled by multiple ROBAR-SV instances on an alternating basis. Additionally increasing its value may help to mitigate temporary connection or DNS problems during instance start process.

Automatic start of ROBAR-SV instances

When automatic start is enabled for a ROBAR-SV instance, it causes the ROBAR-SV instance to be started automatically after rebooting the Management Unit (MU). The function is also available for DEFINED instances (an attempt will be made to start them automatically).

The automatic start can be enabled and disabled using the ROBAR-SV Manager (see "Enabling and disabling automatic start").

Instances with enabled automatic start should not be deleted manually in CLI, only by means of ROBAR-SV Manager or ROBAR menu program. Otherwise it will result in dangling systemd services.

Automatic restart of ROBAR-SV instances

When automatic restart is enabled for a ROBAR-SV instance, ROBAR causes a ROBAR-SV instance to be restarted automatically following an orderly program termination initiated by the user or by program events.

The configuration parameter INIT_RESTART_OPTION in the interface-specific configuration file of ROBAR-SV (see "Interface-specific ROBAR-SV configuration files") determines whether the automatic restart is enabled (YES) or not (NO) for a ROBAR-SV instance when it is started for the first time (default value: NO). The script SET_RESTART_OPTION or the ROBAR-SV Manager is then only required in the case of changes in the restart behavior of the ROBAR-SV instance.

For a ROBAR-SV instance in the DEFINED status, the automatic restart can be enabled or disabled before startup or during ongoing operation with the SET_RESTART_OPTION_ABBA command.

Syntax:

  • SET_RESTART_OPTION_ABBA <instance> YES/NO

If necessary, ascertain the current setting using one of the following commands (only for ROBAR-SV instances, which are not in the DEFINED status):

  • cat /var/lib/robar_abba/<instance>/.ROBAR_RESTART

Note the information on resource bottlenecks given in the paragraph "If the RECOVER_DISK_FULL job..." in chapter "RECOVER_DISK_FULL script" if this function is activated.

The automatic restart can also be enabled and disabled using the ROBAR-SV Manager (see "Enabling and disabling automatic restart").

Changes in the setting for the automatic restart of a ROBAR-SV instance are effective only until the instance is reset or until ROBAR-SV is re-installed. The setting from the interface-specific configuration file of ROBAR-SV then applies.