Re: Amanda clients running Docker
Hello, On Tue, 2018-03-27 at 15:12 +, 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.
Exclude list and tar on SUSE OES.
Hello,
I've been struggling with this for a while. I have this defined in lots
of places now:
exclude list /usr/local/amanda/exclude.conf
e.g.
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/amanda/exclude.conf
priority low
}
but it doesn't create the right command :
/bin/tar --create --file /dev/null --directory / --one-file-system
--listed-incremental /var/lib/amanda/gnutar-lists/localhost__0.new
--sparse --ignore-failed-read --totals .
at the client.
Help?
Thanks,
Owen.
Re: Exclude list and tar on SUSE OES.
Bert, You did put the exclude file on the client, didn't you ? http://www.amanda.org/docs/exclude.html#id2533384 Thanks, but yes. Owen. -- Owen Williams [EMAIL PROTECTED] Work0116 2506349 Home0116 2259109 Mobile 0771 5790631 Senior Computing Officer | Software Engineer Consultant | RedHat Certified Engineer DMU Libraries http://www.blue.dmu.ac.uk/
Using DRDB and disks for tapes.
Hello, Its probably too wacky but has anyone tried setting up DRDB (http://www.drbd.org/) or similar combined with disks instead of tapes to create a simultaneous offsite backup? From the DRDB site: DRDB can be seen as 'Network RAID 1.' A colleague and I are thinking of getting two large RAID arrays keeping one in his machine room and one in mine in different buildings. Then split them in two with DRDB running in pairs on the four partitions. Is there another device in Amanda to do the same thing? Thanks, Owen. -- Owen Williams [EMAIL PROTECTED] Work0116 2506349 Home0116 2259109 Mobile 0771 5790631 Senior Computing Officer | Software Engineer Consultant | RedHat Certified Engineer DMU Libraries http://www.blue.dmu.ac.uk/
Re: Using DRDB and disks for tapes.
A colleague and I are thinking of getting two large RAID arrays keeping one in his machine room and one in mine in different buildings. Then split them in two with DRDB running in pairs on the four partitions. Unless you have 100Bt or better between your machine rooms, you may find that this is quite slow. I'd do some replication benchmarks before doing a full implementation. ;) I'm just hoping the DRDB solution finishes before the rsync one would. The rysnc might bite into core network hours because it starts after amanda has finished. In someways after its setup the DRDB solution will be cleaner than rsync because we'll only be dealing with Amanda. Rysnc would need some sort of wrapper to handle errors. I'm going to do some tesing though. :) Owen.
iptables and ip_conntrack_amanda
Hi, I've just upgraded one of my clients to Fedora Core 2, 2.6.6-1.435.2.3smp and want to try ip_conntrack_amanda (if its even appropriate). Does anyone have an example for /etc/sysconfig/iptables? Thanks, Owen.
Re: Amanda with TL890 tape library on RedHat Linux 8.0
Leonid, I've attached the configs I used on Compaq ML370, TL891, DLT8000. You need mtx installed too. As an aside: If anyone thinks there's glaring mistakes in my setup... Its been working well enough for me stop paying for Arkeia though :) Owen. On Fri, 17 Jan 2003, Leonid Mamtchenkov wrote: Dear All, I'd like to ask if anyone managed to configure amanda to work with TL890 (specifically TL892) tape library on RedHat Linux 8.0. I have tried to use both chg-scsi and chg-multi, but failed with both. chg-scsi did better though. I could load a tape from any slot to a tape drive, label it and perform the backup. But I could not move the tape back to the slot and/or load another tape. amtape kept telling me that the tape was ejected from the DLT drive, but LED display on the library indicated that the tape was still in. chg-multi gave me even more problems. It locks the SCSI devices and amanda operations (as well any other software operating with SCSI) hangs. According to LED display on the library there is no activity what-so-ever. Round-up of what I am using: Hardware: Compaq Proliant DL360 w/ PIII/800MHz x 2 SCSI storage controller: LSI Logic / Symbios Logic (formerly NCR) 53c875 Compaq StorageWorx TL892 10-slot tape library w/ Compaq StorageWorx DLT7000 tape drive x 2 attached Software: RedHat Linux 8.0 with all updates (including kernel: 2.4.18-19.8.0) amanda-2.4.2p2-9 mt-st-0.7-6 Related messages in /var/log/messages: Jan 17 12:09:14 backupsrv kernel: sym53c875-1-5,*: FAST-10 WIDE SCSI 20.0 MB/s (100.0 ns, offset 15) Jan 17 12:09:17 backupsrv last message repeated 3 times If any other information is needed, please let me know. Any ideas and suggestions are very much appreciated. -- Owen Williams Senior Computing Officer [EMAIL PROTECTED]Software Engineer Work0116 2506349 Web Consultant Home0116 2259109 RedHat Certified Engineer Mobile 0771 5790631 DMU Libraries http://www.blue.dmu.ac.uk/ # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /etc/amanda/csd/amanda.conf. # org Blue # your organization name for reports mailto# space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 8# maximum dumpers that will run in parallel netusage 10 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 1 weeks # the number of days in the normal dump cycle runspercycle 4 # the number of amdump runs in dumpcycle days tapecycle 9 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 40 Mb # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 2 # number of tapes to be used in a single run of amdump tpchanger chg-scsi# the tape-changer glue script tapedev 0
DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/outputerror
Hi,
I've just started using Amanda, hoping/praying I can move away
from Arkeia, wish I still had ADSM. Anyway...
First a contribution, I haven't seen it anywhere else:
define tapetype DLT8000 {
comment Compaq DLT8000 (from tapetype)
length 38119 mbytes
filemark 32 kbytes
speed 2071 kps
}
Everything seems setup OK. The network connections are all working.
Two things though:
WARNING: info file /etc/amanda/Blue/curinfo/node3/_boot/info:
does not exist
WARNING: info file /etc/amanda/Blue/curinfo/node3/_/info: does
not exist
WARNING: info file /etc/amanda/Blue/curinfo/node4/_usr1/info:
does not exist
WARNING: info file /etc/amanda/Blue/curinfo/node4/_boot/info:
does not exist
.
.
.
This will probably go away when I start backing things up???
The second is that I get problems using tapes from 'slot 9' of my
10 slot library. I have a cleaning tape in the tenth. I have
two tape drives. I get:
amcheck-server: slot 9: rewinding tape: Input/output error
I got this first with amlabel. I configured amanda to use the
other drive. I cleaned both drives and tried a new tape in 'slot
9' but I still get the 'rewinding input/output' error.
I'm loathed to start backing things up while it still complains.
Any help would be much appreciated.
Owen.
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/outputerror
Hi, I got bitten by this when using arkeia, hoped I didn't this time. My confs are attached and here is the output from mtx status: # mtx status Storage Changer /dev/changer:2 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A0 Storage Element 2:Full :VolumeTag=A1 Storage Element 3:Full :VolumeTag=A2 Storage Element 4:Full :VolumeTag=A3 Storage Element 5:Full :VolumeTag=A4 Storage Element 6:Full :VolumeTag=A5 Storage Element 7:Full :VolumeTag=A6 Storage Element 8:Full :VolumeTag=A7 Storage Element 9:Full :VolumeTag=A8 Storage Element 10:Full :VolumeTag=C0 Thanks for the very rapid response, Owen. # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /etc/amanda/csd/amanda.conf. # org Blue # your organization name for reports mailto [EMAIL PROTECTED] # space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 2# maximum dumpers that will run in parallel netusage 1000 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 1 weeks # the number of days in the normal dump cycle runspercycle 1 weeks# the number of amdump runs in dumpcycle days tapecycle 9 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 40 Mb # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be used in a single run of amdump tpchanger chg-scsi# the tape-changer glue script tapedev 0 # the no-rewind tape device to be used #rawtapedev /dev/null # the raw device to be used (ftape only) #changerfile /var/lib/amanda/DailySet1/changer #changerfile /var/lib/amanda/DailySet1/changer-status changerfile /etc/amanda/Blue/chg-scsi.conf #changerdev /dev/sg0 tapetype DLT8000# what kind of tape it is (see tapetypes below) labelstr ^[AC][0-9][0-9][0-9][0-9][0-9]$ # label constraint regex: all tapes must match # Specify holding disks. These are used as a temporary staging area for # dumps before they are written to tape and are recommended for most sites. # The advantages include: tape drive is more likely to operate in streaming # mode (which reduces tape and drive wear, reduces total dump time); multiple # dumps can be done in parallel (which can dramatically reduce total dump time. # The main disadvantage is that dumps on the holding disk need to be flushed # (with amflush) to tape after an operating system crash or a tape failure. # If no holding disks are specified then all dumps will be written directly # to
