Hello,
On Tue, 2018-03-27 at 15:12 +0000, Joi L. Ellis wrote:
I’m looking for information about how best to manage Amanda clients upon which
are Devs are running docker containers. Some of the production hosts are also
running containers. Does anyone have suggestions regarding best practices for
backing up docker containers in an Amanda environment? (I don’t use docker and
I haven’t found anything online discussing containers on Amanda clients.)
Any pointers, suggestions, or online references would be very welcome.
Un-orchestrated Docker will have a file ending .yml on the host. In that, you
can expose the part of the filesystem that needs to be backed up by Amanada.
Such as:
volumes:
-
/usr1/home/williams/Dev/docker-availablepcs/plugins:/var/www/html/wp-content/plugins
I'm pretty sure you don't want to take the route of installing the Amanda
client in the container but you could and then use the same .yml to expose the
client port in the container to the host. Allow that port on the host to be
reached by the Amanda server and then model your disklist on that.
Orchestrated Docker should allow you to expose the filesystem to the host for
all Docker containers quite easily.
Depending on what you are backing up already, you might get the Docker
container image for free. On my GNU/Linux box the containers are in
/var/lib/docker/.
Best regards,
Owen.
