Application area: SCSI and ABBA interface
INSTANCES
branches to a menu in which you can manage configured ROBAR-SV instances. This menu is not available when called using the ROBAR-SV Manager; the ROBAR-SV instance is preselected.
ROBAR-SV instances are configured via the ROBAR-SV Manager (see "Creating a new instance") or by creating their interface-specific configuration file (see "Interface-specific ROBAR-SV configuration files").
The menu displays a list of the ROBAR-SV instances which are currently configured and their statuses. The list is sorted according to the status of the ROBAR-SV instances (first the sample configuration file, then the ROBAR-SV instances in the CLEANING status, then RUNNING, STARTING, STOPPING, STOPPED, and DEFINED).
Figure 12: Menu for managing the ROBAR-SV instances (ABBA interface)
The ROBAR-SV instance currently selected is indicated by an arrow in the Current
column. The name of the associated interface-specific configuration file is also displayed in the header behind the keyword CONFIG
.
When you wish to perform an action for an instance in the INSTANCES
menu, first specify inverse highlighting for the instance concerned using the "up arrow" or "down arrow" key. You can then execute the required action on the highlighted instance.
INSTANCES
menu (see above) and the SELECT action.The first time the menu program is started no ROBAR-SV instance is selected. The first instance in the list will be highlighted.
Following a restart of the menu program, the ROBAR-SV instance selected most recently will once again be displayed as the selected ROBAR-SV instance.
The name of the ROBAR-SV instance is displayed in the Config file
column. It corresponds to the name of the associated interface-specific configuration file.
The Status
column displays the status of the ROBAR-SV instance. ROBAR-SV instances can have the following statuses:
DEFINED | The ROBAR-SV instance is configured, i.e. the interface-specific configurationfile exists. |
STARTING | The runtime files of the ROBAR-SV instance are being prepared and the ROBAR processes are starting up. |
RUNNING | The runtime files of the ROBAR-SV instance are configured and the ROBAR processes are running. A connection exists to an archive system. |
STOPPING | The ROBAR processes are being stopped. |
STOPPED | The ROBAR-SV instance was stopped. The configuration file and other working files still exist. No connection exists to an archive system. |
CLEANING | Disk space recovery routine is being run for the instance. |
TEMPLATE | Designates the sample configuration file. It can only be edited. |
The Archive
system
column displays the type of connection to the archive system, i.e. the value of the robot_address1
configuration parameter.
provides the following parameters:
INSTANCES
DELETE
After the relevant question has been answered, removes the ROBAR-SV instance from ongoing operation. Its files, including the configuration file, will be deleted.
EDIT
Calls the preset editor to edit the interface-specific configuration file of the ROBAR-SV instance.
You can also edit the interface-specific configuration file of a running ROBAR-SV instance. The changes will, however, only take effect when the instance has been restarted.
EXIT
Returns you to the main menu.
SELECT
Selects the ROBAR-SV instance highlighted using the "up arrow" or "down arrow" key and resets the arrow in the Current
column. Further actions are performed for this instance.
START
Starts the selected ROBAR-SV instance. Following successful execution the instance is placed in the RUNNING status.
Before starting a ROBAR-SV instance in ROBAR operation for the first time, please also observe the information in the section "Requirements for ROBAR operation".
STOP
Stops the ROBAR processes of the selected ROBAR-SV instance. The instance is placed in the STOPPED status.