We can manually export our backups, but ideally I'd love to be able to have a copy tucked away somewhere reachable in case there are issues reaching Unimus. (Which has happened to me where I lost a couple switches and I couldn't' log into Unimus to get the configs.
1) Schedule exports on a hourly, daily, weekly basis etc
2) Rotation of the exports if possible
3) Options should include FTP S3 Google Drive, etc
4) Option to encrypt or password protect the zip. (Just a bonus)
Export to S3 / Google Drive etc
So, as a preface, this shouldn’t be treated as a “backup of Unimus”, the files that are exported lose a lot of the contextual information Unimus needs for tracking backups. If you want to do a proper backup of your Unimus install we recommend backing up your database. That will give you everything stored in your Unimus instance and you can restore with just the encryption key you used during setup.
Secondly, we are always working on feature requests, but the Devs are swamped at the moment, BUT!!! You can implement most of your features (especially the backing up on a schedule) through the API and utilizing some scripting.
We already have https://blog.unimus.net/unimus-backup-exporter/ which get’s you the majority of the features you are looking for.
Regarding your specific points:
1. We have in the requests queue some features for exporting to folder. Export on schedule is another feature we are considering and what that would look like.
2. Rotation of files is difficult and one of the considerations for us when it comes to export on schedule. I will let you know where that falls in the Dev’s priority list
3. Also on the considerations list. Keep in mind that we already have the Unimus-backup-exporter post.
4. I will talk to the Devs about what we might be able to do in that regard. Probably not a round 1 feature, especially since it makes you fiddle with the file before you can use it. Probably better to save to an encrypted storage system. I will chat with the Devs though and see what they say.
Secondly, we are always working on feature requests, but the Devs are swamped at the moment, BUT!!! You can implement most of your features (especially the backing up on a schedule) through the API and utilizing some scripting.
We already have https://blog.unimus.net/unimus-backup-exporter/ which get’s you the majority of the features you are looking for.
Regarding your specific points:
1. We have in the requests queue some features for exporting to folder. Export on schedule is another feature we are considering and what that would look like.
2. Rotation of files is difficult and one of the considerations for us when it comes to export on schedule. I will let you know where that falls in the Dev’s priority list
3. Also on the considerations list. Keep in mind that we already have the Unimus-backup-exporter post.
4. I will talk to the Devs about what we might be able to do in that regard. Probably not a round 1 feature, especially since it makes you fiddle with the file before you can use it. Probably better to save to an encrypted storage system. I will chat with the Devs though and see what they say.
I'm sorry I didn't mean a full Unimus backup. Just the backups. I have the server virtualized so it is already backed up regularly as a whole.
I'm talking about when the network is down, and we can't reach Unimus to get a config, it would be nice if the export was already automatically copied to another location. So any computer with credentials can log into their system to get a copy of the configs.
Even if it were automatically exported daily to a local directory, I could just set up an RSYNC script to move it out. But taking it one step further would be needing to install aws cli to move to S3 or other external providers.
But having it all copy to a directory on the server such as /backups and there were a fridayexport.zip thursdayexport.zip etc that rotated would be a good start.
I'll check out that 3rd party exporter though. Thanks.
I'm talking about when the network is down, and we can't reach Unimus to get a config, it would be nice if the export was already automatically copied to another location. So any computer with credentials can log into their system to get a copy of the configs.
Even if it were automatically exported daily to a local directory, I could just set up an RSYNC script to move it out. But taking it one step further would be needing to install aws cli to move to S3 or other external providers.
But having it all copy to a directory on the server such as /backups and there were a fridayexport.zip thursdayexport.zip etc that rotated would be a good start.
I'll check out that 3rd party exporter though. Thanks.
The exporter is not 3rd party, it is written and maintained by us. It's just an external application (Bash and/or PowerShell script) so you can run in anywhere (meaning even other hosts than Unimus for off-site backup of the backups in Unimus), as it just connects to the API.
The Exporter will do exactly what you described
We do still plan to develop a larger more complex export feature-set in Unimus itself, but that will take some time, as we want it to be fully configurable as to what, where and how it exports (think automated exports of Backups, Config Searches, Config Push results, or all the data in Unimus itself).
Since that will be a large and complex feature, the Exporter for now serves as a tool to export Device Backups out of Unimus for off-site / emergency access (or to sync backups to GIT) - which if I understand is exactly what you need.