Proxmox VE Host Backup

[tteck]

This script serves as a versatile backup tool for specific files and directories found within the 'etc' directory. It was developed in response to numerous requests for a Proxmox host backup script. The unique feature of this script is its flexibility, it allows users to choose which files and directories to back up, making it suitable for various hosts, not just Proxmox. By default, the compressed backup file is stored in the 'root' directory.

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/host-backup.sh)"

I haven't published this script on the website yet. Before making it official, I'd like to gather user input and feedback.

[tteck]

Backup considerations

aliases
hostname
hosts
lvm
network
pve
resolv.conf
sysctl.conf
vzdump.conf

These are speculative guesses.

[tteck]

When creating a backup of the specified files and directories in my system, the resulting tar file size is 2.6MB.

[Smile2Grow]

Thank you @tteck! Your backup consideration fits for me. Maybe a query makes sense to create exactly this selection or Free Selection as a backup?

[tteck]

Just to mention, I utilize File Browser on my Proxmox host to handle files, including tasks such as downloading and uploading.

[tteck]

If you find that File Browser doesn't meet your expectations, the uninstallation process is straightforward, just re-execute the script.

[Smile2Grow]

The filebrowser makes sense.

[tteck]

The script is currently limited to the /etc/ directory. Would it be more beneficial to allow users to specify the directory they want to work in, such as /root/, /var/, or even /usr/local/bin/?

[tteck]

By implementing this approach, you could back up /etc/pve/, and then, if needed, rerun the script to create a backup for something located in /root/ or any other directory of your choice.

[tteck]

Also, allow users to specify the backup path.

[tteck]

The changes have been implemented.

[tteck]

For consistency, it's necessary to include slashes both before and after the backup path and directory path when entering them.

[endigma]

What's the restore story?

[tteck]

Normal tar rules apply. The -C option specifies the destination directory where the contents of the tarball will be extracted, and if files with the same names already exist in that destination directory, they will be overwritten.

tar -xzf backup-name.tar.gz -C /path/to/destination/directory

e.g. tar -xzf server-var-lib-pve-cluster-backup-2023_09_09.tar.gz -C /var/lib/pve-cluster

[mgrimace]

What about a script that we could use after reinstalling proxmox that asks where the backup was saved, what was backed up (e.g., full, manual), and then automates the restore?

[yodaphone]

this is a good one. worked for me

can we make the selection of directories stick so that we dont have to do this everytime the script is run

[tteck]

No, my apologies.

[hvddrift]

Hi, love all the scripts, (new proxmox user) this one has me a bit stumped.

Not sure if I have missed something entirely, but if I have a SMB attached drive /mnt/pve/unraidpve13
I select /etc and then for example [x] PVE

Then I get this error.

Finished
A backup is rendered ineffective when it remains stored on the host.

[tteck]

How is that an error?

[Jens-Wymeersch]

@tteck as always, this is a very useful script. Is there any way to automate it with a schedule ?
Secondly, a dropdown of all the files, creates a lot of flexibility but means that you have to click a lot. Maybe it is possible to have a suggestion built in (default). What do you think ?

[Jens-Wymeersch]

Never did a cron job before. Probably should learn. But what about the files themselves - a subsection that is really needed instead of full autonomy ?

[tteck]

Since the Proxmox configuration is not expected to undergo frequent changes, I believe there's no necessity for a crontab job.

[Jens-Wymeersch]

Understood. What about a subsection of the files in /etc/ that is needed to be backup'ed. What is the advice there ?

[tteck]

#1770 (comment)

[endigma]

If you want like advanced backups you can use restic or borg or etc they have docs on scheduling and including different files.