Kristijan

Members
  • Posts

    63
  • Joined

  • Last visited

Everything posted by Kristijan

  1. Yes. Tnx. I understand i must restart docker after change. Now I reboot server and its ok . Many tnx all.
  2. Yes. but again I can see 4GB cache. in /mnt/cache is folder appdata. inside is same data as appdata in user folder. can I delete this cache folder?
  3. Yes veeam container have mapping that. /mnt/cache/appdata/veeam/opt Can I chenge cache to user and restart docker? How to delete this cache? I cant find where is located. But why openvpn and play show cache, but in docker setting not set to cache. Here is example for plex settings.
  4. Here is diagnostic. tower-diagnostics-20230112-1227.zip Now I can see unraid registered 4GB cache drive. But I dont have cache drive.
  5. Hi, Today i noticed my appdata is orange trianle (some or all data not protected). I dont have cache drive, all files is on array. I have dual parity. Unraid version is latest stable 6.11.5 I noticed some docker is only on cache, some on cache and disk In options I can see appdata share cache is prefered. This is default setting and I never changed this. Why now some data not protected?
  6. Thank you very much for your help. Don't let this pressure you. It's nothing urgent, but I'd like to sort this out if possible. Now I setup job as you. Job Mode Type Server, Managed By Backup Server. But again error but different.
  7. I I have noticed in 3:40 something happens end unraid kill VM. How i can find what usage ram? Now htop on unraid and gui dont show same ram usage. Before 3:40 htop and gui show same usage. Here is usage 14.2GB RAM In GUI show 76%
  8. Ok. Thank you. What do you recommend for plex limit? now usege is 180mb. Is 500mb limit ok?
  9. But I dont have Extra parameters line. I must create or?
  10. My free memory is only 300mb. I use 16GB all other ram i cached. What is recommendation to limit docker? Can yout tell me how to limit docker? I never limit docker, i dont see this options. Tnx
  11. Yes I use plex docker. But I can see dont use a lot of memory. 186mb is used.
  12. Yes. I did so. Protected computer is docker. Backup server is veem server ip address This error I have
  13. Hi, I have unraid with few VMs and my problem is I often have out of memory and unraid killed VM random. System have 32GB ram and I have 3 VMs with 4GB ram and 2 VMs with 2GB ram. This is about 16GB ram. I used few docker, but memory usage is less then 1GB. In htop Remaining ram is cached, but I dont know why is out of memory when system have 15GB RAM cached. I used latest stable unraid release 6.11.5
  14. OK ,i will start new trade. VM is normally started, and then I start new unraid kill one vm and i can see in unraid log out of memory, but I have 32GB memory and starter few vm with 4 and 2 GB.
  15. I use only ip. Now I removed DNS name of docker. Yes I add user veeam-backup in credentials on veeam. Yes i can reach container and log in sucess via ssh. But when i try to access to map with log give me permisson denied. I try with sudo but map not open. But when I add docker in veeam all is ok same in your screenshot. But when i setup file level backup and add /mnt/user/appdata for test veem tell agent upgrade is needed and I give error os is not supported.
  16. Hi, Now I have this problem. Cached RAM is about 50% and when i turn on new VM other shutting down. Unraid dont free up cached space. This is log for VM which killed. How to fix this. I used latest stable unraid version 6.11.5 -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x4"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/001 Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x5","drive":"libvirt-3-format","id":"virtio-disk2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/en_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090817.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":0,"drive":"libvirt-2-format","id":"ide0-0-0","bootindex":2}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.160-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":1,"drive":"libvirt-1-format","id":"ide0-0-1"}' \ -netdev tap,fd=38,vhost=on,vhostfd=43,id=hostnet0 \ -device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:46:c6:b0","bus":"pci.0","addr":"0x3"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=36,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:1,websocket=5701,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x2"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x6"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/12 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2023-01-10T22:48:49.034467Z qemu-system-x86_64: terminating on signal 15 from pid 6937 (/usr/sbin/libvirtd) 2023-01-10 22:48:50.035+0000: shutting down, reason=destroyed 2023-01-11 09:23:29.045+0000: starting up libvirt version: 8.7.0, qemu version: 7.1.0, kernel: 5.19.17-Unraid, hostname: Tower LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-9-001 Windows 10' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-9-001 Windows 10/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-9-001 Windows 10/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-9-001 Windows 10/.config' \ /usr/local/sbin/qemu \ -name 'guest=001 Windows 10,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-9-001 Windows 10/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/c0a6f337-6367-466f-9268-f1e99af23c35_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-i440fx-3.0,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -accel kvm \ -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none \ -m 4096 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296}' \ -overcommit mem-lock=off \ -smp 4,sockets=1,dies=1,cores=4,threads=1 \ -uuid c0a6f337-6367-466f-9268-f1e99af23c35 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=39,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pci.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pci.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pci.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pci.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x4"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/001 Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x5","drive":"libvirt-3-format","id":"virtio-disk2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/en_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090817.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":0,"drive":"libvirt-2-format","id":"ide0-0-0","bootindex":2}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.160-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":1,"drive":"libvirt-1-format","id":"ide0-0-1"}' \ -netdev tap,fd=40,vhost=on,vhostfd=46,id=hostnet0 \ -device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:46:c6:b0","bus":"pci.0","addr":"0x3"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=38,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:2,websocket=5702,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x2"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x6"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/31 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2023-01-11 09:58:28.730+0000: shutting down, reason=crashed
  17. Yes I put your DNS name but I add docker with IP address. Files seems look ok. Yes container is in privileged mode and I can connect to SSH. Network is br0 I cant see log files. I give no such file or directory. Again I have error OS not supported and cant upgrade veem agent on container. I dont know where is problem everything looks like your screenshots.
  18. Veeam version Build 11.0.1.1261 P20220302 Community edition. I installed this version 2 days ago with default settings.
  19. Container update finished sucess with yum update, but veeam cant update agent again. Same error os is not supported and backup failed. Docker normally can see files on unraid.
  20. Tnx. I setup Veeam B&R and add docker to managed server in veeam? Now i setup backup job and give following error Veem tell docker upgrade is required and fail. What is wrong?
  21. Yes. Veeam is great. One more question. When setup Veeam B&R on windows machine I only add docker as backup target and thats is? Is needed adjust any on docker? Is possible to backup usb drive?
  22. Ok. Tnx. After install Veeam B&R on windowd machine I can add this client on veem server. Is needed any adjust on client (docker)? What i can backup with this client? How to backup VM in unraid? Normally veeam will install client on all VM? This docker I only ise for backup flash or? Many thanks.
  23. I only insalled container according to your screenshot. Do I need windows system with Veeam B&R? I thought I needed to install veeam in docker. Maybe I got it wrong, then what is the function of docker?