-
Is there a special reason for this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yes. I recently moved my home server to proxmox. The whole server now runs in a Ubuntu VM. I wanted to keep the size of the backups small but still be able to restore full functionality in case of a failure. MediaCovers, Plex metadata, etc. take up several gigabytes of space. Plus they do not compress well. They can be recreated easily if lost. So I moved those to a separate VM disk that is not backed up. The folder from this VM disk is mounted as a volume. I will clarify this in my docker compose. The size of my backups went down from 51 GB to 5.6 GB this way. For a normal install, this is not needed. |
Beta Was this translation helpful? Give feedback.
Yes.
I recently moved my home server to proxmox. The whole server now runs in a Ubuntu VM. I wanted to keep the size of the backups small but still be able to restore full functionality in case of a failure.
MediaCovers, Plex metadata, etc. take up several gigabytes of space. Plus they do not compress well. They can be recreated easily if lost.
So I moved those to a separate VM disk that is not backed up. The folder from this VM disk is mounted as a volume. I will clarify this in my docker compose.
The size of my backups went down from 51 GB to 5.6 GB this way.
For a normal install, this is not needed.