Search results

I share my scripts with you, for if it's of any help to someone. https://github.com/omgslinux/proxmox-firewall

It's even better to export PBS_REPOSITORY and have the password in a secret file with PBS_PASSWORD_FILE. Your cmd line should work, but I'm afreid you should use namespaces to identify host backups (with --ns <namespace>) Then, for restoring, the docs say that it's better to use a "manual"...

I just want to share this, after unsuccessfully trying to understand the reason looking at the docs about nesting. I searched the web for a common application problem, like "/run/php directory not created by php-fpm service". Lots of answers but found none focusing the real problem. In my...

Hi. Surely this has been somehow managed before, but I'm not aware of the current status. PVE has filter rules management, which is great, but I miss a way to have a smart way for, at least, basic NAT rules. Several years ago I wrote a custom script with "high scalable" easy use and that's...

Sorry for changing thr issue (though may be related to the solution): are there any plans to support bind mounts via UI instead of having to edit manually the conf file?

What do you mean with "moving"? If the disk is NOT the same, I think it's better to run a sync job and pulling all the data. Regardless any other things, I'd advice to take your time and stick on the sync option. Once everything's synced, think what you want to do with the existing "old" pbs.

If I'm not wrong, it looks like the previous backup was about 2 months ago. Did you verify this backup? Do other backups in the same datastore succeed? Did you check both filesystems?

I tend to believe one should have a "small" PBS ct in PVE, and from then on, have as many remote replicas you just want. In PVE, have a "local" storage and another storage for the PBS. The idea is to backup the PBS ct to the local storage "when needed" (this backup should be less than 2GB), and...

I've just tried another browser, and have the same problem. Besides, I think if it was a browser issue, the schedule should work, but it doesn't. Nothing related to the pbs storage works from PVE. I guess that the PVE can't be "too old".

I think you can try with smaller vms or cts. If most (or all) fail verification, it's likely the filesystem where the datastore lies needs to be repaired. It happened to me about one week ago.

If you have enough free storage somewhere else (and setup as storage), you can move an "oversized" disk to another storage via the Hardware option by selecting the disk and then choose DiskAction and Move Storage.

I'm using at a server running Debian bullseye (PVE 7.4) and I have a PBS for backups. Everything was working from PVE until about one week ago (maybe I upgraded to pbs 3.3). I had a daily backup job for a pool. If I try to run the job manually from the gui, I get a "Broken pipe (596)" error...

Thanks. I've used vzdump from the command line and works perfectly, so it's not a pbs issue. I'll post in pve forum.

Did you create a bridge with that subnet? Then, you just have to assign one of the IPs to the vm. Also, take a look at https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_network_routed

I have to say that with VE 8 and ifupdown2, I've been able to play with several bridges and vnets from the gui and everything worked without any problem. I encourage the poster to try this way.

With SDN, you can create zones and vnets.

I'm having this issue in a bullseye installation (the pbs is 3.3). It was working and stopped working getting "broken pipe (596)". I have just a few cts in root ns, and the rest in different namespaces. The pbs backups are unaccesible from pve, but pbs works nice with host backups. I've...

I've just tried right now (yesterday I had to login again) and it works. It wasn't urgent. Surely it was something related to the browser (I use brave). Thanks for your help.

Hi. I'm dealing with the sync features. I guess that the most usual scenario is to have a local pbs, with all the data to be synced, and one (or more) targets. In the targets, the datastore is initially empty, without any namespace. Then, I find there are two chances: 1) Sync all at the same...

Ok, thanks. I'll try inmediately.