Backup aptly local repos

[Tom Denley]

We are using aptly to manage a few local repositories.  I wondered what you would recommend as a backup strategy?

Currently I'm considering using rsync for the rootDir/db and rootDir/pool directories and leaving rootDir/public behind.  A restore could then recreate the public directory with aptly publish update.  This avoids any problems with rsync and hard links, which I assume aptly uses.  Does aptly use any hard links within the rootDir/pool directory?

Does this seem like a sane backup strategy, or is there a better solution?

[Andrey Smirnov]

Hi Tom!

Yes, your strategy should be ok. rootDir/db and rootDir/pool should be enough to recreate all your local repos. You might have to drop and recreate all your published repositories to restore from backup.

rootDir/public contains metadata files (Release, Packages, ...) which should be relatively small and hardlinks to rootDir/pool. rsync might fail to handle them correctly unpredictably.

--
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.

--
Andrey Smirnov,
+79261724320

[mauro...@digital.cabinet-office.gov.uk]

Hi Tom, Andrey,

I understood I need to copy /db and /pool, but how can I recreate all my repos and relative snapshots from these two directories?

Thanks

[Andrey Smirnov]

So if you've got /db and /pool, it means that aptly internal DB and package pool is there.

So you can once again publish all your repos. In fact, `aptly publish list` will give you the list of things which were published.