Search results

  1. E

    Some backups are not saved in the namespace

    That is the great mystery, I only migrated the VMs from the one node away and back. I did nothing with VMs on other nodes.
  2. E

    Some backups are not saved in the namespace

    More ups ... Some VMs of this node were backuped twice this night. For example vm/114: stored in root at 2022-07-18 23:00:12 (count 5) stored in ednt at 2022-07-19 00:09:13 (count 1) But as you can see in the first post, there is only one backup job where this VM is included.
  3. E

    Some backups are not saved in the namespace

    Hi, partly success. But ... still some VMs and all CTs are not stored in the namespace. All with count 5 are still wrong. Here is the status of vm/114 proxmox-support: pbs-dirty-bitmap: 1 pbs-dirty-bitmap-migration: 1 pbs-dirty-bitmap-savevm: 1...
  4. E

    Some backups are not saved in the namespace

    I did now an online migration with the VMs. They report now 1.31 as pbs-library. But what's with the CTs ? Do they also need a 'restart' ?
  5. E

    Some backups are not saved in the namespace

    ct/225 is a container. From vm/236: proxmox-support: pbs-dirty-bitmap: 1 pbs-dirty-bitmap-migration: 1 pbs-dirty-bitmap-savevm: 1 pbs-library-version: 1.2.0 (6e555bc73a7dcfb4d0b47355b958afd101ad27b5) pbs-masterkey: 1 query-bitmap-info: 1...
  6. E

    Some backups are not saved in the namespace

    proxmox-ve: 7.2-1 (running kernel: 5.11.22-5-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.35-3-pve: 5.15.35-6 pve-kernel-5.15.27-1-pve: 5.15.27-1...
  7. E

    Some backups are not saved in the namespace

    I already edited the first post. It is a cluster and all wrong stored machines are running on one PVE. But this PVE is also on the latest software release. 'Upgrade' shows no available packages and when I connect to the GUI on this PVE I get also 7.2-7 as version. What do you mean with...
  8. E

    Some backups are not saved in the namespace

    Hi, I just tried to store the backups in a namespace. Most VMs and CTs are now stored inside the namespace, but some machines are stored in root. They are all in the same backup job. PVE Storage: PVE Backup job: PBS datastore: All other machines are inside of the namespace. All...
  9. E

    Since 4 weeks it starts again with failing backups.

    Backup Server 2.2-3 latest version from pbs-no-subscription Client cluster 7.1-11 I can not update at the moment, because I can not transfer or shutdown some LXCs on the cluster. Clientside: () INFO: starting new backup job: vzdump 102 104 105 106 107 108 110 303 304 208 130 131 210 134 135...
  10. E

    Since 4 weeks it starts again with failing backups.

    Here is a shorter error message of an other VM: 2022-06-30T01:31:40+02:00: starting new backup on datastore 'backup-41': "vm/1135/2022-06-29T23:31:21Z" 2022-06-30T01:31:40+02:00: download 'index.json.blob' from previous backup. 2022-06-30T01:35:41+02:00: register chunks in...
  11. E

    Since 4 weeks it starts again with failing backups.

    Hi, for a long time I got always some failing backups from Prxmox clustr to the PBS. I also reported this long time ago. Then, 3 month ago, after somenew updates it worked like charm. Now, since arround 3 or 4 weeks, again after some updates, it starts to fail on many machines. Here is one...
  12. E

    After latest update some VMs had no network

    Hi, after the lates update (ceph) some machines had no network. Circumstances: Firewall enabled on network card level, but disabled firewall of VM and disabled firewall on node and cluster. After removing the firewall flag on the network card level it starts to work again. Then I was also...
  13. E

    Debian update with open-vswitch stopped networking

    As I have written: /etc/init.d/networking stop /etc/init.d/networking start was enough to activate the network again. No reboot was required. (In our case)
  14. E

    Debian update with open-vswitch stopped networking

    Mar 28 08:02:06 pm-ceph-167 chronyd[2556]: chronyd exiting Mar 28 08:02:06 pm-ceph-167 systemd[1]: Stopping chrony, an NTP client/server... Mar 28 08:02:06 pm-ceph-167 systemd[1]: chrony.service: Succeeded. Mar 28 08:02:06 pm-ceph-167 systemd[1]: Stopped chrony, an NTP client/server. Mar 28...
  15. E

    Debian update with open-vswitch stopped networking

    Hi, the pveversion: proxmox-ve: 7.1-1 (running kernel: 5.15.12-1-pve) pve-manager: 7.1-11 (running version: 7.1-11/8d529482) pve-kernel-5.15: 7.1-13 pve-kernel-helper: 7.1-13 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.27-1-pve: 5.15.27-1 pve-kernel-5.15.19-2-pve: 5.15.19-3 pve-kernel-5.15.12-1-pve...
  16. E

    Debian update with open-vswitch stopped networking

    Hi, this morning I installed the latest debian updates on our cluster. I do 4 servers at once. 3 of the first 4 were losing the network connection. All 3 of them uses OVS the 4th is using linux bridges, The last message on the proxmox console was always, that it is not possible to start...
  17. E

    corosync was not able to come back

    Hi, last friday we had, unfortunately, a loop in our network. Maybe for 60 to 120 seconds, then I pulled the connector which causes the loop. After this everything looks fine again, until ... someone wants to login to our proxmox cluster: it was not possible via web. Luckily it was possible via...
  18. E

    One server always failing the backup

    I posted the requested stuff, and ...
  19. E

    [SOLVED] Why zfs as datastore for pbs?

    We use HP servers. So we build a RAID on controller basis, use ext4 as fs and use it as directory. This results in much less RAM consumption and it is faster too. But we also use a remote PBS to sync this.
  20. E

    One server always failing the backup

    Hi, here we go: Backup log: INFO: Starting Backup of VM 1025701 (qemu) INFO: Backup started at 2021-12-07 01:25:23 INFO: status = running INFO: VM Name: ispconfig-10257 INFO: include disk 'virtio0' 'hdd-1:vm-1025701-disk-0' 100G INFO: include disk 'virtio1' 'hdd-1:vm-1025701-disk-1' 512G...