Search results

  1. K

    Questions about encryption

    Thanks Fabian, but I don't understand the part how I can browse the backup on the node (stored on the Proxmox backup server). Can you explain this a littlebit more?
  2. K

    Questions about encryption

    Dear all, I made my backups encrypted with the option "Auto-generate a client encryption key, saved privately on cluster filesystem". But how can I browse this folder on the Proxmox backupserver? And if I want to restore this backup to another node (not the node where the backup came from) is...
  3. K

    Proxmox Backup Server (beta)

    Ok great! Is there any documentation about this? Would like to backup Centos7/8 servers to Proxmox backup.
  4. K

    Proxmox Backup Server (beta)

    It's a great product, I love it! Question: I can backup easily Proxmox containers and vm's, but what is this 'host' meant to do? I this to backup for example a centos8 installation not running in Proxmox? Would be great to backup external servers not running Proxmox. Thanks
  5. K

    No I did not, but they told me it's nothing to worry about and everything seems to run fine.

    No I did not, but they told me it's nothing to worry about and everything seems to run fine.
  6. K

    CT backups fails

    Any news on this?
  7. K

    CT backups fails

    What happens if you do a 'suspend' backup? In most of the cases this works for me, but this is not a good solution ofcourse (because the server will be offline for minutes).
  8. K

    CT backups fails

    Hi Oguz, Yes I did a shutdown on this container first before running fsck and I have this problem one more containers. Config: Ceph, Proxmox 6.2, containers running all Centos7, about 10 nodes with SSD. Do you need more info? Maybe its a coincidence but it looks like backups will fail when...
  9. K

    CT backups fails

    Hi There! Some Container backups always fail, I also did a fsck but that doesn't seem to work. Hereby the error: INFO: starting new backup job: vzdump 176 --compress zstd --mode snapshot --storage local --node node003 --remove 0 INFO: filesystem type on dumpdir is 'zfs' -using...
  10. K

    No network after restart Containers

    After rebooting alle nodes it worked again.
  11. K

    No network after restart Containers

    Good afternoon, Running xx nodes with Ceph and Proxmox 6.2. Kernel 5.3.18-3 Kernelcare Centos7 containers When I shutdown a container in Proxmox and start it again it will have no network connection. When I do a reboot in ssh with for example 'init 6' it works again. I have this problem after...
  12. K

    Move container to other datacenter

    Good afternoon, I want to move a container to another datacenter also running a Proxmox cluster (same versions), what is the best way to do this manually ? Is this possible ? I will change the IP ofcourse after the transfer. Thanks!
  13. K

    Can't add monitor

    And every night at 00:00 I get this error message, is this something to worry about? Mar 29 00:00:00 node002 ceph-mon[3003622]: 2020-03-29 00:00:00.129 7ff1636b6700 -1 Fail to open '/proc/2987489/cmdline' error = (2) No such file or directory Mar 29 00:00:00 node002 ceph-mon[3003622]...
  14. K

    Can't add monitor

    I recreated all 3 monitors threw the GUI, but they all have the same keyring, is that correct? And I still got this error on all 3 monitors, is this important? 2020-03-27 22:00:05.118 7ff15cea9700 -1 mon.node002@1(electing) e29 failed to get devid for : fallback method has serial ''but no...
  15. K

    Can't add monitor

    Ok but I found out when I run different monitor keyrings the monitors doesn't start. What is best to do now?
  16. K

    Can't add monitor

    Talking about this keyring: /var/lib/ceph/mon/ceph-node005/keyring When I use a unique keyring the monitor doesn't start. When I use all the same keyrings the monitor works. But I get this error: mon.node005@0(electing) e16 failed to get devid for : fallback method has serial ''but no model
  17. K

    Can't add monitor

    Every monitor needs a unique keyring ?
  18. K

    Can't add monitor

    I found out this node had a different keyring, I don't understand why but I copied this from another node... double checked all the files (some with wrong owner and group rights) and now it starts.