This section describes how you can add a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your syslog-ng Store Box (SSB) configuration on the Microsoft Azure Portal side.

If you need more disk space than the disk size of your default data disk available in syslog-ng Store Box (SSB), from version 6.9.0, you can also add a custom cloud service provider data disk to your configuration. From 6.9.0, SSB supports adding a Microsoft Azure-managed disk and from 6.10.0, SSB supports adding additional disks in VMware ESXi to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.

In version 7.0 LTS, 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.

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your SSB configuration requires procedures that you must complete in a strict order, both on the SSB side, and on the Microsoft Azure Portal, too.

NOTE: After you configure your custom Microsoft Azure-managed disk on the Microsoft Azure side, you must add the disk to your SSB configuration, and then assign the SSB logspace of your choice to it on the SSB side.

For more information about how you can add a Microsoft Azure-managed disk to your SSB configuration on the SSB side, see Adding a new custom cloud service provider data disk to your SSB configuration on the SSB side.

Prerequisites

When adding a new Microsoft Azure-managed disk that you will later want to add to your SSB configuration, consider the following prerequisites in advance:

  • 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.

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

Limitations

When adding a new Microsoft Azure-managed disk that you will later want to add to your SSB configuration, 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.

  • In version 7.0 LTS, 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.

  		•

    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.

  • 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.

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

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

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your SSB configuration requires procedures that you must complete in a strict order.

To add a new Microsoft Azure-managed disk as a custom cloud service provider data disk on the Microsoft Azure Portal side,

  1. Shut down your SSB device completely.

  2. Log in to the Microsoft Azure Portal.

  3. Navigate to the virtual machine of your SSB device.

    Figure 46: Home > All resources> <your-virtual-machine-in-microsoft-azure>

  4. Follow the instructions of the Microsoft Azure online tutorial documentation to attach a new data disk with the size of your choice to the virtual machine of your SSB device.

    After successfully attaching the data disk, it appears under the Disks of the virtual machine of your SSB device.

    Figure 47: Home > All resources> <your-virtual-machine-in-microsoft-azure> > Settings > Disk - The new data disk attached to the virtual machine of your SSB device

    NOTE: The LUN (Logical Unit Number) value of your attached data disk corresponds to the last digit of the Host:Channel:Target:LUN (HCTL) of your custom cloud service provider data disk on the SSB side.

    Figure 48: Log > Disks> <your-custom-data-disk> - The LUN value corresponds to the last digit of the HCTL on the SSB side

  5. Restart the virtual machine for your SSB device, add the newly created Microsoft Azure-managed disk to your SSB configuration as a custom cloud service provider data disk, and then assign the SSB logspace of your choice to the newly added custom cloud service provider data disk.