Recent content by HamsDa

I found this. This is my daily backup-schedule kicking in. sudo journalctl --since today -u proxmox-backup-proxy Apr 21 00:00:03 pbs proxmox-backup-proxy[836]: starting new backup on datastore 'backup': "vm/101/2021-04-20T22:00:02Z" Apr 21 00:00:03 pbs proxmox-backup-proxy[836]: GET /previous...

Touching a file seems to work without any problems. I gotta say it's slow, but I guess that's just because it's an SMB share and right now there's an rsync job running for some data on the same hard disk. cd /mnt/backup/.chunks/bb9f sudo -u backup touch testing ls -a drwxr-xr-x 2 backup backup...

Thank you very much, especially for that strace command. It would've probably taken me another week to understand how to do that :p I attached the files to this post. There were 2 more files (pbs_.892 and pbs_.896) but they were empty. grep ENOENT over all pbs_ files results...

Do you have any hint what might be wrong? rsync, scp and rdiff-backup work correctly here.

65537 I executed it on the SMB Server, instead of PBS. The find command took longer than I wanted to wait on PBS, while on the SMB server it was finished nearly instantly.

ls -la on /mnt/backup/ shows the following files: drwxr-xr-x backup backup .chunks -rwxr-xr-x backup backup .gc-status -rwxr-xr-x backup backup .lock drwxr-xr-x backup backup vm Inside .chunks there are about a quadrillion folders ranging from 0000 to ffff.

Hello fabian, Here's my /etc/fstab mount //192.168.10.254/backup_proxmox /mnt/backup cifs credentials=/home/SOMEUSER/.smbcredentials,uid=34,noforceuid,gid=34,noforcegid,defaults,noauto,nofail,x-systemd.automount,x-systemd.requires=network-online.target 0 0 The datastore creation has been done...

I have the same problem. Proxmox VE hosting Proxmox BS. Proxmox BS mounted SMB datastore in /mnt/backup/ proxmox-backup-manager versions proxmox-backup-server 1.1.2-1 running version: 1.1.2 cat /etc/proxmox-backup/datastore.cfg datastore: backup gc-schedule 04:00 keep-daily 10...

I would keep that USB HDD connected at all times, to automate the VM backups. It wouldn't be nice if my USB HDD die by lightning strike or fire, but this drive would only backup VMs for fast-restore if I mess something up while meddling with the system. For the data backup, I would use my...

To be honest, that is exactly what we are doing in our company. We're a small company and our customers are small companies too. I only got into this company this year, but I've never seen any of our customers having 2 servers. All of them just have 1 server where the Backup-VM is running and...

I have absolutely no problem with losing all my VMs, the Hypervisor and all of the configuration. I'm trying to use ansible whenever possible, so it wouldn't be that hard to recover from losing everything. What I absolutely cannot lose is my data (and it may be the best way to RSYNC it to my...

Hi tburger and Dunuin, thank you for helping me! After reading your posts, I guess I really jumped on the wrong train of thought there. Especially did I not think about failure domains, thanks for that hint! Regarding your advice, what about this: M.2 SSD => ZFS Root pool => VMs, ISOs, etc...

Hello dear Proxmox Community and merry Christmas to everyone! I am fairly new to Proxmox, only experimented with it inside another Hypervisor. I got myself an Intel NUC10i7 (6 cores + hyperthreading, 64 GB RAM and 2x 2TB SSD [1x SATA, 1x M.2]), which I want to be a Proxmox VE Hypervisor. I...