fluisterben

My vdisk1.img in its VM config keeps getting renamed to /vdisk1.img.snap.img so at next boot it doesn't boot because the img name is wrong. Something in your script is not renaming correctly, or doesn't do it in the right order..

Are there size or other limits set to the RAM used by the OS? I.e. can we use "/" for anything and then have it be in RAM (assuming we copy it out at shutdown and put it back after startup, say) ?

How does one exclude files based on extension? I.e. *.log *.nfo *.tgz (the box in the config form doesn't say anything about what the syntax should be) In rsync I often use --min-size=1 --no-specials --no-devices --no-links is there a way to also exclude these from the file integrity checks?

# apt install qemu-guest-agent for debian/ubuntu etc.

Is there a reason you don't have this on github ? And a question; You do the delta copying, but with the timestamps in the resulting copies, how do you delta (which files are compared)? Either way, thanks for the script. Someone should just update the TS, the original script on github. to /mnt/user/backup/vm 2019-05-24 17:32 information: debz can be found on the system. attempting backup. 2019-05-24 17:32 information: /mnt/user/backup/vm/debz exists. continuing. 2019-05-24 17:32 information: debz is running. can_backup_vm set to y enable_backup_running_vm is set to 1 debz will not shutdown 2019-05-24 17:32 information: debz is running. can_backup_vm set to y 2019-05-24 17:32 action: actually_copy_files is 1. 2019-05-24 17:32 action: can_backup_vm flag is y. starting backup of debz configuration, nvram, and vdisk(s). sending incremental file list debz.xml sent 7,190 bytes received 35 bytes 14,450.00 bytes/sec total size is 7,096 speedup is 0.98 2019-05-24 17:32 information: backup of debz xml configuration to /mnt/user/backup/vm/debz/20190524_1732_debz.xml complete. debz.xml:5: namespace warning : xmlns: URI unraid is not absolute ^ sending incremental file list 721212e9-ebd2-5da3-4140-6a299e24765f_VARS-pure-efi.fd sent 131,241 bytes received 35 bytes 262,552.00 bytes/sec total size is 131,072 speedup is 1.00 2019-05-24 17:32 information: backup of debz nvram to /mnt/user/backup/vm/debz/20190524_1732_721212e9-ebd2-5da3-4140-6a299e24765f_VARS-pure-efi.fd complete. 2019-05-24 17:32 qemu-agent is installed and running, adding --quiesce parameter to make sure we have a consistent disk state before snapshot and backup. Allows the guest to flush its I/O into a stable state before the snapshot is created, which allows use of the snapshot without having to perform a fsck or losing partial database transactions. Domain snapshot snap.img created for debz '/mnt/cache/domains/debz/vdisk1.img.snap.img' -> '/mnt/user/backup/vm/debz/20190524_1732_vdisk1.img.snap.img' 2019-05-24 17:32 information: backup of vdisk1.img.snap.img vdisk to /mnt/user/backup/vm/debz/20190524_1732_vdisk1.img.snap.img complete. Block commit: [100 %] Successfully pivoted sleeping for 5 seconds after merging snapshot to vdisk before deleting snapshot Removing snapshot snap.img 2019-05-24 17:32 information: /mnt/user/isos/debian-9.8.0-amd64-netinst.iso of debz is an iso not a vdisk. skipping. 2019-05-24 17:32 action: vm_original_state is running. starting debz. debz is running and enable_backup_running_vm = 1 2019-05-24 17:32 information: backup of debz to /mnt/user/backup/vm/debz completed. 2019-05-24 17:32 information: cleaning out backups older than 8 days in location ONLY if newer files exist in /mnt/user/backup/vm/debz/ 2019-05-24 17:32 information: cleaning out backups over 9 in location /mnt/user/backup/vm/debz/ find: '/mnt/user/backup/vm/debz/*.qcow2': No such file or directory find: '/mnt/user/backup/vm/debz/*.tar.gz': No such file or directory 2019-05-24 17:32 information: finished attempt to backup debz to /mnt/user/backup/vm. 2019-05-24 17:32 information: cleaning out logs over 1. 2019-05-24 17:32 information: removed '/mnt/user/backup/vm//20190524_1727_unraid-vmbackup.log' 2019-05-24 17:32 information: cleaning out error logs over 10. find: '/mnt/user/backup/vm//*unraid-vmbackup_error.log': No such file or directory 2019-05-24 17:32 Stop logging to log file.

I know quite wel how to write cron jobs, it's just completely unclear what to put in the textform on the User scripts page. Or what the scheduled times are as set in the dropdown.

The 'Schedule' exact times used by User scripts, where do I set and find them? Are they simply crontab tasks of the unraid slackware, or what? I would like 'Daily' to be Nightly at 5:45 CET. And yes, I see there's a 'corntab' option (it's actually spelled wrong there) but totally unclear what the syntax is.

Actually, what happens is that setting that mount changes the bus number in the XML of the VM, making your network fail. Change it back to what it was initially and your network will be back again. So, if you go to your VMs, click on the icon to Stop it, Edit it and upper right corner shows the XML view button. See here for an example:

OK, figured out after which change network fails, as soon as I add a mount (fill in under the Edit VM setup); Unraid Share: Unraid Mount tag: at next boot of the VM, network iface is down. After checking the XML, this is what it does; <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/nxt/'/> <target dir='/nxt/'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:57:cb:d9'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> note that it changed bus=0x01 into bus=0x03 for the network interface. Changing that back to 0x01 for the network interface fixed network, but the mount does not seem to work when I change that bus to 0x03, or that may not be the reason, don't know yet.

Tried that, still no network access. Seems to be something inside the Ubuntu guest that causes the network to fail. I've just recreated an entire VM with the exact same properties, but starting with a larger disk, same problem. I'll now create a new fresh VM, from scratch, and will check each step and see where it goes wrong. May be of interest to other users..

I have done nothing out of the ordinary with this VM, no xml editing, I don't even know where those xml files are located. Funny thing is: I tried expanding the disk size internally, but it needs network access to install the required apps for that to work. So yeah, catch 22 there. Also; Is there a VNC access tool that actually copy pastes from and into the terminal window? The Remote VNC included with Unraid does not do that. Really annoying. I tried the virt-manager docker in hopes to change network settings for the VM, installed it, but it doesn't connect to anything, doesn't prompt me to do anything, it's basically a tool for advanced users without proper docs. Must say I really expected more from Unraid and its VM Manager, or its plugins/apps.

I changed the disk-size in Unraid's UI of an Ubuntu mini sourced VM I've setup as a server for various things, and now the VM has no network whatsoever. What's up with that? If changing disk-size has this effect on a basic ubuntu VM, I would not qualify unraid as 'stable' or something to 'sell', to be honest (I'm 7 days into using the trial). Also, I noticed that its disksize is still not expanded, when I connect via VNC and check on this VM, it's still showing its old size. While the Unraid UI says it has 20GB, df -h shows me it only has 12GB still.

Why are you constantly assuming we all use VM's to run Windows instances? Please provide examples how to do the exact same for Linux VM's.