Search results

All is Okay. I was up late and could have been looking at the wrong pbs server.. we have 3. the datastore is at the pbs web page.

Hello after manually adding to datastore.cfg , the new datastore does not show up on pbs web page. I tried doing this: systemctl restart proxmox-backup.service , did not fix. Any suggestions to get the manually added datastore to the pbs web page?

so I'll try manually adding the storage to /etc/proxmox-backup/datastore.cfg . 1ST I am rsyncing the usb directory to regular storage ....

I am curious , how did all the backups get deleted?

yearly we rsync pbs backups to a large usb. For a court case I need to access emails from one of the usb's . I tried adding a new datastore using the directory . but got this error: () unable to create chunk store 'usb12' subdir "/media/usb12/pbs-backups/daily/.chunks" - unable to create...

it looks like the issue was caused by a hardware issue on one node. I unpinned older kernel from the other 4 nodes two weeks ago, and the issue did not occur.

Hi Chris, the node got disconnected to the cluster network. so there could be faulty hardware as the local write to nvme disk could be causing some network connect issue. I will try using a 6.8 kernel to another node. and keep 6.5 to the rest.

Hello we have a 5 node cluster. a couple of months ago we had this issue, to solve I pinned a 6.5 kernel. Last night I unpinned and booted the 5 nodes to use 6.8.4-2-pve. at 2AM shortly after a vzdump backup to this storage : dir: z-local-nvme path /nvme-ext4 content...

Dunuin: thanks for the help. Email notification is now working. I just had to put email addresses in at Configuration > Access Controls for each user. by default we have postfix working at all systems. The sync issue started when root's password was changed last November at the sync...

Hello I have two remote PBS servers which are used as re mote sync for our main pbs system. Those had been working rock solid for a few years. However I just checked both and sync jobs have been failing since 11/11/2023 . Questions: 1- is there a way of getting notified when a sync job...

Thank you for that data.

We backup a particular KVM to two different datastores. to one datastore the backup takes 10-11 minutes each time . to the other datastore the backup time is less then 20 seconds. backup to the slow data store has the following messages in log: INFO: scsi0: dirty-bitmap status...

we have an issue with one of our VM's and slow backup. we see this each time just on that vm during backup: INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared I am working on why that is , searched forum and see you have the same issue. I assume that bad...

Hello Where can I get information on what tags are and how to use? I tried to search tags on forum and did not see an answer. Also is there a way to search documentation for something like this? best regards, Rob Fantini

thank you for pointing that out..... I was dealing with this at 2AM and got it wrong ;-) qm unlock 125 worked..

Ok so these started again. I thought updates and reboots after I last posted had solved the issue.. This time backup to PBS worked, local vzdump failed . # stat /dev/rbd-pve File: /dev/rbd-pve Size: 60 Blocks: 0 IO Block: 4096 directory Device: 0,5 Inode: 2238...

here is the qm config for a vm that had the issue: # qm config 902 bootdisk: scsi0 cores: 1 ide2: none,media=cdrom memory: 1024 name: ldap-master2 net0: virtio=92:EC:4F:23:5C:37,bridge=vmbr3,tag=3 numa: 0 onboot: 1 ostype: l26 protection: 1 scsi0...

Hello we have the rcu issue . 5 nodes with all systems using CPU "type 80 x Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz (2 Sockets)" How do I set -pcid ?

I had the same issue . Thank you gabriel for the suggestion to turn off lastpass.... that fixed my issue.

after rebooting the node I could restore the PCT: recovering backed-up configuration from 'pbs-daily:backup/ct/604/2023-08-31T20:37:10Z' /dev/rbd0 Creating filesystem with 3670016 4k blocks and 917504 inodes Filesystem UUID: 4ff60784-0624-452e-abdf-b21ba0f165a5 Superblock backups stored on...