- A single Database Server using local disk space for storage.
- One primary Database Server and one secondary Database Server for disaster recovery. Both Database Servers use local disk space for storage.
- Two Database Servers in a high availability cluster using local disk space for storage.
- Two Database Servers in a high availability cluster using local disk for storage with an additional Database Server for disaster recovery.
Use the following menu options to navigate the SL1 user interface:
- To view a pop-out list of menu options, click the menu icon (
). - To view a page containing all the menu options, click the Advanced menu icon (
).
This
Local Storage
ScienceLogic Database Servers include one of two types of local storage: HDD or SSD.
- For SL1 systems that monitor 5,000 or more devices, Database Servers with SSD will provide significantly improved performance.
- For SL1 systems that monitor 10,000 or more devices, Database Servers with SSD are the required design standard.
Single Database Server Using Local Disk Space
The following restrictions apply to this configuration:
- The interface layer is optional only if the system meets all of the requirements listed in the Interface Layer Requirements section in the Distributed Architecture section.
- To use the scheduled full backup feature with this configuration, the maximum amount of space used for data storage on the Database Server must be less than half the total disk space on the Database Server.
Database with Disaster Recovery
The following restrictions apply to this configuration:
- To use the scheduled full backup feature with this configuration, the maximum amount of space used for data storage on the Database Server must be less than half the total disk space on the Database Server.
- To use the scheduled online full backup feature, a Distributed SL1 system deployed on a database with disk storage must have a database less than 250 GB in size.
- For large SL1 Systems, you must use the backup options for offline backups (that is, the backup is not created locally and copied but instead is written directly to offline storage) from the Disaster Recovery database.
- The interface layer is optional only if the system meets all of the requirements listed in the Interface Layer Requirements section in the Distributed Architecture
Clustered Databases with High Availability using Local Disk
The following restrictions apply to this configuration:
- The two clustered Database Servers must be located in the same facility and attached directly to each other with a network cable.
- The two clustered Database Servers must use DRBD Replication to ensure data is synched between the two servers.
- The interface layer is optional only if the system meets all of the requirements listed in the Interface Layer Requirements section in the Distributed Architecture
- To use the scheduled online full backup feature, a Distributed SL1 system deployed on a database with disk storage must have a database less than 250 GB in size.
- The backup from DR feature cannot be used with this configuration.
Clustered Databases with High Availability Using Local Disk and Disaster Recovery
The following restrictions apply to this configuration:
- The two clustered Database Servers must be located in the same facility and attached directly to each other with a network cable.
- The two clustered Database Servers must use DRBD Replication to ensure data is synched between the two servers.
- The scheduled full backup feature cannot be used with this configuration.
- For large SL1 Systems, ScienceLogic recommends using the backup options for offline backups (that is, the backup is not created locally and copied but instead is written directly to offline storage) from the Disaster Recovery database.
-
The interface layer is optional only if the system meets all of the requirements listed in the Interface Layer Requirements section in the Distributed Architecture