I have a strange issues with amanda backup.
I'm using amanda 3.3.7, LTO 6 tapes and the single tape drive.
Size of backup varies between 1 - 1.5 TB.
backup-server is a server which has:
- tape drive connected
- staging space of a size 100GB
[amandabackup@backup-server /]$ df -h /amdumps/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_rootvg-lv_amdumps
106G 60M 101G 1% /amdumps
- /backup nfs filesystem used for clients to backup their data
[amandabackup@backup-server /]$ df -h /backup/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/backupvg-backuplv
1.4T 1.2T 130G 91% /backup
Quite often backup fails with the errors:
FAILURE DUMP SUMMARY:
backup-server /backup lev 0 FAILED [data write: Broken pipe]
backup-server /backup lev 0 partial taper: No space left on device,
splitting not enabled
backup-server /backup lev 0 FAILED [data write: Broken pipe]
backup-server /backup lev 0 FAILED 1 tapes filled; runtapes=1 does not
allow additional tapes
It looks strange as there should be plenty space left on the tape (LTO6 -
2.5TB for uncompressed and 6.25 TB for compressed).
Other issue is that this backup-server:/backup filesystem is the biggest one
and it is backed up directly to the tape without using holding disk.
The issues here is that despite the settings that I have in amanda.conf:
inparallel 10 # maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
dumporder "ssssssssss" # specify the priority order of each dumper
# s -> smallest size
# S -> biggest size
# t -> smallest time
# T -> biggest time
# b -> smallest bandwitdh
# B -> biggest bandwitdh
# try "BTBTBTBTBTBT" if you are not holding
# disk constrained
taperalgo first # The algorithm used to choose which dump image to
send
# to the taper.
# Possible values:
[first|firstfit|largest|largestfit|smallest|last]
# Default: first.
# first First in - first out.
# firstfit The first dump image that will fit
on the current tape.
# largest The largest dump image.
# largestfit The largest dump image that will fit
on the current tape.
# smallest The smallest dump image.
# last Last in - first out.
It is sent to the taper as a first one and other client's backups are
waiting in the holding disk area while it finishes.
And if the backup of backup-server:/backup fails - other clients won't be
backed up at all.
So my question to experts here is:
1) How to make backup of the 1TB backup-server:/backup filesystem to
the tape on backup-server more reliable
2) How to force amanda to put the backup-server:/backup filesystem at
the end of the queue to the taper?
Kind Regards,
Dmitry
--
Disclaimer: Asparona is part of the Deloitte group of companies. Deloitte
refers to the New Zealand member firm of Deloitte Touche Tohmatsu Limited.
The information contained in this document is confidential to the
addressee(s) and may be legally privileged. Any view or opinions expressed
are those of the author and may not be those of the organisation to which
the author belongs. No guarantee or representation is made that this
communication is free of errors, viruses or interference. If you have
received this e-mail message in error please delete it and notify me.
