Note: Before you begin, run a backup first. Some of these commands are potentially destructive and may cause damage to your system if not carried out correctly.

1. Using your VM Hypervisor, add a new hard drive to your VM, and start the appliance.

2. Log in to the system console.

3. To check whether Debian installed and picked up your new hard drive, run the following command: 

   fdisk -l 

4. Confirmation: The disk /dev/sdb is picked up, and there are no partitions.

1. Log in to the system console.

2. Run the following command:

   cfdisk /dev/sdb

   Note: The cfdisk controller will load up, and here you can create a new partition on your drive.

3. From the menus at the bottom select the following:

   1. New > Primary > Size in MB.

   2. Select Write.

   3. Select Quit. Your new partition is created at /dev/sdb1.

4. Format the new disk:

   mkfs.ext3 /dev/sdb1

   Note: This command formats the partition with the ext3 file system, which should work fine for your Debian system.

1. Log in to the system console.

2. Mount the drive to create a directory for the drive:

   mkdir /store

3. Use the following command to mount the drive to a specific directory:

   mount -t ext3 /dev/sdb1 /store

4. Use the following command to check if the drive is mounted:

   ls -lsa /store

Everything is now up and running. However, you must add the new drive to /etc/fstab so that it is mounted automatically when the server reboots:

1. Open the fstab file: vi /etc/fstab.

2. Add the following line to the end of the file:

   /dev/sdb1 /store ext3 defaults,errors=remount-ro 0 1

3. Save the file.

1. Log in to the system console.

2. Stop the Kerio Connect server:

   /etc/init.d/kerio-connect stop

3. Copy all data from the old message store:

   cp -R -p /opt/kerio/mailserver/store/* /store

4. Change the message store directory path in the Kerio Connect configuration:

   sed -i -e "s/\/opt\/kerio\/mailserver\/store/\/store/" /opt/kerio/mailserver/mailserver.cfg

5. Start Kerio Connect:

   /etc/init.d/kerio-connect start

Due to the limited disk size in the virtual appliance, set log rotation for log files by size with a limited number of files.