syslog-ng Store Box 7.2.0 - Administration Guide

Prerequisites

When adding a new custom cloud service provider data disk to your SSB configuration on the SSB side, consider the following prerequisites in advance:

• If you want to add a custom cloud service provider data disk to your SSB configuration, you must add a new custom cloud service provider data disk on your cloud service provider side before you can add it to your configuration on the SSB side.

• If you want to add custom cloud service provider data disks to your configuration in SSB, you must add the custom cloud service provider data disk under Log > Disks > <your-custom-data-disk>, and commit your changes. After that, the newly added custom cloud service provider data disk will be available for selection in the dropdown list under Log > Logspaces > <your-new-logspace-with-custom-data-disk> > Storage > Disk.

Limitations

When adding a new custom cloud service provider data disk to your SSB configuration on the SSB side, consider the following limitations in advance:

• Caution: HAZARD OF DATA LOSS! Although it is possible to decrease the size of Microsoft Azure and VMware ESXi managed disks, One Identity does not support decreasing the size of custom cloud service provider data disks already added to your SSB configuration. One Identity only supports increasing the size of such custom cloud service provider data disks after adding them to your SSB configuration.

• NOTE: Resizing your custom cloud service provider data disk on the Microsoft Azure or VMware ESXi side may be quick, depending on your infrastructure, but your SSB configuration must resize the file system on your SSB side to match the resizing on the Microsoft Azure or VMware ESXi side. As a result, depending on the original size of the custom cloud service provider data disk and on the size you will expand it to, starting the virtual machine for your SSB device after you expand the size of your custom cloud service provider data disk may take a long time.

• NOTE: If you fail to assign the newly created SSB logspace of your choice to the new custom cloud service provider data disk, SSB will not automatically detect and use the new custom cloud service provider data disk to store messages on it.

• You can only configure custom cloud service provider data disks for logspaces that you newly create. One Identity does not support configuring custom cloud service provider data disks in logspaces that you configured and committed earlier.

• In version 7.2.0, SSB supports adding Microsoft Azure managed disks of up to 32,767 GiB storage space to your SSB device. For more information about managed data disks in Microsoft Azure, see Disk type comparison in the Microsoft Azure online documentation.

• If you want to add custom cloud service provider data disks to your configuration in SSB, you must add the custom cloud service provider data disk under Log > Disks > <your-custom-data-disk>, and commit your changes. After that, the newly added custom cloud service provider data disk will be available for selection in the dropdown list under Log > Logspaces > <your-new-logspace-with-custom-data-disk> > Storage > Disk.

• Transporting custom cloud service provider data disks between SSB devices is not supported.

• CAUTION: HAZARD OF DATA LOSS! One Identity does not support decreasing the size of an additional VMware ESXi hard disk added to your SSB configuration as a custom cloud service provider data disk.

  You can only add, remove, or resize a custom cloud service provider data disk in your configuration after shutting your SSB device down first. Hot swaps are not supported.

• You can only add an Azure managed disk as a custom cloud service provider data disk to your SSB on the Microsoft Azure portal side.

• SSB only accepts and detects empty disks as custom cloud service provider data disks. As a result, you can only add a newly created Azure managed disk or VMware ESXi disk as a custom cloud service provider data disk to your SSB configuration. Adding an already existing Azure managed disk (by clicking Attach existing disks on the Microsoft Azure portal) or already existing VMware ESXi disk is not supported.

• One Identity does not support adding Microsoft Azure or VMware ESXi managed disks to your SSB logspaces as a shared disk.

• The number of managed disks you can add on the Microsoft Azure portal depends on the type of Microsoft Azure subscription you are using.

After adding a new custom cloud service provider data disk on your cloud service provider side, you can add the new custom cloud service provider data disk on the SSB side.

To add a new custom cloud service provider data disk to your SSB configuration,

1. On the SSB side, shut down your SSB device

   1. Navigate to Basic Settings > System.

   2. Under System control, click Shutdown.

2. On the cloud service provider side, complete the following steps depending on which cloud service provider you want to use:

   • On Microsoft Azure: To add a managed disk as a custom cloud service provider data disk in Microsoft Azure, complete the steps described in Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk on the Microsoft Azure Portal side

   • On VMware ESXi: To add an additional hard disk as a custom cloud service provider data disk in VMware ESXi, complete the steps described in Adding an additional disk in VMware ESXi as a custom cloud service provider data disk on the vSphere Client side

3. In the virtual machine for your SSB device, complete the following steps on the SSB web interface:

   1. Navigate to Log > Disks.

      SSB will automatically detect newly added custom cloud service provider data disks and display them:

      Figure 162: Log > Disks - New disks detected

      

   2. Enter a name for your new custom cloud service provider data disk, and click .

      Figure 163: Log > Disks > <your-custom-data-disk>

      

   3. Navigate to Log > Logspaces, and assign the SSB logspace of your choice to the custom cloud service provider data disk.

      NOTE: If you fail to assign the newly created SSB logspace of your choice to the new custom cloud service provider data disk, SSB will not automatically detect and use the new custom cloud service provider data disk to store messages on it.

      NOTE:After adding a newly created custom cloud service provider data disk to your SSB configuration, and assigning the SSB logspace of your choice to it, removing the custom cloud service provider data disk from your SSB configuration has a strict order, especially if there are referenced objects tied to the custom cloud service provider data disk. For more information about the process to remove such custom cloud service provider data disks from your SSB configuration, see Removing a custom cloud service provider data disk from your SSB configuration.

      NOTE: For newly created logspaces, selecting a data disk for your logspace is required.