Adding a disk to the FortiAnalyzer-VM for logging (optional)

In the future or depending on your license requirements, you may need to add more disks to your FortiAnalyzer-VM instances.

1. In the Azure portal, under the FortiAnalyzer Virtual machine Settings > Disks, click Create and attach new disk.

   

2. Input the required parameters (Disk name, Storage type, Size, and Encryption type) and click Save.

   

   Refer to Azure Managed Disks Overview for details about Azure disks.

   On Azure VMs, data may be lost from temporary disks during a maintenance event or when powering off. Therefore, temporary disks (typically /dev/sdb) cannot be used and will not appear under exec lvm info in the CLI for FortiAnalyzer-VM. For more information, see Azure managed disks overview.

3. Log into the FortiAnalyzer-VM management GUI console.

4. Open the CLI console.

   

5. In the command prompt window, enter exec lvm info. The newly added disk appears as Unused.

   

6. Enter exec lvm extend to incorporate the disk to the FortiAnalyzer system. Entering y reboots the instance.

   

7. Navigate to the FortiAnalyzer dashboard. You will see now that the available disk size has changed. You can also run exec lvm info again in the CLI to see that the additional disk is now in use.

   

   The FortiAnalyzer system reserves a certain portion of disk space for system use and unexpected quota overflow. The remaining space is available for allocation to devices. Reports are stored in the reserved space. The following describes the reserved disk quota relative to the total available disk size (other than the root device):

   • Small disk (equal to 500 GB): reserves 20% or 50 GB of disk space, whichever is smaller.
   • Medium disk (less than or equal to 1 TB): reserves 15% or 100 GB of disk space, whichever is smaller.
   • Medium to large disk (less than or equal to 5 TB): reserves 10% or 200 GB of disk space, whichever is smaller.
   • Large disk (less than 5 TB): reserves 5% or 300 GB of disk space, whichever is smaller.
8. Configure the consumable disk space for logging. 200 GB is reserved. Therefore, 1.8 TB is available for consumption out of the 2 TB of disks.