I got expected errors, but the Container was created and not destroyed like in GUI Restore, and it is starting, but because of the used Services inside of the VM i get some problems with mounts and services.
extracting archive '/stor-zfs-2tb/test/dump/vzdump-lxc-107-2019_07_27-12_14_28.tar'...
Ah shit lol :D you're right... it worked... now i need to test if a restore in shell using "-unprivileged" with "-ignore-unpack-errors 1" is working to get an unprivileged container of the privileged backup.
OK backup is done now, but restore on new server fails...
extracting archive '/opt/sh2tosh3/dump/vzdump-lxc-107-2019_07_27-12_14_28.tar'
tar: -: Cannot open: Permission denied
tar: Error is not recoverable: exiting now
TASK ERROR: unable to restore CT 101 - command 'lxc-usernsexec -m...
No, it's possible to chose the CIFS Storage as Backup Target, but when starting a backup, this gets shown:
Proxmox uses the local storage (/var/tmp/...) for temporary files, and the local storage has not enough space to create the backup.
What i tried now, was changing the /etc/vzdump.conf...
I'm trying to move a big Container from an Debian 9 Proxmox 5 System to a new Debian 10 Proxmox 6 System. The Container has a local disk on ZFS and 2 Mount Points on ZFS.
When i'm trying to create Backup,i got the problem that i do not have enough local space.
I mounted an external Storage...
Are there already any working Solutions for the Buster VM Problems?
Host with Debian Buster, PVE6 installed using the Repos, create a container with Buster Template, install MariaDB-Server and it won't start.
Same problem with other Tools like Dovecot.
In MariaDB it can be fixed by commenting...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.