Hi,
In the web-interface, for any VM/CT you have a entry with name "Replication"!
Good luck!
Best practice for Proxmox self-backup
- Thread starter speedbird
- Start date
-
- Tags
- backup proxmox host
Hi,
In the web-interface, for any VM/CT you have a entry with name "Replication"!
Good luck!
Hello
Thank for the script
I try to backup the server with it .
Then I try to restore to same machine but with fresh install (same version of proxmox) but pve-cluster refuses to start
I receive pmxcfs error 255
Tried to run pmxcfs I receive :
fuse: mountpoint is not empty
fuse: if you are sure it is safe , use the 'nonempty' mount option
This happenes (if i understood well) because /etc/pve is not empty (probably as it has my setup)
How to continue from there?
How to try to mount the nonempty /etc/pve ?
Thank you
Thank for the script
I try to backup the server with it .
Then I try to restore to same machine but with fresh install (same version of proxmox) but pve-cluster refuses to start
I receive pmxcfs error 255
Tried to run pmxcfs I receive :
fuse: mountpoint is not empty
fuse: if you are sure it is safe , use the 'nonempty' mount option
This happenes (if i understood well) because /etc/pve is not empty (probably as it has my setup)
How to continue from there?
How to try to mount the nonempty /etc/pve ?
Thank you
move your copy of /etc/pve away:
`mv /etc/pve /etc/pve.bck`
restart the pve-cluster service/pmxcfs:
`systemctl restart pve-cluster`
once this works - copy the files you need from /etc/pve.bck to /etc/pve
First BIG THX to all here & esp DerDanilo, & we WILL USE this !!
adding my 2 cents
Instead of pick & choose which dir & so & such .. take the entire root fs, so, if using, gd 'ol fashioned LVM and old school way of using fsarchiver cmd line utility like this:
# create the LV snapshot of the root file system
$ lvcreate -L 10G -s -n snapROOTlabel /dev/pve/root
# run the fsarchiver util or put it into script
$ fsarchiver -j 16 -z 9 -L savethisrootfssnapshotlabel savefs ./nameoffsarchiverfsbackup.fsa /dev/mapper/pve-snapROOTlabel
# -j 16 means use 16 cores (multi threading), -z 9 means use lzma level nine compression (opting to use lzma legacy instead of something like zstd or etc .. ), -L is just labeling it ..
# get rid of the snapshot LV after thE backup script finishes ..
$ lvremove /dev/pve/snapROOTlabel
adding my 2 cents
Instead of pick & choose which dir & so & such .. take the entire root fs, so, if using, gd 'ol fashioned LVM and old school way of using fsarchiver cmd line utility like this:
# create the LV snapshot of the root file system
$ lvcreate -L 10G -s -n snapROOTlabel /dev/pve/root
# run the fsarchiver util or put it into script
$ fsarchiver -j 16 -z 9 -L savethisrootfssnapshotlabel savefs ./nameoffsarchiverfsbackup.fsa /dev/mapper/pve-snapROOTlabel
# -j 16 means use 16 cores (multi threading), -z 9 means use lzma level nine compression (opting to use lzma legacy instead of something like zstd or etc .. ), -L is just labeling it ..
# get rid of the snapshot LV after thE backup script finishes ..
$ lvremove /dev/pve/snapROOTlabel
No, the script currently doesn't have a restore function.
But the backup ist really just an archive of the backuped folders, so you can extract it and put the files of your chosing back.
E.g. the vm<ID>.conf files to recreate all your guests. Of course, the VM/container data (vol or subvols) needs to be there as well, as it is not part of this backup.
I would recommend cherry-picking the part of the configuration you put back, as a newly installed system is sometimes an opportunity for decluttering. At least for me it is.