On 11/15/18 2:49 PM, Chris Hoogendyk wrote: > This > <https://wiki.zmanda.com/index.php/Backup_client_(old)#Chris_Hoogendyk.27s_Example> > is a bit dated, but may give you an idea of how to attack it. However, > it could be that with the api work that Dustin did there is a better way > of doing this with the newer versions of Amanda.
Yes, it sounded to me as if this was a question for the Application / Script API. Amanda has very flexible support for letting you write a script that can turn whatever-you've-got into a stream of bytes in any way that makes sense, and turn a stream of bytes back into whatever-it's-supposed-to-be, and Amanda will use that for backups, and store the byte streams away, and amrecover will fetch the bytes back and use your app/script to turn them back into whatever-it's-supposed-to-be. The API in the current released versions has a kind of steep learning curve. There is an open pull request aimed at making it much easier to use: https://github.com/zmanda/amanda/pull/78 The pull request also includes several more example apps and scripts, for things like backing up filesystems on LVM using snapshots, making consistent hot backups of Subversion repositories or 389 Directory Server instances, another approach to ZFS backups where some other process is creating regular snapshots and Amanda just works from those, etc. The examples should give a good sense of what can be built when the API is easy enough to work with. The docs for those examples are here: https://github.com/zmanda/amanda/files/1265069/AppScriptWithAbstractClasses.pdf -Chap
