Proxmox backup onto a sata ssd using a usb adapter

[michaelthompson1991]

So when I set proxmox up to run home assistant I had the ssd off my old pi with the usb adapter so I thought id use this as a backup of proxmox.

I believe i used this guide [https://smarthomescene.com/guides/h...des/how-to-backup-home-assistant-in-proxmox/) and a bit of ChatGPT to get me through bits I didn’t understand.

Now the drive I used for the backup to is 240gb but proxmox thinks is just under 99gb, see screenshots. The drive is setup as a VZDump backup file, see screenshots again.

Im not really sure what’s wrong or how to make the drive the full size, and it wont matter if I have to wipe the drive because I only run home assistant on it currently and I also have backups for this in google drive.

Can anyone help or be of guidance please?

See screenshots [https://imgur.com/a/FcE4AwG](https://imgur.com/a/FcE4AwG)

I can provide more screenshots if needed if you let me know what I need to screenshot.

Thanks everyone!

 

[mariol]

Are you sure that the USB drive is mounted correctly? Please give me the output of:

df -h

and

mount

 

[michaelthompson1991]

Im not sure, but I’m assuming not. Heres the results https://imgur.com/a/tTtmjCU

 

[mariol]

Im not sure, but I’m assuming not. Heres the results https://imgur.com/a/tTtmjCU

Thank you. No usb drive mounted. How did you integrate them, or wanted to integrate them? You can use the FSTAB for mouting drives manually.

Please post your storage.cfg too:

cat /etc/pve/storage.cfg

 

[michaelthompson1991]

Well i just used the blog post i linked in the first post. Heres what happened when I enter the code https://imgur.com/a/4E54ZmB

 

[mariol]

Well i just used the blog post i linked in the first post. Heres what happened when I enter the code https://imgur.com/a/4E54ZmB

This is only the Proxmox Storage cfg. In your case, this now points to an empty directory, i.e. to your mount point. But maybe backup files have already been copied into it. You must delete them before mounting. Your USB drive must then be mounted there.

Yes, they write also that you have to mount your drive. But this is only temporary. After a reboot your mount is gone. So if you like, use the FSTAB for creating fix mounts.

 

[michaelthompson1991]

Yeah backups have been working its just the disk isn’t full size. When you say reboot do you mean delete backups, reboot proxmox then proceed with
Create the directory, change name and location if you want
mkdir / mnt/backups
#Mount
the drive to the created directory, change to your drive label and folde
mount
/dev/sdc /mnt/backups #Change to your drive and folder
XPROXMOXVitualEnvironment74-3Search
Server View
Node ove
Datacenter
~ Eo pve
101 (zigbee2mqtt)
- 102 (pihole)
103 jellytin)
77100(haos9.5)
Q Search
@Summary
• Notes
>_ Shell
=( local (pve)
# Documentation Greate VM Create CT root@pam
3 Reboot C Shutdown >- Shell: Bulk Actions • Help
Disk model: Flash Disk
Units: sectors of 1 * 512 - 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier:
6D608513-0856-4294-9868-99D007735571
Device
Start
End
Sectors Size Type

 

[mariol]

Yeah backups have been working its just the disk isn’t full size. When you say reboot do you mean delete backups,

No, I mean reboot. Here's an example for you: Let's assume your USB hard disk is /dev/sde1 and your mountpoint is /mnt/pve/usb-backup.

Create the mount point:

mkdir /mnt/pve/usb-backup

Mount the USB drive manually:

mount /dev/sde1 /mnt/pve/usb-backup

With "df -h" you are now abel to see your usb drive mounted in your system:

Filesystem            Size  Used Avail Use% Mounted on
udev                  386M     0  386M   0% /dev
tmpfs                 597M  1.6M  596M   1% /run
/dev/mapper/pve-root   20G  7.3G   11G  40% /
tmpfs                 3.0G   46M  2.9G   2% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 4.0M     0  4.0M   0% /sys/fs/cgroup
efivarfs              256K   47K  205K  19% /sys/firmware/efi/efivars
/dev/sda2             511M   12M  500M   3% /boot/efi
/dev/sdc1              79G  2.8G   72G   4% /mnt/pve/local-directory
/dev/fuse             128M   32K  128M   1% /etc/pve
tmpfs                 597M     0  597M   0% /run/user/0
/dev/sde1              98G   36K   93G   1% /mnt/pve/usb-backup

As next step you have created your directory storage over UI, this look like this:

dir: usb-backup
        path /mnt/pve/usb-backup
        content backup
        prune-backups keep-all=1
        shared 0
        is_mountpoint 1

With an additional manual option: is_mountpoint 1

From the docs:
--is_mountpoint <string> (default = no)
Assume the given path is an externally managed mountpoint and consider the storage offline if it is not mounted. Using a boolean (yes/no) value serves as a shortcut to using the target path in this field.

No now you also in the WebUI the right space:


If you reboot your machine, the drive will be unmounted and never be mounted again, so with out the option "is_mountpoint 1" you are able after a reboot to backup again, but not on your usb drive. All backups are copied to /mnt/pve/usb-backup, which means root storage when unmounted.

The additional option prevents this, look at the logs:

Oct 18 10:06:42 pve pvedaemon[555896]: unable to activate storage 'usb-backup' - directory is expected to be a mount point but is not mounted: '/mnt/pve/usb-backup'

You also have the option (as I described above) to permanently bind the USB disk in the system with the FSTAB. It will then be mounted again automatically when you restart the system. Nevertheless, they must be unhooked before “pulling off”. Since the data is written async, your data may otherwise be corrupt.

umount /dev/sde1