Search results

Very excited with this feature : Snapshots for thick-provisioned LVM shared storage, e.g., for setups connected over iSCSI or Fibre Channel to a SAN.

We use PBS with proxmox backup client for the backup of openstack instance / physical hardware. We backup the entire disk , so it's very big in size, the speed for the backup is good ( thanks dedup / compression ), but the restore is horrible. I think the culprit is similar in the proxmox...

Can we hope that the proxmox-backup-client ( for restoring entire disk ) will have this improvement too in the future ?

Bonjour, We have a little issue. If a user blacklist a sender email, the score is 100. The next day, is the user receive another email, the mail is in quarantine , but not block. ( https://forum.proxmox.com/threads/blacklist-not-working.41418/ ). Is it possible to filter the daily report...

We have also encounter the same errors during the backup, with namespace en information ( token ) long, because it can't create the temporary file.

Its's works but a have a little inconvenient : pbs1 ns1 backup : A, B , C, D synchro every day on pbs2 with a bigger retention. --> pbs ns1 backup : A,, B, C, D, E, F, G .... i wanted tu push back the backup ( G for exemple ) to PBS 1 , in order to have pbs1 ns1...

Well. I had the pbs serveur himself to the pbs remote and it seems to works.

The idea is great . But ( in the web page, maybe in command line we can do it ), we can't synchronise 2 namespace on the same datastore. We have to select another datastore, and in this case all the data will be read/write again.:( But if it was possible, it would be a great idea ideed. :rolleyes:

Bonjour, We have one PBS ( PBS1 ) on one site synchronize to another PBS ( PBS2 ) one another site. Instance running on the first site doesn't have access to the PBS on the other site. Only 2 pbs are on the same network. we have a small retention on site 1 , and a big on the second site...

Do you have any news concerning this issue? i think i have the same problem with the promox-backup-client with the map command for mounting the backup. The message seems identitcal. ( i change some inforlmtion in the command line for posting.. ) proxmox-backup-client map...

Bonjour, Can you confirm that the dirty bitmap is always clear after a storage move for a VM hard drive, even if the VM is still running with no reboot? So if we change the storage, we have to re-read oall the data for the backup with PBS ? Thanks.

I can create a prune job directly on the web interface on pbs, and after, i can launch the prune job when i click run now. it's work My idea was to create the prune job automatically ( with a prune Schedule) via the Api. And after that it's the pbs server who's launch the prune task ( prune...

I also altered the response. For the long name, they are generated automaticly via a backup script ( we use volume id), that's why there are long. I try with a short token I try with a login/pass, it's the same. there is a lot of "-" in the name of the namespace / group ( like 15 occurence )...

I ll try with a login/password. But the goal is to launcher the command in a script so the token seems more the way to go. For the file/ namespace name, i just quickly remplace the real name for posting here. Thanks for the reply

Hello i try tu run the prune command with the proxmox-backup-client like this : with the same command without the option -dry-run : It'a like it stuck for creating the tempfile for the backup, and the command don't work because of it Any idea ?

For redhat 9 ), i use the .deb version with a conversion to rpm with alien , so far so good; I juste have to install the package fuse-libs.

ansible?

you can use pbs-backup-client with some script, to backup what you want ( file / harddrive/partition. )

ksm /ballooning is active ? https://pve.proxmox.com/wiki/Dynamic_Memory_Management

I say it's a nice fetaure;). This week i make a script that backup the entire disk of a physical server with pbs-backup-client to a pbs server ,and another script with proxmox-backup-restore that restore the backup into a vm, on proxmoxve on a offsite site in case of a big disaster.