ProxmoxTools

📦 A collection of stuff that I and others wrote for Proxmox 📦

Features

-<--->-

Remove Proxmox Nag

Removes the nag from Proxmox | Tested 5.1-3 - 6.2-4

Download the script
cd /root/; wget -qO- https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/ProxmoxNag.sh > ProxmoxNag.sh
Make the script executable and run it chmod +x ProxmoxNag.sh; ./ProxmoxNag.sh

Remove Proxmox Nag and Community repo

Removes the nag from Proxmox | Tested 5.1-3 - 6.2-4

Download the script
cd /root/; wget -qO- https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/proxmoxve_community.sh > proxmoxve_community.sh
Make the script executable and run it chmod +x proxmoxve_community.sh; ./proxmoxve_community.sh

Backup

User Mode:

Download the script
cd /root/; wget -qO- https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/prox_config_backup.sh > prox_config_backup.sh
Set the permanent backups directory export BACKUP_DIR="/root/proxmox_backups/"
Create a proxmox_backups folder and make the script executable mkdir /root/proxmox_backups/; chmod +x ./prox_config_backup.sh
Shut down ALL VMs + LXC Containers if you want to go the save way. (Not required) service pve-manager stop
Run the script ./prox_config_backup.sh

Automatic Mode:

Oneline the script with -a
cd /root/; wget -qO- https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/prox_config_backup.sh > prox_config_backup.sh; chmod +x ./prox_config_backup.sh; export BACKUP_DIR="/mnt/pve/freenas/"; ./prox_config_backup.sh -a

Restore

On my machine, you end up with a GZipped file of about 1-10 MB with a name like "proxmox_backup_proxmoxhostname_2017-12-02.15.48.10.tar.gz".
Depending upon how you schedule it and the size of your server, that could eventually become a space issue so don't
forget to set up some kind of archive maintenance.

To restore, move the file back to proxmox with cp, scp, webmin, a thumb drive, whatever.
I place it back into the /var/tmp directory from where it came.

# Unpack the original backup
tar -zxvf proxmox_backup_proxmoxhostname_2017-12-02.15.48.10.tar.gz
# unpack the tared contents
tar -xvf proxmoxpve.2017-12-02.15.48.10.tar
tar -xvf proxmoxetc.2017-12-02.15.48.10.tar
tar -xvf proxmoxroot.2017-12-02.15.48.10.tar

# If the services are running, stop them:
for i in pve-cluster pvedaemon vz qemu-server; do systemctl stop $i ; done

# Copy the old content to the original directory:
cp -avr /var/tmp/var/tmp/etc/* /etc/
cp -avr /var/tmp/var/tmp/var/* /var/
cp -avr /var/tmp/var/tmp/root/* /root/


# And, finally, restart services:
for i in qemu-server vz pvedaemon pve-cluster; do systemctl start $i ; done

If nothing goes wrong, and you have separately restored the VM images using the default ProxMox process.
You should be back where you started. But let's hope it never comes to that.

Leave cluster

With this script you can leave a cluster or a local created cluster. By uncommenting line 27 you would also delete all configs of containers and co.

Currently its here: /: leave-cluster.sh
Download the script
cd /root/; wget -qO- https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/leave-cluster.sh > leave-cluster.sh
Make the script executable and run it chmod +x leave-cluster.sh; ./leave-cluster.sh

API

The Proxmox API scripts are located in the API folder. Currently there are:

/api/lxc: startlxc.sh, stoplxc.sh, shutdownlxc.sh, restartlxc.sh, suspendlxc.sh and resumelxc.sh
/api/vm: startvm.sh, stopvm.sh, shutdownvm.sh, restartvm.sh, resetvm.sh, suspendvm.sh and resumevm.sh

Sources

http://ziemecki.net/content/proxmox-config-backups

Feel free to post issues

Authors & contributors

The original setup of this repository is by Marlon.

For a full list of all authors and contributors, check the contributor's page.

Troubleshooting

6.3 KiB Raw Blame History