VM Backup Plugin


Recommended Posts

Im getting this error about not being able to run the script, even though it still exists, im running it manually now and its running fine, but the scheduling bit of the plugin doesnt wanna find it for some reason?

 

Event: Unraid Status
Subject: VM Backup plugin
Description: cannot run /boot/config/plugins/vmbackup/configs/Weekly_Backups/
Importance: warning

2022-05-22 04:40 User script file does not exist. Exiting.

 

Link to comment
4 hours ago, rorton said:

Im getting this error about not being able to run the script, even though it still exists, im running it manually now and its running fine, but the scheduling bit of the plugin doesnt wanna find it for some reason?

 

Event: Unraid Status
Subject: VM Backup plugin
Description: cannot run /boot/config/plugins/vmbackup/configs/Weekly_Backups/
Importance: warning

2022-05-22 04:40 User script file does not exist. Exiting.

 

I've been getting a similar error for a while. I posted about it a page or so back, but we never did get it resolved. Maybe you'll have better success? I'd love to hear the solution. It's really annoying to have those error messages pop up every time it tries to run. In my case, the job errors out, then completes successfully, which is rather confusing, to say the least.

Link to comment
Posted (edited)

I have strange errors after update to 6.10.0 (6.10.1 too). It happens every time when VMBackup script running. But backup itself seems to be completed successfully because VM image and all files was copied to the destination.

 

2022-05-23 21:30:03 failure: copy of /mnt/remotes/192.168.2.45_Backups/WINDOWS/Windows 10/20220522_2130_vdisk1.img to /mnt/remotes/192.168.2.45_Backups/WINDOWS/Windows 10/20220523_2130_vdisk1.img failed.

This is confusing, why script tries to copy old image file to a new one? Why this error happening?

 

Also I'm not sure why this is got failed, because SMB share where I'm copying backups is 100% working fine and reliable. Is this issue with file permission? All files got 0666 rights and share user as a owner.

Edited by SuberSeb
Link to comment

Hiya, firstly, thanks for creating and contributing this plugin. It's solving a really important issue for me so I really appreciate all the work. 

 

Could someone explain what to do when a partial img exists.

 

What causes it?

Is this a failed copy? 

Should I delete this?

 

Also, does anyone know of a good guide to convert a raw disk type to qcow2 so I can snapshot?

 

Thanks

 

 image.png.10c93ce2261790bd9e614f839701710b.png

Link to comment

To convert a raw disk you just use the qemu-img command on a linux box eg:

 

qemu-img convert -p -c -O qcow2 originaldisk.qcow2 newdisk.qcow2

 

Resulting newdisk.qcow2 is in qcow format.

 

You can check with qemu-img info newdisk.qcow2

  • Like 2
Link to comment
13 hours ago, Luis Belo said:

Hi,

My config menu it doesn´t show Unassigned Devices... I would like to safe the backups to a external drive.
Any one can help me please?

 

Thanks
image.png.30e0b7eefb5d2268b06b995755b13917.pngimage.png.bad2e49618adc42df720bca1d8b905ed.png

I pasted/write the UD Path manually. I have the same Issue. Only Local/Array Path are showed.

Link to comment

A noob question, dunno if this already has been processed, but I'm running to an error. Got a external_ssd which does the job for backups, but something is going wrong:

 

Quote

2022-05-29 01:00:01 Start logging to log file.
2022-05-29 01:00:02 information: send_notifications is 1. notifications will be sent.
2022-05-29 01:00:02 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled.
2022-05-29 01:00:02 information: keep_log_file is 1. log files will be kept.
2022-05-29 01:00:02 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep.
2022-05-29 01:00:02 information: enable_vm_log_file is 0. vm specific logs will not be created.
2022-05-29 01:00:02 information: backup_all_vms is 1. vms_to_backup will be ignored. all vms will be backed up.
2022-05-29 01:00:02 information: use_snapshots is 1. vms will be backed up using snapshots if possible.
2022-05-29 01:00:02 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected.
2022-05-29 01:00:02 information: set_vm_to_original_state is 1. vms will be set to their original state after backup.
2022-05-29 01:00:02 information: number_of_days_to_keep_backups is 0. backups will be kept indefinitely. be sure to set number_of_backups_to_keep to keep backups storage usage down.
2022-05-29 01:00:02 information: number_of_backups_to_keep is 2. this is probably a sufficient number of backups to keep.
2022-05-29 01:00:02 information: inline_zstd_compress is 0. vdisk images will not be inline compressed.
2022-05-29 01:00:02 information: pigz_compress is 0. backups will not be post compressed.
2022-05-29 01:00:02 information: snapshot_extension is snap. continuing.
2022-05-29 01:00:02 information: snaphot extension not found in vdisk_extensions_to_skip. extension was added.
2022-05-29 01:00:02 information: snapshot_fallback is 0. snapshots will fallback to standard backups.
2022-05-29 01:00:02 information: pause_vms is 0. vms will be shutdown for standard backups.
2022-05-29 01:00:02 information: enable_reconstruct_write is 0. reconstruct write will not be enabled by this script.
2022-05-29 01:00:02 information: compare_files is 0. files will not be compared after backups.
2022-05-29 01:00:02 information: backup_xml is 1. vms will have their xml configurations backed up.
2022-05-29 01:00:02 information: backup_nvram is 1. vms will have their nvram backed up.
2022-05-29 01:00:02 information: backup_vdisks is 1. vms will have their vdisks backed up.
2022-05-29 01:00:02 information: start_vm_after_backup is 0. vms will not be started following successful backup.
2022-05-29 01:00:02 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup.
2022-05-29 01:00:02 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups.
2022-05-29 01:00:02 information: rsync_only is 0. cp will be used when applicable.
2022-05-29 01:00:02 information: actually_copy_files is 1. files will be copied.
2022-05-29 01:00:02 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks.
2022-05-29 01:00:02 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks.
2022-05-29 01:00:02 information: keep_error_log_file is 1. error log files will be kept.
2022-05-29 01:00:02 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep.
2022-05-29 01:00:03 information: started attempt to backup Youtube, HomeAssistant, OPNSense, Mailserver to /mnt/disks/External_SSD/VMs
2022-05-29 01:00:03 information: Youtube can be found on the system. attempting backup.
2022-05-29 01:00:03 information: creating local Youtube.xml to work with during backup.
2022-05-29 01:00:03 information: /mnt/disks/External_SSD/VMs/Youtube does not exist. creating it.
2022-05-29 01:00:03 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. Youtube is running. can_backup_vm set to y.
2022-05-29 01:00:03 information: actually_copy_files is 1.
2022-05-29 01:00:03 information: can_backup_vm flag is y. starting backup of Youtube configuration, nvram, and vdisk(s).
2022-05-29 01:00:03 information: copy of Youtube.xml to /mnt/disks/External_SSD/VMs/Youtube/20220529_0100_Youtube.xml complete.
2022-05-29 01:00:03 information: Youtube does not appear to have an nvram file. skipping.
2022-05-29 01:00:03 information: able to perform snapshot for disk /mnt/user/domains/Youtube/yt.img on Youtube. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-05-29 01:00:03 information: qemu agent found. enabling quiesce on snapshot.
2022-05-29 01:00:03 information: snapshot command succeeded on yt.snap for Youtube.
2022-05-29 01:01:41 failure: copy of /mnt/user/domains/Youtube/yt.img to /mnt/disks/External_SSD/VMs/Youtube/20220529_0100_yt.img failed.
2022-05-29 01:01:41 information: backup of /mnt/user/domains/Youtube/yt.img vdisk to /mnt/disks/External_SSD/VMs/Youtube/20220529_0100_yt.img complete.
2022-05-29 01:01:47 information: commited changes from snapshot for /mnt/user/domains/Youtube/yt.img on Youtube.
2022-05-29 01:01:47 information: forcibly removed snapshot /mnt/user/domains/Youtube/yt.snap for Youtube.
2022-05-29 01:01:47 information: the extensions of the vdisks that were backed up are img.
2022-05-29 01:01:47 information: vm_state is running. vm_original_state is running. not starting Youtube.
2022-05-29 01:01:47 information: backup of Youtube to /mnt/disks/External_SSD/VMs/Youtube completed.
2022-05-29 01:01:47 information: number of days to keep backups set to indefinitely.
2022-05-29 01:01:47 information: cleaning out backups over 2 in location /mnt/disks/External_SSD/VMs/Youtube/
2022-05-29 01:01:47 information: did not find any config files to remove.
2022-05-29 01:01:47 information: did not find any nvram files to remove.
2022-05-29 01:01:47 information: did not find any vdisk image files to remove.
2022-05-29 01:01:47 information: did not find any vm log files to remove.
2022-05-29 01:01:47 information: removing local Youtube.xml.
2022-05-29 01:01:48 information: HomeAssistant can be found on the system. attempting backup.
2022-05-29 01:01:48 information: creating local HomeAssistant.xml to work with during backup.
2022-05-29 01:01:48 information: /mnt/disks/External_SSD/VMs/HomeAssistant does not exist. creating it.
2022-05-29 01:01:48 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. HomeAssistant is running. can_backup_vm set to y.
2022-05-29 01:01:48 information: actually_copy_files is 1.
2022-05-29 01:01:48 information: can_backup_vm flag is y. starting backup of HomeAssistant configuration, nvram, and vdisk(s).
2022-05-29 01:01:48 information: copy of HomeAssistant.xml to /mnt/disks/External_SSD/VMs/HomeAssistant/20220529_0100_HomeAssistant.xml complete.
2022-05-29 01:01:48 information: copy of /etc/libvirt/qemu/nvram/598920d7-3307-26f7-cd04-76b7c6bae81b_VARS-pure-efi.fd to /mnt/disks/External_SSD/VMs/HomeAssistant/20220529_0100_598920d7-3307-26f7-cd04-76b7c6bae81b_VARS-pure-efi.fd complete.
2022-05-29 01:01:48 information: able to perform snapshot for disk /mnt/user/domains/HomeAssistant/hassos_vm.img on HomeAssistant. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-05-29 01:01:48 information: qemu agent found. enabling quiesce on snapshot.
2022-05-29 01:01:48 information: snapshot command succeeded on hassos_vm.snap for HomeAssistant.
2022-05-29 01:03:11 failure: copy of /mnt/user/domains/HomeAssistant/hassos_vm.img to /mnt/disks/External_SSD/VMs/HomeAssistant/20220529_0100_hassos_vm.img failed.
2022-05-29 01:03:11 information: backup of /mnt/user/domains/HomeAssistant/hassos_vm.img vdisk to /mnt/disks/External_SSD/VMs/HomeAssistant/20220529_0100_hassos_vm.img complete.
2022-05-29 01:03:18 information: commited changes from snapshot for /mnt/user/domains/HomeAssistant/hassos_vm.img on HomeAssistant.
2022-05-29 01:03:18 information: forcibly removed snapshot /mnt/user/domains/HomeAssistant/hassos_vm.snap for HomeAssistant.
2022-05-29 01:03:18 information: the extensions of the vdisks that were backed up are img.
2022-05-29 01:03:18 information: vm_state is running. vm_original_state is running. not starting HomeAssistant.
2022-05-29 01:03:18 information: backup of HomeAssistant to /mnt/disks/External_SSD/VMs/HomeAssistant completed.
2022-05-29 01:03:18 information: number of days to keep backups set to indefinitely.
2022-05-29 01:03:18 information: cleaning out backups over 2 in location /mnt/disks/External_SSD/VMs/HomeAssistant/
2022-05-29 01:03:18 information: did not find any config files to remove.
2022-05-29 01:03:18 information: did not find any nvram files to remove.
2022-05-29 01:03:18 information: did not find any vdisk image files to remove.
2022-05-29 01:03:18 information: did not find any vm log files to remove.
2022-05-29 01:03:18 information: removing local HomeAssistant.xml.
2022-05-29 01:03:18 information: OPNSense can be found on the system. attempting backup.
2022-05-29 01:03:18 information: creating local OPNSense.xml to work with during backup.
2022-05-29 01:03:18 information: /mnt/disks/External_SSD/VMs/OPNSense does not exist. creating it.
2022-05-29 01:03:18 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. OPNSense is running. can_backup_vm set to y.
2022-05-29 01:03:18 information: actually_copy_files is 1.
2022-05-29 01:03:18 information: can_backup_vm flag is y. starting backup of OPNSense configuration, nvram, and vdisk(s).
2022-05-29 01:03:18 information: copy of OPNSense.xml to /mnt/disks/External_SSD/VMs/OPNSense/20220529_0100_OPNSense.xml complete.
2022-05-29 01:03:18 information: copy of /etc/libvirt/qemu/nvram/18bd3c40-f1b1-b053-17cc-a0968516c6d9_VARS-pure-efi.fd to /mnt/disks/External_SSD/VMs/OPNSense/20220529_0100_18bd3c40-f1b1-b053-17cc-a0968516c6d9_VARS-pure-efi.fd complete.
2022-05-29 01:03:18 information: able to perform snapshot for disk /mnt/user/domains/OPNSense/vdisk1.img on OPNSense. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-05-29 01:03:18 information: qemu agent not found. disabling quiesce on snapshot.
2022-05-29 01:03:18 information: snapshot command succeeded on vdisk1.snap for OPNSense.
2022-05-29 01:03:49 failure: copy of /mnt/user/domains/OPNSense/vdisk1.img to /mnt/disks/External_SSD/VMs/OPNSense/20220529_0100_vdisk1.img failed.
2022-05-29 01:03:49 information: backup of /mnt/user/domains/OPNSense/vdisk1.img vdisk to /mnt/disks/External_SSD/VMs/OPNSense/20220529_0100_vdisk1.img complete.
2022-05-29 01:03:55 information: commited changes from snapshot for /mnt/user/domains/OPNSense/vdisk1.img on OPNSense.
2022-05-29 01:03:55 information: forcibly removed snapshot /mnt/user/domains/OPNSense/vdisk1.snap for OPNSense.
2022-05-29 01:03:55 information: the extensions of the vdisks that were backed up are img.
2022-05-29 01:03:55 information: vm_state is running. vm_original_state is running. not starting OPNSense.
2022-05-29 01:03:55 information: backup of OPNSense to /mnt/disks/External_SSD/VMs/OPNSense completed.
2022-05-29 01:03:55 information: number of days to keep backups set to indefinitely.
2022-05-29 01:03:55 information: cleaning out backups over 2 in location /mnt/disks/External_SSD/VMs/OPNSense/
2022-05-29 01:03:55 information: did not find any config files to remove.
2022-05-29 01:03:55 information: did not find any nvram files to remove.
2022-05-29 01:03:55 information: did not find any vdisk image files to remove.
2022-05-29 01:03:55 information: did not find any vm log files to remove.
2022-05-29 01:03:55 information: removing local OPNSense.xml.
2022-05-29 01:03:55 information: Mailserver can be found on the system. attempting backup.
2022-05-29 01:03:55 information: creating local Mailserver.xml to work with during backup.
2022-05-29 01:03:55 information: /mnt/disks/External_SSD/VMs/Mailserver does not exist. creating it.
2022-05-29 01:03:55 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. Mailserver is running. can_backup_vm set to y.
2022-05-29 01:03:55 information: actually_copy_files is 1.
2022-05-29 01:03:55 information: can_backup_vm flag is y. starting backup of Mailserver configuration, nvram, and vdisk(s).
2022-05-29 01:03:55 information: copy of Mailserver.xml to /mnt/disks/External_SSD/VMs/Mailserver/20220529_0100_Mailserver.xml complete.
2022-05-29 01:03:55 information: copy of /etc/libvirt/qemu/nvram/cf6719b9-1ba1-084c-2eb3-a6cb477dc1f2_VARS-pure-efi.fd to /mnt/disks/External_SSD/VMs/Mailserver/20220529_0100_cf6719b9-1ba1-084c-2eb3-a6cb477dc1f2_VARS-pure-efi.fd complete.
2022-05-29 01:03:55 information: able to perform snapshot for disk /mnt/user/domains/Mailserver/vdisk1.img on Mailserver. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-05-29 01:03:55 information: qemu agent found. enabling quiesce on snapshot.
2022-05-29 01:03:55 information: snapshot command succeeded on vdisk1.snap for Mailserver.
2022-05-29 01:10:21 failure: copy of /mnt/user/domains/Mailserver/vdisk1.img to /mnt/disks/External_SSD/VMs/Mailserver/20220529_0100_vdisk1.img failed.
2022-05-29 01:10:21 information: backup of /mnt/user/domains/Mailserver/vdisk1.img vdisk to /mnt/disks/External_SSD/VMs/Mailserver/20220529_0100_vdisk1.img complete.
2022-05-29 01:10:27 information: commited changes from snapshot for /mnt/user/domains/Mailserver/vdisk1.img on Mailserver.
2022-05-29 01:10:27 information: forcibly removed snapshot /mnt/user/domains/Mailserver/vdisk1.snap for Mailserver.
2022-05-29 01:10:27 information: extension for /mnt/user/isos/CentOS-Stream-8-x86_64-latest-boot.iso on Mailserver was found in vdisks_extensions_to_skip. skipping disk.
2022-05-29 01:10:27 information: the extensions of the vdisks that were backed up are img.
2022-05-29 01:10:27 information: vm_state is running. vm_original_state is running. not starting Mailserver.
2022-05-29 01:10:27 information: backup of Mailserver to /mnt/disks/External_SSD/VMs/Mailserver completed.
2022-05-29 01:10:27 information: number of days to keep backups set to indefinitely.
2022-05-29 01:10:27 information: cleaning out backups over 2 in location /mnt/disks/External_SSD/VMs/Mailserver/
2022-05-29 01:10:27 information: did not find any config files to remove.
2022-05-29 01:10:27 information: did not find any nvram files to remove.
2022-05-29 01:10:27 information: did not find any vdisk image files to remove.
2022-05-29 01:10:27 information: did not find any vm log files to remove.
2022-05-29 01:10:27 information: removing local Mailserver.xml.
2022-05-29 01:10:27 information: finished attempt to backup Youtube, HomeAssistant, OPNSense, Mailserver to /mnt/disks/External_SSD/VMs.
2022-05-29 01:10:27 information: cleaning out logs over 1.
2022-05-29 01:10:27 information: did not find any log files to remove.
2022-05-29 01:10:27 information: cleaning out error logs over 10.
2022-05-29 01:10:27 information: did not find any error log files to remove.
2022-05-29 01:10:27 warning: errors found. creating error log file.
2022-05-29 01:10:27 Stop logging to log file.

 

Did I forget something in the settings or do I need to give the external_ssd some extra permissions?

Link to comment

I'm testing this to backup some vm's which are using vmdk files from my previous esx environment. I noticed the backup files generated are just copying the vmdk and not the actual vmdk flat file (which has the actual data in it). Am I missing something, or is vmdk support not there yet?

Link to comment
20 hours ago, Elmojo said:

Please explain what you did, for the benefit of future noobs who may run into the same issue. 😁

Reformatted the external SSD to xfs and everything works like it should.

 

On 5/29/2022 at 11:34 AM, Revan335 said:

I pasted/write the UD Path manually. I have the same Issue. Only Local/Array Path are showed.

 

Just manually add the share folder to your external disk. /mnt/disks/external_ssd (in my case!)

Link to comment
Posted (edited)

Anyone else having this issue where this plugin is causing some error at startup ? this erros is seen at Unraid startup. it goes away when the system is started/rebooted without the vm backup plugin installed. 

 


error: failed to connect to the hypervisor 
error: Operation not supported: Cannot use direct socket mode if no URI is set

 

as i understand, it's because the VM service isn't started when the plugin is being installed during boot. is there a setting in the plugin that can be set so the plugin only kicks off after the VM service is started or it wont start at all if the vm/array auto start is disabled. 

 

Note: i am running unraid 6.10.2

Edited by Domotics
Link to comment
On 5/25/2022 at 3:45 PM, PeteAsking said:

To convert a raw disk you just use the qemu-img command on a linux box eg:

 

qemu-img convert -p -c -O qcow2 originaldisk.qcow2 newdisk.qcow2

 

Resulting newdisk.qcow2 is in qcow format.

 

You can check with qemu-img info newdisk.qcow2

To build on this, you can also convert to and from RAW, VMDK/VHD/VHDX (HyperV),  and VDI (Oracle Virtual Box). 

 

Windows has a version of qemu-img as well.  FYI, you may run into issues with boot partitions and other boot related items, these can be resolved obviously. 

 

LOTS of qemu info at this link-->  qemu-img commands and options

 

qemu-img for Windows here

Spoiler

 

 

Link to comment

Hi again M8s, 

I've the backup files but with qcow2... And I can't restore with the script... It sais that don't exist... And now I don't any other backup... All my stuff are in that qcow2 image. 

I already convert it to img but no results 😭 any ideias

Thanks 

Link to comment
On 6/6/2022 at 6:08 PM, Luis Belo said:

Hi again M8s, 

I've the backup files but with qcow2... And I can't restore with the script... It sais that don't exist... And now I don't any other backup... All my stuff are in that qcow2 image. 

I already convert it to img but no results 😭 any ideias

Thanks 

Dont manipulate the qcow image you will damage it if you dont understand what you are doing.


Unraid has no issues opening a qcow image it is the default image type.


Simply copy the qcow image to your unraid box and create a new vm with manual disk and browse to the disk location that you copied it to. Simple. Converting a qcow to img is not a statement that has any meaning. That is just the extension of the file. An .img can already be a qcow.

Link to comment
1 hour ago, PeteAsking said:

Dont manipulate the qcow image you will damage it if you dont understand what you are doing.


Unraid has no issues opening a qcow image it is the default image type.


Simply copy the qcow image to your unraid box and create a new vm with manual disk and browse to the disk location that you copied it to. Simple. Converting a qcow to img is not a statement that has any meaning. That is just the extension of the file. An .img can already be a qcow.

Thanks for the reply. 

I have also tried that and didn't work. 

Just copy the qcow2 image to a new/fresh VM and always show me the uefi boot screen. 

Note:  with the same exact hardware configuration. 

Link to comment
On 6/8/2022 at 1:14 AM, Luis Belo said:

Thanks for the reply. 

I have also tried that and didn't work. 

Just copy the qcow2 image to a new/fresh VM and always show me the uefi boot screen. 

Note:  with the same exact hardware configuration. 

I dont see how that is possible. Are you sure you chose the same type of bios eg: if you chose i440fx and seabios before, then creating a new vm with OVMF and Q35 will render it unbootable. You cant change those once set.

Link to comment

A really great plugin to backup VM. Used with restore script and all is working perfectly! That's great!


I have just one small problem.


In Manage Configs section, i can add a new config but i cannot copy/rename/delete because no configs are showed (see attached image). I think there is something wrong with this function

$("#select_configs_div").fileTree()

Inside file

/usr/local/emhttp/plugins/vmbackup/include/javascript/vmbackup.js

Of course i could be wrong about that function and that file.
Tested with Chrome, Firefox and Edge. No select appears and so i cannot copy/rename/delete.
Any suggestions?

 

Thank you all!

1.png

2.png

Edited by paffeke
correct some typos
Link to comment
  • 2 weeks later...

Hi, has anyone been able to make a config with this plugin and the latest Unraid? The Apply button only greys out when i leave number of backups to keep and days retention to 0. Any other value and it has a red line underneath the input field and apply button does nothing.

 

I've tried to uninstall and reinstall but now on reinstall its not showing in settings either :(

Link to comment
Posted (edited)

The plugin works ok for me if I disable snapshots. They used to work with snapshots as well until "recently"? I'm not sure what happened.

 

2022-07-03 02:00:01 information: able to perform snapshot for disk /mnt/user/domains/vmname/vdisk1.img on vmname. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-07-03 02:00:01 information: qemu agent found. enabling quiesce on snapshot.
2022-07-03 02:00:01 failure: snapshot command failed on vdisk1.snap for vmname.
2022-07-03 02:00:13 failure: snapshot_fallback is 0. skipping backup for vmname to prevent data loss. no cleanup will be performed for this vm.
2022-07-03 02:00:17 information: finished attempt to backup vmname to /mnt/disks/ssd1tb/vm_backups.

 

Not sure what happened.

 

I forgot to add the error from the actual logs. I'll attach them here since they're kinda long.

vmerror.txt

 

 

Edited by Chunks
added logs
Link to comment
  • 2 weeks later...
On 7/3/2022 at 7:41 AM, Chunks said:

The plugin works ok for me if I disable snapshots. They used to work with snapshots as well until "recently"? I'm not sure what happened.

 

2022-07-03 02:00:01 information: able to perform snapshot for disk /mnt/user/domains/vmname/vdisk1.img on vmname. use_snapshots is 1. vm_state is running. vdisk_type is raw
2022-07-03 02:00:01 information: qemu agent found. enabling quiesce on snapshot.
2022-07-03 02:00:01 failure: snapshot command failed on vdisk1.snap for vmname.
2022-07-03 02:00:13 failure: snapshot_fallback is 0. skipping backup for vmname to prevent data loss. no cleanup will be performed for this vm.
2022-07-03 02:00:17 information: finished attempt to backup vmname to /mnt/disks/ssd1tb/vm_backups.

 

Not sure what happened.

 

I forgot to add the error from the actual logs. I'll attach them here since they're kinda long.

vmerror.txt 6.84 kB · 0 downloads

 

 

It seems like this is the issue, 

error: unsupported configuration: external snapshot file for disk hdc already exists and is not a block device: /mnt/user/domains/vmname/vdisk1.snap

 

I'm not sure what exactly is causing this, but I wonder if you have tried to update VirtIO drivers? Also- how many backups do you have allowed for the VM? If it is only 1 backup- can you try 2? 

Link to comment
  • 2 weeks later...

VM Backup often running v0.2.3 - 2021.03.11

Seems to me like the VM Backup is running multiple times in the backup queue. I think this started before upgrading to UR 6.10.3.

Before it took about 45-60 minutes zu backup the few VMs, now it is doing so multiple times taking, maybe 4,5 hours.

 

now I remember: before updating unraid I tried to initiate a manual backup and that didn't start, then, over a couple of minutes I hit the backup button multiple times and that seems to have gone into the scheduled behaviour.

 

where might I see where those (redundand?) backup tasks are stored, since this behaviour endures an unraid restart.

 

p.s. as last user postet: Great Job - I've been using your script for a while and it save me a lot of time. Thanks for that!
 

unraid backup3.PNG

unraid backup2.PNG

unraid backup.PNG

Edited by RinxKninks
adding images
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.