Search results

@wbumiller, is your procedure still supposed to work in 2019 ? I just followed your steps to shrink a 256GB raw file to 32GB (with less than 10GB of real data), it seemed to work fine, the container starts OK, but no login prompt on console (so I guess the OS doesn't boot). I did manually a...

@sebalou, note : if you choose snapshot mode (like you did) and your underlying FS doesn't support snapshots, then Proxmox falls back to suspend mode (which needs a lot of disk space) So, in your case, I see two solutions : - stop mode, if you can afford to take your container offline during...

Well, kinda...I added some more disks ! The first phase of a backup creates an exact replica of the container in a tmp dir (no compression here). In the second phase, it compresses the replica and sends it to its final destination (backup dir) So yes, to backup a 300G container you need 300GB...

Hi, For some reasons irrelevant to explain, I used to connect to VMs with an external VNC Viewer (TigerVNC), by setting up inetd.conf on the server. Until PVE 5.1 everything worked fine. I just set up a 5.4 server, and now vncviewer only prompts for password, not for username. It seems PVE...

Hi, I just got this TAR warning when I restored an LXC backup to a new Proxmox server (5.3) : $ sudo pct restore 1011 /home/.DATA1/BACKUPS/dump/vzdump-lxc-1011-2019_03_22-23_24_38.tar.lzo --storage disks --force true (...) extracting archive...

Local storage. It's a small setup, just one proxmox server with local storage, and an NFS Server to store the backups. My understanding is that backing up first syncs the container to tmp, then archives and compresses this tmp to the final destination tar.lzo file. So in fact I have 2 related...

Hi, I'm doing backups on an NFS Share, and I'm looking to increase the speed. Log says « temporary directory is on NFS, (...) consider configuring a local tmpdir via /etc/vzdump.conf" My understanding is setting up a local tmp dir means it will be faster (it won't copy over network twice). But...

OK I'll do the upgrade But out of curiosity, is there a way to increase the startup timeout of an LXC container ?

I've got a small Proxmox 5.1 server running 8 LXC containers (Debian). Randomly, when the server reboots (usually after a power outage), 1 of the 8 containers (always the same) doesn't start. I can start it manually without any problem. Only difference between this container and the 7 others ...

Well, in some cases it does make sense to keep old data around : I have a mail server inside an LXC container, with a dedicated disk for the data (mail repository), which I didn't include to the proxmox backups (voluntarily, I wanted to keep the system backups separated from the data backups) ...

I think the way LXC backup/restore works toward additional mounted disks can be misleading and dangerous (I recently lost some data, fortunately not important). Let's say I have a container with an additional disk (mp0, "Backup" checkbox left unchecked, so the disk is NOT included in backups)...

+1 it would be great to be able to set "noatime" option when mounting an LXC disk