The log archive size of the network devices are increasing every year due to heavy data traffic. Even though we may only keep for one year retention for this kind of log, capacity planning is a must on every year to ensure the log storage will not getting exhausted.

1)  In the FortiAnalyzer/FortiManager CLI, run the following command to check if the logical volume manager (LVM) is enabled:

#execute lvm start

2) Provision the disk on the VM

3) Run the following command in the FortiAnalyzer/FortiManager CLI:

#execute lvm info

The output should look similar to:

FortiAnalyzer # execute lvm info
Disk1  :         Used       41GB
Disk2  :       Unused      200GB
Disk3  :  Unavailable        0GB
Disk4  :  Unavailable        0GB
Disk5  :  Unavailable        0GB
Disk6  :  Unavailable        0GB
Disk7  :  Unavailable        0GB
Disk8  :  Unavailable        0GB
Disk9  :  Unavailable        0GB
Disk10 :  Unavailable        0GB
Disk11 :  Unavailable        0GB
Disk12 :  Unavailable        0GB

Note : If the new disk is still not visible in the above table, reboot the unit.

#execute rebootThen repeat step 4 to make sure the new disk is detected.

4)  Extend the file system on the new disk.

#execute lvm extend disk2
This operation will need to reboot the system.
Do you want to continue? (y/n) y

Note : As of FortiAnalyzer/FortiManager 6.0.3 the arguments of this command are removed, and the syntax is just:
#execute lvm extendThis will extend the file system over all “Unused” disks from step 4)

5.)  Upon reboot, run below command again to confirm if the operation is successful:

#execute lvm info

FortiAnalyzer # execute lvm info
Disk1  :         Used       41GB
Disk2  :         Used      200GB
Disk3  :  Unavailable        0GB
Disk4  :  Unavailable        0GB
Disk5  :  Unavailable        0GB
Disk6  :  Unavailable        0GB
Disk7  :  Unavailable        0GB
Disk8  :  Unavailable        0GB
Disk9  :  Unavailable        0GB
Disk10 :  Unavailable        0GB
Disk11 :  Unavailable        0GB
Disk12 :  Unavailable        0GB