If the Disk of a Linux VM is encrypted, it's not possible to make a backup in OnApp any more.
A backup of an encrypted Windows VM works, because OnApp uses in this case ntfsclone and don't try to mount the disk:
>Running: mkdir -p /onapp/backups/n/i
>Running: dd if=/dev/nbd0 of=/onapp/backups/n/i/nilgtrzfgblmme.mbr bs=512 count=1Running: kpartx -s -p X -a /dev/nbd0
>Running: ntfsclone -q -s -O /onapp/backups/n/i/nilgtrzfgblmme /dev/mapper/nbd0X1 > /tmp/onapp-tmp-ntfsclone-nilgtrzfgblmme.log 2>&1 || ( cat /tmp/onapp-tmp-ntfsclone-nilgtrzfgblmme.log; rm -f /tmp/onapp-tmp-ntfsclone-nilgtrzfgblmme.log; exit 1 )
>Running: rm -f /tmp/onapp-tmp-ntfsclone-nilgtrzfgblmme.log
For the backup of a Linux VM, the server tries to mount the disk, which fails when the disk is encrypted:
>Running: mkdir /mnt/onapp-backup-vcfw5bjehwfony
>Running: kpartx -s -p X -a /dev/nbd0
>Running: mount -t ext3 /dev/mapper/nbd0X1 /mnt/onapp-backup-vcfw5bjehwfony
>mount: wrong fs type, bad option, bad superblock on /dev/mapper/nbd0X1,
>missing codepage or helper program, or other error
>In some cases useful info is found in syslog - try dmesg | tail or so
>Fatal: Execution of mount -t ext3 /dev/mapper/nbd0X1 /mnt/onapp-backup-vcfw5bjehwfony failed
For such scenarios we'd like to have the possibility to make full disk backups. If the backup would make a Backup of the whole disk and not only of the filesystem or files on it, the backup solutions would be compatible with different types of filesystems, even if they are encrypted. It seems the backup solution is now only compatible with ntfs, ext3 and ext4.
When the system would make a backup of the whole lv / disk, the system would probably be compatible with all filesystems (fat32, vfat, raiserfs, ext-1, etc).
Please sign in to leave a comment.