Compare commits
No commits in common. "3152096ed05e0e917e2c2845541b119927a2a155" and "ea1a07ef580ce15f06f908f3a89b86999afeb9f8" have entirely different histories.
3152096ed0
...
ea1a07ef58
@ -1,58 +0,0 @@
|
|||||||
# amanda-client
|
|
||||||
|
|
||||||
## DESCRIPTION
|
|
||||||
|
|
||||||
A container for running an amanda-client of the [Amanda](https://amanda.org] project
|
|
||||||
within a containerized environment. This image is based on Debian:stable-slim.
|
|
||||||
|
|
||||||
The image contains the minimal set of tools to run amanda-client and the client
|
|
||||||
software is compiled from the latest stable release available at the time of build.
|
|
||||||
|
|
||||||
The container starts an inetd daemon that listens for connections and starts the amanda-client.
|
|
||||||
It is **always** running as the user *backup*. This can not be changed at runtime only by
|
|
||||||
creating an image of your own.
|
|
||||||
|
|
||||||
## Authentication
|
|
||||||
|
|
||||||
This container only supports authentication via SSL certificates.
|
|
||||||
|
|
||||||
**The container does not create any certificates**
|
|
||||||
|
|
||||||
Certificates have to be provided by mounting a volume containing the certificate and key files:
|
|
||||||
|
|
||||||
- mount the ca certificate file as `/usr/local/etc/amanda/ssl/CA/crt.pem`
|
|
||||||
- mount the client certificate file as `/usr/local/etc/amanda/ssl/me/crt.pem`
|
|
||||||
- mount the client key file as `/usr/local/etc/amanda/ssl/me/private/key.pem`
|
|
||||||
|
|
||||||
Amanda also requires an authorization file which amanda-servers are allowed to connect to each client.
|
|
||||||
|
|
||||||
- mount an amandahosts file as `/var/backups/amandahosts`
|
|
||||||
|
|
||||||
A Typical amandahosts file looks like this:
|
|
||||||
|
|
||||||
'''
|
|
||||||
amanda-server-kslave-amd6401.amanda.svc.cluster.local backup noop, selfcheck, sendsize, sendbackup, amdump
|
|
||||||
'''
|
|
||||||
|
|
||||||
## USAGE
|
|
||||||
|
|
||||||
You have to mount all volumes which should be backupd by Amanda into the container. For kubernetes
|
|
||||||
you have to run one amanda-client container per namespace and mount all PhysicalVolumeClaims for that namespace into the container.
|
|
||||||
|
|
||||||
The path to this PVC has to be used within the amanda-servers disklist.
|
|
||||||
|
|
||||||
There are no environment variables for running the client. You just mount all the required
|
|
||||||
files and start the container.
|
|
||||||
|
|
||||||
## Project Websites
|
|
||||||
|
|
||||||
- [Issues & Roadmap](https://rm.byterazor.de/projects/kumanda)
|
|
||||||
- [Git Repository](https://gitea.federationhq.de/Kubernetes/Kumanda)
|
|
||||||
|
|
||||||
## Authors
|
|
||||||
|
|
||||||
- Dominik Meyer <dmeyer@federationhq.de>
|
|
||||||
|
|
||||||
## License
|
|
||||||
|
|
||||||
GPLv3
|
|
@ -1,13 +1,8 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
|
|
||||||
if [ -z ${AMANDA_CONFIG} ]; then
|
amcleanup -k server
|
||||||
echo "it set best practise to set the AMANDA_CONFIG environment variable"
|
amcheck server
|
||||||
AMANDA_CONFIG="server"
|
amdump server
|
||||||
fi
|
amstatus server
|
||||||
|
|
||||||
amcleanup -k ${AMANDA_CONFIG}
|
|
||||||
amcheck ${AMANDA_CONFIG}
|
|
||||||
amdump ${AMANDA_CONFIG}
|
|
||||||
amstatus ${AMANDA_CONFIG}
|
|
||||||
|
|
||||||
exit 0
|
exit 0
|
Loading…
Reference in New Issue
Block a user