remove
Re: Amanda stop working after amflush
On Fri, Jul 04, 2003 at 10:19:31AM +0100, Angie Yee wrote:
> Hello there,
>
> I have a problem with the amanda backup.
>
> Amanda is totally stop working after I amflush all the logfiles in
> /usr/am_dump.
?Logfiles? I presume you mean dump files.
Why did you have to amflush them?
Did you get a good report from amflush?
> When I execute amcleanup, the messages shown as below:
> amcleanup: no unprocessed logfile to clean up.
> Scanning /usr/am_dump...
Why did you have to do an amcleanup?
> When I execute amcheck, here is the message:
> Amanda Tape Server Host Check
> -
> Holding disk /usr/am_dump: 6291244 KB disk space available, that's plenty
> NOTE: skipping tape-writable test
> Tape fs3_3 label ok <***I have put this tape on Wednesday and this is
> still OK on Friday!!!***
Yes, but have any amdumps run since then?
What did your amdump reports say?
> Server check took 3.831 seconds
>
> Amanda Backup Client Hosts Check
>
> Client check: 1 host checked in 0.033 seconds, 0 problems found
>
> When I execute amrecover, here is the message:
> AMRECOVER Version 2.4.2p2. Contacting server on fs3 ...
> 220 fs3 AMANDA index server (2.4.2p2) ready.
> 200 Access OK
> Setting restore date to today (2003-07-04)
> 200 Working date set to 2003-07-04.
> 200 Config set to FS3.
> 200 Dump host set to fs3.
> Can't determine disk and mount point from $CWD
>
> Then I setdisk to /vol0, the error message is:
> Scanning /usr/am_dump...
> 200 Disk set to /vol0.
> No index records for disk for specified date
> If date correct, notify system administrator
Maybe there were no amdumps between Tuesday 7/1
and 7/4. Thus there were no index records for 7/4.
What if you set the date to earlier?
> Please find an attachment of amanda.conf file. Would you please advise
> where is it gone wrong?
I'd rather see the reports. But looking at your first few lines
of amanda.conf I suspect you are not getting any.
> org "abc"# your organization name for reports
Is that the name of your organization?
> mailto "[EMAIL PROTECTED]" # space separated list of operators at your site
Is that your email address?
You can't get the reports mailed to you if it is not.
> dumpuser "root" # the user to run dumps under
Do you really run your dumps as root? Most don't.
> dumpcycle 2 weeks
> runspercycle 10
> tapecycle 10 tapes
DANGER! DANGER! DANGER! tapecycle equals runspercycle
> runtapes 1 # number of tapes to be used in a single run of amdump
> tapedev "/dev/nst0" # the no-rewind tape device to be used
> rawtapedev "/dev/null" # the raw device to be used (ftape only)
>
> tapetype DLT# what kind of tape it is (see tapetypes below)
> labelstr "^fs3_[0-9]" # label constraint regex: all tapes must match
this won't allow for tapes numbered with more than one digit.
>
> holdingdisk sda5 {
> comment "main holding disk"
> directory "/usr/am_dump"# where the holding disk is
> use 3 Gb# how much space can we use on it
> chunksize 1Gb # size of chunk if you want big dump to be
> }
>
> # reserve 30 # percent
You are not using your holding disk unless you set a reserve value.
The default is to reserve all of the holding disk for degraded mode.
> infofile "/usr/am_log/FS3/curinfo" # database DIRECTORY
> logdir "/usr/am_log/FS3" # log directory
> indexdir "/usr/am_log/FS3/index"# index directory
Just to be sure, /usr/am_log/FS3/ is where your amanda.conf file is?
> define tapetype DLT {
> comment "DLT tape drives"
> length 35025 mbytes # 80 Gig tapes
> filemark 2528 kbytes# I don't know what this means
> speed 2534 kbytes # 1.5 Mb/s
> }
>
>
> # dumptypes
which are you using?
>
> define dumptype global {
> comment "Global definitions"
> index yes
> }
>
> define dumptype always-full {
> global
> comment "Full dump of this filesystem always"
> compress none
> priority high
> index yes
> dumpcycle 0
> }
>
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> index yes
> exclude list "/usr/local/lib/amanda/exclude.gtar"
> priority low
> }
>
> define dumptype user-tar {
> define dumptype user-tar {
This doesn't look right. Is it in your amanda.conf like that?
> root-tar
> comment "user partitions dumped with tar"
> index yes
> priority medium
> }
>
> define dumptype high-tar {
> root-tar
> comment "partitions dumped with tar"
> index yes
> priority high
> }
>
> define dumptype comp-root-tar {
> root-tar
> comment "Root partitions with compression"
> compress client fast
> index yes
> }
>
> define dumptype comp-user-tar {
> user-tar
> compress client fast
> index yes
> }
>
> define dumptype holding-disk {
Re: using same tape again?
I see the problem, I must have messed up these numbers when I was copying the config from my other machine. I changed the numbers so that they make sense now: was > > 20306290 DailySet103 reuse now > > 20030629 DailySet103 reuse thanks On Fri, Jul 04, 2003 at 02:39:46PM -0400, Eric Siegerman wrote: > On Fri, Jul 04, 2003 at 11:00:26AM -0700, Scott Petler wrote: > > > > I am using amanda to back up to a second hard disk. I get the > > following message: > > > > These dumps were to tape DailySet101. > > ^^^ > > *** A TAPE ERROR OCCURRED: [[writing file: No space left on device]]. > > Some dumps may have been left in the holding disk. > > Run amflush to flush them to tape. > > The next tape Amanda expects to use is: DailySet101. > > ^^^ > > > > Why is it going to use the same "tape" again? > > [...] > > * > > tapelist *** > > * > > > > 20030704 DailySet101 reuse > > [...] > > 20306290 DailySet103 reuse > > 20306290 DailySet102 reuse > > I'm not sure whether this is it, but ... DailySet102 and the rest > aren't due to expire for 27 years or so... It seems a bit odd to > me that Amanda would be willing to reuse DailySet101 in this > case, instead of complaining, but that's another question. > > -- > > | | /\ > |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] > | | / > When I came back around from the dark side, there in front of me would > be the landing area where the crew was, and the Earth, all in the view > of my window. I couldn't help but think that there in front of me was > all of humanity, except me. > - Michael Collins, Apollo 11 Command Module Pilot
Re: using same tape again?
On Fri, Jul 04, 2003 at 11:00:26AM -0700, Scott Petler wrote: > > I am using amanda to back up to a second hard disk. I get the > following message: > > These dumps were to tape DailySet101. > ^^^ > *** A TAPE ERROR OCCURRED: [[writing file: No space left on device]]. > Some dumps may have been left in the holding disk. > Run amflush to flush them to tape. > The next tape Amanda expects to use is: DailySet101. > ^^^ > > Why is it going to use the same "tape" again? > [...] > * > tapelist *** > ***** > > 20030704 DailySet101 reuse > [...] > 20306290 DailySet103 reuse > 20306290 DailySet102 reuse I'm not sure whether this is it, but ... DailySet102 and the rest aren't due to expire for 27 years or so... It seems a bit odd to me that Amanda would be willing to reuse DailySet101 in this case, instead of complaining, but that's another question. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
using same tape again?
localhost /tools hard-disk-tar localhost /usr hard-disk-tar localhost /var hard-disk-tar * tapelist *** * 20030704 DailySet101 reuse 20306300 DailySet114 reuse 20306300 DailySet113 reuse 20306290 DailySet112 reuse 20306290 DailySet111 reuse 20306290 DailySet110 reuse 20306290 DailySet109 reuse 20306290 DailySet108 reuse 20306290 DailySet107 reuse 20306290 DailySet106 reuse 20306290 DailySet105 reuse 20306290 DailySet104 reuse 20306290 DailySet103 reuse 20306290 DailySet102 reuse
Re: missing backup data
James Williamson wrote: I've been doing some more experimenting / research and it looks like it's a blocksize issue. If I check the status of the drive it reports that the blocksize is 512 bytes. That is a fixed blocksize (as opposed to variable blocksize). 'man amanda' (2.4.3) says the default block size is 32KB with the minimum being 32KB and the maximum being 32KB so I've arrived at the This means that amanda will do write()'s with a blocksize of 32k. If your tapedrive were set to variable blocksize, that would be blocksize on the tape. But you are using a fixed blocksize of 512 bytes. Now the kernel will "reblock" automatically the 32k amanda writes in 512 byte blocks on tape. I don't really understand the what the block size means / does, there doesn't appear to be much info in the man pages / docs. I'd apprecate any help. The nice thing about open software is that you can read the source, or, if that's too complicated (like for me), you can at least read the comments about in it. Read the comments in: /usr/src/linux/drivers/scsi/README.st I had to read it several times before I understood it, but it helped a lot. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: repost (still need some help) :-)
On Friday 04 July 2003 10:20, Mikkel Gadegaard wrote: >I had amanda up and running only to discover that the machine acting > as host didn't have enough HD capacity to run Amanda smoothly. The > project layed low for several weeks until I got hold of a new and > bigger machine. > >Installed RedHat 9.0 on it and installed amanda and mtx > >started configuring everything as I remember doing it the last time, > but now I've run into problems (So I obviously couldn't remember it > :-) > [...] >tpchanger "chg-zd-mtx" # the tape-changer glue > script tapedev "/dev/nst0" # the no-rewind > tape device used >changerfile "/var/lib/amanda/BackUp/changer" # path to changer.conf >changerdev "/dev/sg2"# the changer device > used I believe you have the 'tapedev' specified wrong. At least when using chg-scsi, that is a number only that points to the config number in chg-scsi.conf because it can contain more than one changers configuration info, therefore its the config number. In my case its the first and only, but thats beside the point. It looks like this in amanda.conf: tpchanger "chg-scsi" # the tape-changer glue script tapedev "0" # the no-rewind tape device to be used changerfile "/usr/local/etc/amanda/DailySet1/chg-scsi.conf" And of course make sure you are using a consistent name for the changer.conf file. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: repost (still need some help) :-)
- Original Message -
From: Mikkel Gadegaard
To: [EMAIL PROTECTED]
Sent: Friday, July 04, 2003 3:20 PM
Subject: repost (still need some help) :-)
I had amanda up and running only to discover that the machine acting as host
didn't have enough HD capacity to run Amanda smoothly. The project layed low
for several weeks until I got hold of a new and bigger machine.
Installed RedHat 9.0 on it and installed amanda and mtx
started configuring everything as I remember doing it the last time, but now
I've run into problems (So I obviously couldn't remember it :-)
a mtx -f /dev/sg2 status gives me the following:
# mtx -f /dev/sg2 status
Storage Changer /dev/sg2:1 Drives, 19 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full :VolumeTag=01L1
Storage Element 2:Full :VolumeTag=02L1
Storage Element 3:Full :VolumeTag=03L1
Storage Element 4:Full :VolumeTag=04L1
Storage Element 5:Full :VolumeTag=05L1
Storage Element 6:Full :VolumeTag=06L1
Storage Element 7:Full :VolumeTag=07L1
Storage Element 8:Full :VolumeTag=08L1
Storage Element 9:Full :VolumeTag=09L1
Storage Element 10:Full :VolumeTag=10L1
Storage Element 11:Full :VolumeTag=11L1
Storage Element 12:Full :VolumeTag=12L1
Storage Element 13:Empty:VolumeTag=
Storage Element 14:Empty:VolumeTag=
Storage Element 15:Empty:VolumeTag=
Storage Element 16:Empty:VolumeTag=
Storage Element 17:Empty:VolumeTag=
Storage Element 18:Full :VolumeTag=
Storage Element 19:Empty:VolumeTag=
I can load and unload tapes with mtx -f /dev/sg2 load/unload without
problems.
My amanda.conf looks like this:
#
# amanda.conf - configurtaion file for backup routines at Videlity A/S.
# Augmented from the sample amanda.conf provided by CS.UMD.EDUpe is used
(see below for tapetypes)
# belstr "^VidelityBackUp[0-9][0-9]*$" # label constraint regex: all
tapes must match
# This amanda.conf should be placed in /etc/amanda/BackUp/amanda.conf
#
# Next part defines the holding disks which is the part of the harddisk
amanda uses to store
org "BackUp" # Name of BackUp scheme
#
mailto [EMAIL PROTECTED]# report status to this adress
dumpuser "root" # The user who should run the
backup
comment "primary holding disk"
inparallel 4 # maximum dumpers that will run
in parallel
netusage 600 Kbps# maximum usage of LAN in KB
per secisk
}
dumpcycle 7 days # Number of days in a dump
cycle
runspercycle 5 days # number of dumb runs in each
cycle
tapecycle 12 tapes # number of tapes in rotation
indexdir "/var/lib/amanda/BackUp/index" # index directory
bumpsize 20 Mb # minimum savings (threshold)
to bump level 1 -> 2
bumpdays 1 # minimum days in each level
bumpmult 4 # threshold = bumbsize *
bumpmult(level-1)
etimeout 300 # number of seconds per
filesystem for estimates
runtapes 1 # number of tapes to be used in
a single run of amdump
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nst0" # the no-rewind tape device
used
changerfile "/var/lib/amanda/BackUp/changer" # path to changer.conf
changerdev "/dev/sg2"# the changer device used
tapetype ultrium1# what kind of tape is used
(see below for tapetypes)
labelstr "^VidelityBackUp[0-9][0-9]*$" # label constraint regex: all
tapes must match
#
# Next part defines the holding disks which is the part of the harddisk
amanda uses to store
# data from a client still not written to tape.
#
holdingdisk hd1 {
comment "primary holding disk"
directory "/backup" # where the holding disk is
use -30 Mb # use all but 30 Mb on the
holding disk
}
infofile "/var/lib/amanda/BackUp/curinfo"# database filename
logdir "/var/lib/amanda/BackUp"# log directory
indexdir "/var/lib/amanda/BackUp/index" # index directory
# tapetypes
define tapetype ultrium1 {
comment "Ultrium1 tapes for Dell PowerVault 128T"
length 103911 mbytes
filemark 524 kbytes
speed 2158 kps
}
define dumptype normal_backup {
compress NONE
index yes
maxdumps 5
program "GNUTAR"
record yes
}
define dumptype client_compression {
normal_backup
compress client fast
}
My changer.conf placed at "/var/lib/amanda/BackUp/changer.conf" looks like
this:
firstslot=1
lastslot=19
cleanslot=18
AUTOCLEAN=0
autocleancount=9
havereader=1
offlinestatus=1
OFFLINE_BEFORE_UNLOAD=0
All this taken from the old
repost (still need some help) :-)
I had amanda up and
running only to discover that the machine acting as host didn't have enough HD
capacity to run Amanda smoothly. The project layed low for several weeks until I
got hold of a new and bigger machine.
Installed RedHat 9.0
on it and installed amanda and mtx
started configuring
everything as I remember doing it the last time, but now I've run into
problems (So I obviously couldn't remember it :-)
a mtx -f /dev/sg2
status gives me the following:
# mtx -f /dev/sg2
status Storage Changer /dev/sg2:1 Drives, 19 Slots ( 0 Import/Export
)Data Transfer Element 0:Empty Storage
Element 1:Full :VolumeTag=01L1 Storage
Element 2:Full :VolumeTag=02L1 Storage
Element 3:Full :VolumeTag=03L1 Storage
Element 4:Full :VolumeTag=04L1 Storage
Element 5:Full :VolumeTag=05L1 Storage
Element 6:Full :VolumeTag=06L1 Storage
Element 7:Full :VolumeTag=07L1 Storage
Element 8:Full :VolumeTag=08L1 Storage
Element 9:Full :VolumeTag=09L1 Storage
Element 10:Full :VolumeTag=10L1 Storage
Element 11:Full :VolumeTag=11L1 Storage
Element 12:Full :VolumeTag=12L1 Storage
Element 13:Empty:VolumeTag= Storage Element
14:Empty:VolumeTag= Storage Element
15:Empty:VolumeTag= Storage Element
16:Empty:VolumeTag= Storage Element
17:Empty:VolumeTag= Storage Element 18:Full
:VolumeTag= Storage Element
19:Empty:VolumeTag=
I can load and
unload tapes with mtx -f /dev/sg2 load/unload without
problems.
My amanda.conf looks
like this:
## amanda.conf - configurtaion file for
backup routines at Videlity A/S.# Augmented from the sample amanda.conf
provided by CS.UMD.EDUpe is used (see below for tapetypes)# belstr
"^VidelityBackUp[0-9][0-9]*$" # label
constraint regex: all tapes must match# This amanda.conf should be placed in
/etc/amanda/BackUp/amanda.conf## Next part defines the holding disks
which is the part of the harddisk amanda uses to storeorg
"BackUp"
# Name of BackUp scheme#mailto me@work.com
# report status to this adressdumpuser
"root"
# The user who should run the backup comment "primary
holding disk"inparallel
4
# maximum dumpers that will run in parallelnetusage 600
Kbps
# maximum usage of LAN in KB per secisk}dumpcycle 7
days
# Number of days in a dump cyclerunspercycle 5
days
# number of dumb runs in each cycletapecycle 12
tapes
# number of tapes in rotationindexdir
"/var/lib/amanda/BackUp/index" # index
directorybumpsize 20
Mb
# minimum savings (threshold) to bump level 1 -> 2bumpdays
1
# minimum days in each levelbumpmult
4
# threshold = bumbsize * bumpmult(level-1)
etimeout
300
# number of seconds per filesystem for estimates
runtapes
1
# number of tapes to be used in a single run of amdumptpchanger
"chg-zd-mtx"
# the tape-changer glue scripttapedev
"/dev/nst0"
# the no-rewind tape device usedchangerfile "/var/lib/amanda/BackUp/changer"
# path to changer.confchangerdev
"/dev/sg2"
# the changer device used
tapetype
ultrium1
# what kind of tape is used (see below for tapetypes)labelstr
"^VidelityBackUp[0-9][0-9]*$" # label
constraint regex: all tapes must match
## Next part defines the holding disks which is
the part of the harddisk amanda uses to store# data from a client still not
written to tape.#
holdingdisk hd1 { comment
"primary holding disk" directory
"/backup"
# where the holding disk is use -30
Mb
# use all but 30 Mb on the holding disk}
infofile
"/var/lib/amanda/BackUp/curinfo" # database
filenamelogdir
"/var/lib/amanda/BackUp"
# log directoryindexdir
"/var/lib/amanda/BackUp/index" # index
directory
# tapetypes
define tapetype ultrium1 {
comment "Ultrium1 tapes for Dell PowerVault 128T" length
103911 mbytes filemark 524 kbytes
speed 2158 kps}
define dumptype normal_backup
{ compress NONE index
yes maxdumps 5 program
"GNUTAR" record yes}
define dumptype client_compression
{ normal_backup compress client
fast}
My changer.conf
placed at "/var/lib/amanda/BackUp/changer.conf" looks like
this:
firstslot=1lastslot=19cleanslot=18
AUTOCLEAN=0autocleancount=9
havereader=1
offlinestatus=1
OFFLINE_BEFORE_UNLOAD=0
All this taken from
the old machine which was working, now to the problems:
amcheck BackUp
gives:
Amanda Tape Server
Host Check--
Re: missing backup data
Thanks for your help, > James Williamson wrote: > > We've got Amanda set up to backup to a Onstream tape driver (SC-30), > > Are you aware there are two "generations" of Onstream tape drives? Yes, I've got the second generation. > > > when we run amdump it reports that it's successully backed up the contents > > of the disklist. > > However, when it comes to try and restore something on the disklist using > > amrecover it reports this error: > > > > EOF, check amidxtapid.debug file on backup. > > amrecover: short block 0 bytes > > UNKNOWN file > > amrecover: Can't read file header > > > > I've gone through the docs and a likely cause seems to be the wrong tape's > > in the drive and / or the tape needs rewinding. I've tried both these > > without > > any joy. In fact, I've got the dumpcycle set to 0 and the number of > > tapecycle > > set to 1. I'm under the impression that with this configuration Amanda will > > dump everything in my disklist daily. I've gone through the docs and tried > > this to see what's on the disk: > > > > amrestore -p /dev/nosst0 no-such-host > /dev/null > > > > which returns this: > > > > amrestore:0: skipping start of tape: date 20030703 label nameon1 > > amrestore:1: skipping ..backup file1... > > > > Yet if I run it again I get this: > > > > amrestore: WARNING: not at start of tape file numbers will be offset > > amrestore:1: skipping ..backup file2... > > > > and so on. I've been doing some more experimenting / research and it looks like it's a blocksize issue. If I check the status of the drive it reports that the blocksize is 512 bytes. 'man amanda' (2.4.3) says the default block size is 32KB with the minimum being 32KB and the maximum being 32KB so I've arrived at the conclusion that this is something to do with the blocksize. I've attempted to change it with defsetblk to 32KB and re-ran the dump, yet when I attempt amrestore -p /dev/nosst0 no-such-host > /dev/null it still always returns just one file, surely it should return all the files on the tape? I've seen from doing some searching that people have had similar problems with the default 512 byte block size which Onstream tape drivers ship with. I've experimented with tar to ensure the tape drive will backup and restore files which works. I don't really understand the what the block size means / does, there doesn't appear to be much info in the man pages / docs. I'd apprecate any help. Regards, James Williamson Name On The Net Ltd www.nameonthe.net > > > > I'm assuming that amrestore invoked in this manner will iterate through each > > file without having to be manually restarted. Does this mean when I use > > amrecover > > I must wind the tape to the correct place? Please excuse me if my knowledge > > of tape driver is woefully inadequate. > > Yes you have to rewind yourself. > Before amanda 2.4.4, it was usually faster to rewind and then fsf > manually to the correct position on tape, and than start amrecover. > If you didn't position the tape, amanda had to read the tape up > that position, which is much slower than fsf. > Since amanda 2.4.4, amanda can do that for you, if you add the > directive "amrecover_do_fsf on" in your amanda.conf. > > > -- > Paul Bijnens, XplanationTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** > > >
Re: to compress or not to compress ???
Also sprach Paul Bijnens (Fri 04 Jul 02003 at 10:51:47AM +0200): > > In docs/RESTORE, you can find all the commands you need to use > an amanda tape without amanda software. That is an excellent document! I'm sorry that I bothered the list before finding and reading it . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
amanda-users@amanda.org
Hi there, yes and no... the problem is not in amanda it is in linux-dump. if you read the manpage of dump the first lines tell you: NAME dump - ext2 filesystem backup this should be clear enough.. Christoph Rainer Hofmann wrote: As far as I know amanda cannot handle reiserfs, when using dump. You have to configure tar. Rainer Am Samstag, 5. Juli 2003 01:29 schrieb Sterpu Victor: I have succesfuly installed amanda. However, on the servers I have installed drbd. And it seems that amanda does not hork with drbd. Or maybe amanda does not work with reiserfs partitions? Does somewoane succesfuly tried this combination? Even that all the checks are succesfully: amcheck -c amcheck -s amcheck -l , when I try a amdump , the amandas log says: sendsize[11909]: time 0.014: /dev/nb0: Bad magic number in super-block while opening filesystem sendsize[11909]: time 0.015: DUMP: The ENTIRE dump is aborted. sendsize[11909]: time 0.015: . sendsize[11909]: estimate time for /mail level 0: 0.011 sendsize[11909]: no size line match in /sbin/dump output for "/mail" I dont know where to look next. Amanda works fine, drbd works fine, but they dont work together. Victor - This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/
Amanda stop working after amflush
Hello there, I have a problem with the amanda backup. Amanda is totally stop working after I amflush all the logfiles in /usr/am_dump. When I execute amcleanup, the messages shown as below: amcleanup: no unprocessed logfile to clean up. Scanning /usr/am_dump... When I execute amcheck, here is the message: Amanda Tape Server Host Check - Holding disk /usr/am_dump: 6291244 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape fs3_3 label ok <***I have put this tape on Wednesday and this is still OK on Friday!!!*** Server check took 3.831 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.033 seconds, 0 problems found When I execute amrecover, here is the message: AMRECOVER Version 2.4.2p2. Contacting server on fs3 ... 220 fs3 AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2003-07-04) 200 Working date set to 2003-07-04. 200 Config set to FS3. 200 Dump host set to fs3. Can't determine disk and mount point from $CWD Then I setdisk to /vol0, the error message is: Scanning /usr/am_dump... 200 Disk set to /vol0. No index records for disk for specified date If date correct, notify system administrator I have no idea what is going with Amanda, please help. Please find an attachment of amanda.conf file. Would you please advise where is it gone wrong? I am using amanda version 2.4.2p2. Thanks very much for your help. BR, Angie org "abc"# your organization name for reports mailto "[EMAIL PROTECTED]" # space separated list of operators at your site dumpuser "root" # the user to run dumps under inparallel 4# 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 netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec #dumpcycle 4 weeks # the number of days in the normal dump cycle #runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) #tapecycle 25 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 dumpcycle 2 weeks runspercycle 10 tapecycle 10 tapes ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 20 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. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # 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-manual" # the tape-changer glue script tapedev "/dev/nst0" # the no-rewind tape device to be used rawtapedev "/dev/null" # the raw device to be used (ftape only) #changerfile "/usr/adm/amanda/DailySet1/changer" #changerfile "/usr/adm/amanda/DailySet1/changer-status" #changerfile "/u
Re: missing backup data
James Williamson wrote: We've got Amanda set up to backup to a Onstream tape driver (SC-30), Are you aware there are two "generations" of Onstream tape drives? The first generation had firmware problems, which made it unusable. The company went down since, and you cannot get a firware upgrade. The european part of Onstream continued business, and, it seems, their hardware is much more reliable. (personally I have no experience with any Onstream device -- this is just what I heard.) If you're unlucky and have the first generation hardware, it could be the cause of your problems. when we run amdump it reports that it's successully backed up the contents of the disklist. However, when it comes to try and restore something on the disklist using amrecover it reports this error: EOF, check amidxtapid.debug file on backup. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header I've gone through the docs and a likely cause seems to be the wrong tape's in the drive and / or the tape needs rewinding. I've tried both these without any joy. In fact, I've got the dumpcycle set to 0 and the number of tapecycle set to 1. I'm under the impression that with this configuration Amanda will dump everything in my disklist daily. I've gone through the docs and tried this to see what's on the disk: amrestore -p /dev/nosst0 no-such-host > /dev/null which returns this: amrestore:0: skipping start of tape: date 20030703 label nameon1 amrestore:1: skipping ..backup file1... Yet if I run it again I get this: amrestore: WARNING: not at start of tape file numbers will be offset amrestore:1: skipping ..backup file2... and so on. I'm assuming that amrestore invoked in this manner will iterate through each file without having to be manually restarted. Does this mean when I use amrecover I must wind the tape to the correct place? Please excuse me if my knowledge of tape driver is woefully inadequate. Yes you have to rewind yourself. Before amanda 2.4.4, it was usually faster to rewind and then fsf manually to the correct position on tape, and than start amrecover. If you didn't position the tape, amanda had to read the tape up that position, which is much slower than fsf. Since amanda 2.4.4, amanda can do that for you, if you add the directive "amrecover_do_fsf on" in your amanda.conf. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: to compress or not to compress ???
Michael D. Schleif wrote: Also sprach Joshua Baker-LePain (Thu 03 Jul 02003 at 05:41:32PM -0400): On Thu, 3 Jul 2003 at 4:20pm, Michael D. Schleif wrote Also, using only amrestore, is it possible to get at individual files/directories, or is it only a matter of restoring the entire dump/tarball? Yes, depending. If you use dump, you can usually pipe amrestore to 'restore -i', the interactive restore, which will let you pick and choose. If you use tar, you can do a 'tar t' to get a table of contents, and then 'tar x myfile ./mydir/myfile2' to get particular files. This is where I'm getting lost: # sudo mt -f /dev/nst0 rewind # sudo tar tvf /dev/nst0 tar: /dev/nst0: Cannot read: Cannot allocate memory tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now What do you think? First you have to realize that on a tape you can put any sequence of bytes. To read and write those bytes from/to tape, it's also important that you do that with a suitable blocksize. In theory you could read the tape with "cat", but cat does not have a way to specify the read blocksize. That's why we use the "dd" command. If you read a tape, you have to do it with a blocksize equal or greater than the blocksize used when written. Amanda writes your tapes with a 32k blocksize (you can change the default blocksize in recent versions -- know your config!) A file on tape is any sequence of bytes. You can put many files on tape sequentially, each separated with a filemarker. After the last file is an end of data marker. The format of an amanda is as follows: The first file is the amanda header. Then follow the different dump images. The first block (32k in de the default setup) contains in simple ascii the description of what follows/ The header looks like: AMANDA: TAPESTART DATE 20030702 TAPE Test-01 ^L [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] nulls to fill up the rest of the blocksize The next files are each contain a header of 1 block, that contains the description of the next bytes: AMANDA: FILE 20030702 sunny /space lev 0 comp N program /usr/local/bin/amgtar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /usr/local/bin/amgtar -f... - ^L [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ascii nulls to fill up the rest of the block As you can see, amanda explains even what command you can use to read it: it contains a tar file, and to read it skip over the 32k header and feed those bytes to tar. What you should be doing was: mt -f /dev/nst0 rewind mt -f /dev/nst0 fsf 1 # skip over the tape label dd if=/dev/nst0 bs=32k skip=1 | tar -tvf - If you had used software compression, add the "z" flag to gnutar. In docs/RESTORE, you can find all the commands you need to use an amanda tape without amanda software. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: to compress or not to compress ???
Michael D. Schleif wrote: I am curious as to a procedure of manually -- without amanda -- viewing and restoring from amanda-written tapes . . . There is a good explanation of all the possible restore scenario's in docs/RESTORE. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
amanda-users@amanda.org
On Saturday 05 July 2003 06:47, Sterpu Victor wrote:
>Works. Thank you.
>But.
>My partition that I want to backup has 30G(only 13G are used).
>My tape has 20G uncompressed, 40G compressed.
>My dump type:
>define dumptype comp-high {
>global
>program "GNUTAR"
>comment "very important partitions on fast machines"
>compress server best
>priority high
>}
>And my log:
>FAIL planner cyrusback /mail 20030705 0 [dump larger than tape,
> 6364450 KB, but cannot incremental dump new disk]
>FATAL planner cannot fit anything on tape, bailing out
>WARNING driver WARNING: got empty schedule from planner
>
>I belive my partition should fit the tape.
>
> Victor
>
Hummm, and your tapetype is? clip it out of your amanda.conf and post
it please.
[...]
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: to compress or not to compress ???
Michael D. Schleif wrote: Also, what is the best way to turn off compression? ... Will this persist across power cycles? Will previously hardware compressed tapes turn hardware compression back on? See also: http://groups.yahoo.com/group/amanda-users/message/44453 http://groups.yahoo.com/group/amanda-users/message/43705 (I have this strange feeling of deja-vu :-) ) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Compression and X
Steven J. Backus wrote: The only compression option I can see on my mt is defcompression, so to turn it off is: /bin/mt -f defcompression 0 correct? Yes, but maybe it's not enough, see: http://groups.yahoo.com/group/amanda-users/message/44453 http://groups.yahoo.com/group/amanda-users/message/43705 Also, when I built amanda I did: --enable-FEATURE=x 'cuz I thought there's some sort of X interface to amanda. Now I'm not so sure. What is this x thing? Forget it. The letters "FEATURE" and "x" are just placeholders to show the syntax of the command. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
