Noob questions on backup locations

[molnarti]

I have just discovered this tool and its pretty much what i was looking for (and hoping PBS would support it once, since its on their roadmap for quite some time). However I am struggling to set this up properly:

where do i configure the backup location?

backups are currently made to /opt/proxmox-backup/backup which i find suboptimal for various reasons:

• if my PVE disk fails, backups are lost
• the root partition of all my PVE hosts are set intentionally to just 16 GB which works great for me, but i never intended this to use backups
• i have my NAS NFS share mounted to my proxmox host which would the intended and ideal location for backups

I can see the LOCAL_BACKUP_PATH="${BASE_DIR}/backup" in the config, but dont see where ${BASE_DIR} is configured. i guess i could change this to my mounted remote directory, but in that case it would not be a local backup anymore....

what are secondary and cloud backups?

its also not clear to me how to configure those. maybe by mounted NAS folder should be a secondary storage, but do i need a local primary first to have a secondary one?
the env file mentions CLOUD_BACKUP_PATH="/proxmox-backup/backup" but that does not sound like cloud backup location to me. under cloud backup i imagine something like an S3 bucket, which should be supported by rclone, but again its not clear to me how to configure it in proxmox-backup context

Thanks in advance for any help

[tismofied]

Replying because I am in same situation.
It also says run @proxmoxan_bot to put in the id for telegram but it doesn't say where to run it.
A step by step setup guide with example at least for the env config file would be amazingly helpful.

[molnarti]

the telegram part was quite easy to set up. open telegram, search for the bot, don't get discouraged that it talks italian at first, type in /start and follow the prompts to enter your code

[tis24dev]

Replying because I am in same situation. It also says run @proxmoxan_bot to put in the id for telegram but it doesn't say where to run it. A step by step setup guide with example at least for the env config file would be amazingly helpful.

Hello! Yes, the documentation will be improved in the future. We are currently rewriting the code, which is taking a lot of time, but we will endeavour to improve the documentation as soon as possible!
Please let me know if you were able to activate the bot after @molnarti 's explanation.

[tis24dev]

I have just discovered this tool and its pretty much what i was looking for (and hoping PBS would support it once, since its on their roadmap for quite some time). However I am struggling to set this up properly:

where do i configure the backup location?

backups are currently made to /opt/proxmox-backup/backup which i find suboptimal for various reasons:

• if my PVE disk fails, backups are lost
• the root partition of all my PVE hosts are set intentionally to just 16 GB which works great for me, but i never intended this to use backups
• i have my NAS NFS share mounted to my proxmox host which would the intended and ideal location for backups

I can see the LOCAL_BACKUP_PATH="${BASE_DIR}/backup" in the config, but dont see where ${BASE_DIR} is configured. i guess i could change this to my mounted remote directory, but in that case it would not be a local backup anymore....

what are secondary and cloud backups?

its also not clear to me how to configure those. maybe by mounted NAS folder should be a secondary storage, but do i need a local primary first to have a secondary one? the env file mentions CLOUD_BACKUP_PATH="/proxmox-backup/backup" but that does not sound like cloud backup location to me. under cloud backup i imagine something like an S3 bucket, which should be supported by rclone, but again its not clear to me how to configure it in proxmox-backup context

Thanks in advance for any help

Hi!
We are improving the script and migrating it to improve all these things.
I will try to answer you in a concise and direct manner:
/env/backup.env contains all the settings you require and which you can modify yourself.
Secondary and cloud are copies of the backup. The script makes a local copy (that's what I thought, but you can change the path and save it wherever you want). It is designed to be local to minimise the risk of problems.
If you enable the secondary path and the cloud path, copies and rotations will be made on those files to secure the backups and logs.

PS: important note, if you enable the secondary/cloud path, also write the path for the secondary/cloud logs (it can be the same path), otherwise it will be disabled.

Try it and let me know if I have explained it correctly. Please let me know if you need any further information!

[molnarti]

thanks for the explanation. most of my confusion came from the "local" backup. but i now understand this rather a "primary" backup that can be placed anywhere.
however, cloud backup is still unclear to me. from the .env file it looks like just another local path. can i configure some remote servers here? if yes, what protocols are supported and what is the syntax?

[tis24dev]

cloud use rclone,
You must configure your rclone by connecting it to your personal cloud and writing the name you gave to that configuration in the backup.env configuration file, linking this script to your rclone configuration.

[tismofied]

I had truenass permissions issue. All sorted for now. Thank you!