Search results

Understood. I added a feature request. Thanks for your help! :)

I tried to copy the part of the existing pbs-backup datastore and modify it. Following the requested output: root@pbs:~# cat -A /etc/proxmox-backup/datastore.cfg datastore: pbs-backup$ ^Icomment $ ^Inotify gc=error,sync=error,verify=error$ ^Inotify-user root@pam$ ^Ipath /pbs-backup$ $...

Hi and thanks for your reply. I tried and edited said datastore.cfg datastore: pbs-backup comment notify gc=error,sync=error,verify=error notify-user root@pam path /pbs-backup datastore: sandisk comment notify gc=error,sync=error,verify=error...

I have configured and used a local datastore for sync to a removable disk. Then removed the datastore and unattached the disk. I had removed the datastore, as else if just unplugging the usb disk, I had an error in dashboard usage because of the missing datastore. Now a week later I want to...

I understand. So thank you for your information. Is there any way to track the status on @Stoiko Ivanov 's work? I would like to follow the status in order to know when there is any progress, maybe even help testing if I can assist on this.

As Fabian Grünbichler stated: it seems like this issue was lost when upstream moved their github repository. AFAIK there hasn't been any progress on this front yet. Thus I would like to kindly ask if this issue could be recreated? Else there won't probably be any progress upstream, right?. It...

For the purpose of testing created two groups prefer_node1 and prefer_node2 and assigned the VMs to those groups. I have a not booted stopped VM on node 2 but I assigned it to prefer_node1 group. I have configured max. restart 0, max. relocate 1 and request state: stopped. My expectation would...

Great. Thanks for your confirmation. I will maybe check this out, or perhaps we even leave it as is, because I am not sure yet if it is desirable that the VMs migrate back automatically. The failed node may need some attention or fix after all, before putting it back on service. But good to...

The failover works fine, meaning the VMs are started on the remaining node as expected when one node is shutdown. One question I still have though. When the failed node comes back, is it normal / by design that I have to migrate the VMs back manually, or should they get migrated back...

How do you deal with the problem that as long as the removable media is disconnected you get an error on the dashboard / datastore usage section? Do you remove the datastore before unplugging the external disk?

A button to deactivate a datapool or zfs dataset should do? At the moment I do the following from shell before removing the external usb disk from ProxMoxBackupServer: proxmox-backup-manager datastore remove Datastore-Name.

It's ok for me, I don't have a good idea on how one could do this better, maybe just prepend "UTC" on the filename so it's clear that this is not localtime. Thanks for your info.

Thats possible. Can the filename date be modified somewhere so the time corresponds to the actual time? ProxMox VE and PBS both show correct time when issuing date in console.

While the backup is executed on the time it was planed, ex. 12.10 in the filename of the corresponding "vzdump" file, it is 11.10. Is this a bug?

ok, thanks for confirmation. I will check if I can backup the opnsense and a second vm providing vpn connection to local ressources by installing pbs on the remote site and creating a local pbs instance on the remote site. If that works without interrupting services, I then could sync to local...

Are there plans to add some menu for local removable storages? I am asking as the workaround works fine but it's a pitty that while the stick is unplugged on the dashboard you see error because of unavailable datastore.

I tested that and it technically works, but I would like to know if I could run into problems with this. I am wondering as the same disk is running, while the dummy vm is backed up shutdown. Is my understanding correct that the disk is shortly freezed thus the backup should be consistent and not...

I do :) Could it work if I create a dummy vm, and modify the dummy vm.conf to contain the opnsense vm disk and backup the dummy vm to pbs or is this a bad idea?

I tried to backup our opnsense vm that is on a remote proxmox. Unfortunatelly it does not work. Is this not possible due to missing qemu-guest agent? So is qemu-guest-agent mandatory? There is an error happening during freeze at the beginning of the backup job.

Thanks for clarification - that should work then. The storages are named identically and disks are regularely replicated. Yes, two nodes with a QDevice configured on our pbs. Yeah, or maybe even do a livetest with a shutdown of a node or just unplugging it from the storage network, once our...