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 to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.
In version 6.9.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.
This section describes the data disk information available for custom cloud service provider data disks on the web interface.
For more information about custom cloud service provider data disks on the cloud service provider side, see Adding a new custom cloud service provider data disk on the cloud service provider side.
For more information about custom cloud service provider data disks on the side, see Adding a new custom cloud service provider data disk to your SSB configuration.
For more information about assigning the SSB logspace of your choice to a custom cloud service provider data disk, see Assigning the SSB logspace of your choice to a custom cloud service provider data disk.
Data disk information for your custom cloud service provider data disks
After adding the new custom cloud service provider data disk to your SSB configuration, the following data disk information will be displayed under Log > Disks > <your-custom-data-disk>:
Figure 148: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks
-
Status: The connectivity status of the custom cloud service provider data disk between the SSB side and the cloud service provider side.
The possible status states are the following:
-
attached: The custom cloud service provider data disk is successfully attached to the virtual machine for your SSB device on the cloud service provider (in this case, Microsoft Azure) side.
-
missing: The custom cloud service provider data disk is committed to your SSB configuration, but the SSB device can not detect or access it on the cloud service provider side for some reason (for example, it was removed on the Microsoft Azure side earlier, or there is a connectivity issue with the Microsoft Azure portal).
-
File system ID: The unique identifier for your file system on the SSB side.
-
Host:Channel:Target:LUN (HCTL): The locally unique identifier for your custom cloud service provider data disk, which consists of the colon-separated data of the Host, the Channel, the Target, and the LUN (Logical Unit Number) value.
The last digit of the custom cloud service provider data disk's Host:Channel:Target:LUN (HCTL) corresponds to the attached custom cloud service provider data disk's LUN value on the Microsoft Azure portal:
Figure 149: Log > Disks > <your-custom-data-disk> — Data disk information for your newly added custom cloud service provider data disks
Figure 150: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks, with no SSB logspace assigned to them yet
-
Device name: The navigation path to your device on the SSB side.
-
Disk utilization: The utilization ratio of your custom data disk (in percentage), followed by the exact amount of free space, and the full size of the disk, in brackets.
-
(Optional) Onscreen information about logspaces assigned to the data disk: When you have not assigned the SSB logspace of your choice to the custom cloud service provider data disk yet, you will see the There are no available logspaces on this disk yet. onscreen information displayed on the SSB web interface.
-
(Optional) Logspaces available on this disk: When you have already assigned the SSB logspace of your choice to the custom cloud service provider data disk, the assigned logspaces will be listed here.
Figure 151: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks, with the SSB logspace of your choice assigned to them
This section describes the required procedure if you want to remove a previously added custom cloud service provider data disk (for example, a Microsoft Azure managed disk) from your syslog-ng Store Box (SSB) configuration.
For more information about adding a custom cloud service provider data disk to your SSB configuration, see Adding a new custom cloud service provider data disk to your SSB configuration.
Prerequisites
When removing a custom cloud service provider data disk from your SSB configuration, consider the following prerequisites in advance:
-
One Identity recommends that you archive or backup all data from the logspaces that you want to delete from your custom cloud service provider data disk.
-
If there are any referenced objects (for example, logspaces, filtered logspaces, multiple logspaces, remote logspaces, and logpaths) connected to your custom cloud service provider data disk, you must disconnect them from your custom cloud service provider data disk before removing it from your SSB configuration.
Limitations
When removing a custom cloud service provider data disk from your SSB configuration, consider the following limitations in advance:
-
NOTE: After adding a newly created custom cloud service provider data disk to your SSB configuration, and attaching it to a logspace, removing the custom data disk from your SSB configuration has a strict order, especially if there are referenced objects connected to the custom cloud service provider data disk. One Identity recommends that you always complete the following steps in this particular order when removing a custom cloud service provider data disk from your SSB configuration.
- You can not remove a custom cloud service provider data disk from your SSB configuration if there are any referenced objects connected to it. In these cases, you must disconnect them from your custom cloud service provider data disk before removing it from your SSB configuration.
Removing a custom cloud service provider data disk from your SSB configuration
If you have carefully considered the prerequisites and limitations, complete the following steps in this exact same order.
To remove a custom cloud service provider data disk from your SSB configuration,
-
On the SSB side, archive or backup your logspace data, remove the logspaces from your configuration, then shut down your SSB device.
-
Navigate to Log > Logspaces.
-
(Optional) Archive or backup all data from the logspaces that you want to delete from your custom cloud service provider data disk.
-
Delete all logspaces on your custom cloud service provider data disk and click 
.
-
Navigate to Log > Disks, delete the custom cloud service provider data disk of your choice, and click .
-
Navigate to Basic Settings > System.
-
Under System control, click Shutdown.
-
On the Microsoft Azure side, stop, deallocate, and detach your custom cloud service provider data disk, then restart the virtual machine for your SSB device.
-
Log in to your cloud service provider's portal (in this case, the Microsoft Azure portal).
-
Wait until the power state of your SSB device's virtual machine is Stopped.
For more information about power states in Microsoft Azure, see VM power states in the Microsoft Azure online tutorial documentation.
-
Deallocate the virtual machine for your SSB device, then wait until its power state is Stopped (deallocated).
-
Follow the instructions of the Microsoft Azure online tutorial documentation to detach your custom data disk from the virtual machine for your SSB device.
-
Restart the virtual machine for your SSB device.
This section describes how you can increase the size of a custom cloud service provider data disk that you use in your syslog-ng Store Box (SSB) configuration.
Prerequisites
When increasing the size of a custom cloud service provider data disk that you use in your SSB configuration, consider the following prerequisites in advance:
Limitations
When increasing the size of a custom cloud service provider data disk that you use in 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 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. |
Increasing the size of a custom cloud service provider data disk that you use in your SSB configuration
If the custom cloud service provider data disk that you recently added to your SSB configuration does not have enough disk space, you can increase its size on the cloud service provider side.
To increase the size of a custom cloud service provider data disk that you use in your SSB configuration,
- On the SSB side, shut down your SSB device
-
Navigate to Basic Settings > System.
-
Under System control, click Shutdown.
- On the cloud service provider side, complete the following steps:
-
Log in to your cloud service provider's portal (in this case, the Microsoft Azure portal).
-
Wait until the virtual machine of your SSB device is in the Stopped power state.
For more information about the power states of virtual machines in Microsoft Azure, see VM power states in the Microsoft Azure online tutorial documentation.
-
Deallocate the virtual machine for your SSB device, then wait until it is in the Stopped (deallocated) power state.
-
Follow the instructions of Resize a managed disk in the Azure portal in the Microsoft Azure online tutorial documentation to increase the size of your custom cloud service provider data disk.
Figure 152: Home > All resources > <your-virtual-machine-in-microsoft-azure> > <your-data-disk-in-microsoft-azure> - The Size + performance page for your managed disk in Microsoft Azure
-
Start the virtual machine for your SSB device.
NOTE: Resizing your custom cloud service provider data disk on the Microsoft Azure side is quick, but your SSB configuration must resize the file system on your SSB side to match the resizing on the Microsoft Azure 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.
Forwarding messages from SSB
The syslog-ng Store Box (SSB) appliance can forward log messages to remote destinations. The remote destination can be an SQL database running on a remote server, a syslog or log analyzing application running on a remote server, or a Hadoop Distributed File System (HDFS) destination.
