Search results

@ggoller so as you see, the security isn't a key reason. I think if there was a checkbox (just as an example), what login mechanism to use, it would be great and as i said before, will make the area of use much wider.

> Why should Proxmox They do not have to but may to. The core changes are already done. In order to make their product applicable on more wide range devices (including low power). @Neobin special for you -- please, visit the GitHub link, there is an interested chard of ready-to-go device (NAS)...

Not that I want it, but there is simply no choice if you are using products of Synology/QNAP/etc. Specifically in my case the kernel version is 3.10.x. (Synology DS916+, not so old) But you can also look at the thread on GitHub for understanding, that there is a lot of people with the same...

It is impossible to login into PBS when the latter is deployed in container which uses kernel 3.x (Synology/QNAP devices). Please look at this discussion and the merge, and if it ok, could you accept it into the main branch. https://github.com/ayufan/pve-backup-server-dockerfiles/pull/15

liberodark Thanks for you advice. It took away my headache :)

I've tried to add these lines: lxc.idmap: u 468000000 1000000000 1000000 lxc.idmap: g 468000000 1000000000 1000000 lxc.idmap: u 0 100000 65536 lxc.idmap: g 0 100000 65536 The entire content of the file: $ sudo cat /etc/pve/lxc/503.conf arch: amd64 cores: 1 features: nesting=1 hostname...

According to the problem with file permissions. Could be the problem in this line? run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp534436_3023/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0...

Do these errors require some fixing or not? As i understood the backup on PVE is made by root. INFO: Upload directory '/mnt/vzsnap0' to 'pbs_backup_user@pbs@backup1.myserver.com:8007:private-all' as root.pxar.didx INFO: failed to open file: ".bash_history": access denied INFO: failed to open...

According to the user permissions for backup. What user is responsible for that on the pve nodes? Do i need to replicate my user intended for backups also on the pve nodes? E.g. my user on the Proxmox Backup is 'pbs_backup_user', so, i have to recreate this account on pve?

Great thanks for the help and your product! The culprit was '/var/log/lastlog'. `ls` said that the space occupied by that file is ~130GB. I had to just truncate the lastlog on all machines and containers.

And what about file permissions. Why does it matter for backup? These files are inside the container and have permissions for user inside the container itself.

But it doesn't happen for replication. Couldn't it be that the backup take into account some of these disks ? udev 126G 0 126G 0% /dev/tty tmpfs 126G 0 126G 0% /dev/shm tmpfs 26G...

Environment: $ pveversion pve-manager/6.4-13/9f411e79 (running kernel: 5.4.143-1-pve) # proxmox-backup-manager versions proxmox-backup-server 2.1.2-1 running version: 2.1.2 Replication process (from one pve node to another): The size is about 1.29G and the time ~20 seconds. 2022-01-04...