Recent content by greg

Greetings I have a problem which is crippling me for a while... A CT is being backed up daily to PBS ; it's about 300G in total and about 600M changes daily. The backup process takes more than 14 hours, which data throughput measured by iftop at about 14kbps. Other CTs and VMs on the same...

I was able to make it work just following the instruction (leaving out the quotes). However, Internet.bs API key is actually a master key and is not restricted and therefore not suitable for such a purpose without opening a security breach.

Did you manage to do that? I'd be interested to know how it's working. Thanks

Thanks for your answer. The root cause is probably a heavy sql query (such as a query involving several millions lines). During that time, the server just "disappear" (it doesn't even ping), and when it's back there's a gap in the RDD graphs of the Proxmox GUI. The memory graph is flat at 25%...

Greetings I have a CT with a MariaDB inside it; I noticed that when a very heavy sql-related load occurs, the whole host system becomes unresponsive for an extended period of time: I cannot even use an already established ssh connection. Is there a way to "contain" a CT so I can at least keep...

Yes blocking all tasks in what I want. I definitely don't want a migration in the middle of a live event :) What would be the preferred parameter? I tried "mounted" and it said: CT is locked (snapshot-delete)

Thanks for your answer. Maybe I could use pct set --lock ? Then all operation would failed or be postponed?

Greetings I have a cluster of servers which are regularly doing backups and snapshots. During some production-critical periods, I need to "hold" such traffic/load which could impact the performances. What do you think would be the proper way to do that? Thanks in advance Regards

Actually for me this was 2 years ago, so my cluster evolved :) Upgrades were made, and this machine has been retired. I hope @henryd99 will find a solution! (fingers crossed). Regards

Good luck, I didn't find any solution but hard reboot...

Is there a possibility to resume the replication without erasing all the data on the target side (and therefore re-sending a lot of data)? Thanks in advance Regards

Thanks a lot for taking the time to explain. I understand it better now: you restore from the host side, but not necessarily the original host. it's really cool. Does the backup includes all disks from the original CT/VM? I've seen the unused disks are skipped.

Thanks for your answer. I've been running a cluster for years, so I'm aware of the various pitfalls, including the IDs. My concern was more about the VM/CT config. I noticed you cannot restore a backup from the backup server, you have to do it from the host, that means from a configured VM/CT...

Greetings I'm a long time user of Proxmox but a recent user of PBS and I love it. I was wondering: I have VMs which are off but I keep for archiving. Would it be possible to backup them, and delete the VM from the node? would I be able to restore them one day if needed? Thanks in advance...

If your nodes are in the same cluster, you can easily and automatically snapshot/replicate from one to the other.