Re: Testing tapes before use / bad tape
Hi! Am So, 2003-11-23 um 14.16 schrieb Gene Heskett: > There is amtapetype, which will destructively write the tape till it > hits EOT, and will tell you the size it found. See the man page for > running options to help speed it up as its quite slow, doing 2 > passes. SYNOPSIS amtapetype [-h] [-c] [-b blocksize] [-e estsize] [-f tapedev] [-t typename] Hmm, the only option that sounds like it could speed up the process is blocksize. Does anyone know a good value for this? Is the test faster the bigger I choose this value? (so 1 would take about 1 GB) Thanks in advance, Martin Öhler
Re: Testing tapes before use / bad tape
Martin Oehler wrote: Hi! Am So, 2003-11-23 um 14.16 schrieb Gene Heskett: There is amtapetype, which will destructively write the tape till it hits EOT, and will tell you the size it found. See the man page for running options to help speed it up as its quite slow, doing 2 passes. SYNOPSIS amtapetype [-h] [-c] [-b blocksize] [-e estsize] [-f tapedev] [-t typename] Hmm, the only option that sounds like it could speed up the process is blocksize. Does anyone know a good value for this? Read on a few lines further in the man page. The most important parameter for speed is the estimated size. It's the stop/start when writing a filemark that slows down the most. The default estimated size is 1 Gbyte. Amtapetype will write 100+200 files to the tape only if the estimated size is more or less ok. If you insert a a tape with 200 Gbyte real capacity, amtapetype will actually write 2+6 files to the tape. If start/stop takes about a second, then there will be 8 seconds lost in writing filemarks only, instead of the expected 300 seconds. Is the test faster the bigger I choose this value? (so 1 would take about 1 GB) 32 Kbyte (the amanda default) is just fine. -- 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: Testing tapes before use / bad tape
On Monday 24 November 2003 03:46, Martin Oehler wrote: >Hi! > >Am So, 2003-11-23 um 14.16 schrieb Gene Heskett: >> There is amtapetype, which will destructively write the tape till >> it hits EOT, and will tell you the size it found. See the man >> page for running options to help speed it up as its quite slow, >> doing 2 passes. > >SYNOPSIS > amtapetype [-h] [-c] [-b blocksize] [-e estsize] [-f > tapedev] [-t typename] > >Hmm, the only option that sounds like it could speed up the process >is blocksize. Does anyone know a good value for this? I would use that only if you are using a non-std blocksize, which I am, rather than the default 512 byte, I'm using 32768 for reasons other than any percieved speed advantage. There isn't any as long as the drive is streaming. But changing this is an mt command I think, done ahead of time. I do mine in /etc/rc.d/rc.local at boot time. However, there must be a tape in the drive or that fails later for amanda. >Is the test faster the bigger I choose this value? (so 1 would take >about 1 GB) The -e size option allows it to march right along on the first pass, so if you have an 80G tape (see the options defines for estsize syntax) you can pass this to it. We're told that speeds up the first pass considerably. Doing this to a tape also should tell you whether or not the drives internal compression is in use, which for amanda, should be turned off as that hides the true size of the tape from amanda. Amanda counts bytes sent to the drive after any gzip is applied, and if the drives compressor is on, the data normally will grow slightly and amanda may hit EOT thinking it still has 10-15% of the tape left. Turning off the drives internal compressor can be a problem child too, and must be done external to amanda. However I've worked out a script that saves the tapes label info, turns the compressor off, and re-writes the label. The programming switches on the drive must also be set to the off position before doing this, and on some drives, you will have to powercycle the drive to get it to re-read the switches state. Since the switches aren't that accessable normally, the machine powerdown done to remove and access the drive will take care of that. >Thanks in advance, >Martin Öhler Humm, do I recall that name from a decade or so back when I was running an amiga? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% 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: Running amdump leads to high CPU load on Linux server
On Sun, 23 Nov 2003 at 7:46pm, Kurt Raschke wrote > I've recently begun to have trouble with the Linux system that is my > amanda server...when amdump runs, the load spikes to between 4.00 and > 6.00, and the system becomes nearly unresponsive for the duration of > the backup. The server is backing up several local partitions, and > also two partitions on remote servers. I've tried starting amdump > with nice and setting it to a low priority, but when gtar and gzip are > started by amanda, the priority setting is somehow lost. The server > isn't even trying to back up multiple partitions in parallel, so I'm > at a loss as to how this is happening, especially on a fairly fast > server (dual Athlon MP 2000). > > Any suggestions? If you need to see the amanda logs or anything else > that would help, just ask. Are these IDE disks? Make sure DMA is turned on... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Testing tapes before use / bad tape
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote: > Hi! > > Am So, 2003-11-23 um 14.16 schrieb Gene Heskett: > > There is amtapetype, which will destructively write the tape till it > > hits EOT, and will tell you the size it found. See the man page for > > running options to help speed it up as its quite slow, doing 2 > > passes. > Check your tapes capacity and rated writing speed. Be sure they are the native values, not the values for HW compression on. Then divide one by the other. You come out with a "time" value that I'm betting will be about 3 hours. This is the time for a single pass under the vendor's optimum conditions. You will probably not reach their rated speed. As amtapetype makes two complete passes, double that time value. This is the minimum time an amtapetype run could take. It is not amtapetype that is slow, it is the medium. As Paul B. notes, make sure you give amtapetype a reasonable estimate of the native size of the tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amtapetype idea (Was: Testing tapes before use / bad tape)
On Mon, Nov 24, 2003 at 10:23:12AM +0100, Paul Bijnens wrote:
>
> Read on a few lines further in the man page. The most important
> parameter for speed is the estimated size. It's the stop/start when
> writing a filemark that slows down the most. The default estimated
> size is 1 Gbyte. Amtapetype will write 100+200 files to the tape only
> if the estimated size is more or less ok. If you insert a a tape
> with 200 Gbyte real capacity, amtapetype will actually write 2+6
> files to the tape. If start/stop takes about a second, then there
> will be 8 seconds lost in writing filemarks only, instead of
> the expected 300 seconds.
Might it be a good idea to have amtapetype note too many files
being written during the first phase and taking some action?
Maybe with an option to override the checking.
Possible actions:
- abort with an error message to rerun with a different estimate
when the number of files written exceeded some value, say 250
- print an error message recommending the operator interupt the
and rerun with a corrected estimate, eg.
amtapetype: pass 1: estimated tape capacity (X GB) error: expected
to write 100 files, now writing file Y00: restart recommended
In your example above (200GB tape with default estimate) I
think the error message would come out about every minute or
two. For a dds3 tape, about every 20 min.
Aside from the new option processing to set an "override flag)
I think all it would take is an if statement like:
if (files_written % 100 && files_written > 100 && ! overried_flag)
{
print/log errors
}
jl
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amcheck: skipping tape test because amdump or amflush seem to be running
Hello honourable readers of the list, After some succesfull testing, I wanted to make a run for real. As recommended in the FAQ I removed: -curinfo -any log files from the log directory -tapelist -reseted the changer state file so I run the amcheck on a particular configuration and I do get: Amanda Tape Server Host Check - Holding disk /var/backups/holdingdisk: 1431256 KB disk space available, that's plenty WARNING: skipping tape test because amdump or amflush seem to be running WARNING: if they are not, you must run amcleanup NOTE: info dir /var/lib/amanda/test/curinfo/dell: does not exist NOTE: index dir /var/lib/amanda/test/index/dell: does not exist Server check took 0.023 seconds --- so I run amcleanup on the configuration and amcheck does not believe me. I checked that I did not forget to delete the recommended files no process is running, no tape is in the drive I remember I had that problem before but forgot to take notes and my memory fails me right now. Does anybody out there keep notes in a beter way or has a non failling memory :=) archives and google search did not help much on this topic cedric
include problems with Amanda-2.4.4-20030428?
Hi,
I'm having strange problems with the include thingy in an
entry in my disklist:
bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
include "./0*"
exclude "./[1-9]*"
high-tar
} 1
Looking at what got written to tape (a full backup) I see only
directories (no files at all!), and even from the exclude part...ie
just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
the way down...
I'm compiling 2.4.4p1-20031120 right now.
But before putting that online, does anyone knows about this
problem, and if so, will 2.4.4p1-20031120 do the trick?
TIA,
jf
--
We see in what we think we fear
The clouding of our thoughts made clear
mtx and storedge L9 on solaris 7 server
can someone give me some pointers about accessing my juke box using mtx? I cannot figure out what device to use. nwadmin reports the control port at [EMAIL PROTECTED] and the tape device as /dev/rmt/1hbn , this is a link to : /devices/[EMAIL PROTECTED],2000/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0:hbn any pointers appreciated. -- Alastair J. Neil Unix Systems Administrator IT&E Labs, George Mason University
Re: include problems with Amanda-2.4.4-20030428?
Hello again,
Oups, forgot to mention one important fact: the gnutar version:
/usr/freeware/bin/tar --version
tar (GNU tar) 1.13.25
* Jean-Francois Malouin <[EMAIL PROTECTED]> [20031124 12:00]:
> Hi,
>
> I'm having strange problems with the include thingy in an
> entry in my disklist:
>
> bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
> include "./0*"
> exclude "./[1-9]*"
> high-tar
> } 1
>
> Looking at what got written to tape (a full backup) I see only
> directories (no files at all!), and even from the exclude part...ie
> just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> the way down...
>
> I'm compiling 2.4.4p1-20031120 right now.
> But before putting that online, does anyone knows about this
> problem, and if so, will 2.4.4p1-20031120 do the trick?
>
> TIA,
> jf
> --
> We see in what we think we fear
> The clouding of our thoughts made clear
--
We see in what we think we fear
The clouding of our thoughts made clear
Memory requirements for Amanda Server
We are building an amanda backup server and have a question regarding memory requirements. My guess is that Amanda is more processor intensive than memory intensive. Is this correct? For a dedicated backup server that won't be doing much of anything else, is 512MB of memory enough? Thanks, Bryan Walton
Re: amcheck: skipping tape test because amdump or amflush seem to be running
Cedric Boudin wrote: Hello honourable readers of the list, After some succesfull testing, I wanted to make a run for real. As recommended in the FAQ I removed: -curinfo -any log files from the log directory -tapelist -reseted the changer state file so I run the amcheck on a particular configuration and I do get: Amanda Tape Server Host Check - Holding disk /var/backups/holdingdisk: 1431256 KB disk space available, that's plenty WARNING: skipping tape test because amdump or amflush seem to be running WARNING: if they are not, you must run amcleanup NOTE: info dir /var/lib/amanda/test/curinfo/dell: does not exist NOTE: index dir /var/lib/amanda/test/index/dell: does not exist Server check took 0.023 seconds --- so I run amcleanup on the configuration and amcheck does not believe me. I checked that I did not forget to delete the recommended files no process is running, no tape is in the drive Then there probably is a file named "amflush". Rename it to "amflush.0" or "amflush.1" (next free number). Maybe you ran amflush or other testing as root? Then some files/directores were created as root, and now owned by root, amanda cannot write in them. I remember I had that problem before but forgot to take notes and my memory fails me right now. Does anybody out there keep notes in a beter way or has a non failling memory :=) archives and google search did not help much on this topic cedric -- 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] *a** * 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: Memory requirements for Amanda Server
> We are building an amanda backup server and have a question regarding > memory requirements. My guess is that Amanda is more processor > intensive than memory intensive. Is this correct? For a dedicated > backup server that won't be doing much of anything else, is 512MB of > memory enough? i have such a beast running on RedHat with 256 meg of RAM and its fine thanks
Re: amcheck: skipping tape test because amdump or amflush seem to be running
Paul Bijnens writes: > Cedric Boudin wrote: > > > Hello honourable readers of the list, > > > > After some succesfull testing, I wanted to make a run for real. As > > recommended in the FAQ I removed: > > > > -curinfo > > -any log files from the log directory > > -tapelist > > -reseted the changer state file > > > > so I run the amcheck on a particular configuration and I do get: > > > > Amanda Tape Server Host Check > > - > > Holding disk /var/backups/holdingdisk: 1431256 KB disk space available, that's > > plenty > > WARNING: skipping tape test because amdump or amflush seem to be running > > WARNING: if they are not, you must run amcleanup > > NOTE: info dir /var/lib/amanda/test/curinfo/dell: does not exist > > NOTE: index dir /var/lib/amanda/test/index/dell: does not exist > > Server check took 0.023 seconds > > > > --- > > so I run > > amcleanup on the configuration > > > > and amcheck does not believe me. > > > > I checked that I did not forget to delete the recommended files > > > > no process is running, no tape is in the drive > > Then there probably is a file named "amflush". Rename it to "amflush.0" > or "amflush.1" (next free number). > Maybe you ran amflush or other testing as root? Then some > files/directores were created as root, and now owned by root, amanda > cannot write in them. I've cleaned everything up the amanda instalation is if a dare say virginal. I can't figure out where amcheck does get the info. No amanda process is runing and I' doubled checked theres is absolutely no file whatsover in /var/lib/amanda/test (indices or curinfo) and /var/log/amanda is as empty as it could be. I chown'ed all the dirs the amanda user is sole user
Re: Memory requirements for Amanda Server
On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote: We are building an amanda backup server and have a question regarding memory requirements. My guess is that Amanda is more processor intensive than memory intensive. Is this correct? For a dedicated backup server that won't be doing much of anything else, is 512MB of memory enough? i have such a beast running on RedHat with 256 meg of RAM and its fine My amanda backup server is a pentium 90 with 32M of ram, running FreeBSD 4.9. Seems to work no problem (admittedly, I only have about 30-40 disk-list entries, writing to DDS3) Ricky
Re: Memory requirements for Amanda Server (fwd)
Remember that Amanda is a driver, a scheduling tool that invokes tools on each of the amanda clients (except in the case of server side compression). Amanda queries each client (possibly having a client on the server machine), determines answers to various space issues and then issues commands for the clients to execute. Amanda itself doesn't use a lot of resources, not if your talking about the server side of things. As far as the client side - its no different if you invoke dump/tar and optionally zgzip as local root or remotely via amanda, the results will be the same. - Forwarded message from Richard Morse - On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote: > > >> We are building an amanda backup server and have a question regarding >> memory requirements. My guess is that Amanda is more processor >> intensive than memory intensive. Is this correct? For a dedicated >> backup server that won't be doing much of anything else, is 512MB of >> memory enough? > > i have such a beast running on RedHat with 256 meg of RAM and its fine My amanda backup server is a pentium 90 with 32M of ram, running FreeBSD 4.9. Seems to work no problem (admittedly, I only have about 30-40 disk-list entries, writing to DDS3) Ricky - End of forwarded message from Richard Morse -
Re: include problems with Amanda-2.4.4-20030428?
* Paul Bijnens <[EMAIL PROTECTED]> [20031124 13:02]:
> Jean-Francois Malouin wrote:
>
> >Hi,
> >
> >I'm having strange problems with the include thingy in an
> >entry in my disklist:
> >
> >bullcalf /data/nihpd/nihpd1/data/assembly_0
> >/data/nihpd/nihpd1/data/assembly {
> >include "./0*"
> >exclude "./[1-9]*"
> >high-tar
> >} 1
> >
> >Looking at what got written to tape (a full backup) I see only
> >directories (no files at all!), and even from the exclude part...ie
> >just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> >the way down...
>
>
> Can you explain a little more? Show the relevant index.
> The index file itself starts with the directories, and then follows
> with the files in the directories. But you shouldn't see anything
> from the excluded parts. (Actually the exclude above can be omitted
> entirely.)
>
I didn't have a look at the index file, but here's an excerpt:
top:
/
/-/
/-/0/
/-/0/behavioural/
/-/0/behavioural/cantab/
/-/0/behavioural/carey/
/-/0/behavioural/cbcl/
/-/0/behavioural/cvlt2/
/-/0/behavioural/cvltc/
end:
/998601/1/mri/work/xfms/nihpd_998601_v1_obj1_t2w_1.t2w.clp.t1tal.xfm
/998601/1/mri/work/xfms/nihpd_998601_v1_obj1_t2w_1.t2w.clpt2t1native.xfm
/998724/1/behavioural/cbcl/998724v1_profexport.DBF
/998724/1/behavioural/cbcl/998724v1_profexport.txt
/998724/1/behavioural/cbcl/998724v1_rawexport.DBF
/998724/1/behavioural/cbcl/998724v1_rawexport.txt
/998724/1/behavioural/dps4/998724v1y.chr
So you're right, there are files in there. My mistake. I probably
looked at the wrong place. However the index entries start with a "/"
NOT "./" so is this the problem? That would explain why the
include/exclude pattern failed as the directories starting with
something else that "./0" should be excluded , right?
Looking at what is on the tape I see :
mt -f /hw/tape/tps12d1nrnsv fsf 1
dd if=/hw/tape/tps12d1nrnsv bs=32k skip=1 | /usr/freeware/bin/tar tf
./
./-/
./-/0/
./-/0/behavioural/
./-/0/behavioural/cantab/
./-/0/behavioural/carey/
./-/0/behavioural/cbcl/
./-/0/behavioural/cvlt2/
./-/0/behavioural/cvltc/
something's fishy...
> >I'm compiling 2.4.4p1-20031120 right now.
> >But before putting that online, does anyone knows about this
> >problem, and if so, will 2.4.4p1-20031120 do the trick?
>
> There was a bug in 2.4.4p1 that if the include was not a pattern, it
> would not work. That was only for "include". I believe the above
> should work find, even in a plain 2.4.4.
> Stupid question: the client has the same/correct version too?
client is the server, and the only one for this conf.
regards,
jf
>
> --
> 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 *
> ***
>
--
We see in what we think we fear
The clouding of our thoughts made clear
Re: amtapetype idea (Was: Testing tapes before use / bad tape)
Jon LaBadie wrote: Might it be a good idea to have amtapetype note too many files being written during the first phase and taking some action? Maybe with an option to override the checking. My idea was to write only one large file in the first pass, just until it hits end of tape. Then rewind and write tapesize/100 files to measure the size of a filemark. That way you don't need to give an estimated tapesize at all. Never got enough time to implement it though: "Wife, children, house,... the full catastrophy" -- Zorba The Greek. You ony have to look out for overflow while doing the math for blocksize, speed etc. (200 Gbyte > 2^32 bytes) -- 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: Memory requirements for Amanda Server
On Mon, 2003-11-24 at 13:02, Bryan K. Walton wrote: > We are building an amanda backup server and have a question regarding > memory requirements. My guess is that Amanda is more processor > intensive than memory intensive. Is this correct? For a dedicated > backup server that won't be doing much of anything else, is 512MB of > memory enough? Bryan, That would be plenty! We're backing up 30-40 GB a night with a Debian box and 128MB of RAM. The CPU is more critical, especially if you anticipate doing any server-side compression. It will also help with restores of compressed images. Holding-disk space is the other area not to skimp on. :) HTH, Eric
Re: include problems with Amanda-2.4.4-20030428?
On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
> Hi,
>
> I'm having strange problems with the include thingy in an
> entry in my disklist:
>
> bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
> include "./0*"
> exclude "./[1-9]*"
> high-tar
> } 1
>
> Looking at what got written to tape (a full backup) I see only
> directories (no files at all!), and even from the exclude part...ie
> just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> the way down...
>
Don't know about your bad backup, but in your DLE you should not
have both the include and THAT exclude. I.e., the include will
automatically drop any toplevel dir that does not match "./0*".
I think the only valid exclude usage would be for things under
the 0* directories. For example 'exclude "./0*/tmp"'. Though
I must admit I've never tried that combination.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: mtx and storedge L9 on solaris 7 server
On Mon, Nov 24, 2003 at 12:15:26PM -0500, Alastair Neil wrote: > can someone give me some pointers about accessing my juke box using > mtx? I cannot figure out what device to use. > > nwadmin reports the control port at [EMAIL PROTECTED] and the tape device as > /dev/rmt/1hbn , this is a link to : > /devices/[EMAIL PROTECTED],2000/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0:hbn > > any pointers appreciated. > Do you have any entries under /dev/changers or /dev/scsi/*? Using the Solaris "sgen" driver (scsi general) others have reported that they get devices /dev/changer/???. I get something under /dev/scsi/sequential/???. From that I manually create a /dev/changer/??? link because it "makes sense". Check the archives or your vendors docs for comments about setting up /kernel/drv/sgen.conf if you haven't already done so. You say your tapedevice is /dev/rmt/1. What is /dev/rmt/0? Do you have another tape drive? If not, maybe you should remove all the symbolic links in /dev/rmt and run devfsadm(1m) to recreate them. If both reappear, then perhaps one is the tape drive and the other is the changer device. I get both the /dev/scsi device from the sgen driver and an extra /dev/rmt device from the st driver. The latter is also my changer, I can use either. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: mtx and storedge L9 on solaris 7 server
On Mon, 2003-11-24 at 13:24, Jon LaBadie wrote: > On Mon, Nov 24, 2003 at 12:15:26PM -0500, Alastair Neil wrote: > > can someone give me some pointers about accessing my juke box using > > mtx? I cannot figure out what device to use. > > > > nwadmin reports the control port at [EMAIL PROTECTED] and the tape device as > > /dev/rmt/1hbn , this is a link to : > > /devices/[EMAIL PROTECTED],2000/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0:hbn > > > > any pointers appreciated. > > > > Do you have any entries under /dev/changers or /dev/scsi/*? no /dev/scsi directory nor /dev/changers > > Using the Solaris "sgen" driver (scsi general) others have reported > that they get devices /dev/changer/???. I get something under > /dev/scsi/sequential/???. From that I manually create a > /dev/changer/??? link because it "makes sense". > > Check the archives or your vendors docs for comments about setting > up /kernel/drv/sgen.conf if you haven't already done so. > > You say your tapedevice is /dev/rmt/1. What is /dev/rmt/0? Do > you have another tape drive? If not, maybe you should remove > all the symbolic links in /dev/rmt and run devfsadm(1m) to > recreate them. If both reappear, then perhaps one is the > tape drive and the other is the changer device. I get both > the /dev/scsi device from the sgen driver and an extra /dev/rmt > device from the st driver. The latter is also my changer, I > can use either. /dev/rmt/0 is the built in DAT drive, I'm confident that I have the right tape device. It looks like sgen is not configured so I have created a sgen.conf file and then I'll schedule a reboot -- -rv to see if the devices files you mentioned are created. Thanks for your help I think you have set me on the right track. regards, Alastair -- Dr. Alastair J. Neil Unix Systems Administrator IT&E Labs, George Mason University
Re: include problems with Amanda-2.4.4-20030428?
* Jon LaBadie <[EMAIL PROTECTED]> [20031124 14:15]:
> On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
> > Hi,
> >
> > I'm having strange problems with the include thingy in an
> > entry in my disklist:
> >
> > bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
> > include "./0*"
> > exclude "./[1-9]*"
> > high-tar
> > } 1
> >
> > Looking at what got written to tape (a full backup) I see only
> > directories (no files at all!), and even from the exclude part...ie
> > just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> > the way down...
> >
>
> Don't know about your bad backup, but in your DLE you should not
> have both the include and THAT exclude. I.e., the include will
> automatically drop any toplevel dir that does not match "./0*".
That is want I want!
All subdirs in there have a pattern [0-9]\{6\} , ie, 6 digits. There
are other subdirs but there are not to be backed up. You see, my
problem is that /data/nihpd/nihpd1/data/assembly can contains 100's of
GB and I'm using 4 LTO tape drives, so I have to split that thing in
small chuncks...
Eventually I'll have 10 DLE's, those starting with ./0* ./1* ...
you get the picture.
>
> I think the only valid exclude usage would be for things under
> the 0* directories. For example 'exclude "./0*/tmp"'. Though
> I must admit I've never tried that combination.
Have a look at my other post in this thread. The index file for that
DLE doesn't start with "./" but with "/"...Is my gnutar at fault here?
I thought that v1.13.25 had good karma...
thanks for the help,
jf
>
> --
> Jon H. LaBadie [EMAIL PROTECTED]
> JG Computing
> 4455 Province Line Road(609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
--
We see in what we think we fear
The clouding of our thoughts made clear
Re: Memory requirements for Amanda Server
> > We are building an amanda backup server and have a question regarding > > memory requirements. My guess is that Amanda is more processor > > intensive than memory intensive. Is this correct? For a dedicated > > backup server that won't be doing much of anything else, is 512MB of > > memory enough? > > i have such a beast running on RedHat with 256 meg of RAM and its fine Mandrake, 128 meg of RAM, 200MHz Pentium Pro (yes, we -are- talking Socket 8 here :> ). Runs Amanda for an external DDS-3 changer (desktop backups), Arkeia for an internal DDS-4 single (server backups), with Amanda and Arkeia jobs running simultaneously every night. Works like a champ. -- Daniel Bentley - Network Technician, QSI Corporation (www.qsicorp.com) chown -R us *base*
Re: amtapetype idea (Was: Testing tapes before use / bad tape)
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote: > Jon LaBadie wrote: > > >Might it be a good idea to have amtapetype note too many files > >being written during the first phase and taking some action? > >Maybe with an option to override the checking. > > My idea was to write only one large file in the first pass, just > until it hits end of tape. Then rewind and write tapesize/100 files > to measure the size of a filemark. > That way you don't need to give an estimated tapesize at all. > > Never got enough time to implement it though: Just revert to an earlier version :) Way back tapetype wrote pass 1 with no files. Then in pass 2 it wrote lots of small files (one 32K block) comes to mind. That of course was rediculous when V large tape sizes came along. I submitted a change that did a similar calculation to that you suggest, but wrote 1000 files. After that was in place for a while, someone noted a problem. What it was I don't recall, but someone, I think JRJ, changed it to the 100/200 file scheme. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck: skipping tape test because amdump or amflush seem to be running
On Mon, Nov 24, 2003 at 07:29:03PM +0100, Cedric Boudin wrote: > > I've cleaned everything up the amanda instalation is if a dare say > virginal. I can't figure out where amcheck does get the info. No > amanda process is runing and I' doubled checked theres is absolutely > no file whatsover in /var/lib/amanda/test (indices or curinfo) and > /var/log/amanda is as empty as it could be. I chown'ed all the dirs > the amanda user is sole user > Does "amgetconf" give you the expected values for logdir, infofile, and indexdir? Ex, does "amgetconf logdir" report /var/log/amanda or some other dir. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: include problems with Amanda-2.4.4-20030428?
On Mon, Nov 24, 2003 at 02:57:56PM -0500, Jean-Francois Malouin wrote:
> * Jon LaBadie <[EMAIL PROTECTED]> [20031124 14:15]:
> > On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
> > > Hi,
> > >
> > > I'm having strange problems with the include thingy in an
> > > entry in my disklist:
> > >
> > > bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
> > > include "./0*"
> > > exclude "./[1-9]*"
> > > high-tar
> > > } 1
> > >
> > > Looking at what got written to tape (a full backup) I see only
> > > directories (no files at all!), and even from the exclude part...ie
> > > just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> > > the way down...
> > >
> >
> > Don't know about your bad backup, but in your DLE you should not
> > have both the include and THAT exclude. I.e., the include will
> > automatically drop any toplevel dir that does not match "./0*".
>
> That is want I want!
> All subdirs in there have a pattern [0-9]\{6\} , ie, 6 digits. There
> are other subdirs but there are not to be backed up. You see, my
> problem is that /data/nihpd/nihpd1/data/assembly can contains 100's of
> GB and I'm using 4 LTO tape drives, so I have to split that thing in
> small chuncks...
>
> Eventually I'll have 10 DLE's, those starting with ./0* ./1* ...
> you get the picture.
>
> >
> > I think the only valid exclude usage would be for things under
> > the 0* directories. For example 'exclude "./0*/tmp"'. Though
> > I must admit I've never tried that combination.
>
> Have a look at my other post in this thread. The index file for that
> DLE doesn't start with "./" but with "/"...Is my gnutar at fault here?
> I thought that v1.13.25 had good karma...
No, the index should start with "/",
but it should not start with "/-/"
unless you have a top-level directory named "-".
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Memory requirements for Amanda Server
On Mon, Nov 24, 2003 at 01:45:00PM -0500, Richard Morse wrote: > On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote: > > >>We are building an amanda backup server and have a question regarding > >>memory requirements. > > > > My amanda backup server is a pentium 90 with 32M of ram, running > FreeBSD 4.9. Seems to work no problem (admittedly, I only have about > 30-40 disk-list entries, writing to DDS3) Might be the smallest amanda server running :)) Anyone out there running amanda on a 386 or 486 with 16M of ram? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: include problems with Amanda-2.4.4-20030428?
* Jon LaBadie <[EMAIL PROTECTED]> [20031124 15:23]:
> On Mon, Nov 24, 2003 at 02:57:56PM -0500, Jean-Francois Malouin wrote:
> > * Jon LaBadie <[EMAIL PROTECTED]> [20031124 14:15]:
> > > On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote:
> > > > Hi,
> > > >
> > > > I'm having strange problems with the include thingy in an
> > > > entry in my disklist:
> > > >
> > > > bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly {
> > > > include "./0*"
> > > > exclude "./[1-9]*"
> > > > high-tar
> > > > } 1
> > > >
> > > > Looking at what got written to tape (a full backup) I see only
> > > > directories (no files at all!), and even from the exclude part...ie
> > > > just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all
> > > > the way down...
> > > >
> > >
> > > Don't know about your bad backup, but in your DLE you should not
> > > have both the include and THAT exclude. I.e., the include will
> > > automatically drop any toplevel dir that does not match "./0*".
> >
> > That is want I want!
> > All subdirs in there have a pattern [0-9]\{6\} , ie, 6 digits. There
> > are other subdirs but there are not to be backed up. You see, my
> > problem is that /data/nihpd/nihpd1/data/assembly can contains 100's of
> > GB and I'm using 4 LTO tape drives, so I have to split that thing in
> > small chuncks...
> >
> > Eventually I'll have 10 DLE's, those starting with ./0* ./1* ...
> > you get the picture.
> >
> > >
> > > I think the only valid exclude usage would be for things under
> > > the 0* directories. For example 'exclude "./0*/tmp"'. Though
> > > I must admit I've never tried that combination.
> >
> > Have a look at my other post in this thread. The index file for that
> > DLE doesn't start with "./" but with "/"...Is my gnutar at fault here?
> > I thought that v1.13.25 had good karma...
>
> No, the index should start with "/",
> but it should not start with "/-/"
> unless you have a top-level directory named "-".
yes, there is a directory "./-"
Most prob'ly a luser typo :)
jf
>
> --
> Jon H. LaBadie [EMAIL PROTECTED]
> JG Computing
> 4455 Province Line Road(609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
--
We see in what we think we fear
The clouding of our thoughts made clear
Re: amcheck: skipping tape test because amdump or amflush seem to be running
> Paul Bijnens writes:
> > Cedric Boudin wrote:
> >
> > > Hello honourable readers of the list,
> > >
> > > After some succesfull testing, I wanted to make a run for real. As
> > > recommended in the FAQ I removed:
> > >
> > > -curinfo
> > > -any log files from the log directory
> > > -tapelist
> > > -reseted the changer state file
> > >
> > > so I run
> > > amcleanup on the configuration
> > >
> > > and amcheck does not believe me.
> > >
> > > I checked that I did not forget to delete the recommended files
> > >
> > > no process is running, no tape is in the drive
> >
> > Then there probably is a file named "amflush". Rename it to "amflush.0"
> > or "amflush.1" (next free number).
> > Maybe you ran amflush or other testing as root? Then some
> > files/directores were created as root, and now owned by root, amanda
> > cannot write in them.
>
> I've cleaned everything up the amanda instalation is if a dare say
> virginal. I can't figure out where amcheck does get the info. No
> amanda process is runing and I' doubled checked theres is absolutely
> no file whatsover in /var/lib/amanda/test (indices or curinfo) and
> /var/log/amanda is as empty as it could be. I chown'ed all the dirs
> the amanda user is sole user
>
When I have been testing many different tapeless configuration, I used
two shell scripts:
First removes any amanda files:
#
rm -fr /usr/local/etc/amanda/YourConfig/curinfo/*
rm -fr /usr/local/etc/amanda/YourConfig/index/*
rm -f /usr/local/etc/amanda/YourConfig/log.2003*
rm -fr /usr/local/etc/amanda/YourConfig/oldlog/*
rm -f /usr/local/etc/amanda/YourConfig/amdump.*
rm -f /usr/local/etc/amanda/YourConfig/amflush.*
rm -f /usr/local/etc/amanda/YourConfig/multi-changer-status
rm -f /usr/local/var/amanda/gnutar-lists/*
rm -fr /tmp/amanda
cp -f /dev/null /etc/amandates
chown amanda.disk /etc/amandates
chmod 660 /etc/amandates
#
The second removes any "tape" dependent files and creates new "tapes":
#
rm -fr /archive_disk/tape_A*
rm -f /usr/local/etc/amanda/YourConfig/multi-changer-status
rm -f /usr/local/etc/amanda/YourConfig/tapelis*
touch /usr/local/etc/amanda/YourConfig/tapelist
for t in {1,2,3,4,5,6}; do {
mkdir /archive_disk/tape_A$t;
mkdir /archive_disk/tape_A$t/data;
};
done
for t in {1,2,3,4,5,6}; do {
/usr/local/libexec/chg-multi -slot advance;
/usr/local/sbin/amlabel YourConfig YourConfig0$t slot $t;
};
done
/usr/local/libexec/chg-multi -slot advance
#
You can modify and try to use them.
Wojtek
RE: UPDATE: SOLVED:Cannot backup firewall
> On Thu, 20 Nov 2003 at 8:26am, Rebecca Pakish Crum wrote > > > I'm running amanda 2.4.2p2 on a RH box as my backup server. I > > installed the amanda client on my (sol8) firewall on > Friday, and set > > up a rule for the server to get to the firewall for amanda > services - > > amcheck runs fine and reports no errors. But when my amdump > kicks off > > at night, my report says: > > > > firewall.unter /export/home/rebecca lev 0 FAILED [could not > connect to > > firewall.unterlaw.com] > > You have to allow traffic on not just the amanda port, but also high > numbered TCP ports for the data connections. On Linux > clients, I put in > the following iptables rules: > > # Amanda from chaos > -A INPUT -p udp -s $SERVER_IP_ADDRESS -d 0/0 --dport 10080 -j > ACCEPT -A INPUT -p tcp -m tcp -s $SERVER_IP_ADDRESS -d 0/0 > --dport 1025:65535 -j ACCEPT > > With just the first rule (allowing UDP traffic to port > 10080), the client > will pass amcheck but fail amdump. The second rule (allowing TCP > traffic to all non-priviledged ports) actually allows data to flow. > Thought I should send a note and let everyone know that this fixed my problem. I forgot to update it last week. THANK YOU! > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
Re: Testing tapes before use / bad tape
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote: > Hmm, the only option that sounds like it could speed up the [amtapetype] process > is blocksize. Does anyone know a good value for this? The same value as amdump will be using! With some tape technologies, the tape's capacity depends very much on the block size. In such a case, using a different block size for the test would give misleading results. On Sun, Nov 23, 2003 at 10:28:38AM +0100, Martin Oehler wrote: > My second problem is how to handle the "short write"? > I have to send in the tape, but the are 3-4 GB of data on this tape. > Without this data, my backup is inconsistent. The only possibility > I see (at the moment) is doing a full backup of the partitions having > some data on this tape. That's one possibility. You can use "amadmin force", staging the full backups over a few runs if necessary to fit them in. Another possibility would be to wait a tapecycle (or at the very least a dumpcycle) for the backups to expire on their own. (Don't forget to erase the tape before sending it back, if it contains anything confidential.) -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: amcheck: skipping tape test because amdump or amflush seem to be running
Jon LaBadie writes: > On Mon, Nov 24, 2003 at 07:29:03PM +0100, Cedric Boudin wrote: > > > > I've cleaned everything up the amanda instalation is if a dare say > > virginal. I can't figure out where amcheck does get the info. No > > amanda process is runing and I' doubled checked theres is absolutely > > no file whatsover in /var/lib/amanda/test (indices or curinfo) and > > /var/log/amanda is as empty as it could be. I chown'ed all the dirs > > the amanda user is sole user > > > > Does "amgetconf" give you the expected values for logdir, infofile, > and indexdir? Ex, does "amgetconf logdir" report > /var/log/amanda or some other dir. yes it does the directories do exist are writable and owned by amanda user
Re: amtapetype idea (Was: Testing tapes before use / bad tape)
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote: > My idea was to write only one large file in the first pass, just > until [amtapetype] hits end of tape. One problem with that is that the drive's internal buffering might distort the results, by letting amtapetype think it has successfully written blocks that in fact won't make it to tape. (That's a problem anyway, of course, but sticking in a filemark every once in a while puts a known upper bound on the error.) Perhaps amtapetype could have a "test-tape" flag, that would basically tell it to suppress the second pass. Or the second pass could become a verification pass (just re-seed the random-number generator to the value from the beginning of the write pass). Or provide both options. Of course that would make "amtapetype" a rather misleading name. "amtape" would be a great choice for a new name; too bad it's taken :-/ -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: amcheck: skipping tape test because amdump or amflush seem to be running
On Monday 24 November 2003 13:29, Cedric Boudin wrote: >Paul Bijnens writes: > > Cedric Boudin wrote: > > > Hello honourable readers of the list, > > > > > > After some succesfull testing, I wanted to make a run for real. > > > As recommended in the FAQ I removed: > > > > > > -curinfo > > > -any log files from the log directory > > > -tapelist > > > -reseted the changer state file > > > > > > so I run the amcheck on a particular configuration and I do > > > get: > > > > > > Amanda Tape Server Host Check > > > - > > > Holding disk /var/backups/holdingdisk: 1431256 KB disk space > > > available, that's plenty WARNING: skipping tape test because > > > amdump or amflush seem to be running WARNING: if they are not, > > > you must run amcleanup > > > NOTE: info dir /var/lib/amanda/test/curinfo/dell: does not > > > exist NOTE: index dir /var/lib/amanda/test/index/dell: does not > > > exist Server check took 0.023 seconds > > > > > > --- > > > so I run > > > amcleanup on the configuration > > > > > > and amcheck does not believe me. > > > > > > I checked that I did not forget to delete the recommended files > > > > > > no process is running, no tape is in the drive > > > > Then there probably is a file named "amflush". Rename it to > > "amflush.0" or "amflush.1" (next free number). > > Maybe you ran amflush or other testing as root? Then some > > files/directores were created as root, and now owned by root, > > amanda cannot write in them. > >I've cleaned everything up the amanda instalation is if a dare say >virginal. I can't figure out where amcheck does get the info. No >amanda process is runing and I' doubled checked theres is absolutely >no file whatsover in /var/lib/amanda/test (indices or curinfo) and >/var/log/amanda is as empty as it could be. I chown'ed all the dirs >the amanda user is sole user > Your user who is running amanda, needs to be a member of the rgoup backup or disk in order to have sufficient perms to do the job. On my system the user running amanda is amanda, so the chown command would be, from one level out of the root directory of anything amanda related "chown -R amanda:disk nameofdir" You must do this recursively, hence the -R. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% 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: amcheck: skipping tape test because amdump or amflush seem to be running
Gene Heskett writes: > On Monday 24 November 2003 13:29, Cedric Boudin wrote: > >Paul Bijnens writes: > > > Cedric Boudin wrote: > > > > Hello honourable readers of the list, > > > > > > > > After some succesfull testing, I wanted to make a run for real. > > > > As recommended in the FAQ I removed: > > > > > > > > -curinfo > > > > -any log files from the log directory > > > > -tapelist > > > > -reseted the changer state file > > > > > > > > so I run the amcheck on a particular configuration and I do > > > > get: > > > > > > > > Amanda Tape Server Host Check > > > > - > > > > Holding disk /var/backups/holdingdisk: 1431256 KB disk space > > > > available, that's plenty WARNING: skipping tape test because > > > > amdump or amflush seem to be running WARNING: if they are not, > > > > you must run amcleanup > > > > NOTE: info dir /var/lib/amanda/test/curinfo/dell: does not > > > > exist NOTE: index dir /var/lib/amanda/test/index/dell: does not > > > > exist Server check took 0.023 seconds > > > > > > > > --- > > > > so I run > > > > amcleanup on the configuration > > > > > > > > and amcheck does not believe me. > > > > > > > > I checked that I did not forget to delete the recommended files > > > > > > > > no process is running, no tape is in the drive > > > > > > Then there probably is a file named "amflush". Rename it to > > > "amflush.0" or "amflush.1" (next free number). > > > Maybe you ran amflush or other testing as root? Then some > > > files/directores were created as root, and now owned by root, > > > amanda cannot write in them. > > > >I've cleaned everything up the amanda instalation is if a dare say > >virginal. I can't figure out where amcheck does get the info. No > >amanda process is runing and I' doubled checked theres is absolutely > >no file whatsover in /var/lib/amanda/test (indices or curinfo) and > >/var/log/amanda is as empty as it could be. I chown'ed all the dirs > >the amanda user is sole user > > > > Your user who is running amanda, needs to be a member of the rgoup > backup or disk in order to have sufficient perms to do the job. Amanda at my place is called backup and belongs to grp backup can read write in /var/lib/amanda/ 700 /etc/amanda 700 /var/backups/holdingdisk 700 /var/log/amanda 700 > > On my system the user running amanda is amanda, so the chown command > would be, from one level out of the root directory of anything amanda > related "chown -R amanda:disk nameofdir" > > You must do this recursively, hence the -R. > > -- > Cheers, Gene > AMD [EMAIL PROTECTED] 320M > [EMAIL PROTECTED] 512M > 99.27% 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: amcheck: skipping tape test because amdump or amflush seem to be running
On Monday 24 November 2003 20:42, Cedric Boudin wrote: >Gene Heskett writes: [...] >Amanda at my place is called backup and belongs to grp backup >can read write in /var/lib/amanda/ 700 /etc/amanda 700 >/var/backups/holdingdisk 700 /var/log/amanda 700 I don't think those '700' perms are kosher. Its beginning to sound as if you didn't unpack, configure and make amanda while su'ed to the proper user. The only time you become root is to do the 'make install'. Here, any amanda related directory looks like this to an ls -l drwxr-xr-x2 amanda disk 4096 Nov 24 00:05 DailySet1 And any file (except a select few in libexec and bin) should look like this: -rw-r--r--1 amanda disk2 Nov 24 16:15 tape-slot At this point I think I would clean house on everything but /usr/local/etc/amanda (assuming your configs are in there) cd to /usr/local/etc and do a 'chown -R amanda:disk amanda' changing the first amanda there to whatever the backup user is on your system. Then cd to one level above the src dir, wipe it out, su to your user, unpack a new one, configure and make it while still as that user. I use a script that tends to keep me honest about the build, and it looks like this, edit the details to suit your general framework. --- #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo " Warning " echo "Amanda needs to be configured and built by the user amanda," echo "but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=your-machines-FQDN \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make Make that script executable, or run it from a shell. When its done, su root, and 'make install' All your perms problems should now be history. > > On my system the user running amanda is amanda, so the chown > > command would be, from one level out of the root directory of > > anything amanda related "chown -R amanda:disk nameofdir" > > > > > > > > You must do this recursively, hence the -R. > > > > -- > > Cheers, Gene > > AMD [EMAIL PROTECTED] 320M > > [EMAIL PROTECTED] 512M > > 99.27% 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. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% 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: Running amdump leads to high CPU load on Linux server
On Sun, Nov 23, 2003 at 07:46:32PM -0500, Kurt Raschke wrote: > ...when amdump runs, the load spikes to between 4.00 and > 6.00, and the system becomes nearly unresponsive for the duration of > the backup. The server is backing up several local partitions, and > also two partitions on remote servers. Are you short of RAM? If the system's paging heavily, that'd make it crawl too. > I've tried starting amdump > with nice and setting it to a low priority, but when gtar and gzip are > started by amanda, the priority setting is somehow lost. Not surprising. Recall that Amanda runs client/server even when backing up the server's DLE's. The client-side processes are descendents of [x]inetd, not of amdump, and so don't inherit the latter's "nice" level. > The server > isn't even trying to back up multiple partitions in parallel, By this do you mean, "only one DLE at a time"; or "only one DLE *from the server* at a time, along with remote backups in parallel"? If the latter, well, of course there's some amount of server-side work even for the remote DLEs. Is the compression for the remote DLEs client- or server-side? If the latter, change "some amount" to "a lot" in the previous sentence :-) -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: Memory requirements for Amanda Server
On Mon, Nov 24, 2003 at 03:26:39PM -0500, Jon LaBadie wrote: > Anyone out there running amanda on a 386 or 486 with 16M of ram? Not any more, but I did in 1995 or thereabouts :-) 486-DX33 (or was it a DX2/66?) with 16 whole megabytes worth of 30-pin SIMMs. It turned out that (a) that wasn't enough RAM, and (b) FreeBSD 2.0.5's low-memory robustness left a fair amount to be desired, as I discovered a few times when I came in in the morning to find the backup server down, and the /var partition, where the holding disk was, thoroughly trashed. (It also turns out that FreeBSD still supports the *3*86 -- last month's 4.9 release contains a bug fix for it. I imagine Linux still does too. Both are equally gratifying...) I think the Amanda version was 2.2.6 -- just saw that mentioned near the beginning of the ChangLog, and it rings a bell. Interesting limitations (some from memory, some from ChangeLog; some probably incorrect): - No changer support. One tape per run; that's it, that's all. - No indexing, no amrecover. Amrestore would pull dumps off the tape, but from there you were strictly on your own. - No gnutar; it was strictly dump. - No "reserve". Effectively, it was hard-wired to 100%. - No "runspercycle". - No chunked dumps on holding disk. - No promote_hills() in the planner. If you missed a tape (e.g. for a holiday), causing that night's full dumps to be postponed, they'd have a strong tendency to stay clumped together with the next night's full dumps for a long time, at least on a small network like the one I was responsible for. - Blair Zajac's extensive patch set hadn't yet been merged into the canonical sources. If you wanted them, you had to download and apply them yourself. I don't believe Jean-Louis was involved yet (from the ChangeLog, runspercycle and chunked dumps were among his early patches); I'm not even sure that (the long-departed) Alexandre Oliva and John R. Jackson were around back then. Truth be told, I think Amanda was rather moribund at the time (hence the existence of BZ's patches in the first place); ISTR that it was Alexandre who woke the project up again. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
