dinislage/proxmox-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
TechHome
2020-06-14 14:42:53 +02:00
committed by GitHub
parent 51aff02a3d
commit a4c20d8bdb
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5
View File
@@ -27,6 +27,7 @@ Removes the nag from Proxmox | Tested 5.1-3 - 6.2-4
* Make the script executable and run it ```chmod +x ProxmoxNag.sh; ./ProxmoxNag.sh```
### Backup
User Mode:
* Download the [script](https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/prox_config_backup.sh)
```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/"```
@@ -34,6 +35,10 @@ Removes the nag from Proxmox | Tested 5.1-3 - 6.2-4
* 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](https://raw.githubusercontent.com/marrobHD/proxmox-tools/master/prox_config_backup.sh) 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