Search results

  1. vooze

    Problems with Veeam

    I actually just posted to Veeam support as well. Just posting here as well hoping more people have this problems and get some faster help, but will deninitly keep you updated :)
  2. vooze

    Problems with Veeam

    Hi! For about 10 days it was working fine, then today after importing about 8 VMs from VMware ESXI (supported Proxmox function) now Veeam can't index the Proxmox host no matter what I try. I get this message: Successfully validated the connection Successfully updated the server Failed to...
  3. vooze

    Veeam Backup and Recovery supports Proxmox as of 28 Aug 2024

    Ah, I see. So really it's only relevant for SQL servers?
  4. vooze

    Veeam Backup and Recovery supports Proxmox as of 28 Aug 2024

    I don't understand it says Veeam does not support application aware, I just tested and I can restore files, AD objects and Exchange mailboxes. Does not have a SQL to test with. So what is missing exactly?
  5. vooze

    proxmox RYZEN

    I'm running 5.0 with Ryzen 7 1700 on B350 (AsRock board) with no problems.
  6. vooze

    [SOLVED] Setup VLANs with OVS, need help

    Wow, do I feel stupid, I forgot to install openvswitch-switch. The thread on reddit did not mention that I needed a package, and I just found out on proxmox wiki. Everything works with the initial config. Hope this helps others! Thanks for lot for your help :D
  7. vooze

    [SOLVED] Setup VLANs with OVS, need help

    Thank for for your reply. I have already tried without bonds (just using one nic) and it did not make a difference. I can't really just tcpdump, since the host have no interfaces up and running, when trying to ping something, I simply get "no network connection" or something along those lines...
  8. vooze

    [SOLVED] Setup VLANs with OVS, need help

    Hi I'm trying to setup VLANs for my Proxmox 5.0 server. Looking at https://www.reddit.com/r/homelab/comments/5zt504/proxmox_vlans/ I have made the following /etc/network/interfaces: auto lo iface lo inet loopback auto enp6s0 iface enp6s0 inet manual auto enp5s0 iface enp5s0 inet manual...
  9. vooze

    Question about updates.

    If could also use the no-subscription repo, which will have a newer kernel as well.
  10. vooze

    Proxmox 5.0 no access to the web page

    Are you sure you are connecting to the web interface with https?
  11. vooze

    Planning Proxmox VE 5.1: Ceph Luminous, Kernel 4.13, latest ZFS, LXC 2.1

    oh.. are you using nouveau or nvidia-driver with ubuntu? It is also possible that ubuntu 16.04 uses a different nouveau version than debian 9 (proxmox)
  12. vooze

    Planning Proxmox VE 5.1: Ceph Luminous, Kernel 4.13, latest ZFS, LXC 2.1

    Yeah it makes sense the amd GPU will work, since nouveau was at fault here.
  13. vooze

    Planning Proxmox VE 5.1: Ceph Luminous, Kernel 4.13, latest ZFS, LXC 2.1

    I'm sorry to hear about that :( The only difference then is the 1030 vs 710, but since nouveau is blacklisted it should really not matter I think?
  14. vooze

    Planning Proxmox VE 5.1: Ceph Luminous, Kernel 4.13, latest ZFS, LXC 2.1

    Are you certain the nouveau driver is blacklisted correct? I have helped probably 5 people on this forum and it have solved it for them all.
  15. vooze

    howto fix poor Windows 2016 Server performance

    but intel optane only have a TBW of 185 TB with 32 GB version, which will go quite fast with a slog I think..
  16. vooze

    ZFS poor performance

    This is really a mood point if you can't do real jbod anyway.. You will destroy your data at some point with a hardware raid (raid0) ..
  17. vooze

    [SOLVED] Disable ZFS compression

    turning off compression is completely safe. I personally have it enabled for all my VMs/containers since they compress somthing like 1.5x (which is really good) for linux .iso's i just turn compression off. root@ryzen:~# zfs get compressratio NAME PROPERTY VALUE...
  18. vooze

    memory usage

    Install balloon driver in Windows.
  19. vooze

    Proxmox - AMD Ryzen 1700 - Nested

    To my understanding, this bug should only occur when compiling on all cores right?