luca2

Hi, thx for pointing this out. It does not apply to me since I do not use cache for my shares. I only use cache for storing the vdisks.

Since it does not include system/appdata/domains shares I choosed user0. I don't want those system shares to be shared to the vm. I access them only with krusader's plugin. Anything I may be missing?

ok, after some research I found some info and this is what I did to solve it... edit vm xml and add in the GUI**: "unraid share"=/mnt/user0/movies/ "unraid mount tag"=movies then in the vm do this (or any folder you want): mkdir /home/ws1/movies then: sudo -s nano /etc/fstab and add at the end this line: movies /home/ws1/movies 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 Reboot and that's it. **the edit of the xml does this: <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user0/movies/'/> <target dir='movies'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </filesystem> I still have a question: if I want to add a second mapped unraid share ... can I just follow the same procedure and add this to the xml? <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user0/series/'/> <target dir='series'/> <alias name='fs0'/> </filesystem>

Hi, how can I find the version of openvpn-as running in this dockker?

In windows/linux I executed the script from the browser connection to Unraid, using the Andrew Zawadzki´s "scripts plugin". I checked the ram usage with window´s task manager and linux´s equivalent. Now I did run a backup again, running the script as I did before, but now I did select the option "run in background" and added 2 more cores to unraid. I checked the cpu and ram usage with the commands you provided. As you posted the cpu usage is around 12%-18% and ram usage is 0.2%. The backup did run without any problems. Great! I gues if I start the script using Andrew Zawadzki´s "scripts plugin" but do not select "run in background" it eats up all my ram. Not Unraid´s ram, but the ram of the pc I use to connect via browser to Unraid´s GUI. This is what I get when the script finishes: Number of files: 57,852 (reg: 52,321, dir: 5,531) Number of created files: 57,852 (reg: 52,321, dir: 5,531) Number of deleted files: 0 Number of regular files transferred: 52,321 Total file size: 169,921,241,556 bytes Total transferred file size: 169,921,241,556 bytes Literal data: 169,921,241,556 bytes Matched data: 0 bytes File list size: 2,883,435 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 169,966,133,523 Total bytes received: 1,038,847 sent 169,966,133,523 bytes received 1,038,847 bytes 72,188,223.56 bytes/sec total size is 169,921,241,556 speedup is 1.00 Try #1 to make backup visible Preserve daily backup: 20201117_114137 Script Finished Nov 17, 2020 12:20.52 Full logs for this script are available at /tmp/user.scripts/tmpScripts/backuptoextHDD_data/log.txt I don´t know if the output is what I should get. I selected "notification=1" in the script. But you can see I get in the log "Try #1 to make backup visible"...what does it mean? Anyway, good news everything went smooth and with no errors. Thx for your work.

Hi, How should I do that to obtain best performance. I want to play a movie located in one of my shares from my debian vm. Rgds

I could spend some time testing this script. I tried to backup 383GB and still got some trouble. Regarding the interrupted backup process I observed it is consuming excessive ram. I tried with a windows 10 x64 laptop with 4GB ram only. The script stops after couple of minutes. Now I tried with a linux vm running 6 cores and 9gb ram + 9gb swap space. I was monitoring ram consumption and it starts eating up ram until it consumes all physical ram and also some swap space. Suddenly it comes to a point where it finds a balance consuming only 15% ram and 19% swap space. Anyway after some time running (340gb backup of 380gb) my vm freezes for a a moment and the script ends without copying the 380gb. I looked at the log file in the new folder created by this script and there is no single error reported. Maybe there is a different log we could look at? Also, I can confirm I cannot edit any share while the script is running. Let me know what logs you need to look at it.

Hi, I tried to backup one share (inicial backup). It did not finish. I run the script but it was not running in the background, so I guess due to this it stopped. Maybe I touched something when I went back to the scripts page. Will try tomorrow again. When it ends does the pop up inform that the backup finished? Also, I noticed when it was running I could not change any share permission(read/write) of the other shares. Is this normal? Rgds Sent from my NX569J using Tapatalk

Hi, I finally started testing today (did pick up a small share). I still must do some daily backups but it is very easy. Thx! Besides shares backups, I have a particular scenario where I placed some important shares (which are critical to me) in a disk (disk1) which belongs to the array. I am thinking about doing a backup of the full disk instead of several backups of the shares. Do you think it would be posible? Now I get this when I backup a share (isos) using your script. It is the first full backup. /mnt/disks/UD_hdd2/backuptoexternalHDD/Shares/isos/20201023_195306 Maybe in my specific scenario I am looking for this: /mnt/disks/UD_hdd2/backuptoexternalHDD/disk1/20201023_195306 Since I am not into coding I just want to make sure it is feasible. If yes pls let me know what I should look into and I will try to modify the script to adapt it. Rgds.

Thx for your detailed explanation. Will try it hopefully this weekend. Sent from my NX569J using Tapatalk

thx mate!

Hi, new to linux .. excuse my ignorance ... -If I delete the main backup file (the 1st one created=full backup) > I lost everything, right? -If I delete any of the "incremental" backups (the ones starting after the 1st backup) > I should at least have the latest backup file + the 1st one to recover my latest backup status? Just want to make sure what this means. Let´s assume I created a 1st full backup in 10th october 2019. Then I have not been running my server everyday, so I have not daily incremental backups (it is posible that some months the server is not powered on too). Assume on the 1st january 2021 my server is not working. The rule means it will delete all daily and monthly backups (incremental) created during 2020? Rgds

Yes. The script contains: logger Pictures share -t$PROG_NAME logger Unmounting PicturesBackup -t$PROG_NAME logger Pictures Backup drive can be removed -t$PROG_NAME logger Pictures Backup Drive Not Mounted -t$PROG_NAME Excuse my ignorance, but those "Pictures" should not be changed?

Hi, I discovered the script (at the opening post) to make a copy of several shares to an external hdd. In my case I would like to copy several shares (actually all of them on only 1 disk [disk1] ) to an external hdd mounted using UD in /mnt/disks/UD_hdd2. In my scenario what should I change in the script to rsync "disk1" with the external drive? Apart from the latter anything else I should take into account? Rgds

Hi, I would appreciate if you owners of a similar setup can tell me you experiences with unraid so far. I am interested in the following: 1) best iommu grouping out of the box for pass through...pls recommend which motherboard would you buy now 2) any problems still with linux kernel lower than 5, I am thinking of still sticking to latest unraid stable version 3) motherboard that accepts pciexpress bifurcation (not only for raid but also for running 2xgpus@x8_4.0), so that I can put 2 cards in 1 slot 4) any other issues I must be aware of (cpu-core tuning, ....) I considering making a move to invest in such a platform to run 3 vm's with fully dedicated gpu's + 1/2 more to run via VNC. Also some dockers. And also running some nvme raid to be used as disk pool for the vm's. X570 offers only limited pciexpress lanes I cannot use it for this setup. I doubt x670 will soon come out and even then will add more lines. Since it is a big investment for me I would like to make sure in a certain degree that it will work before I pull the trigger. Hope to hear your thoughts. Rgds Sent from my NX569J using Tapatalk

Hi Binhex, thx a lot for this enhancements! I just updated to the latest version. When I try to enter the new variables, I only have this options (but the last 34 are missing: display, required, passwork mask): If I remove the template and re-add it from CA do I need to make a manual backup before? I guess this will solve the previous issue I mentioned. This is my actual setup:

Great answer! This is exactly what I was looking for. Thx mate. Sent from my NX569J using Tapatalk

If I press F3 this is what is opened (no pic). But if you go to VIEW>and select SHOW PREVIEWS the same .jpeg file is displayed in krusader as I wish (just too small). So I think Krusader already has the viewer embedded, just need to find out how to associate a file to it and which viewer is the one krusader is using.

Hi, when I try to click on a .jpg I cannot visualize it. This dialog appears but I cannot assign any programm since I do not know what either krusader may have built-in or what I could use from unraid. Let me know pls how I can solve this.

+1 Sent from my NX569J using Tapatalk

Forgot to ask how to decompress this file .zst?

ok thx. I just re-run the script and now I get this ... definitly a space saver!

Hi, where do I find this option your pic shows? I am running just the script (JTOK) and don´t have this option neihter remember to see it somewhere else.

Hi, I wish someone confirms to me if everything is fine with my backup. This is my config: 2020-07-24 08:41:41 information: send_notifications is 1. notifications will be sent. 2020-07-24 08:41:41 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled. 2020-07-24 08:41:42 information: keep_log_file is 1. log files will be kept. 2020-07-24 08:41:42 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep. 2020-07-24 08:41:42 information: enable_vm_log_file is 0. vm specific logs will not be created. 2020-07-24 08:41:42 information: backup_all_vms is 0. only vms listed in vms_to_backup will be backed up. 2020-07-24 08:41:42 information: use_snapshots is 0. vms will not be backed up using snapshots. 2020-07-24 08:41:42 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected. 2020-07-24 08:41:42 information: set_vm_to_original_state is 1. vms will be set to their original state after backup. 2020-07-24 08:41:42 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. 2020-07-24 08:41:42 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. 2020-07-24 08:41:42 information: inline_zstd_compress is 1. vdisk images will be inline compressed but will not be compared afterwards or post compressed. 2020-07-24 08:41:42 information: zstd_level is 3. 2020-07-24 08:41:42 information: zstd_threads is 2. 2020-07-24 08:41:42 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip. 2020-07-24 08:41:42 information: snapshot_fallback is 0. snapshots will fallback to standard backups. 2020-07-24 08:41:42 information: pause_vms is 0. vms will be shutdown for standard backups. 2020-07-24 08:41:42 information: enable_reconstruct_write is 0. reconstruct write will not be enabled by this script. 2020-07-24 08:41:42 information: backup_xml is 1. vms will have their xml configurations backed up. 2020-07-24 08:41:42 information: backup_nvram is 1. vms will have their nvram backed up. 2020-07-24 08:41:42 information: backup_vdisks is 1. vms will have their vdisks backed up. 2020-07-24 08:41:42 information: start_vm_after_backup is 0. vms will not be started following successful backup. 2020-07-24 08:41:42 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup. 2020-07-24 08:41:42 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups. 2020-07-24 08:41:42 information: rsync_only is 0. cp will be used when applicable. 2020-07-24 08:41:42 information: actually_copy_files is 1. files will be copied. 2020-07-24 08:41:42 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks. 2020-07-24 08:41:42 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks. 2020-07-24 08:41:42 information: keep_error_log_file is 1. error log files will be kept. 2020-07-24 08:41:42 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep. And this is the attempt to backup one of the vm´s: 2020-07-24 08:41:42 information: c3po can be found on the system. attempting backup. 2020-07-24 08:41:42 information: creating local c3po.xml to work with during backup. 2020-07-24 08:41:42 information: /mnt/user/backup/unraid/vm/c3po exists. continuing. 2020-07-24 08:41:42 information: copy of backup of /mnt/user/backup/unraid/vm/c3po/20200422_1928_vdisk1.img vdisk to /mnt/user/backup/unraid/vm/c3po/20200724_0841_20200422_1928_vdisk1.img starting. 2020-07-24 08:51:28 information: copy of /mnt/user/backup/unraid/vm/c3po/20200422_1928_vdisk1.img to /mnt/user/backup/unraid/vm/c3po/20200724_0841_20200422_1928_vdisk1.img complete. 2020-07-24 08:51:29 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2020-07-24 08:51:29 information: c3po is shut off. vm desired state is shut off. can_backup_vm set to y. 2020-07-24 08:51:29 information: actually_copy_files is 1. 2020-07-24 08:51:29 information: can_backup_vm flag is y. starting backup of c3po configuration, nvram, and vdisk(s). 2020-07-24 08:51:29 information: copy of c3po.xml to /mnt/user/backup/unraid/vm/c3po/20200724_0841_c3po.xml complete. 2020-07-24 08:51:29 information: c3po does not appear to have an nvram file. skipping. 2020-07-24 08:54:47 information: copy of /mnt/cache/domains/c3po/20200422_1928_vdisk1.img to /mnt/user/backup/unraid/vm/c3po/20200724_0841_20200422_1928_vdisk1.img.zst complete. 2020-07-24 08:54:47 information: backup of /mnt/cache/domains/c3po/20200422_1928_vdisk1.img vdisk to /mnt/user/backup/unraid/vm/c3po/20200724_0841_20200422_1928_vdisk1.img.zst complete. 2020-07-24 08:54:47 information: the extensions of the vdisks that were backed up are img. 2020-07-24 08:54:47 information: vm_state is shut off. vm_original_state is shut off. not starting c3po. 2020-07-24 08:54:47 information: backup of c3po to /mnt/user/backup/unraid/vm/c3po completed. 2020-07-24 08:54:47 information: number of days to keep backups set to indefinitely. 2020-07-24 08:54:47 information: number of backups to keep set to infinite. 2020-07-24 08:54:47 information: removing local c3po.xml. Now, I get this output in my backup folder: It seems everything works as axpected although I have not tried to recover my vm using the backup file (vdisk) yet. What do you think? What is actually the .ZST file. I see the actual vdisk of the vm (20200724_0841_20200422_1928_vdisk1.img) and the associated ZST file, but do not understand their relationship and how should be the vm restored (if I need to)...will it work just copying over to the vm the 20200724_0841_20200422_1928_vdisk1.img?