VM Backup Plugin


Recommended Posts

Tried to update the app today but failed. Tried uninstall and reinstall, same error: "plugin: run failed:".  Maybe I should not have updated when it was running ok? Can someone help me plz. Thx 

 

plugin: installing: vmbackup.plg Executing hook script: pre_plugin_checks plugin: downloading: vmbackup.plg ... done Executing hook script: pre_plugin_checks Removing package: xmlstarlet-1.6.1-x86_64-1_slonly Removing files: --> Deleting symlink /usr/bin/xmlstarlet WARNING: /usr/bin/xml changed after package installation. --> Deleting /usr/bin/xml WARNING: /usr/doc/xmlstarlet-1.6.1/AUTHORS changed after package installation. done +

============================================================================== | Installing new package /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz +============================================================================== Verifying package xmlstarlet-1.6.1-x86_64-1_slonly.txz. Installing package xmlstarlet-1.6.1-x86_64-1_slonly.txz: PACKAGE DESCRIPTION: # xmlstarlet (command line xml tool) # # XMLStarlet is a command line XML toolkit that can be used to # transform, query, validate, and edit XML documents and files using # a simple set of shell commands, which work similarly to 'grep', # 'sed', 'awk', 'tr', 'diff', or 'patch' on plain text files. # # Homepage https://sourceforge.net/projects/xmlstar/ # Executing install script for xmlstarlet-1.6.1-x86_64-1_slonly.txz. plugin: downloading: vmbackup-v0.2.5-2022.12.25.txz ... done +==============================================================================

 

| Skipping package vmbackup-v0.2.5-2022.12.25 (already installed) +==============================================================================

 

plugin: run failed:

/bin/bash Executing hook script: post_plugin_checks

Link to comment
  • 3 weeks later...

Good evening,

First off let me say thank you for creating this plugin. It has been one of the better plugins I've installed.

 

Unfortunately this plugin has caused some issues to where now a file for the VM, including the backup folders file structure, has been deleted.

 

Are you able to assist with this?

Link to comment
On 2/21/2023 at 7:39 PM, BTCB said:

Good evening,

First off let me say thank you for creating this plugin. It has been one of the better plugins I've installed.

 

Unfortunately this plugin has caused some issues to where now a file for the VM, including the backup folders file structure, has been deleted.

 

Are you able to assist with this?

If the data is missing there isn't anything that can be done. I would check your backup location in the plugin. Also, verify the backup settings in terms of how many backups to keep.   @everybody mentioned some good info as well. 

 

If you are backing up to a remote location there may be some other gremlins to chase down. 

Link to comment
  • 1 month later...
  • 4 weeks later...

Although I was not able to successfully use the script, I was able to follow the manual method successfully. In hindsight it was fairly simple. After restoring a VM for the first time, I noticed a few things:

  • In the future, choose VM names carefully. No spaces or weird shit. 
  • Remember previous rule.
  •  

I suspect the issues I had w/ the script were a result of my naming scheme for vms not being consistent or based in reality. I noticed my mistakes while reviewing the .xml file. VM name was "Windows_10" but I must have renamed it at some point in the past because within the XML i noticed "Windows 10". I also removed the date from the .fd file. The XML referenced an .fd file w/o a date in the name. 

 

From: 20230513_0305_8839995b-3d3b-115b-49bd-90e6e647bc45_VARS-pure-efi.fd

To: 8839995b-3d3b-115b-49bd-90e6e647bc45_VARS-pure-efi.fd

 

 

This community is pretty damn cool. Thanks for all yin's efforts. 

 

Unraid v6.11.5

Edited by darthkielbasa
Additional info for clarity
Link to comment
  • 2 weeks later...

So i am a bit confused about what is wrong with my config.  Any help is appreciated.

 

2023-06-05 13:42:44 Start logging to log file.
2023-06-05 13:42:44 information: send_notifications is 1. notifications will be sent.
2023-06-05 13:42:44 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled.
2023-06-05 13:42:44 information: keep_log_file is 1. log files will be kept.
2023-06-05 13:42:44 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep.
2023-06-05 13:42:44 information: enable_vm_log_file is 0. vm specific logs will not be created.
2023-06-05 13:42:44 information: backup_all_vms is 1. vms_to_backup will be ignored. all vms will be backed up.
2023-06-05 13:42:44 information: use_snapshots is 0. vms will not be backed up using snapshots.
2023-06-05 13:42:44 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected.
2023-06-05 13:42:44 information: set_vm_to_original_state is 1. vms will be set to their original state after backup.
2023-06-05 13:42:44 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.
2023-06-05 13:42:44 information: number_of_backups_to_keep is 0. an infinite number of backups will be kept. be sure to set number_of_days_to_keep_backups to keep backups storage usage down.
2023-06-05 13:42:44 information: inline_zstd_compress is 1. vdisk images will be inline compressed but will not be compared afterwards or post compressed.
2023-06-05 13:42:44 information: zstd_level is 3.
2023-06-05 13:42:44 information: zstd_threads is 2.
2023-06-05 13:42:44 information: include_extra_files is 0. extra files and folders will not be included in the backup.
2023-06-05 13:42:44 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip.
2023-06-05 13:42:44 information: snapshot_fallback is 0. snapshots will fallback to standard backups.
2023-06-05 13:42:44 information: pause_vms is 0. vms will be shutdown for standard backups.
2023-06-05 13:42:44 information: enable_reconstruct_write is 1. reconstruct write will be enabled during the backup.
2023-06-05 13:42:44 information: backup_xml is 1. vms will have their xml configurations backed up.
2023-06-05 13:42:44 information: backup_nvram is 1. vms will have their nvram backed up.
2023-06-05 13:42:44 information: backup_vdisks is 1. vms will have their vdisks backed up.
2023-06-05 13:42:44 information: start_vm_after_backup is 0. vms will not be started following successful backup.
2023-06-05 13:42:44 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup.
2023-06-05 13:42:44 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups.
2023-06-05 13:42:44 information: rsync_only is 0. cp will be used when applicable.
2023-06-05 13:42:44 information: actually_copy_files is 1. files will be copied.
2023-06-05 13:42:44 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks.
2023-06-05 13:42:44 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks.
2023-06-05 13:42:44 information: keep_error_log_file is 1. error log files will be kept.
2023-06-05 13:42:44 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep.
2023-06-05 13:42:44 information: started attempt to backup flashman, lasermanex, Numbermanexe, Stoneman, bass, virtualmin, Glyde, Macinabox BigSur to /mnt/user/VMBACKUPS
2023-06-05 13:42:44 information: Reconstruct write enabled.
2023-06-05 13:42:44 information: flashman can be found on the system. attempting backup.
2023-06-05 13:42:44 information: creating local flashman.xml to work with during backup.
2023-06-05 13:42:44 information: /mnt/user/VMBACKUPS/flashman does not exist. creating it.
2023-06-05 13:42:44 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on flashman was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 13:42:44 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 13:42:44 information: flashman is running. vm desired state is shut off.
2023-06-05 13:42:46 information: performing 20 30 second cycles waiting for flashman to shutdown cleanly.
2023-06-05 13:42:46 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 13:43:16 information: flashman is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 13:43:16 information: actually_copy_files is 1.
2023-06-05 13:43:16 information: can_backup_vm flag is y. starting backup of flashman configuration, nvram, and vdisk(s).
2023-06-05 13:43:16 information: copy of flashman.xml to /mnt/user/VMBACKUPS/flashman/20230605_1342_flashman.xml complete.
2023-06-05 13:43:16 information: copy of /etc/libvirt/qemu/nvram/0cdc1d3a-fd5f-018f-b281-4c709a5044bb_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/flashman/20230605_1342_0cdc1d3a-fd5f-018f-b281-4c709a5044bb_VARS-pure-efi.fd complete.
2023-06-05 13:43:16 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on flashman was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:00:59 information: copy of /mnt/user/domains/Windows Server 2016/vdisk1.img to /mnt/user/VMBACKUPS/flashman/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:00:59 information: backup of /mnt/user/domains/Windows Server 2016/vdisk1.img vdisk to /mnt/user/VMBACKUPS/flashman/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:00:59 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:00:59 information: vm_state is shut off. vm_original_state is running. starting flashman.
2023-06-05 14:01:05 information: backup of flashman to /mnt/user/VMBACKUPS/flashman completed.
2023-06-05 14:01:05 information: number of days to keep backups set to indefinitely.
2023-06-05 14:01:05 information: number of backups to keep set to infinite.
2023-06-05 14:01:05 information: removing local flashman.xml.
2023-06-05 14:01:05 information: lasermanex can be found on the system. attempting backup.
2023-06-05 14:01:05 information: creating local lasermanex.xml to work with during backup.
2023-06-05 14:01:05 information: /mnt/user/VMBACKUPS/lasermanex does not exist. creating it.
2023-06-05 14:01:05 information: extension for /mnt/user/isos/ubuntu-22.04-live-server-amd64.iso on lasermanex was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:01:05 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:01:05 information: lasermanex is running. vm desired state is shut off.
2023-06-05 14:01:05 information: performing 20 30 second cycles waiting for lasermanex to shutdown cleanly.
2023-06-05 14:01:05 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:01:35 information: lasermanex is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:01:35 information: actually_copy_files is 1.
2023-06-05 14:01:35 information: can_backup_vm flag is y. starting backup of lasermanex configuration, nvram, and vdisk(s).
2023-06-05 14:01:35 information: copy of lasermanex.xml to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_lasermanex.xml complete.
2023-06-05 14:01:35 information: copy of /etc/libvirt/qemu/nvram/0963b0b4-8fad-2ff7-461a-367f15356126_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_0963b0b4-8fad-2ff7-461a-367f15356126_VARS-pure-efi.fd complete.
2023-06-05 14:03:25 information: copy of /mnt/user/domains/lasermanex/vdisk1.img to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:03:25 information: backup of /mnt/user/domains/lasermanex/vdisk1.img vdisk to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:03:25 information: extension for /mnt/user/isos/ubuntu-22.04-live-server-amd64.iso on lasermanex was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:03:25 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:03:25 information: vm_state is shut off. vm_original_state is running. starting lasermanex.
2023-06-05 14:03:27 information: backup of lasermanex to /mnt/user/VMBACKUPS/lasermanex completed.
2023-06-05 14:03:27 information: number of days to keep backups set to indefinitely.
2023-06-05 14:03:27 information: number of backups to keep set to infinite.
2023-06-05 14:03:27 information: removing local lasermanex.xml.
2023-06-05 14:03:27 information: Numbermanexe can be found on the system. attempting backup.
2023-06-05 14:03:27 information: creating local Numbermanexe.xml to work with during backup.
2023-06-05 14:03:27 information: /mnt/user/VMBACKUPS/Numbermanexe does not exist. creating it.
2023-06-05 14:03:27 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Numbermanexe was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:03:27 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:03:27 information: Numbermanexe is running. vm desired state is shut off.
2023-06-05 14:03:31 information: performing 20 30 second cycles waiting for Numbermanexe to shutdown cleanly.
2023-06-05 14:03:31 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:04:01 information: Numbermanexe is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:04:01 information: actually_copy_files is 1.
2023-06-05 14:04:01 information: can_backup_vm flag is y. starting backup of Numbermanexe configuration, nvram, and vdisk(s).
2023-06-05 14:04:01 information: copy of Numbermanexe.xml to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_Numbermanexe.xml complete.
2023-06-05 14:04:01 information: copy of /etc/libvirt/qemu/nvram/6f69c2e7-1e84-8a67-e6e5-177b7fc67135_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_6f69c2e7-1e84-8a67-e6e5-177b7fc67135_VARS-pure-efi.fd complete.
2023-06-05 14:09:05 information: copy of /mnt/user/domains/Numbermanexe/vdisk1.img to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:09:05 information: backup of /mnt/user/domains/Numbermanexe/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:09:05 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Numbermanexe was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:09:05 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:09:05 information: vm_state is shut off. vm_original_state is running. starting Numbermanexe.
2023-06-05 14:09:08 information: backup of Numbermanexe to /mnt/user/VMBACKUPS/Numbermanexe completed.
2023-06-05 14:09:08 information: number of days to keep backups set to indefinitely.
2023-06-05 14:09:08 information: number of backups to keep set to infinite.
2023-06-05 14:09:08 information: removing local Numbermanexe.xml.
2023-06-05 14:09:08 information: Stoneman can be found on the system. attempting backup.
2023-06-05 14:09:09 information: creating local Stoneman.xml to work with during backup.
2023-06-05 14:09:09 information: /mnt/user/VMBACKUPS/Stoneman does not exist. creating it.
2023-06-05 14:09:09 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:09:09 information: Stoneman is running. vm desired state is shut off.
2023-06-05 14:09:09 information: performing 20 30 second cycles waiting for Stoneman to shutdown cleanly.
2023-06-05 14:09:09 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:09:39 information: Stoneman is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:09:39 information: actually_copy_files is 1.
2023-06-05 14:09:39 information: can_backup_vm flag is y. starting backup of Stoneman configuration, nvram, and vdisk(s).
2023-06-05 14:09:39 information: copy of Stoneman.xml to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_Stoneman.xml complete.
2023-06-05 14:09:39 information: copy of /etc/libvirt/qemu/nvram/067810a2-b75d-ef76-aa6e-cb4c419bb5d9_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_067810a2-b75d-ef76-aa6e-cb4c419bb5d9_VARS-pure-efi.fd complete.
2023-06-05 14:12:10 information: copy of /mnt/user/domains/Ubuntu/vdisk1.img to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:12:10 information: backup of /mnt/user/domains/Ubuntu/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:12:10 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:12:10 information: vm_state is shut off. vm_original_state is running. starting Stoneman.
2023-06-05 14:12:14 information: backup of Stoneman to /mnt/user/VMBACKUPS/Stoneman completed.
2023-06-05 14:12:14 information: number of days to keep backups set to indefinitely.
2023-06-05 14:12:14 information: number of backups to keep set to infinite.
2023-06-05 14:12:14 information: removing local Stoneman.xml.
2023-06-05 14:12:14 information: bass can be found on the system. attempting backup.
2023-06-05 14:12:14 information: creating local bass.xml to work with during backup.
2023-06-05 14:12:14 information: /mnt/user/VMBACKUPS/bass does not exist. creating it.
2023-06-05 14:12:14 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on bass was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:12:14 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:12:14 information: bass is running. vm desired state is shut off.
2023-06-05 14:12:15 information: performing 20 30 second cycles waiting for bass to shutdown cleanly.
2023-06-05 14:12:15 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:12:45 information: bass is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:12:45 information: actually_copy_files is 1.
2023-06-05 14:12:45 information: can_backup_vm flag is y. starting backup of bass configuration, nvram, and vdisk(s).
2023-06-05 14:12:45 information: copy of bass.xml to /mnt/user/VMBACKUPS/bass/20230605_1342_bass.xml complete.
2023-06-05 14:12:45 information: copy of /etc/libvirt/qemu/nvram/4a9d6e0c-922c-1b44-39fb-dbf629120504_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/bass/20230605_1342_4a9d6e0c-922c-1b44-39fb-dbf629120504_VARS-pure-efi.fd complete.
2023-06-05 14:12:45 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on bass was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:17:48 information: copy of /mnt/user/domains/bass/vdisk1.img to /mnt/user/VMBACKUPS/bass/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:17:48 information: backup of /mnt/user/domains/bass/vdisk1.img vdisk to /mnt/user/VMBACKUPS/bass/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:17:48 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:17:48 information: vm_state is shut off. vm_original_state is running. starting bass.
2023-06-05 14:17:53 information: backup of bass to /mnt/user/VMBACKUPS/bass completed.
2023-06-05 14:17:53 information: number of days to keep backups set to indefinitely.
2023-06-05 14:17:53 information: number of backups to keep set to infinite.
2023-06-05 14:17:53 information: removing local bass.xml.
2023-06-05 14:17:53 information: virtualmin can be found on the system. attempting backup.
2023-06-05 14:17:53 information: creating local virtualmin.xml to work with during backup.
2023-06-05 14:17:53 information: /mnt/user/VMBACKUPS/virtualmin does not exist. creating it.
2023-06-05 14:17:53 information: extension for /mnt/user/isos/ubuntu-20.04.4-live-server-amd64.iso on virtualmin was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:17:53 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:17:53 information: virtualmin is running. vm desired state is shut off.
2023-06-05 14:17:53 information: performing 20 30 second cycles waiting for virtualmin to shutdown cleanly.
2023-06-05 14:17:53 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:18:23 information: virtualmin is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:18:23 information: actually_copy_files is 1.
2023-06-05 14:18:23 information: can_backup_vm flag is y. starting backup of virtualmin configuration, nvram, and vdisk(s).
2023-06-05 14:18:23 information: copy of virtualmin.xml to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_virtualmin.xml complete.
2023-06-05 14:18:23 information: copy of /etc/libvirt/qemu/nvram/b1999575-4fe4-9b2d-fa8c-a02e2eb41c39_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_b1999575-4fe4-9b2d-fa8c-a02e2eb41c39_VARS-pure-efi.fd complete.
2023-06-05 14:20:32 information: copy of /mnt/user/domains/virtualmin/vdisk1.img to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:20:32 information: backup of /mnt/user/domains/virtualmin/vdisk1.img vdisk to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:20:32 information: extension for /mnt/user/isos/ubuntu-20.04.4-live-server-amd64.iso on virtualmin was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:20:32 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:20:32 information: vm_state is shut off. vm_original_state is running. starting virtualmin.
2023-06-05 14:20:38 information: backup of virtualmin to /mnt/user/VMBACKUPS/virtualmin completed.
2023-06-05 14:20:38 information: number of days to keep backups set to indefinitely.
2023-06-05 14:20:38 information: number of backups to keep set to infinite.
2023-06-05 14:20:38 information: removing local virtualmin.xml.
2023-06-05 14:20:38 information: Glyde can be found on the system. attempting backup.
2023-06-05 14:20:38 information: creating local Glyde.xml to work with during backup.
2023-06-05 14:20:38 information: /mnt/user/VMBACKUPS/Glyde does not exist. creating it.
2023-06-05 14:20:38 information: extension for /mnt/user/isos/en_windows_server_2019_updated_sept_2019_x64_dvd_199664ce.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:20:38 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:20:38 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:20:38 information: Glyde is running. vm desired state is shut off.
2023-06-05 14:20:39 information: performing 20 30 second cycles waiting for Glyde to shutdown cleanly.
2023-06-05 14:20:39 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state.
2023-06-05 14:21:09 information: Glyde is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:21:09 information: actually_copy_files is 1.
2023-06-05 14:21:09 information: can_backup_vm flag is y. starting backup of Glyde configuration, nvram, and vdisk(s).
2023-06-05 14:21:09 information: copy of Glyde.xml to /mnt/user/VMBACKUPS/Glyde/20230605_1342_Glyde.xml complete.
2023-06-05 14:21:09 information: copy of /etc/libvirt/qemu/nvram/8f67ba84-f35f-8371-568b-c57337895cdd_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Glyde/20230605_1342_8f67ba84-f35f-8371-568b-c57337895cdd_VARS-pure-efi.fd complete.
2023-06-05 14:21:09 information: extension for /mnt/user/isos/en_windows_server_2019_updated_sept_2019_x64_dvd_199664ce.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:21:09 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk.
2023-06-05 14:29:02 information: copy of /mnt/user/domains/Glyde/vdisk1.img to /mnt/user/VMBACKUPS/Glyde/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:29:02 information: backup of /mnt/user/domains/Glyde/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Glyde/20230605_1342_vdisk1.img.zst complete.
2023-06-05 14:29:02 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:29:02 information: vm_state is shut off. vm_original_state is running. starting Glyde.
2023-06-05 14:29:10 information: backup of Glyde to /mnt/user/VMBACKUPS/Glyde completed.
2023-06-05 14:29:10 information: number of days to keep backups set to indefinitely.
2023-06-05 14:29:10 information: number of backups to keep set to infinite.
2023-06-05 14:29:10 information: removing local Glyde.xml.
2023-06-05 14:29:10 information: Macinabox BigSur can be found on the system. attempting backup.
2023-06-05 14:29:10 information: creating local Macinabox BigSur.xml to work with during backup.
2023-06-05 14:29:10 information: /mnt/user/VMBACKUPS/Macinabox BigSur does not exist. creating it.
2023-06-05 14:29:10 information: skip_vm_shutdown is false. beginning vm shutdown procedure.
2023-06-05 14:29:10 information: Macinabox BigSur is shut off. vm desired state is shut off. can_backup_vm set to y.
2023-06-05 14:29:10 information: actually_copy_files is 1.
2023-06-05 14:29:10 information: can_backup_vm flag is y. starting backup of Macinabox BigSur configuration, nvram, and vdisk(s).
2023-06-05 14:29:10 information: copy of Macinabox BigSur.xml to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_Macinabox BigSur.xml complete.
2023-06-05 14:29:10 information: copy of /etc/libvirt/qemu/nvram/5d6a9774-95ee-4494-9c56-fe6054f4e6bf_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_5d6a9774-95ee-4494-9c56-fe6054f4e6bf_VARS-pure-efi.fd complete.
2023-06-05 14:29:10 failure: copy of /mnt/user/domains/Macinabox BigSur/BigSur-opencore.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-opencore.img.zst failed.
2023-06-05 14:29:10 information: backup of /mnt/user/domains/Macinabox BigSur/BigSur-opencore.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-opencore.img.zst complete.
2023-06-05 14:29:18 information: copy of /mnt/user/isos/BigSur-install.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-install.img.zst complete.
2023-06-05 14:29:18 information: backup of /mnt/user/isos/BigSur-install.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-install.img.zst complete.
2023-06-05 14:29:18 failure: copy of /mnt/user/domains/Macinabox BigSur/macos_disk.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_macos_disk.img.zst failed.
2023-06-05 14:29:18 information: backup of /mnt/user/domains/Macinabox BigSur/macos_disk.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_macos_disk.img.zst complete.
2023-06-05 14:29:18 information: the extensions of the vdisks that were backed up are img.
2023-06-05 14:29:18 information: vm_state is shut off. vm_original_state is shut off. not starting Macinabox BigSur.
2023-06-05 14:29:18 information: backup of Macinabox BigSur to /mnt/user/VMBACKUPS/Macinabox BigSur completed.
2023-06-05 14:29:18 information: number of days to keep backups set to indefinitely.
2023-06-05 14:29:18 information: number of backups to keep set to infinite.
2023-06-05 14:29:18 information: removing local Macinabox BigSur.xml.
2023-06-05 14:29:18 information: finished attempt to backup flashman, lasermanex, Numbermanexe, Stoneman, bass, virtualmin, Glyde, Macinabox BigSur to /mnt/user/VMBACKUPS.
2023-06-05 14:29:18 information: Reconstruct write disabled.
2023-06-05 14:29:18 information: cleaning out logs over 1.
2023-06-05 14:29:18 information: removed '/mnt/user/VMBACKUPS/logs/20230605_1341_unraid-vmbackup.log'.
2023-06-05 14:29:18 information: cleaning out error logs over 10.
2023-06-05 14:29:18 information: did not find any error log files to remove.
2023-06-05 14:29:18 warning: errors found. creating error log file.
2023-06-05 14:29:18 Stop logging to error log file.
 

 

Did this fail?  If so, what needs done to fix it?

Link to comment
  • 4 weeks later...

since updating to 6.12.1 from 6.11.5 when i make backups with the plugin it's creating hard links. i have 1 disk with 2 shares on it. my vms are on one share and the backup is backing them up to the other share so different share same disk. in 6.11.5 this didn't happen. i have exclusive shares turned on and both of these shares are considered exclusive shares. any idea how to get non hard links when using the plugin? i also make a user script to do my backups and it also made them hard links so i'm guessing it has something to do with the exclusive share thing but i'm not sure.

edit: i turn off hard links and exclusive shares in global share settings yet it's still happening. i'm confused.

Edited by jcofer555
update
Link to comment

Can anyone help edit @petchav's script to work with VM names that include spaces? I don't know bash scripting, but have been trying to figure it out for the last hour. The most positive change I made is to line 87, 

mkdir /mnt/user/domains/$VM_NAME

which I edited to 

mkdir "/mnt/user/domains/$VM_NAME"

 

That got me past creating incorrect directories. Now if my VM name is "Windows 11", then it will create the correct directory in the domains folder. However, it is still failing after that with `!!! Backup file not found !!!`

 

I've tried adding quotes at various places in lines 102, 112 & 120 but still the script fails at the same point. I've also tried adding quotes in various places to lines 89, 95, 110, 116 & 117 which are the lines that define `BACKUP_FILE`, but again, not making any progress. 

 

Figured someone that knows scripting and the correct syntax might be able to fix the script easily

Link to comment
11 minutes ago, ramair02 said:

Can anyone help edit @petchav's script to work with VM names that include spaces?

I don't know what that script is you are referring to, but all my VMs have spaces in the name, and just using this plugin, they back up just fine if I run them manually.  I've been having trouble with them failing to run on the schedule for a while now, but I think that's a separate issue. 

 

EDIT:  Oh, the restoration script!  I had forgotten all about that!  Hmm, that never got fixed?

Edited by Elmojo
Link to comment
4 minutes ago, Elmojo said:

I don't know what that script is you are referring to, but all my VMs have spaces in the name, and just using this plugin, they back up just fine if I run them manually.  I've been having trouble with them failing to run on the schedule for a while now, but I think that's a separate issue. 

 

EDIT:  Oh, the restoration script!  I had forgotten all about that!  Hmm, that never got fixed?

Yes, sorry for not being more clear! I am talking about the restoration script. It works great for VMs with no spaces in the name and I'm sure it can be fixed to work with VMs that do have spaces in their names, but it's not something I've been able to figure out with my limited knowledge.

Link to comment

Hi guys I'm the author of the restore backup script, I've just seen that I have several comments here and under the youtube video regarding VM names with spaces such as "windows 11". Unfortunately, I don't have a Unraid server at the moment, so I'm unable to run any tests.
 

I'm saying this from memory, but it seems to me that I've tested the case where the VM has a name with a space and it worked like this. 

When the script tells you "Enter name of virtual machine, like:”

You can try typing the VM name between "" like this: "Windows 11”.
 

So on the screen it should look like this:
Enter name of virtual machine, like: "Windows 11"
 

@ramair02 I hope this solves your problem. (use the original unmodified script)

If it doesn't work, you'll have to give me more information, an error message or something, because without a server at my disposal I really can't tell what's going on.

Edited by petchav
Link to comment

Thanks for the response @petchav! Unfortunately, typing the VM name within the CLI wrapped in quotes does not work.

 

Here's an example of the script not working with a VM name that has spaces.

image.thumb.png.0ce3496bfa792f48788de4562032dc82.png

 

Here it is working perfectly for a VM name that does not have any spaces.

image.thumb.png.be5286a78c0a0ab80be01e7c4ba4244d.png

 

And here it is failing when wrapping the VM name in quotes.

image.thumb.png.62a0412e3abbe36be1ac435f5e2d158c.png

 

The error message is simply `!!! Backup file not found !!!`. I think there is another line or two in the script where the path needs to be wrapped in quotes, but I can't figure out where.

Link to comment

@ramair02 Ok I understand the problem I'll look into making a fix, send me a private message with your email address or other social network. I'll send you a corrected version if it works for you then I'll publish it on the github (I have no other way to test that the fix works well ^^)

edit: ok you created a github issue, I hadn't seen, no need to PM me :)

Edited by petchav
  • Like 1
Link to comment
  • 5 weeks later...

Is someone stil using this plugin? it has been in beta quite a while.
It works great for making backups of my vms. 

But i have noticed the plugin is uninstalled after I reboot my server.

Does else have this problem and is there something I can do to fix it?

(I used community application plugin to install the vm backup plugin)

Link to comment

Lots of us still use it, and I believe it's still in semi-active development.

It indeed has some outstanding issues, but I've never heard of it getting uninstalled at reboot. 

That sounds like an issue on your server side.  Sorry I don't have any suggestions for a specific solution, but you might want to do some research in general on plugins getting uninstalled when you reboot. Maybe that's happened to other plugins?

Link to comment
20 minutes ago, CodeGlitcher said:

Is someone stil using this plugin? it has been in beta quite a while.
It works great for making backups of my vms. 

But i have noticed the plugin is uninstalled after I reboot my server.

Does else have this problem and is there something I can do to fix it?

(I used community application plugin to install the vm backup plugin)

Just to say I have the same problem. Any time I reboot my server, this plugin appears n a list of plugins with errors. I can delete the plugin, reinstall and it works perfectly till the next reboot. 

Link to comment
2 minutes ago, rorton said:

this plugin appears n a list of plugins with errors

Is that the same as what @CodeGlitcher is experiencing?  He said his is uninstalling itself.  That doesn't sound like the same thing to me.

What unRAID version are you both running?  We need more info to troubleshoot this.  If you're on 6.12.x, then that may be your problem right there.  Quite a few dockers and plugins aren't playing nice with 6.12 yet.  For example, I rely on ZeroTier for a connection to my files for work, but it's not quite reliable on 6.12 yet, so I can't upgrade.  I'm still on 6.11.5 until they get that sorted out.  You may be seeing something similar here.

Link to comment
10 minutes ago, Elmojo said:

Is that the same as what @CodeGlitcher is experiencing?  He said his is uninstalling itself.  That doesn't sound like the same thing to me.

What unRAID version are you both running?  We need more info to troubleshoot this.  If you're on 6.12.x, then that may be your problem right there.  Quite a few dockers and plugins aren't playing nice with 6.12 yet.  For example, I rely on ZeroTier for a connection to my files for work, but it's not quite reliable on 6.12 yet, so I can't upgrade.  I'm still on 6.11.5 until they get that sorted out.  You may be seeing something similar here.

sorry, I may have been assuming what @CodeGlitcher was experiencing was the same, is it is sort of uninstalling itself. 

 

My issue is that when I reboot, the box comes up and the plug-in sits in the Plugin file install errors (as image)

 

1871603520_Screenshot2023-08-03at21_09_30.thumb.png.38a04684e6ed1332b514379b1ca7ef8a.png

 

If I delete and then manually install again, it works. 

 

I have just rebooted to get the screenshot, if there are any logs I can provide from anywhere please let me know

 

Im using 6.12.3, and has been happening on all 6.12 versions

Link to comment

I do have this in my syslog too...

 

Aug  3 21:08:40 Unraid root: plugin: installing: vmbackup.plg
Aug  3 21:08:40 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz

 

if I then delete the plugin, and then reinstall, I see this in syslog...

 

Aug  3 21:24:51 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz
Aug  3 21:24:52 Unraid root: plugin: checking: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - MD5
Aug  3 21:24:52 Unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz
Aug  3 21:24:52 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/vmbackup-v0.2.5-2022.12.25.txz
Aug  3 21:24:52 Unraid root: plugin: checking: /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz - MD5
Aug  3 21:24:52 Unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz
Aug  3 21:24:55 Unraid root: plugin: vmbackup.plg installed

 

Link to comment

I know next to nothing about plugin development or installation, but it looks to me like, in the first case, it's trying to install the plugin, not run one that's already installed.   This leads me back to my original guess of there being something fishy going on with compatibility (or lack thereof) with v6.12.  I'd start there, and ask for general help (in another thread maybe?) where those who are familiar with how plugins act can perhaps help track down the specific issue.

All I know is that mine works fine(ish), and I'm on 6.11.5. Sorry.

  • Thanks 1
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.