To attach a recording volume to your Teramind appliance, follow the steps below:

1. Create and attach a disk with your Hypervisor tools. Please refer to the On-Premise Deployment Guide for steps to attach a second virtual disk to the Teramind VM.

2. Stop the Teramind service, execute:

3. Run the ‘lsblk’ command to check if the OS is able to recognize the new disk:

4. Create a new partition with the following command:

Press n to create a new partition, then p to specify it’s a primary one. Leave the rest of the options (First and Last sector) as is:

Press p again to print/view the new partition table:

Press w to write changes to the disk

5. Create a file system on the new partition using the following command:

6. Verify the new partition is visible by executing the following command:

7. Find the new partition’s ID by executing the 'blkid' command:

Copy the UUID:

8. Edit /etc/fstab, put the UUID from Step 7 above to a mounted record:

9. This step is optional. If you don't have any existing recordings in your rec directory, please go to Step 10. Otherwise, do the following to keep the recordings intact (so that you can later resync them in Step 13).
Rename your current recordings directory to something else (e.g., rec_old):

Create a new directory where future screen recordings will be stored (you can use your old directory name 'rec' since you renamed it already):

10. Execute the following command to mount the disk:

Ensure the disk is mounted with lsblk and df:

11. Fix the recording volume permissions to allow the Teramind service to record files with the following commands:

12. Start the Teramind service and start recording the screen data to the new disk with the following command:

13. If you created a backup of your previously captured screen recordings (in Step 9), you can now transfer the backup data to the newly mounted disk with the following command:

This might take some significant amount of time depending on how many records currently exist in your rec_old directory. Once rsync is finished, you can safely delete your rec_old directory with the following command:

14. Open your admin dashboard and verify if the disk is being displayed properly.

To mount a recording volume to a NAS (Network Attached Storage), follow the steps below:

1. Add access to files on the NAS within the local network (NFS). Here's an example of how to do that on a Synology NAS:

2. Stop the Teramind service using the following command:

3. Transfer your existing recording to NAS with rsync. For example:

4. Connect to the tm_onsite database. For a typical on-premise deployment, the command will be:

5. Insert the values into the kv_store row, adjusted for the actual NFS share IP and path. For example:

To verify the value was added, you can use this query:

Or to delete the entry if needed:

6. Restart the service using the following command:

7. Verify the NFS share is mapped with either of these two commands:

To expand a recording volume, follow the steps below:

1. First, expand the disk from your hypervisor management console. You may need to first shut down the Teramind appliance before access to edit the disk is permitted. If you have snapshots/checkpoints for the Teramind VM, you may also have to merge them first.

2. Ensure the OS is able to recognize a resized disk. You might need to reboot it. Use the lsblk command to check:

If it isn’t recognized, force a rescan of the disk devices using one of the following commands:

Where the X in the above example refers to the volume letter such as sda or sdb.

OR,

3. Execute the fdisk command below to see a partition table:

Here, sdX stands for your volume. For example:

4. Execute the fdisk command below to edit the partition:

Here, sdX stands for your volume. For example:

5. Type d at the Command prompt to delete the primary partition:

6. Type n at the Command prompt to create a new partition:

7. Type p for a primary partition and just press Enter at the partition number, first sector and last sector prompts to keep the default values. IMPORTANT: answer No to the "Do you want to remove the signature?" prompt:

8. Type p to print/view the partition table and ensure everything looks good:

9. Type w to write a modified table:

10. Update the OS kernel’s table to recognize new disk size by executing the following commands:

Here, sdX stands for your volume. For example:

11. Execute the lsblk command to ensure the OS can recognize the new partition size. If it hasn’t, reboot the OS:

12. If everything looks good, execute the resize2fs command to expand the file system. For example:

Here, sdX stands for your volume. For example:

13. Execute the following command to see if the changes have been applied successfully:

1. First, you need to access your instance via SSH or directly from your VM's management console.

2. Use the sudo and fdisk commands on the volume you have to increase to more than 2 terabytes.

Here, sdX stands for your volume. For example:

You might see a warning message about DOS partition size limit. You can ignore it:

3. Type p to show the partition table:

4. Type g to create a new empty GPT partition table:

5. Type n to add that partition (leave all entries to their default values):

6. Type p to check that the partition table had been modified:

7. Type w to save changes to the table:

8. Run the following command:

9. Run the following command to resize the volume:

Here, sdB stands for your volume. For example:

10. In some cases, you may need to reboot for the changes to take effect.