Skip to main content
Version: 7.5.10 (latest)

SUSE Virtualization (Harvester) VM Backup and Restore Support Limitations

This document outlines the backup and restore support limitations for SUSE Virtualization Virtual Machines (VMs) in Veeam Kasten. Certain conditions should be kept in mind before initiating the backup or restore process:

1. DHCP-identifier​

If using DHCP for network connectivity, the network interface configuration for VMs should have DHCP identifier configured to use MAC address, as otherwise the SUSE Virtualization DHCP server may fail to assign an IP address to the VM after it is restored via Kasten. An example of the cloud-init configuration is shown below: 

    cloud-user@customer-test-vm:~$ sudo cat /etc/netplan/50-cloud-init.yaml
    network:
        ethernets:
            enp1s0:
                dhcp4: true
                dhcp-identifier: mac
        version: 2

2. QEMU Guest Agent​

The QEMU guest agent should be activated within your VM to ensure the consistent backup of data. The guest agent can halt write functions during the backup procedure, thus preventing data manipulation or loss. For more information, refer to the Harvester instruction installing the QEMU guest agent.

3. Volume Snapshot Class Annotation​

For successful operations with Harvester VMs, users need to annotate the Volume Snapshot Class (VSC) with a specific annotation. Currently, the support is limited to VSCs having the "parameters.type.snap" (same as the default "longhorn-snapshot"). One of its limitations is that users cannot restore the VM using a "local" restore point. Only 'Import and Restore' are feasible - this implies each Veeam Kasten VM backup needs to be exported to a location specified in a "Location Profile" before a VM restoration.

4. Backup of SSH Key Objects​

If "SSH Key" objects - represented as Kubernetes Custom Resource Definition named "KeyPair" need to be backed up, additional Veeam Kasten policy configuration may be necessary. This is because "KeyPair" objects may be located in a different Kubernetes namespace than that of the VM.

5. Block Mode Export of Encrypted VM Images and VM Image Volumes​

Currently, block mode export of encrypted/decrypted VM images and volumes created from such images is not supported.