Each archive system is operated via a so-called ROBAR-SV instance.
Archive systems with SCSI interface are divided into partitions. Each partition requires its own ROBAR-SV instance.
If you intend to run several ETERNUS CS systems at the same time, a separate ROBAR-SV instance is needed for each archive system.
A ROBAR-SV instance consists of:
its interface-specific configuration file (see "Interface-specific ROBAR-SV configuration files")
The name of the ROBAR-SV instance’s interface-specific configuration file is identical to the name of the ROBAR-SV instance.its runtime files (see section "Runtime files for a ROBAR-SV instance" in chapter "Directories and files of ROBAR-SV")
its ROBAR processes for communication with the archive system and the BS2000 systems
An installation of ROBAR-SV on the ROBAR server enables multiple archives (storage locations) or partitions to be operated via different ROBAR-SV instances, see "Working with multiple archives".
The ROBAR administrator configures a ROBAR-SV instance by creating an interface-specific configuration file with the name of the ROBAR-SV instance.
The ROBAR operator manages the configured ROBAR-SV instances in the ROBAR-SV Manager (ROBAR-SV Instances menu) or in the robar menu program (INSTANCES menu). He/She can select, start and stop the ROBAR-SV instances and display information about them. The ROBAR-SV instance selected remains preset for further actions.
ROBAR-SV instances can also be predefined in the global configuration file ROBAR-SV. They are then started automatically, see section "ABBA, SCSI configuration parameter" in chapter "Global configuration file for ROBAR-SV".