→ Applies to: Hyperion 9.x and above
Ensure the following prerequisites are met before starting:
– An existing backup in Proxmox is required to restore the VM
Prepare the Target VM in Hyperion
Step 1. Create a new VM (“How to Create a VM in SynetoOS 6”)
IMPORTANT
Do not power on the VM.
Ensure the VM has the same configuration as the original, including:
- Same number of disks (e.g., 2 disks → 2 disks, 3 disks → 3 disks, etc.)
- Same amount of RAM
- Same number of CPUs
Step 2. Connect to Hyperion CLI ("How to Connect to SynetoOS 6 CLI")
Step 3. List the location of the newly created VM (replace <vm_name> with the name of the new virtual machine)
virsh domblklist <vm_name>EXAMPLE OUTPUT
Target Source ----------------------------------------------- sda /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/test_1.img sdb /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/test_2.imgSave the path to the VM datastore, in this case:
/hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c
Step 4. Create a new directory within the VM datastore folder (replace <path_to_datastore> with the path from Step 3)
mkdir <path_to_datastore>/importEXAMPLE
mkdir /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import
Step 5. Give permissions to the newly created directory (replace <path_to_datastore> with the path from Step 3)
chmod 777 <path_to_datastore>/importEXAMPLE
chmod 777 /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import
Extract and Transfer the Backup from Proxmox
Step 1. Connect to Proxmox via SSH as root (replace <proxmox_ip_address> with the correct ip address)
ssh root@<proxmox_ip_address>
Step 2. Become Super User
sudo su
Step 3. Save the backup path
pvesm status --pathEXAMPLE OUTPUT
Name Type Status Total Used Free % Path local dir active 98497792 42158080 51288064 42% /var/lib/vzSave the VM backup path, in this case is:
/var/lib/vz
Step 4. Write down the VMID of the VM
qm listEXAMPLE OUTPUT
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 100 Win11-Pro running 8192 64.00 12450Save the VMID, in this case is:
100
Step 5. Create a new directory to extract the backup files (replace <path_to_backup> with the path from Step 3 and <proxmox_vmid> with the VMID from Step 4)
mkdir -p <path_to_backup>/dump/extract/<proxmox_vmid>/EXAMPLE
mkdir -p /var/lib/vz/dump/extract/100/
Step 6. Extract the backup (replace <path_to_backup> with the path from Step 3 and <proxmox_vmid> with the VMID from Step 4)
zstdcat <path_to_backup>/dump/vzdump-qemu-100-2026_03_17-17_59_00.vma.zst | vma extract -v - <path_to_backup>/dump/extract/<proxmox_vmid>/EXAMPLE
zstdcat /var/lib/vz/dump/vzdump-qemu-100-2026_03_17-17_59_00.vma.zst | vma extract -v - /var/lib/vz/dump/extract/100/
Step 7. Copy the extracted files from Proxmox to Hyperion (replace <path_to_backup> with the path from Step 3, <proxmox_vmid> with the VMID from Step 4, <ip_address_hyperion> with Hyperion IP address and <path_to_datastore> with the path from Step 3 in the Prepare the Target VM in Hyperion subsection)
scp <path_to_backup>/dump/extract/<proxmox_vmid>/* admin@<ip_address_hyperion>:<path_to_datastore>/import/EXAMPLE
scp /var/lib/vz/dump/extract/100/* admin@10.0.0.181:/hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import/Wait for the operation to complete
Restore the VM Disk Images on Hyperion
Step 1. Connect to Hyperion CLI ("How to Connect to SynetoOS 6 CLI")
Step 2. Identify the copied disks (replace <path_to_datastore> with the path from Step 3 in the Prepare the Target VM in Hyperion subsection)
ls -R <path_to_datastore>/import/EXAMPLE OUTPUT
import/: 100 import/100: total 42G -rw-r--r-- 1 root root 512 Mar 17 18:05 configuration.conf -rw-r--r-- 1 root root 40G Mar 17 18:10 disk-drive-ide0.raw -rw-r--r-- 1 root root 2.1G Mar 17 18:12 disk-drive-ide1.raw -rw-r--r-- 1 root root 16M Mar 17 18:05 fwdata.fwThe extracted file names may vary depending on the disk bus type:
- IDE:
disk-drive-ide0.raw- SCSI:
disk-drive-scsi0.raw- VirtIO:
disk-drive-virtio0.raw- SATA:
disk-drive-sata0.rawIf multiple disks are present, the file names will increment for each additional disk:
disk-drive-scsi0.raw– first diskdisk-drive-scsi1.raw– second diskdisk-drive-scsi2.raw– third disk, and so onSave the RAW disks name, in this case is:
disk-drive-ide0.rawanddisk-drive-ide1.raw
Step 3. Save the VM disks name (replace <path_to_datastore> with the path from Step 3 in the Prepare the Target VM in Hyperion subsection)
ls -lh <path_to_datastore>/*.imgEXAMPLE OUTPUT
-rw------- 1 root root 40G Mar 25 10:00 test_1.img -rw------- 1 root root 100G Mar 25 10:00 test_2.imgSave the IMG disks name, in this case is:
test_1.imgandtest_2.img
Step 4. Replace the newly created VM disks with the Proxmox VM disks copied (replace <path_to_datastore> with the path from Step 3 in the Prepare the Target VM in Hyperion subsection, <raw_disk_name> with the Disk Name from Step 2 and <img_name> with the VM Name from Step 3)
cp <path_to_datastore>/import/<raw_disk_name> <path_to_datastore>/<img_name>EXAMPLE
cp /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import/disk-drive-ide0.raw /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/test_1.imgcp /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import/disk-drive-ide1.raw /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/test_2.imgIMPORTANT
Ensure command is run for every available disk
Remove Temporary Files After VM Health Checks
Step 1. Connect to Hyperion CLI ("How to Connect to SynetoOS 6 CLI")
Step 2. Delete leftovers (replace <path_to_datastore> with the path from Step 3 in the Prepare the Target VM in Hyperion subsection)
rm -rf <path_to_datastore>/importEXAMPLE
rm -rf /hybrid/syn-volumes/bff3ff6f-9693-4d70-bc1885558d0b1a7c/import