[SOLVED] Backup failed unable to open file Permission denied

trollmars

New Member
Oct 30, 2020
7
3
3
48
Hi,

benutze noch PVE 6.2.Dazu der PBS.
Wollte jetzt mal upgraden auf 7.

Mein Backup geht von den meisten CTs und VMs auf einen PBS. Das lief auch bi gestern hervorragend !

Jetzt wollte ich bevor ich upgrade ein 2 Node Cluster erstellen,
Um wichtige CT/VMs auf einen anderen Node zu haben falls das Upgrade auf 7 auf dem Haupt Node fehl schlägt.

Jetzt zum Problem.
Es gehen keine Backups mehr auf den PBS,
Wenn ich manuell via GUI trigggere kommt (hier CT 202):




Code:
INFO: starting new backup job: vzdump 202 --mode snapshot --remove 0 --node pve-main --storage PBS-Main
INFO: Starting Backup of VM 202 (lxc)
INFO: Backup started at 2022-09-07 23:33:45
INFO: status = running
ERROR: Backup of VM 202 failed - unable to open file '/etc/pve/nodes/pve-main/lxc/202.conf.tmp.32010' - Permission denied
INFO: Failed at 2022-09-07 23:33:45
INFO: Backup job finished with errors
TASK ERROR: job errors


Woher kommt das?
Es muss ja irgendwas mit dem Cluster zutun haben.
 
Last edited:
Hi,
Thx!

I figured out that my now offlline node 2 causes the problem.
I do "pvecm expected 1" and now the backup to PBS works as aspected.
Meanwhile i do "pvecm delnode node 2".

Thx for the Qdevice.
But i guess i go the road to pve 7.2 with a second pve as Standalone,
rebuild important VMs and CTs on it and do then upgrade my main PVE to 7,2.

THX
 
  • Like
Reactions: sterzy
Since your issue is resolved, can you please mark the thread as solved. Thanks!
 
Hello. I have the same issue which started after upgrading to Proxmox 8.1.5. My cluster with 2 nodes.
_________________________________________________

ERROR: Backup of VM 135 failed - unable to open file '/etc/pve/nodes/pve3/qemu-server/135.conf.tmp.4137127' - Permission denied
INFO: Failed at 2024-04-05 19:34:09
INFO: Starting Backup of VM 136 (qemu)
INFO: Backup started at 2024-04-05 19:34:09
INFO: status = running

________________________________________________
pvecm status
Cluster information
-------------------
Name: cluster1
Config Version: 6
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Fri Apr 5 20:46:22 2024
Quorum provider: corosync_votequorum
Nodes: 2
Node ID: 0x00000001
Ring ID: 1.3670
Quorate: Yes

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 2
Quorum: 2
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 NODE_IP_1 (local)
0x00000003 1 NODE_IP_2

________________________________________________________
 
Hey,

this is likely a different issue, can you please open a new thread and not revive threads that have been closed for a year and a half?

Thanks!
 
  • Like
Reactions: vionix

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!