CT restores backup to wrong disks?

[MisterY]

Hi,

I got an Ubuntu 16.10 container running with Root disk stored on the SSD-ZFS-Raid1 (local-zfs) pool of Proxmox and one mp0 stored at the ZFS-RaidZ1 Pool.
I make Backups to a single HDD.
After restoring a Backup, both mountpoints are now on the single Disk?? how can I move them back to both ZFS-Pools?

This is the config of the backup:
mp0: ZFSTank:subvol-107-disk-1,mp=/mnt/data,backup=1,size=300G
rootfs: local-zfs:subvol-107-disk-1,size=15G

edit: Okay, I restored it again, now to the ZFSTank. Is it only possible to restore it to one location? Because the IO delay of my nextcloud is now way higher than before on the SSDs...

 

[fabian]

(note: please don't cross post the same issue (https://forum.proxmox.com/threads/lxc-ssd-volume-lxc-container-file.33079/#post-168764))

the GUI only allows to use the "simple restore mode", where all backed up mount points get restored to the one selected storage. the API and pct allow a more advanced reconfiguration of the container, including its mount points. e.g., you can do the following:

pct restore CTID ARCHIVE -rootfs local-zfs:SIZE,OTHEROPTIONS -mp0 zfs-raidz1:SIZE,mp=/PATH,OTHEROPTIONS

you can even do completely different mount point options and splits when restoring (e.g., a backup with two mount points can be restored to a single rootfs, and vice versa; you can change their sizes; etc.pp.). you can basically set any option when restoring, and the special "allocate a new storage volume"-syntax of "STORAGE:SIZE" works as well.

also see http://pve.proxmox.com/pve-docs/pve-admin-guide.html#_backup_and_restore and "man pct"

 

[MisterY]

Do I have to set the size everytime?

it works when I move the files to the local-zfs, but I can't do Backups.

 

[fabian]

Do I have to set the size everytime?

it works when I move the files to the local-zfs, but I can't do Backups.

yes, you have to set the size in advanced mode (you have to specify where it should create which image after all). in "simple" mode, the sizes and other options from the backed up config file are used.

 

[MisterY]

root@pve:/mnt/sdc1/dump# pct restore 111 vzdump-lxc-109-2017_05_05-15_24_08.tar.lzo -rootfs local-zfs:SIZE=15G -mp0 ZFSTank:SIZE=300G,mp=/mnt/data1
400 Parameter verification failed.
rootfs: invalid format - format error
rootfs.volume: property is missing and it is not optional
rootfs.local-zfs:SIZE: property is not defined in schema and the schema does not allow additional properties

mp0: invalid format - format error
mp0.ZFSTank:SIZE: property is not defined in schema and the schema does not allow additional properties
mp0.volume: property is missing and it is not optional

what am I doing wrong?

 

[fabian]

the syntax is "STORAGE:SIZE", e.g. "local-zfs:15" to allocate a 15G volume on the storage local-zfs

 

[MisterY]

now it tells me that the disk size exceeded? It looks like that it doesn't recognize that the mp0 should be created on the ZFSTank...

edit: my fault.. it has to be mnt/data in my case..


thank you for your help

 

[fabian]

well, the new disks you allocate must be big enough for the data you want to restore onto them.. so if you have a backup with a total of e.g., 15G (uncompressed!) and 2G of that is in the directory /some/mp, then you can restore either to a single rootfs with size >=15G, or to a rootfs with size >=13G and a mpX with size >=2G mounted at /some/mp, or some other combination of mount points as long as the stuff you restore to each of them fits within the size you allocate

if something is still unclear, please post the exact command you use to restore (including the complete output), and the configuration in the backup ("pvesm extractconfig PATHTOBACKUPARCHIVE").