Search results

I know. But if only one is kept, you will have much less manual work with deleting it, instead of manually deleting many. In my post on Saturday at 13:09 I showed you a method of manual deleting and I asked whether it worked, but I can't see your reply...

At my server I can see slightly different options - maybe other version or options have aliases... Anyway. What if you execute this command: proxmox-backup-manager prune create SOMEid --store YOURDATASTORENAME --ns YOURNAMESPACE --schedule daily --keep-last 1

If I understand correctly, the VM crashes or freezes. If yes, it may not be able to record an error in the logs. But maybe it writes some error on its (virtual) terminal. So my suggestion is to log in to the VM's virtual serial terminal from the PVE's shell and wait. Maybe the VM will write...

My (blind) ideas: Is "Propagate" set to "Yes" for this user (in Access Control -- Permissions)? It may be needed. In the DatastoreAudit role you wrote Path: /datastore/z_backups. In other roles you wrote Path: /datastore/zfs_backups. I mean this difference: z_... vs. zfs_... I ask just in...

Hi, jaysun_n. I have compared your screenshots to views of my PVE and PBS and I can see that my PVE doesn't show usage of the PBS datastore in the Summary page, either. I remember that in the beginning this caught my attention as well. Now I don't really miss it because for backup administration...

This drwxrwx--- 1000 1000 HDD24TB is the reason (user backup has no access). SMB permissions can be substantial here. I'll try to recollect a similar SMB mounting problem... Maybe you need to use a username and a password of this "1000" user while mounting or not require authentication while...

Are there any unusual entries in the logs of the host and of the VM? Or in "dmesg -T"

If you umount /dev/sda1 what is the output of ls -ld /mnt/HDD24TB ls -lA /mnt/HDD24TB

I have no answer to the earlier questions and I have no experience with PBS as LXC. But searching for something today I have noticed an old thread with Fiona's (a Proxmox Staff Member) post https://forum.proxmox.com/threads/permission-denied-os-error-13-on-vm-backup.131726/post-579322 containing...

Are the permissions above /mnt/HDD24TB/pve-backups enough for backup user to read and execute? What are the outputs of ls -ld /mnt ls -ld /mnt/HDD24TB ? You wrote "the storage is mounted before PBS starts (Systemd-Mount-Unit)". What storage? What kind? A local disk? A NFS? A SMB? Other? What...

Let's check from the beginning :) Have you used the GUI or a shell command? If the command, what command exactly and what was the output? Run apt-get update and post the result. Run apt-get dist-upgrade and post the result. While posting the commands and outputs please use the "Code"...

The network is my second thought as well. As you wrote that servers are connected to the same switch... maybe an old capacitor (I had a similar situation) or bad cable/jack... I would try slower transfer. I don't remember the option name. Something about bandwidth limit or traffic control. I...

Maybe it's not the right trace (as you stated the error is random), but... I'd start with verification of the backups. https://pbs.proxmox.com/docs/maintenance.html#verification ... Aside from using verify jobs, you can also run verification manually on entire datastores, backup groups or...

Could you try the command grep -r 386 /etc/apt and post the result? Place the result inside "Code" markup, please.

No matter whether developers decided on bits or on Bytes, they should place on the graph the unit they chose: "b/s" or "B/s" (or "p"(p like per) for "/" ) Not typing the physical unit on a graph automatically brought down the test grade at my schools :p

Do you mean relayhost? https://www.postfix.org/BASIC_CONFIGURATION_README.html#relayhost https://www.postfix.org/postconf.5.html#relayhost

Maybe try qm disk rescan [OPTIONS] Rescan all storages and update disk sizes and unused disk images. --dryrun <boolean> (default = 0) Do not actually write changes out to VM config(s). --vmid <integer> (100 - 999999999) The (unique) ID of the VM...

Not in detail :), but generally it's described e.g. here: https://en.wikipedia.org/wiki/Thin_provisioning

/dev/sda obviously is not in the perfect condition. This 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1 (the number in the last column is not 0) can mean a problem. And Error 1 occurred at disk power-on lifetime: 45600 hours (1900 days + 0 hours) ...

I guess it's not a full solution (if any), but: does manual deleting some snapshots (backups) work? Datastore --> yourdatastorename --> Content --> Root Namespace --> someNamespaceName --> vm/number --> right-click --> Remove If not removing the full vm/number, then expand this, select some...