Bestway to backup aptly

[Paul]

Hi,
we have multiple local repos, published as components locally and to s3.

Currently I´m wondering if the s3 publish is enough as a "backup strategy". Or if there are some best practices what exactly and how to backup the repository?

Best regards,
Paul

[Andrey Smirnov]

Paul, you can always backup aptly root with anything which can detect and correctly backup/restore hardlinks (just filesystem contents)

--
You received this message because you are subscribed to the Google Groups "aptly-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aptly-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pfei...@sensape.com]

Hi Andrey,

Thank you for your reply!
I saw the following thread:
https://groups.google.com/forum/#!topic/aptly-discuss/ah9xS-Knoa0

So if I understand it correctly, I can also restore everything from our s3-repository. Is this probably enough as a backup solution (to publish it to the s3 and restore everything from it if needed)? Or do I need to back up some additional (maybe meta-) files?

[Andrey Smirnov]

Paul, it depends on the flows. Published repository would only allow you to restore set of published packages broken down into mirrors. If you want to restore more (say, snapshot history), backing up aptly root is required.

[Dmytro Heorhin]

Hi guys,

We have Aptly hosted on Azur virtual machine; we are using FILESYSTEM PUBLISHING to copy the files to a mounted disc (which is Azure storage independent on a VM with Aptly) - this is our backup strategy. In the future, we are considering multiple VMs with Aptly instances.

Is there any other recommended way of backup for this case?

Thanks,

Dima