I've a backup that is configured to start each day at 20.00 pm
but in a bunch of cases it takes 30 hours... normally 6
Is it possible to inercept a running job and procrastinating the new backup?
Even blocking it
I have a backup with 20 ct inside and i will sync only 6 containers on the remote pbs
I've created a use that can access the locale backup, how can i say to the system to
propagate only the 6 containers backup?
I there a method to create such a group?
Just a little question:
if i launch proxmox-backup-client command line on a directory and i interrupt the transfer after a while (two hours)
The transferred files remains on the pbs server and are reused at the next launch or should permit the transfer of
a first whole backup...
I've created a Proxmox Backup Reader that doesn't own backups:
correctly it can read all backups
correctly it can download backups
uncorrectly it cannot download a single file from a ct backup (from the dir icon, not config)
i have a proxmox cluster with a lot of cpu and memory (non completely used)
on node one i have a CT 100 mysql master
on node two i have a CT 101 mysql slave
when they syncronize/replicate host two has too much open files and another postfix CT becomes unusable for 15 minutes
the version is...
I use PBS and i find it very quick and good and i have anoher question:
Is it possible to have container names in the backup interface?
I add a screen shot of the actual backups
Is it possible to have even the name of the container in addition to it's ID?
I mean like the...
I don't know if this is the good place and if not please destroy this thread
I have a 3 nodes glusterfs server but when i probe connecting the client i receive immediate disconnection
gluster volume info
Volume Name: volume1
I've a container that has always problem with the backup on pbs
pbs version is:
proxmox-backup-server 1.0.6-1 running version: 1.0.6
pve-manager/6.3-3/eee5f901 (running kernel: 5.4.65-1-pve)
the backup of a container gives always this problem:
122: 2020-12-21 22:42:41...
in a strange case i've a running container that generates an error while asking
can't open '/sys/fs/cgroup/memory/lxc/107/ns/memory.stat' - No such file or directory
and despite i cannot list any of other container status in the web interface.
If i list each container manually...
in many case i've this problem on one of three proxmox nodes, not always but it happens
: Error: connection error: Connection reset by peer (os error 104) (500)
This appears when browsing from proxmox
I don't know how to debug this situation.
I've other two nodes in...
I have a pbs server installed and a ProxmoxVE cluster separate.
Configured pbs server datastore is mounted over nfs and backup and root could write withouth problem
proxmox-backup-manager datastore list
│ name │ path │ comment...
Is it possible to add a hint to each node interface like
just to intercept correctly (when adding a new machine) the correct interface to join machine to???
I know that this is not in the code and i can write it myself... and send the patch, obviously...
Just a simple question:
anyone tested openvswitch on Proxmox?
Or, better, is it in the future of Proxmox or do you have any other solution for
a virtual switch?
I'm testing 3.x rc1 and i think it's a good solution
(testing on my own lan as stable server)
Found the bug, i hope that Dietmar will be so kind to include the solution.
This code says that the exclude-path is ALWAYS read from command-line
and despite each line in /etc/vzdump.conf will be skipped
# exclude-path list need to be 0 separated