[SOLVED] Backup fails with reference to old SMB share

J

JayB21

New Member
Apr 12, 2025
20
5
3
I'm running into backup errors on some of my VMs

Background.

I'm using HexOS for my NAS and they recently pushed on update that broke SMB and my back up share HexNasBackups wouldn't mount so I deleted it and recreated it as ProxMoxBackups. I still was not able to mount it.

They pushed a fix a day or 2 later and all seemed well. I recreated the storage location and a new backup job.

It works fine for 6 of my 8 VMs but 2 are failing with references to the old share.

INFO: VM Name: PublicMgmt
INFO: include disk 'scsi0' 'HexNasBackups:102/vm-102-disk-0.qcow2' 100G
ERROR: Backup of VM 102 failed - storage 'HexNasBackups' does not exist

The start up seems normal and is pointing to the correct storage except that 102 & 110 fail with the above error. FWIW, 102 is a running VM and 110 is currently off.

INFO: starting new backup job: vzdump 101 102 103 108 109 113 114 110 --node pve --storage ProxMoxBackups --mode snapshot --quiet 1 --compress zstd --fleecing 0 --notes-template '{{guestname}}' --prune-backups 'keep-last=30'

Obviously(?) there's some reference that needs cleaning up but don't know where to find it.
 
Hi, @JayB21
If you issue at the PVE host these commands:

qm config 102
qm config 110

do the results mention HexNasBackups?
 
That's why the backup tries to read them :) .
As you don't want to include them, remove them from the configs of the VMs.

Edit: also check the definitions of the backup jobs.
 
Last edited:
Well that was easy. Thanks.

For my education, any ideas why those would exist on those 2 and no others? I'm pretty sure I created my backup plan for all of them at the same time.,
 
JayB21 said:
For my education, any ideas why those would exist on those 2 and no others? I'm pretty sure I created my backup plan for all of them at the same time.,
Click to expand...
If I understand correctly your posts, now you have removed those "disks" from the definitions of the VMs (and it helped).

If so, the backup plan you created was OK. That is, it wasn't the reason of the errors. The VMs' configs were the reasons.
 
  • Like
Reactions: JayB21
@JayB21 , I'm glad that my replies helped you :) . I understand that your issue is now resolved.
Please mark the thread as "solved" by editing the subject and selecting the prefix [SOLVED] from the drop-down menu.
 
For future reference. For some reason (my incompetence) my VM drives for these 2 VMs were located -on- the NAS, which is of course, why they were showing up in the conf. Also explains how slow the one that was in use was. No idea how I managed that but....

I did a Move Disk from the NAS to local storage on the baremetal PM server and updated the .conf file to point to it and things are working and much faster.
 
  • Like
Reactions: Onslow
You must log in or register to reply here.
Top Bottom
Back