Technical Tip: How to increase the log disk in Azure FortiProxy

[simonz_FTNT]

Description	This article describes how to increase the log disk in Azure FortiProxy.
Scope	FortiProxy.
Solution	To increase the log disk size, identify the correct disk accordingly, below example. OS disk refers to the FortiProxy OS disk (should not be edited or altered) while Data Disks is where refer to Log or WANOPT storage. The below screenshot shows that there is only a single Data Disk with the size of (30GB)   Run this command in FortiProxy to check the number of disks available in the system 'diag hardware deviceinfo disk', below screenshot indicates there are 3 disks in total (SYSTEM, HD1, and Internal-1). Internal-1 is referred to as a Temporary Disk that provides short-term storage for applications and processes and is intended to only store data such as page files, swap files, or SQL Server tempdb. This is not the intention to be used by FortiProxy as a log disk or WANOPT but due to a known bug, it may be used as a Log disk in certain VM sizes. In this example, the Log disk (HD1) will be increased with the label 'LOGUSEDXBA7DF2A9'. Login to the Azure portal (portal.azure.com) and access the FortiProxy instance. Under Overview -> Properties, look for Disk. Select 'Disk' to display the number of disks. Select the Disk Name under Data Disks. Select 'Size' to make the changes. Either select the predefined size available or enter the custom size according In this example, the size will be expanded from (30GB) to (80GB), so 80 is indicated under Custom disk size. Select 'Save' to commit the changes, it might take a while depending on the size of the disk. After done, refresh the portal page to reflect the changes but this will not automatically update into the FortiProxy until it reboots. After rebooting the FortiProxy,  notice that the HD1 disk size has been increased to (80GB) but the actual partition is still showing (30GB). This is normal as what we have done is on the physical disk level but at the OS level it is still in the old size. It is necessary now to format the log disk to get the correct size by running the command 'exe disk format <ref id>' (this will trigger another reboot and all existing logs will be lost). The disk ref ID will change after each format. The disk size has been successfully increased and the ref ID changed to (255). It also can be checked under Log & Report -> Log Setting -> Local Logs. Refer to the below link to check which Azure VM sizes that do not have Temporary Disk. Related document: https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk