Using the ROBAR-SV Manager

The ROBAR-SV Manager is a web application that is called from the SE Manager.

The list of supported browsers is the same as in the SE Manager version targeted by ROBAR-SV. It is provided in the corresponding M2000 Release Notice.

Special aspects when working with SE Manager

• Information on and actions for the ROBAR-SV Manager are available in the SE Manager when the ROBAR-SV Manager is installed as a ROBAR add-on pack (see the "Operation and Administration" manual [14]):

  >	In the SE Manager navigate to the Service function for the relevant management unit. The information on the actions for the ROBAR-SV Manager is displayed in the add-on pack area of the Update tab.
  >	In the Logging area of the SE Manager, select the Audit Logging tab. Entries for important actions are generated there by the ROBAR-SV Manager.
  >	In the Logging area of the SE Manager, select the Event Logging tab. Entries for important events are generated there by the ROBAR-SV Manager.

  • The max_trace_file_age=30 parameter is set by default in the global configuration file of ROBAR-SV, see "Global configuration file for ROBAR-SV".
  • The robaradm and robarsv user groups and the robar user have the following fixed user IDs. These are also retained after new installations or updates.
    • User robar: Id 860
    • User group robarsv: Id 860
    • User group robaradm: Id 865
  • The storage space occupied by the ROBAR instances is monitored periodically using a script and optimized if necessary, see "Disk monitoring on SE servers".
  • The "Configuration Save and Restore" (CSR) function of the SE Manager (see the "Operation and Administration" manual [14]) takes into account the ROBAR configuration when ROBAR-SV is installed in the SE Manager as an add-on pack:
    • When a configuration backup with CSR takes place, backup archives containing the current CMX and ROBAR configuration files are created automatically (by analogy to the description on "Configuration backup and restore"). Any existing CMX and ROBAR backup archives are overwritten. The automatically created CMX and ROBAR backup archives are transferred to the CSR backup archive.
    • In the event of restoral with CSR, the CMX and ROBAR backup archives are restored from the CSR backup archive. Any existing CMX and ROBAR backup archives are overwritten. The restored CMX and ROBAR backup archives can then be used in the ROBAR-SV Manager to restore the CMX and ROBAR configuration files, see "Configuration backup and restore".

  • In the event of a software update of ROBAR-SV or the carrier system, CSR makes the CMX and ROBAR backup archives stored most recently available to ROBAR-SV. ROBAR-SV takes these CMX and ROBAR backup archives into consideration when restoring its configuration files.

When ROBAR-SV is installed or updated, CSR supplies ROBAR-SV with the CMX and ROBAR backup archives only if a CSR configuration backup which contains the CMX and ROBAR backup archives was performed beforehand.

When the carrier system is updated, CSR restoral is automatically performed. In this case CSR supplies ROBAR-SV with the CMX and ROBAR backup archives most recently stored, provided they are available.

The CSR backup incorporates CMX and ROBAR backup archives if the ROBAR add-on pack is correctly installed and the CMX and ROBAR backup archives can be provided at the time the CSR backup takes place.