Volume Best Practices
Volumes on cloud instances have some important limitations with which you should be familiar, for which you need to plan:
- Root or system volumes are fixed length. Linux root volumes are 20GB. Windows system volumes (C:) are 40GB.
- Root or system volumes cannot be extended. If you run out of space, your system will likely crash.
There are several practices that will help you avoid problems with your root file system:
- Root volumes should be the exclusive home for the virtual machine's operating system. Avoid installing applications on the root volume if at all possible. Create and attach additional volumes as needed and install onto those instead. Remember, you can attach as many as 6 additional volumes.
- Do not use root volumes as a dumping ground for miscellaneous files and data. Cleanup after yourself, deleting or moving what is not needed or does not belong.
- If you know files that are ordinarily located on the root volume are going to consume a lot of storage--an example would be logs, consider relocating those to another volume. For example, in Linux, you could mount a new volume at /var/log. In Windows, you could reconfigure the page file to be created on another volume.
- If you perform backups, do not create the backup files on the root volume.
Doing the above will help prevent one of the most common issues users experience: out of disk space errors.
If in doubt, ask one of the engineers at Datapipe for advice or assistance. We would prefer to prevent a problem rather than try to recover from a problem that could have been avoided.