Re: RedHat 7.2 Client timing out?
On Thu, Feb 05, 2004 at 06:20:55AM -0500, Joshua Baker-LePain ([EMAIL PROTECTED]) wrote: > On Thu, 5 Feb 2004 at 2:20am, Michael Kahle wrote [snip] > Well, 7.2 is pretty darn old. But you should be able to get this to work.B "pretty darn old"? If it ain't broke, don't fix it. I have got 4 of those "pretty darn old" servers around, and I am not touching them (other than the occasional bind/sendmail/apache/whatever fix (now non rpm based)). j -- The email address in this email is used for Mailing Lists Only. Please reply ONLY to the list email address, do not reply to the email directly. Goldwaithe's lemma of Murphy's third law: The line in which you are waiting is always the slowest. If you move, the line you move to stops. If you move back, both lines stop, and everyone is angry with you. __, Jobst Schmalenbach, Technical Director _ _.--'-n_/ Barrett Consulting Group P/L & The Meditation Room P/L -(_)--(_)= +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 02:23:42PM -0500, Jon LaBadie wrote: > On Thu, Feb 05, 2004 at 11:04:54AM -0500, stan wrote: > > > > OK, I think I understand. If I do then the follwing should do what I > > intended the original to do: > > > > -- first set --- > > include "./[A-K]*" > > exclude "./[!A-K]*" > > > > -- second set --- > > include "./[!A-K]*" > > > > Or, do I need an exclude on the 2nd set? > > > > I think it is simpler than that. > > -- first set -- > include "./[A-K]*" > > -- second set -- > exclude "./[A-K]*" > > > With the include anything not matching is excluded automatically. > With the exclude, and no include, everything is included except > what is excluded. ool! Thanks for the idea. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin
Re: amrmtape question
I think there should be a command that can completely remove the tape from the Amanda list (remove the label, remove it from the tapelist etc). This will be useful when we need the Amanda tape to do something else, and that's the probelm I am facing now. Kin-Ho Kwan Christoph Scheeder wrote: Hi, amrmtape only removes the entrys for the tape from all databases, but amanda will happily use it if she sees it again as the label on tape is not touched at all. The question is what should be achieved: 1.) make amanda forget about the backups on that tape? -> ok, amrmtape is your friend, it does what you want. 2.) you want amanda to reject the tape when she sees it again? -> "amadmin noreuse" marks the tape as "this tape is not allowed to be overwrite by amanda" 3.) you want to delete the amanda tapelabel and all other data from the tape, so amnda doesn't touch it anymore? -> use dd to overwrite the first block on the tape with 0 or random data. Christoph Dave Ewart schrieb: On Thursday, 05.02.2004 at 10:05 -0500, Kin-Ho Kwan wrote: Hi, Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that Amanda will not use this tape for backup? I try to run "amrmtape -n conf TAPE001", but Amanda still use that tape to backup stuff. Is there any other command I need to run to remove the Amanda label? Reading TFM, I see: -n Generate new tapelist and database files with label removed, but leave them in /tmp and do not update the original copies. I suggest dropping the '-n' ... :-) Dave.
Re: dump incremental level not greater than 1
On Thu, Feb 05, 2004 at 04:15:24PM +0100, [EMAIL PROTECTED] wrote: > in our environment there is one linux system (SuSE 8.1 amanda-2.4.4-41) > where amanda not increase the dump level to 2,3... Presumably the bumpsize/bumpmult/bumpdays criteria are never satisfied. See the documentation of those three amanda.conf parameters in amanda(8). -- | | /\ |-_|/ > 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: amrmtape question
Hi,
before going any further on this path:
Do you/we realy want to change that behavior of amanda ?
It's been there since more or less ancient times!
(At least since amanda-2.4.0 when i started using amanda)
The current behavior has it's pros, but i can't see real contras at
the moment.
amrmtape has always been used to remove the contents of a tape from
amanda's databases, not to make it unusable for amanda.
i can't see a real-life situation where you want to have a tape
with a correct label for a configuration but won't allow amanda to touch
it, that can't be handled with "amadmin noreuse".
I would say we should not touch this behavior without a verry good
reason.
Christoph
Jean-Louis Martineau schrieb:
Hi,
Amanda should not use a tape if it's label is not in the tapelist file.
Could you try this patch.
Jean-Louis
On Thu, Feb 05, 2004 at 05:27:36PM +0100, Christoph Scheeder wrote:
Hi,
amrmtape only removes the entrys for the tape from all databases,
but amanda will happily use it if she sees it again as the label
on tape is not touched at all.
The question is what should be achieved:
1.) make amanda forget about the backups on that tape?
-> ok, amrmtape is your friend, it does what you want.
2.) you want amanda to reject the tape when she sees it again?
-> "amadmin noreuse" marks the tape as
"this tape is not allowed to be overwrite by amanda"
3.) you want to delete the amanda tapelabel and all other data
from the tape, so amnda doesn't touch it anymore?
-> use dd to overwrite the first block on the tape with 0 or random data.
Christoph
Dave Ewart schrieb:
On Thursday, 05.02.2004 at 10:05 -0500, Kin-Ho Kwan wrote:
Hi,
Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that
Amanda will not use this tape for backup?
I try to run "amrmtape -n conf TAPE001", but Amanda still use that
tape to backup stuff. Is there any other command I need to run to
remove the Amanda label?
Reading TFM, I see:
-n Generate new tapelist and database files with label
removed, but leave them in /tmp and do not update the
original copies.
I suggest dropping the '-n' ... :-)
Dave.
diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.4.5b1.orig/server-src/amcheck.c amanda-2.4.5b1.new/server-src/amcheck.c
--- amanda-2.4.5b1.orig/server-src/amcheck.c 2003-11-25 07:21:07.0 -0500
+++ amanda-2.4.5b1.new/server-src/amcheck.c 2004-02-05 11:42:09.0 -0500
@@ -959,7 +959,11 @@ int start_server_check(fd, do_localchk,
tapebad = 1;
} else if(strcmp(label, FAKE_LABEL) != 0) {
tp = lookup_tapelabel(label);
- if(tp != NULL && !reusable_tape(tp)) {
+ if(tp == NULL) {
+ fprintf(outf, "ERROR: label %s match labelstr but it not listed in the tapelist file.\n", label);
+ tapebad = 1;
+ }
+ else if(tp != NULL && !reusable_tape(tp)) {
fprintf(outf, "ERROR: cannot overwrite active tape %s\n", label);
tapebad = 1;
}
diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.4.5b1.orig/server-src/taper.c amanda-2.4.5b1.new/server-src/taper.c
--- amanda-2.4.5b1.orig/server-src/taper.c 2003-11-25 07:21:08.0 -0500
+++ amanda-2.4.5b1.new/server-src/taper.c 2004-02-05 11:42:21.0 -0500
@@ -1791,7 +1791,14 @@ int label_tape()
/* check against tape list */
if (strcmp(label, FAKE_LABEL) != 0) {
tp = lookup_tapelabel(label);
- if(tp != NULL && !reusable_tape(tp)) {
+ if(tp == NULL) {
+ errstr = newvstralloc(errstr,
+ "label ", label,
+ " match labelstr but it not listed in the tapelist file",
+ NULL);
+ return 0;
+ }
+ else if(tp != NULL && !reusable_tape(tp)) {
errstr = newvstralloc(errstr,
"cannot overwrite active tape ", label,
NULL);
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 11:04:54AM -0500, stan wrote: > > OK, I think I understand. If I do then the follwing should do what I > intended the original to do: > > -- first set --- > include "./[A-K]*" > exclude "./[!A-K]*" > > -- second set --- > include "./[!A-K]*" > > Or, do I need an exclude on the 2nd set? > I think it is simpler than that. -- first set -- include "./[A-K]*" -- second set -- exclude "./[A-K]*" With the include anything not matching is excluded automatically. With the exclude, and no include, everything is included except what is excluded. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problem with amflush
Hi, Christoph, on Donnerstag, 05. Februar 2004 at 13:13 you wrote to amanda-users: CS> Hi, CS> i remember i had a simmilar problem about a year ago with amanda. CS> But i didn't have the time to dig deeper in it, as the customer CS> got a bit nervous about not getting flushed his archiv-dumps. CS> So my first try was upgrading amanda to 2.4.4, but that didn't do CS> the trick. CS> Then i moved some amanda-files out of the holding disk, and suddenly CS> it started flushing. Seemd as amada didn't like one of the images in CS> the holdingdisk. CS> So i moved these archives back into the holdingarea, tried to flush CS> again and ... all was flushed fine to tape. CS> So it looks like there a some strange situations in linux which make CS> amflush fail with a specific combination of dumps in the holdingdisk. CS> This problem seems not to be easyly reproduceable, and it seldom CS> occures. Interesting to hear that. I am pretty curious to know what is the problem here. After your mail I would try to move a holdingdisk-dump-dir and see what happens if I was in Rohit's situation. thank you. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amrmtape question
Hi,
Amanda should not use a tape if it's label is not in the tapelist file.
Could you try this patch.
Jean-Louis
On Thu, Feb 05, 2004 at 05:27:36PM +0100, Christoph Scheeder wrote:
> Hi,
>
> amrmtape only removes the entrys for the tape from all databases,
> but amanda will happily use it if she sees it again as the label
> on tape is not touched at all.
>
> The question is what should be achieved:
>
> 1.) make amanda forget about the backups on that tape?
> -> ok, amrmtape is your friend, it does what you want.
>
> 2.) you want amanda to reject the tape when she sees it again?
> -> "amadmin noreuse" marks the tape as
>"this tape is not allowed to be overwrite by amanda"
>
> 3.) you want to delete the amanda tapelabel and all other data
> from the tape, so amnda doesn't touch it anymore?
> -> use dd to overwrite the first block on the tape with 0 or random data.
>
> Christoph
>
> Dave Ewart schrieb:
>
> >On Thursday, 05.02.2004 at 10:05 -0500, Kin-Ho Kwan wrote:
> >
> >
> >>Hi,
> >>
> >>Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that
> >>Amanda will not use this tape for backup?
> >>
> >>I try to run "amrmtape -n conf TAPE001", but Amanda still use that
> >>tape to backup stuff. Is there any other command I need to run to
> >>remove the Amanda label?
> >
> >
> >Reading TFM, I see:
> >
> >-n Generate new tapelist and database files with label
> > removed, but leave them in /tmp and do not update the
> > original copies.
> >
> >I suggest dropping the '-n' ... :-)
> >
> >Dave.
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.4.5b1.orig/server-src/amcheck.c amanda-2.4.5b1.new/server-src/amcheck.c
--- amanda-2.4.5b1.orig/server-src/amcheck.c2003-11-25 07:21:07.0 -0500
+++ amanda-2.4.5b1.new/server-src/amcheck.c 2004-02-05 11:42:09.0 -0500
@@ -959,7 +959,11 @@ int start_server_check(fd, do_localchk,
tapebad = 1;
} else if(strcmp(label, FAKE_LABEL) != 0) {
tp = lookup_tapelabel(label);
- if(tp != NULL && !reusable_tape(tp)) {
+ if(tp == NULL) {
+ fprintf(outf, "ERROR: label %s match labelstr but it not listed in the
tapelist file.\n", label);
+ tapebad = 1;
+ }
+ else if(tp != NULL && !reusable_tape(tp)) {
fprintf(outf, "ERROR: cannot overwrite active tape %s\n", label);
tapebad = 1;
}
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.4.5b1.orig/server-src/taper.c amanda-2.4.5b1.new/server-src/taper.c
--- amanda-2.4.5b1.orig/server-src/taper.c 2003-11-25 07:21:08.0 -0500
+++ amanda-2.4.5b1.new/server-src/taper.c 2004-02-05 11:42:21.0 -0500
@@ -1791,7 +1791,14 @@ int label_tape()
/* check against tape list */
if (strcmp(label, FAKE_LABEL) != 0) {
tp = lookup_tapelabel(label);
- if(tp != NULL && !reusable_tape(tp)) {
+ if(tp == NULL) {
+ errstr = newvstralloc(errstr,
+ "label ", label,
+ " match labelstr but it not listed in the tapelist file",
+ NULL);
+ return 0;
+ }
+ else if(tp != NULL && !reusable_tape(tp)) {
errstr = newvstralloc(errstr,
"cannot overwrite active tape ", label,
NULL);
does amanda count in days or in tapes?
I'm trying to simulate a backup cycle in an accelerated manner. If I use multiple tapes/day, does amanda count in tapes or in days, as reckoned using system clock? Thanks! Eugen Leitl
Re: amrmtape question
Hi, amrmtape only removes the entrys for the tape from all databases, but amanda will happily use it if she sees it again as the label on tape is not touched at all. The question is what should be achieved: 1.) make amanda forget about the backups on that tape? -> ok, amrmtape is your friend, it does what you want. 2.) you want amanda to reject the tape when she sees it again? -> "amadmin noreuse" marks the tape as "this tape is not allowed to be overwrite by amanda" 3.) you want to delete the amanda tapelabel and all other data from the tape, so amnda doesn't touch it anymore? -> use dd to overwrite the first block on the tape with 0 or random data. Christoph Dave Ewart schrieb: On Thursday, 05.02.2004 at 10:05 -0500, Kin-Ho Kwan wrote: Hi, Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that Amanda will not use this tape for backup? I try to run "amrmtape -n conf TAPE001", but Amanda still use that tape to backup stuff. Is there any other command I need to run to remove the Amanda label? Reading TFM, I see: -n Generate new tapelist and database files with label removed, but leave them in /tmp and do not update the original copies. I suggest dropping the '-n' ... :-) Dave.
RE: Problem configure the changer...
> I receive the error: > [EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/libexec/chg-zd-mtx -status changerfile must be specified in > amanda.conf Your problem is your chg-zd-mtx.conf file. You should check the amanda lib directory for the chg-zd-mtx file and read the docs that are in this script. On my system (Debian GNU/Linux "Woody") this file is located in /usr/lib/amanda/chg-zd-mtx. I made this mistake myself. You are using a configuration for a "chg-scsi" script. You need to create a new config file that has the correct configuration information for "chg-zd-mtx". There is no sample mtx config file in the /usr/doc/amanda-common/examples folder. You need to create your own per the instructions in the chg-zd-mtx script itself. Here is my CHANGER.conf file. This is for a Quantum SuperLoader DLT 1280L firstslot=1 lastslot=16 cleanslot=16 autoclean=0 havereader=1 offline_before_unload=0 driveslot=0 poll_drive_ready=3 max_drive_wait=120 Good luck! Michael
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 04:32:26PM +0100, Paul Bijnens wrote:
> stan wrote:
>
> >On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
> >>stan wrote:
> >>
> >/foo/bar/[A-J]*
> >/foo/bar/[K-z]*
> >>
> >>Don't mix uppercase and lowercase in the character maps.
> >>It depends on the current LANG and/or LC_* settings what they
> >>expand to. Probably not what you want.
>
> >Is there a way to this that IS safe given the locale stuff?
>
>
> Stay in a logical range:
>
> is ok: [0-9] [A-Z] [a-z] [!a-z]
>(if you ever used a EBCDIC character set in unix, then even those
> last three were not safe, and included two extra ranges with braces
> etc; no sane person uses EBCDIC anymore today -- I did, but I'm not
> sane.)
>
> is not ok: [A-z] [a-Z]
> (it's not a syntax error, but it does not what you expect it to do!)
>
> The "all except" is encoded by an exclamation mark.
>
> Assume this directory structure:
>
>/d/
>/d/l
>/d/l/e
>/d/d/d
>
> then, this disklist entry does NOT backup /d/d/:
>
>host /d /d {
> include "./l"
> }
>
> so you don't need to an explicit exclude for it.
OK, I think I understand. If I do then the follwing should do what I
intended the original to do:
-- first set ---
include "./[A-K]*"
exclude "./[!A-K]*"
-- second set ---
include "./[!A-K]*"
Or, do I need an exclude on the 2nd set?
What I think this does is abckup _all_ files. Set on gets them if the satrt
with a capital letter in the range A _ >K, and the 2nd set gets all the _do
not_ fit this pattern. Hmm, writing that makes ne realize just how much
better regexs are at expressing these things that English :-)
Thanks for educating me here.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Re: Problem with amflush
Rohit wrote: No core dump was generated. Maybe because the default "ulimit" for core files is 0 (do not generate core files. (try "ulimit -c" in bash) When a program does something illegal, unix dumps it's memory into a file, for the programmers to do some postmortem analysis on the problem. The core file is generated in the current working directory. For amanda that could be: the directory where you started the amflush, or /tmp/amanda, or ~amanda/TheConfig directory (where the amflush.1 file is). I'm not sure which one of the three it is. Try: strace -p pid-of-the-process "strace" (as root or as amanda), shows you the live system calls a program calling. A strong indication of what is is doing (sleep? reading disk? waiting for input on the tty?). (for amflush and driver) Which one is taking CPU? I guess amflush. amflush So I would like to have a core file of amflush. We can force a crash and core dump of a program by sending it signal number 3. First we have to enable the maximum size of a core dump (in this session only, and all the children started by this session). We do this by using the bash builtin command below. Try to examine a core file to find out what it was doing: $ ulimit -c unlimited Then we start amflush as usual. $ amflush Your description of the problem indicates it is now sitting there, doing nothing useful, but taking cpu. So now we force a core dump: and in another window, as amanda or root: $ kill -3 pid-of-amflush and then, cd to where the core file is found (current directory, or /tmp/amanda or ~amanda/TheConfig, I'm not sure), and get a stacktrace: If we have found the core dump (a file with the name "core" in one of those three directories), you can verify if it is indeed a core file of the right program: $ file core core: ELF 32-bit LSB core file of 'amflush' (signal 3), Intel 80386... And then we take the debugger, and have a look in which function the program was, when the hammer hit it. $ gdb /usr/sbin/amflush core gdb> bt I'm not very clear on what you are asking me to do. Can you please elaborate? Here is a typescript: $ ulimit -c unlimited $ ls -l core ls: core: No such file or directory $ sleep 60 & [1] 29644 # We have 60 seconds time to kill that process, the '&' puts it # in the background and bash tells us the pid too # For amflush you'll have to open a different window, and find # the pid by "ps -ef". $ ps -fp 29644 UIDPID PPID C STIME TTY TIME CMD paul 29644 29201 0 16:46 pts/13 00:00:00 sleep 60 $ kill -3 29644 # hit enter here one more time to synchronise the msg: [1]+ Quit(core dumped) sleep 60 $ ls -l core -rw---1 paulnuts90112 Feb 5 16:46 core $ file core core: ELF 32-bit LSB core file of 'sleep' (signal 3), Intel 80386... $ gdb /usr/bin/sleep core GNU gdb 5.2 Copyright 2002 Free Software Foundation, Inc. ... Core was generated by `sleep 60'. Program terminated with signal 3, Quit. ... #0 0x400c75d1 in __libc_nanosleep () at __libc_nanosleep:-1 -1__libc_nanosleep: No such file or directory. in __libc_nanosleep (gdb) # It was in the function nanosleep, and get a backtrace: (gdb) bt #0 0x400c75d1 in __libc_nanosleep () at __libc_nanosleep:-1 #1 0x400c7568 in __sleep (seconds=60) at [...]/linux/sleep.c:85 #2 0x08048972 in error () at error.c:227 #3 0x4003d17d in __libc_start_main (main=0x8048868 , argc=2, ubp_av=0xb694, init=0x8048584, fini=0x8048bfc , rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xb68c) at ../sysdeps/generic/libc-start.c:129 (gdb) quit And if we had the source, we have maybe a clue what was going on (satisfaction *not* garanteed, but for open source software, you do have access to the source!). -- 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: How can I split up a large disk partition?
On Thursday 05 February 2004 09:02, stan wrote:
>On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
>> On Thu, 5 Feb 2004 at 7:49am, stan wrote
>>
>> > Note that for the 2 disks in question, both partial backusp
>> > claim identical size. I beileve that is because they are
>> > assuming the size of the entire partion.
>> >
>> > # black ad1s1e comp-user-no-compress 2 local
>> > black ads1e/ak ad1s1e {
>> >include "./[A-K]*"
>> >exclude "./[L-z]*"
>> >user-tar-no-compress
>> >} 2 local
>> > black ads1e/kz ad1s1e {
>> >include "./[L-z]*"
>> >user-tar-no-compress
>> >} 2 local
>> >
>> > And here is teh dumptupe definition:
>> >
>> > define dumptype root-tar {
>> > program "GNUTAR"
>> > comment "root partitions dumped with tar"
>> > compress none
>> > index
>> > exclude list "/usr/local/lib/amanda/exclude.gtar"
>> > priority low
>> > }
>> >
>> > define dumptype user-tar-no-compress {
>> > compress none
>> > root-tar
>> > comment "user partitions dumped with tar"
>> > priority medium
>> > }
>>
>> The short answer is that order matters. In your disklist entries
>> (DLEs), you specify include, exclude, and then the dumptype. But
>> the dumptype specifies its own exclude (list). In amanda(8), in
>> the part about 'exclude' in the dumptype section, it states that
>> "With the append keyword, the string are appended to the current
>> value of the list, without it, the string overwrite the list."
>> IOW, the 'exclude list' line in the dumptype is overriding the
>> include and exclude directives in your DLEs.
>>
>> So, change your DLEs to specify the dumptype first. Then your
>> include and exclude directives will override those in the
>> dumptype.
>
>I'm confused. The dumptype is defined in amanda.conf, and only the
> disks to backup are defined in the disklist file. I assume that
> amanda.conf is read first, right?
Correct, but when you reference an already defined dumptype, that is
read into *this* specification, including its exclude pattern.
Therefore, if you want a different exclude pattern or file, it must
be specified after the included dumptype so that it can replace the
one in the dumptype.
> The disks are shown in my email
> in the order that they appear in the disklists file.
>
>Should I just remove the exclude file line in the dumptype?
If its not being used anyplace else, you can remove it.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 09:21:16AM -0500, Joshua Baker-LePain wrote:
> On Thu, 5 Feb 2004 at 9:02am, stan wrote
>
> > On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> > > On Thu, 5 Feb 2004 at 7:49am, stan wrote
> > >
> > > > Note that for the 2 disks in question, both partial backusp claim identical
> > > > size. I beileve that is because they are assuming the size of the entire
> > > > partion.
> > > >
> > > > # black ad1s1e comp-user-no-compress 2 local
> > > > black ads1e/ak ad1s1e {
> > > > include "./[A-K]*"
> > > > exclude "./[L-z]*"
> > > > user-tar-no-compress
> > > > } 2 local
> > > > black ads1e/kz ad1s1e {
> > > > include "./[L-z]*"
> > > > user-tar-no-compress
> > > > } 2 local
> > > >
> > > > And here is teh dumptupe definition:
> > > >
> > > > define dumptype root-tar {
> > > > program "GNUTAR"
> > > > comment "root partitions dumped with tar"
> > > > compress none
> > > > index
> > > > exclude list "/usr/local/lib/amanda/exclude.gtar"
> > > > priority low
> > > > }
> > > >
> > > > define dumptype user-tar-no-compress {
> > > > compress none
> > > > root-tar
> > > > comment "user partitions dumped with tar"
> > > > priority medium
> > > > }
> > >
> > > The short answer is that order matters. In your disklist entries (DLEs),
> > > you specify include, exclude, and then the dumptype. But the dumptype
> > > specifies its own exclude (list). In amanda(8), in the part about
> > > 'exclude' in the dumptype section, it states that "With the append
> > > keyword, the string are appended to the current value of the list, without
> > > it, the string overwrite the list." IOW, the 'exclude list' line in the
> > > dumptype is overriding the include and exclude directives in your DLEs.
> > >
> > > So, change your DLEs to specify the dumptype first. Then your include and
> > > exclude directives will override those in the dumptype.
> > >
> >
> > I'm confused. The dumptype is defined in amanda.conf, and only the disks to
> > backup are defined in the disklist file. I assume that amanda.conf is read
> > first, right? The disks are shown in my email in the oreder that they
> > appear in the disklists file.
> >
> > Sould I just remove the exclude file line in the dumptape?
>
> You could, and that would fix it, but you should understand what's going
> on. Yes, amanda.conf is read first. But that's not what I was saying
> above. For each DLE, you specify a dumptype. You can do that simply, by
> just using one that's in amanda.conf. Or you can put an entirely new one
> in braces. In those braces, just as in amanda.conf, you can include
> previously-defined dumptypes.
>
> Read through one of your DLEs line by line, applying directives.
> In the first one, you 'include "./[A-K]*"', then 'exclude "./[L-z]*"', and
> then you have the entry for the dumptype. Logically, amanda continues
> parsing the DLE by parsing the dumptype you specified. So your whole DLE
> looks like this to amanda:
>
> black ads1e/ak ad1s1e {
>include "./[A-K]*"
>exclude "./[L-z]*"
>compress none #NOTE - user-tar starts here
>program "GNUTAR" #...and includes root-tar here
>comment "root partitions dumped with tar"
>compress none
>index
>exclude list "/usr/local/lib/amanda/exclude.gtar"
>priority low #root-tar ends here
>comment "user partitions dumped with tar" #this is the rest of user-tar
>priority medium
> } 2 local
>
> The 'exlude list', coming after the 'exclude', overrides it. If, in those
> braces, you specified user-tar-no-compress before your include and exclude
> directives, then your 'exclude' would override the 'exclude list'.
>
> Make any more sense?
Much more sense.
Thanks for taking the time to educate me on this.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Re: Problem configure the changer...
On Thursday 05 February 2004 09:02, Ilya Basin wrote:
>Hi!
>Could you please help me with the conf of Amanda?
>I don't understand where did I make an error in the
> configuration
>
>I receive the error:
>[EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/libexec/chg-zd-mtx -status
> changerfile must be specified in amanda.conf
>
>But when i test the MTX (ZD for source forge):
>[EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/sbin/mtx -f /dev/sg2
> status Storage Changer /dev/sg2:2 Drives, 61 Slots ( 1
> Import/Export ) Data Transfer Element 0:Empty
>Data Transfer Element 1:Empty
> Storage Element 1:Full :VolumeTag=MSK001
> Storage Element 2:Full :VolumeTag=MSK002
> Storage Element 3:Full :VolumeTag=MSK003
> Storage Element 4:Full :VolumeTag=MSK004
> Storage Element 5:Full :VolumeTag=MSK005
> Storage Element 6:Full :VolumeTag=MSK006
> Storage Element 7:Full :VolumeTag=MSK007
> Storage Element 8:Full :VolumeTag=MSK008
> Storage Element 9:Full :VolumeTag=MSK009
> Storage Element 10:Full :VolumeTag=MSK010
> Storage Element 11:Full :VolumeTag=MSK011
> Storage Element 12:Full :VolumeTag=MSK012
> Storage Element 13:Full :VolumeTag=MSK013
> Storage Element 14:Full :VolumeTag=MSK014
> Storage Element 15:Full :VolumeTag=MSK015
> Storage Element 16:Full :VolumeTag=MSK016
> Storage Element 17:Full :VolumeTag=MSK017
> Storage Element 18:Full :VolumeTag=MSK018
> Storage Element 19:Full :VolumeTag=MSK019
> Storage Element 20:Full :VolumeTag=MSK020
> Storage Element 21:Full :VolumeTag=CLN001
> Storage Element 22:Full :VolumeTag=CLN002
> Storage Element 23:Empty
> Storage Element 24:Empty
> Storage Element 25:Empty
> Storage Element 26:Empty
> Storage Element 27:Empty
> Storage Element 28:Empty
> Storage Element 29:Empty
> Storage Element 30:Empty
> Storage Element 31:Empty
> Storage Element 32:Empty
> Storage Element 33:Empty
> Storage Element 34:Empty
> Storage Element 35:Empty
> Storage Element 36:Empty
> Storage Element 37:Empty
> Storage Element 38:Empty
> Storage Element 39:Empty
> Storage Element 40:Empty
> Storage Element 41:Empty
> Storage Element 42:Empty
> Storage Element 43:Empty
> Storage Element 44:Empty
> Storage Element 45:Empty
> Storage Element 46:Empty
> Storage Element 47:Empty
> Storage Element 48:Empty
> Storage Element 49:Empty
> Storage Element 50:Empty
> Storage Element 51:Empty
> Storage Element 52:Empty
> Storage Element 53:Empty
> Storage Element 54:Empty
> Storage Element 55:Empty
> Storage Element 56:Empty
> Storage Element 57:Empty
> Storage Element 58:Empty
> Storage Element 59:Empty
> Storage Element 60:Empty
> Storage Element 61 IMPORT/EXPORT:Empty
>
>
Only 20 tapes as both drives report they are empty?
>
>Here there are two my files...
>/etc/amanda/Daily01/amanda.conf:
>
>org "Daily01"
>mailto "amanda"
>dumpuser "amanda"
>inparallel 4
>netusage 600 Kbps
>dumpcycle 4 weeks
>runspercycle 20
>
>tapecycle 25 tapes
One really should have at least 2x runspercycle * runtapes in the
tapecycle, unless your data isn't worth much :) Ask yourself what
happens if the last good backup of that item was on the tape you just
reused, that tape is now bad and can't be read, and the system needs
a bare metal recovery. With runspercycle * runtapes * 2 tapes in the
tapecycle, you at least can back up to the previous backup and won't
have to restart your business from scratch.
>runtapes 2
>tpchanger "chg-zd-mtx"
>tapedev "0"
>changerdev /dev/sg2
>changerfile "/etc/amanda/Daily01/chg-zd-mtx"
>
>tapetype DLT7000
>labelstr "^MSK[0-9][0-9]*$"
>
>define tapetype DLT7000 {
>comment "DLT tape drives"
>length 35000 mbytes # 35 Gig tapes
>filemark 8 kbytes # I don't know what this means
>speed 10 mbytes # 10 Mb/s
>}
>
>/etc/amanda/Daily01/chg-zd-mtx.conf:
>number_configs 2
>eject 1 # Tapedrives need an eject command
>sleep 90 # Seconds to wait until the tape
> gets ready cleanmax100 # How many times could a
> cleaning tape get used
>changerdev /dev/sg2
>
>
>#
># Next comes the data for drive 0
>#
>config 0
>drivenum0
>dev /dev/nst0
>scsitapedev /dev/st0
I believe this should be the same as the drive itself, eg
non-rewinding, or /dev/nst0
>driveslot 0
>startuse1 # The slots associated with the
> drive 0 enduse 10 #
>statfile/etc/amanda/dailuyset/tape0-slot # The file
> where the
>actual slot is stored
>autoclean 25
>cleancart 5 # the slot where the
> cleaningcartridge for drive 0 is located
>cleanslot 21
>haver
RE: How to compile Amanda on HPUX
> have anyone successfully compiled amanda on HPUX? Which parameter you > defined for CFLAGS? Compiled fine with the HP-UX ANSI C compiler (v03.37.01) on HP-UX 11i. Here's the original ./configure invocation, from the config/config.h file: #define CONFIGURE_COMMAND "'configure' '--disable-libtool' '--disable-gcc' '--prefix=/opt/amanda' '--with-amandahosts' '--with-assertions' '--with-buffered-dump=yes' '--with-configdir=/opt/amanda/etc' '--with-debugging' '--with-gnutar-listdir=/var/opt/amanda/gnutar-lists' '--with-gnutar=/opt/gnu/bin/tar' '--with-group=amanda' '--with-pid-debug-files' '--with-rundump' '--with-user=amanda' 'CFLAGS=+DAportable -D_XOPEN_SOURCE_EXTENDED -Ae'" (I've also built earlier versions successfully using GCC 2.95.2, but I can't find what I used for CFLAGS in those builds...) I take it that the default CFLAGS value doesn't working for you? Good luck!
Re: How can I split up a large disk partition?
stan wrote:
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
stan wrote:
/foo/bar/[A-J]*
/foo/bar/[K-z]*
Don't mix uppercase and lowercase in the character maps.
It depends on the current LANG and/or LC_* settings what they
expand to. Probably not what you want.
Is there a way to this that IS safe given the locale stuff?
Stay in a logical range:
is ok: [0-9] [A-Z] [a-z] [!a-z]
(if you ever used a EBCDIC character set in unix, then even those
last three were not safe, and included two extra ranges with braces
etc; no sane person uses EBCDIC anymore today -- I did, but I'm not
sane.)
is not ok: [A-z] [a-Z]
(it's not a syntax error, but it does not what you expect it to do!)
The "all except" is encoded by an exclamation mark.
Assume this directory structure:
/d/
/d/l
/d/l/e
/d/d/d
then, this disklist entry does NOT backup /d/d/:
host /d /d {
include "./l"
}
so you don't need to an explicit exclude for it.
--
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 *
***
dump incremental level not greater than 1
Hi in our environment there is one linux system (SuSE 8.1 amanda-2.4.4-41) where amanda not increase the dump level to 2,3... Any ideas ? Thankx a lot in advance Leo --Leopold Schenner (E-Mail: [EMAIL PROTECTED])EBEWE Pharma Tel: ++43 7665 8123 319Mondseestrasse 11 Fax: ++43 7665 8123 114866 Unterach, Austriahttp://www.ebewe.com
Re: amrmtape question
On Thursday, 05.02.2004 at 10:05 -0500, Kin-Ho Kwan wrote: > Hi, > > Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that > Amanda will not use this tape for backup? > > I try to run "amrmtape -n conf TAPE001", but Amanda still use that > tape to backup stuff. Is there any other command I need to run to > remove the Amanda label? Reading TFM, I see: -n Generate new tapelist and database files with label removed, but leave them in /tmp and do not update the original copies. I suggest dropping the '-n' ... :-) Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
amrmtape question
Hi, Is it sufficient enough to just run "amrmtape -n conf TAPE001" so that Amanda will not use this tape for backup? I try to run "amrmtape -n conf TAPE001", but Amanda still use that tape to backup stuff. Is there any other command I need to run to remove the Amanda label? Thanks Kin-Ho Kwan
Re: How can I split up a large disk partition?
On Thu, 5 Feb 2004 at 9:02am, stan wrote
> On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> > On Thu, 5 Feb 2004 at 7:49am, stan wrote
> >
> > > Note that for the 2 disks in question, both partial backusp claim identical
> > > size. I beileve that is because they are assuming the size of the entire
> > > partion.
> > >
> > > # black ad1s1e comp-user-no-compress 2 local
> > > black ads1e/ak ad1s1e {
> > > include "./[A-K]*"
> > > exclude "./[L-z]*"
> > > user-tar-no-compress
> > > } 2 local
> > > black ads1e/kz ad1s1e {
> > > include "./[L-z]*"
> > > user-tar-no-compress
> > > } 2 local
> > >
> > > And here is teh dumptupe definition:
> > >
> > > define dumptype root-tar {
> > > program "GNUTAR"
> > > comment "root partitions dumped with tar"
> > > compress none
> > > index
> > > exclude list "/usr/local/lib/amanda/exclude.gtar"
> > > priority low
> > > }
> > >
> > > define dumptype user-tar-no-compress {
> > > compress none
> > > root-tar
> > > comment "user partitions dumped with tar"
> > > priority medium
> > > }
> >
> > The short answer is that order matters. In your disklist entries (DLEs),
> > you specify include, exclude, and then the dumptype. But the dumptype
> > specifies its own exclude (list). In amanda(8), in the part about
> > 'exclude' in the dumptype section, it states that "With the append
> > keyword, the string are appended to the current value of the list, without
> > it, the string overwrite the list." IOW, the 'exclude list' line in the
> > dumptype is overriding the include and exclude directives in your DLEs.
> >
> > So, change your DLEs to specify the dumptype first. Then your include and
> > exclude directives will override those in the dumptype.
> >
>
> I'm confused. The dumptype is defined in amanda.conf, and only the disks to
> backup are defined in the disklist file. I assume that amanda.conf is read
> first, right? The disks are shown in my email in the oreder that they
> appear in the disklists file.
>
> Sould I just remove the exclude file line in the dumptape?
You could, and that would fix it, but you should understand what's going
on. Yes, amanda.conf is read first. But that's not what I was saying
above. For each DLE, you specify a dumptype. You can do that simply, by
just using one that's in amanda.conf. Or you can put an entirely new one
in braces. In those braces, just as in amanda.conf, you can include
previously-defined dumptypes.
Read through one of your DLEs line by line, applying directives.
In the first one, you 'include "./[A-K]*"', then 'exclude "./[L-z]*"', and
then you have the entry for the dumptype. Logically, amanda continues
parsing the DLE by parsing the dumptype you specified. So your whole DLE
looks like this to amanda:
black ads1e/ak ad1s1e {
include "./[A-K]*"
exclude "./[L-z]*"
compress none #NOTE - user-tar starts here
program "GNUTAR" #...and includes root-tar here
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low #root-tar ends here
comment "user partitions dumped with tar" #this is the rest of user-tar
priority medium
} 2 local
The 'exlude list', coming after the 'exclude', overrides it. If, in those
braces, you specified user-tar-no-compress before your include and exclude
directives, then your 'exclude' would override the 'exclude list'.
Make any more sense?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: Problem configure the changer...
On Thu, 5 Feb 2004 at 5:02pm, Ilya Basin wrote > I receive the error: > [EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/libexec/chg-zd-mtx -status > changerfile must be specified in amanda.conf > /etc/amanda/Daily01/chg-zd-mtx.conf: > number_configs 2 > eject 1 # Tapedrives need an eject command > sleep 90 # Seconds to wait until the tape gets ready > cleanmax100 # How many times could a cleaning tape get > used > changerdev /dev/sg2 *snip* Erm, that doesn't look like a proper chg-zd-mtx config file -- that changer doesn't have a lot of those directives. Maybe chg-scsi would work with those? All the possible config variables for chg-zd-mtx are documented in the chg-zd-mtx script itself installed (by default) in /usr/local/libexec. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote: > stan wrote: > > >>>/foo/bar/[A-J]* > >>>/foo/bar/[K-z]* > > Don't mix uppercase and lowercase in the character maps. > It depends on the current LANG and/or LC_* settings what they > expand to. Probably not what you want. > > Maybe you need this: > > /foo/bar/[A-J]* > /foo/bar/[K-Za-z]* > > Also notice these are not complementary!!! > A file named: > > /foo/bar/123 Acutally thta was why I did waht I did. Looking at man ascii, it appeared that the second line would catch all possible filenames NOT matched by the first one. Is there a way to this that IS safe given the locale stuff? > -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
> stan wrote:
>
> >>>/foo/bar/[A-J]*
> >>>/foo/bar/[K-z]*
>
> Don't mix uppercase and lowercase in the character maps.
> It depends on the current LANG and/or LC_* settings what they
> expand to. Probably not what you want.
>
> Maybe you need this:
>
> /foo/bar/[A-J]*
> /foo/bar/[K-Za-z]*
>
> Also notice these are not complementary!!!
> A file named:
>
> /foo/bar/123
>
> matches neither of the above!
A good point, and although the data in those locations would not presently
fall intot the trap you have spotted, I will take your sugestions to
improve the regex. Thansk for that idea!
>
> >here are my new disklist entries:
> >
> ># black ad1s1e comp-user-no-compress 2 local
> >black ads1e/ak ad1s1e {
> > include "./[A-K]*"
> > exclude "./[L-z]*"
> > user-tar-no-compress
> > } 2 local
>
> You dumptype below has:
>
> >define dumptype user-tar-no-compress {
> >compress none
> >root-tar
> >comment "user partitions dumped with tar"
> >priority medium
> >}
> >
> >What did I do wrong?
>
> Amanda processes the file top to bottom.
> You include the dumptype after the local "exclude" statement,
> and your dumptype also has an exclude. There is no "append"
> keyword on that exclude, so it replaces the current list.
See my ealrier reply as to this.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Re: How can I split up a large disk partition?
On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> On Thu, 5 Feb 2004 at 7:49am, stan wrote
>
> > Note that for the 2 disks in question, both partial backusp claim identical
> > size. I beileve that is because they are assuming the size of the entire
> > partion.
> >
> > # black ad1s1e comp-user-no-compress 2 local
> > black ads1e/ak ad1s1e {
> > include "./[A-K]*"
> > exclude "./[L-z]*"
> > user-tar-no-compress
> > } 2 local
> > black ads1e/kz ad1s1e {
> > include "./[L-z]*"
> > user-tar-no-compress
> > } 2 local
> >
> > And here is teh dumptupe definition:
> >
> > define dumptype root-tar {
> > program "GNUTAR"
> > comment "root partitions dumped with tar"
> > compress none
> > index
> > exclude list "/usr/local/lib/amanda/exclude.gtar"
> > priority low
> > }
> >
> > define dumptype user-tar-no-compress {
> > compress none
> > root-tar
> > comment "user partitions dumped with tar"
> > priority medium
> > }
>
> The short answer is that order matters. In your disklist entries (DLEs),
> you specify include, exclude, and then the dumptype. But the dumptype
> specifies its own exclude (list). In amanda(8), in the part about
> 'exclude' in the dumptype section, it states that "With the append
> keyword, the string are appended to the current value of the list, without
> it, the string overwrite the list." IOW, the 'exclude list' line in the
> dumptype is overriding the include and exclude directives in your DLEs.
>
> So, change your DLEs to specify the dumptype first. Then your include and
> exclude directives will override those in the dumptype.
>
I'm confused. The dumptype is defined in amanda.conf, and only the disks to
backup are defined in the disklist file. I assume that amanda.conf is read
first, right? The disks are shown in my email in the oreder that they
appear in the disklists file.
Sould I just remove the exclude file line in the dumptape?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Problem configure the changer...
Hi!
Could you please help me with the conf of Amanda?
I don't understand where did I make an error in the configuration
I receive the error:
[EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/libexec/chg-zd-mtx -status
changerfile must be specified in amanda.conf
But when i test the MTX (ZD for source forge):
[EMAIL PROTECTED]:/etc/amanda/Daily01$ /usr/sbin/mtx -f /dev/sg2 status
Storage Changer /dev/sg2:2 Drives, 61 Slots ( 1 Import/Export )
Data Transfer Element 0:Empty
Data Transfer Element 1:Empty
Storage Element 1:Full :VolumeTag=MSK001
Storage Element 2:Full :VolumeTag=MSK002
Storage Element 3:Full :VolumeTag=MSK003
Storage Element 4:Full :VolumeTag=MSK004
Storage Element 5:Full :VolumeTag=MSK005
Storage Element 6:Full :VolumeTag=MSK006
Storage Element 7:Full :VolumeTag=MSK007
Storage Element 8:Full :VolumeTag=MSK008
Storage Element 9:Full :VolumeTag=MSK009
Storage Element 10:Full :VolumeTag=MSK010
Storage Element 11:Full :VolumeTag=MSK011
Storage Element 12:Full :VolumeTag=MSK012
Storage Element 13:Full :VolumeTag=MSK013
Storage Element 14:Full :VolumeTag=MSK014
Storage Element 15:Full :VolumeTag=MSK015
Storage Element 16:Full :VolumeTag=MSK016
Storage Element 17:Full :VolumeTag=MSK017
Storage Element 18:Full :VolumeTag=MSK018
Storage Element 19:Full :VolumeTag=MSK019
Storage Element 20:Full :VolumeTag=MSK020
Storage Element 21:Full :VolumeTag=CLN001
Storage Element 22:Full :VolumeTag=CLN002
Storage Element 23:Empty
Storage Element 24:Empty
Storage Element 25:Empty
Storage Element 26:Empty
Storage Element 27:Empty
Storage Element 28:Empty
Storage Element 29:Empty
Storage Element 30:Empty
Storage Element 31:Empty
Storage Element 32:Empty
Storage Element 33:Empty
Storage Element 34:Empty
Storage Element 35:Empty
Storage Element 36:Empty
Storage Element 37:Empty
Storage Element 38:Empty
Storage Element 39:Empty
Storage Element 40:Empty
Storage Element 41:Empty
Storage Element 42:Empty
Storage Element 43:Empty
Storage Element 44:Empty
Storage Element 45:Empty
Storage Element 46:Empty
Storage Element 47:Empty
Storage Element 48:Empty
Storage Element 49:Empty
Storage Element 50:Empty
Storage Element 51:Empty
Storage Element 52:Empty
Storage Element 53:Empty
Storage Element 54:Empty
Storage Element 55:Empty
Storage Element 56:Empty
Storage Element 57:Empty
Storage Element 58:Empty
Storage Element 59:Empty
Storage Element 60:Empty
Storage Element 61 IMPORT/EXPORT:Empty
Here there are two my files...
/etc/amanda/Daily01/amanda.conf:
org "Daily01"
mailto "amanda"
dumpuser "amanda"
inparallel 4
netusage 600 Kbps
dumpcycle 4 weeks
runspercycle 20
tapecycle 25 tapes
runtapes 2
tpchanger "chg-zd-mtx"
tapedev "0"
changerdev /dev/sg2
changerfile "/etc/amanda/Daily01/chg-zd-mtx"
tapetype DLT7000
labelstr "^MSK[0-9][0-9]*$"
define tapetype DLT7000 {
comment "DLT tape drives"
length 35000 mbytes # 35 Gig tapes
filemark 8 kbytes # I don't know what this means
speed 10 mbytes # 10 Mb/s
}
/etc/amanda/Daily01/chg-zd-mtx.conf:
number_configs 2
eject 1 # Tapedrives need an eject command
sleep 90 # Seconds to wait until the tape gets ready
cleanmax100 # How many times could a cleaning tape get
used
changerdev /dev/sg2
#
# Next comes the data for drive 0
#
config 0
drivenum0
dev /dev/nst0
scsitapedev /dev/st0
driveslot 0
startuse1 # The slots associated with the drive 0
enduse 10 #
statfile/etc/amanda/dailuyset/tape0-slot # The file where
the
actual slot is stored
autoclean 25
cleancart 5 # the slot where the cleaningcartridge for
drive 0 is located
cleanslot 21
havereader 1
offline_before_unload 1
unloadpause 15
poll_drive_ready5
max_drive_wait 120
initial_poll_delay 10
cleanfile /etc/amanda/DailySet01/tape0-clean # The file where the
cleanings are recorded
usagecount /etc/amanda/DailySet01/totaltime0
tapestatus /etc/amanda/DailySet01/tapestatus0 # here will some status
infos be stored
labelfile /etc/amanda/DailySet01/labelfile0 # Use this if you have an
barcode reader
#
# Next comes the data for drive 1
#
config 1
drivenum1
dev /dev/nst1
scsitapedev /dev/st1
driveslot 0
startuse11 # The slots associated with the drive 0
enduse 20 #
statfile/
Re: How can I split up a large disk partition?
stan wrote:
/foo/bar/[A-J]*
/foo/bar/[K-z]*
Don't mix uppercase and lowercase in the character maps.
It depends on the current LANG and/or LC_* settings what they
expand to. Probably not what you want.
Maybe you need this:
/foo/bar/[A-J]*
/foo/bar/[K-Za-z]*
Also notice these are not complementary!!!
A file named:
/foo/bar/123
matches neither of the above!
here are my new disklist entries:
# black ad1s1e comp-user-no-compress 2 local
black ads1e/ak ad1s1e {
include "./[A-K]*"
exclude "./[L-z]*"
user-tar-no-compress
} 2 local
You dumptype below has:
define dumptype user-tar-no-compress {
compress none
root-tar
comment "user partitions dumped with tar"
priority medium
}
What did I do wrong?
Amanda processes the file top to bottom.
You include the dumptype after the local "exclude" statement,
and your dumptype also has an exclude. There is no "append"
keyword on that exclude, so it replaces the current list.
Two possible solution:
1. use the "append" keyword on the right place
2. put the dumptype before the exlude line:
black ads1e/ak ad1s1e {
user-tar-no-compress
include append "./[A-K]*"
exclude append "./[!A-K]*"
} 2 local
(actually that last exclude is not necessary. You may
find yourself why as homework :-) )
Verify what would the parameters of a host:/DLE with
$ amadmin Theconfig disklist Host /D/L/E
--
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: How can I split up a large disk partition?
On Thu, 5 Feb 2004 at 7:49am, stan wrote
> Note that for the 2 disks in question, both partial backusp claim identical
> size. I beileve that is because they are assuming the size of the entire
> partion.
>
> # black ad1s1e comp-user-no-compress 2 local
> black ads1e/ak ad1s1e {
> include "./[A-K]*"
> exclude "./[L-z]*"
> user-tar-no-compress
> } 2 local
> black ads1e/kz ad1s1e {
> include "./[L-z]*"
> user-tar-no-compress
> } 2 local
>
> And here is teh dumptupe definition:
>
> define dumptype root-tar {
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> index
> exclude list "/usr/local/lib/amanda/exclude.gtar"
> priority low
> }
>
> define dumptype user-tar-no-compress {
> compress none
> root-tar
> comment "user partitions dumped with tar"
> priority medium
> }
The short answer is that order matters. In your disklist entries (DLEs),
you specify include, exclude, and then the dumptype. But the dumptype
specifies its own exclude (list). In amanda(8), in the part about
'exclude' in the dumptype section, it states that "With the append
keyword, the string are appended to the current value of the list, without
it, the string overwrite the list." IOW, the 'exclude list' line in the
dumptype is overriding the include and exclude directives in your DLEs.
So, change your DLEs to specify the dumptype first. Then your include and
exclude directives will override those in the dumptype.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: How to compile Amanda on HPUX
On Thu, Feb 05, 2004 at 01:06:58PM +1100, Yung Le wrote: > Hi, > have anyone successfully compiled amanda on HPUX? Which parameter you > defined for CFLAGS? > Regards, > Yung What version of HP-IX? And have you checked to see if the porting center has a ported copy for your version? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin
Re: Problem with amflush
> You'll have to find out why there is no schedule generated. > The schedule is generated by "amflush" and piped into "driver". > Is there a core dump in /tmp/amanda or in ~/amanda/TheConfig ? > Can you find out if they are running? And what it's doing? No core dump was generated. > Try: strace -p pid-of-the-process > > (for amflush and driver) > Which one is taking CPU? I guess amflush. amflush > Try to examine a core file to find out what it was doing: >$ ulimit -c unlimited >$ amflush > and in another window, as amanda or root: > >$ kill -3 pid-of-amflush > > and then, cd to where the core file is found (current directory, > or /tmp/amanda or ~amanda/TheConfig, I'm not sure), and > get a stacktrace: > >$ gdb /usr/sbin/amflush core >gdb> bt I'm not very clear on what you are asking me to do. Can you please elaborate? Thanks! Rohit
Re: How can I split up a large disk partition?
On Tue, Feb 03, 2004 at 07:23:20PM -0500, Joshua Baker-LePain wrote:
> On Tue, 3 Feb 2004 at 7:16pm, stan wrote
>
> > I've got a couple of 120G disk that contain files in a serries of
> > directories. I need to split these up to allow my DLT40 tape to back up
> > smaller checks.
> >
> > What I have in mind is something like this:
> >
> > /foo/bar/[A-J]*
> > /foo/bar/[K-z]*
> >
> > But if I put that in the disklist file amcheck says it's invalid.
> >
> > Is there any way I can acomplish this?
>
> This is a *very* frequently asked question (in fact we just finished a
> thread on this). The list archives should be rife with examples (as is
> the disklist included in the amanda tarball). If those don't help you
> out, come on back with your disklist file and the exact errors you're
> getting.
OK, I tried to get this set up, but I must be missing something On last
nights run Amanda failed to backup all of these new "disk" entries. It
thought they were all larger than the tape, which the whole partitons are,
but the subsets I defined ate not.
Here's what amstatus had to say while running:
Script started on Thu Feb 5 06:25:13 2004
$ amstatus DailyDump
Using /usr/local/amanda/var/DailyDump/amdump from Thu Feb 5 00:45:01 EST 2004
black:ad0s1a 018781k finished (1:02:44)
black:ad0s1f 0 1386k finished (1:01:23)
black:ad0s1g 113591k finished (1:06:13)
black:ad6s1e 0 18086197k writing to tape (3:37:32)
black:ads1e/ak 0 planner: [dump larger than tape, 25191930 KB, but cannot incremental
dump new disk]
black:ads1e/kz 0 planner: [dump larger than tape, 25191930 KB, but cannot incremental
dump new disk]
black:ads2e/ak 0 planner: [dump larger than tape, 20386670 KB, but cannot incremental
dump new disk]
black:ads2e/kz 0 planner: [dump larger than tape, 20386670 KB, but cannot incremental
dump new disk]
Note that for the 2 disks in question, both partial backusp claim identical
size. I beileve that is because they are assuming the size of the entire
partion.
here are my new disklist entries:
# black
black ad0s1a comp-user 1 local
black ad0s1f comp-user 1 local
black ad0s1g comp-user 1 local
# black ad1s1e comp-user-no-compress 2 local
black ads1e/ak ad1s1e {
include "./[A-K]*"
exclude "./[L-z]*"
user-tar-no-compress
} 2 local
black ads1e/kz ad1s1e {
include "./[L-z]*"
user-tar-no-compress
} 2 local
# black ad2s1e comp-user-no-compress 3 local
black ads2e/ak ad2s1e {
include "./[A-K]*"
exclude "./[L-z]*"
user-tar-no-compress
} 3 local
black ads2e/kz ad2s1e {
include "./[L-z]*"
user-tar-no-compress
} 3 local
black ad6s1e comp-user 4 local
And here is teh dumptupe definition:
define dumptype root-tar {
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low
}
define dumptype user-tar-no-compress {
compress none
root-tar
comment "user partitions dumped with tar"
priority medium
}
What did I do wrong?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Re: Problem with amflush
On Thursday 05 February 2004 00:59, Rohit wrote: >> OK, please take that to the next logical step. >> >> Amanda is telling you you have "cruft directories" as well >> as "apparently good amanda directories". Is there anything >> in those directories? Perhaps your apparently good directories >> also contain "cruft", and only cruft *** . >> >> At the end of an amdump run amanda tries to remove the directory >> it was using. It "should" have already removed all files from >> those directories so a basic "rmdir" type remove should work. >> But if any "cruft" is left behind, the "rmdir" action will not >> remove the directory and it will "look like" there is still >> something needing flushing. > >I just checked all the directories begining with 2004* in the > holding disk and yes all of them have amanda backup dumps in them. > >There is one more non amanda directory called "windows". I use this >directory to backup windows servers [non amanda backup process - > manual] > >Thanks! I *think* that would be considered a cruft directory by amanda. Amanda expects to have total control over its holding disk area, so I think I'd move that one out off amanda's playpen. That might solve your problems, given enough flush time and tapes. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: Problem with amflush
Hi, i remember i had a simmilar problem about a year ago with amanda. But i didn't have the time to dig deeper in it, as the customer got a bit nervous about not getting flushed his archiv-dumps. So my first try was upgrading amanda to 2.4.4, but that didn't do the trick. Then i moved some amanda-files out of the holding disk, and suddenly it started flushing. Seemd as amada didn't like one of the images in the holdingdisk. So i moved these archives back into the holdingarea, tried to flush again and ... all was flushed fine to tape. So it looks like there a some strange situations in linux which make amflush fail with a specific combination of dumps in the holdingdisk. This problem seems not to be easyly reproduceable, and it seldom occures. Christoph PS: to make a tape reusable use amrmtape it deletes all references to this tape in the amanda database, but does not touch the tape itself. you won't have to relabel it, it will be recognised as a "new tape" when you insert it. Rohit schrieb: As Paul assumed in another branch of this thread, you might have more than one AMANDA-installation on your machine. Have you tried several installations and maybe failed to remove one? No. It was installed via RPM and it one and only amanda installation I have on that machine. What does a simple "find / -name amflush -type f" give you? # find / -name amflush -type f find: /proc/4059/fd: No such file or directory find: /proc/10993/fd: No such file or directory /usr/sbin/amflush /var/lib/amanda/DailySet1/amflush If you find more than one amflush, it is very likely that you call "the wrong one". Maybe it was compiled with different directories and such. Looks like not. Check if the directories contain something useful or if the contain something that does not belong there. What is the "windows"-dir there? There is one more non-amanda directory called "windows". I use this directory to backup windows servers [non amanda backup process - manual] In a properly configured holdingdisk there should not exist anything else than files created by amdump. "There shall not be anything beside me!", if you like it that way ;) Ok. Can I create one more directory under /backup, set permissions, move all dumps from /backup into the new directory and run amflush again? Will that be okay? Also check permissions and stuff. Checked that. You can refer to my post in reply to Paul's post. I gave some details there. If the s-option of amflush does not work, check your amanda-logdir for files like amflush.log (I assume it would be called like that as I currently have no access to my testbox). This file should contain useful information about what happens and how far the flush gets. Here are the contents of amflush: amflush: datestamp 20040205 driver: pid 7545 executable driver version 2.4.3 driver: send-cmd time 0.098 to taper: START-TAPER 20040205 taper: pid 7546 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400d5000 taper: buffer[01] at 0x400dd000 taper: buffer[02] at 0x400e5000 taper: buffer[03] at 0x400ed000 taper: buffer[04] at 0x400f5000 taper: buffer[05] at 0x400fd000 taper: buffer[06] at 0x40105000 taper: buffer[07] at 0x4010d000 taper: buffer[08] at 0x40115000 taper: buffer[09] at 0x4011d000 taper: buffer[10] at 0x40125000 taper: buffer[11] at 0x4012d000 taper: buffer[12] at 0x40135000 taper: buffer[13] at 0x4013d000 taper: buffer[14] at 0x40145000 taper: buffer[15] at 0x4014d000 taper: buffer[16] at 0x40155000 taper: buffer[17] at 0x4015d000 taper: buffer[18] at 0x40165000 taper: buffer[19] at 0x4016d000 taper: buffer structures at 0x40175000 for 240 bytes taper: read label `Set-1-08' date `20040108' taper: wrote label `Set-1-08' date `20040205' driver: adding holding disk 0 dir /backup size 572408 reserving 572408 out of 572408 for degraded-mode dumps driver: start time 6317.511 inparallel 4 bandwidth 2000 diskspace 572408 dir OBSOLETE datestamp 20040205 driver: drain-ends tapeq LFFO big-dumpers ttt driver: result time 6317.515 from taper: TAPER-OK driver: state time 6317.515 free kps: 2000 space: 572408 taper: idle idle-dumpers: 4 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 6317.515 if : free 600 if ETH0: free 400 if LOCAL: free 1000 driver: hdisk-state time 6317.515 hdisk 0: free 572408 dumpers 0 driver: QUITTING time 6317.533 telling children to quit driver: send-cmd time 6317.533 to taper: QUIT taper: DONE [idle wait: 6316.544 secs] taper: writing end marker. [Set-1-08 OK kb 0 fm 0] driver: FINISHED time 6340.968
Re: Problem with amflush
Rohit wrote: Ok. Can I create one more directory under /backup, set permissions, move all dumps from /backup into the new directory and run amflush again? Will that be okay? No, unless you don't have any chunked files. The header of contination chunk file in holdingdisk contains an abolute pathname (that way amanda could place chunks of one backup over different holdingdisks). Here are the contents of amflush: amflush: datestamp 20040205 driver: pid 7545 executable driver version 2.4.3 driver: send-cmd time 0.098 to taper: START-TAPER 20040205 taper: pid 7546 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400d5000 ... taper: buffer[19] at 0x4016d000 taper: buffer structures at 0x40175000 for 240 bytes Somewhere around these lines, I would expect the instructions like FLUSH host /d/l/e 20040204 /holding/disk/20040204/host._d_l_e.0 These are missing... And of course, nothing happens. taper: read label `Set-1-08' date `20040108' taper: wrote label `Set-1-08' date `20040205' driver: adding holding disk 0 dir /backup size 572408 reserving 572408 out of 572408 for degraded-mode dumps Then it sits idle, still waiting for the above instructions... And almost 2 hours gives up: driver: start time 6317.511 inparallel 4 bandwidth 2000 diskspace 572408 dir ... You'll have to find out why there is no schedule generated. The schedule is generated by "amflush" and piped into "driver". Is there a core dump in /tmp/amanda or in ~/amanda/TheConfig ? Can you find out if they are running? And what it's doing? Try: strace -p pid-of-the-process (for amflush and driver) Which one is taking CPU? I guess amflush. Try to examine a core file to find out what it was doing: $ ulimit -c unlimited $ amflush and in another window, as amanda or root: $ kill -3 pid-of-amflush and then, cd to where the core file is found (current directory, or /tmp/amanda or ~amanda/TheConfig, I'm not sure), and get a stacktrace: $ gdb /usr/sbin/amflush core gdb> bt And send me this output. -- 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: Problem with amflush
> R> Ok. Can I create one more directory under /backup, set permissions, move > R> all dumps from /backup into the new directory and run amflush again? Will > R> that be okay? > > Yes, this should work. I did this, created another directory under /backup called "amanda_hold" and inside it one more directory called "DailySet1". I moved all amanda stuff from /backup to /backup/amanda_hold/DailySet1 directory. I then changed directory permissions [for the new directories which I have created and also windows directory] to amanda.disk. But still amflush does not work. Here is the output of amflush -f $ /usr/sbin/amflush -f DailySet1 Scanning /backup/amanda_hold/DailySet1... 20031230: found Amanda directory. 20040130: found Amanda directory. 20040131: found Amanda directory. 20040201: found Amanda directory. 20040203: found Amanda directory. 20040205: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20031230 B. 20040130 C. 20040131 D. 20040201 E. 20040203 F. 20040205 Select directories to flush [A..F]: [ALL] BCDEF Today is: 20040205 Flushing dumps in 20040130, 20040131, 20040201, 20040203, 20040205 to tape drive "/dev/nst0". Expecting tape Set-1-10 or a new tape. (The last dumps were to tape Set-1-09) Are you sure you want to do this [yN]? y amflush: datestamp 20040205 driver: pid 26065 executable driver version 2.4.3 driver: send-cmd time 0.208 to taper: START-TAPER 20040205 driver: adding holding disk 0 dir /backup/amanda_hold/DailySet1 size 572400 reserving 572400 out of 572400 for degraded-mode dumps taper: pid 26067 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400d5000 taper: buffer[01] at 0x400dd000 taper: buffer[02] at 0x400e5000 taper: buffer[03] at 0x400ed000 taper: buffer[04] at 0x400f5000 taper: buffer[05] at 0x400fd000 taper: buffer[06] at 0x40105000 taper: buffer[07] at 0x4010d000 taper: buffer[08] at 0x40115000 taper: buffer[09] at 0x4011d000 taper: buffer[10] at 0x40125000 taper: buffer[11] at 0x4012d000 taper: buffer[12] at 0x40135000 taper: buffer[13] at 0x4013d000 taper: buffer[14] at 0x40145000 taper: buffer[15] at 0x4014d000 taper: buffer[16] at 0x40155000 taper: buffer[17] at 0x4015d000 taper: buffer[18] at 0x40165000 taper: buffer[19] at 0x4016d000 taper: buffer structures at 0x40175000 for 240 bytes taper: read label `Set-1-09' date `20040205' Since I ran amflush so many times now, I put the same tape which ran with amflush about an hour ago. How do I force amanda to use the tape which I put in the drive? I know nothing was written to the tape, but amanda still thinks that it wrote something to the tape and it asks for the new tape when I run amflush again.
Re: RedHat 7.2 Client timing out?
On Thu, 5 Feb 2004 at 2:20am, Michael Kahle wrote > When I tail the log that amdump creates on the server it gives me the > message: > > START planner date 20040205 > INFO planner Adding new disk fs:md0. > START driver date 20040205 > FAIL planner fs md0 0 [Request to fs timed out.] > FINISH planner date 20040205 > [...etc...] The tool you want to use to debug this is 'amcheck', not amdump. This is a very common error message with new setups. There are several possible fixes here: http://amanda.sourceforge.net/fom-serve/cache/16.html > Is there anyone out there that could help me shed some light on this? > Should I scratch the RPM's and simply recompile my own amanda version from > source? Are there known problems with this version? Well, 7.2 is pretty darn old. But you should be able to get this to work. Go through the FAQ-O-Matic stuff above, look in /tmp/amanda on the client, and see if you can get amcheck happy. If none of that works, come on back with the exact error messages and any relevant log files. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Problem with amflush
Hi, Rohit, on Donnerstag, 05. Februar 2004 at 08:09 you wrote to amanda-users: >> As Paul assumed in another branch of this thread, you might have more >> than one AMANDA-installation on your machine. >> >> Have you tried several installations and maybe failed to remove one? R> No. It was installed via RPM and it one and only amanda installation I R> have on that machine. Ok. >> What does a simple "find / -name amflush -type f" give you? R> # find / -name amflush -type f R> find: /proc/4059/fd: No such file or directory R> find: /proc/10993/fd: No such file or directory R> /usr/sbin/amflush R> /var/lib/amanda/DailySet1/amflush Seems fine to me. R> Ok. Can I create one more directory under /backup, set permissions, move R> all dumps from /backup into the new directory and run amflush again? Will R> that be okay? Yes, this should work. >> Also check permissions and stuff. R> Checked that. You can refer to my post in reply to Paul's post. I gave some R> details there. Try and chown that windows directory to amanda or at least "chgrp disk" it. Right now amanda can't do anything in there, and we should eliminate the possibility of that being the problem. How is your holdingdisk defined? /backup? Then amanda could fall over the cruft in form of /backup/windows being non-readable. Mv the contents to maybe /backup/amanda_hold/ and set your holdingdisk to that. SO you my add another -subdir later for another amanda-conf and the files won't get confused. >> If the s-option of amflush does not work, check your amanda-logdir for >> files like amflush.log (I assume it would be called like that as I >> currently have no access to my testbox). This file should contain >> useful information about what happens and how far the flush gets. R> Here are the contents of amflush: R> amflush: datestamp 20040205 R> driver: pid 7545 executable driver version 2.4.3 R> driver: send-cmd time 0.098 to taper: START-TAPER 20040205 ... R> taper: DONE [idle wait: 6316.544 secs] Hm, this all looks pretty fine. I can only compare it to my tes-install right now which uses chg-disk and has nothing to flush right now. Please try to chown/chgrp that windows-dir or mv it out of the way. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
RedHat 7.2 Client timing out?
Good evening... er... morning. I have just finished configuring Amanda for the first time ever. It seems to be working just fine locally, but backing up a remote client is giving me some problems. My amanda-server is a IBM Netfinity 5500 w/ a ServeRAID controller. I am running a semi-stock 2.4.18 kernel with only the ServeRAID drivers compiled in. I have installed amanda using apt-get and configured it for my Quantum SuperLoader DLT 1280L. After an evening of monkeying around, I feel quite satisfied with what I have accomplished thus far. The DLT is working fine. Using amdump I am able to backup my home directory on this backup server. The autoloader is moving tapes around using the "chg-zd-mtx" bridge script. (Any advantage/disadvantage to using this -vs.- the "chg-scsi-chio"?) The bar code scanner is reporting back info on my tapes, etc. The package maintainer for the Debian package (Amanda-2.4.2p2) uses "backup" as the amanda user. On the client machine I am trying to backup (RedHat 7.2), the rpm (amanda-2.4.2p2-4) uses the user "amanda" as the amanda user. Could this be the source of my woes? When I tail the log that amdump creates on the server it gives me the message: START planner date 20040205 INFO planner Adding new disk fs:md0. START driver date 20040205 FAIL planner fs md0 0 [Request to fs timed out.] FINISH planner date 20040205 [...etc...] I am able to resolve the host "fs" from my backup server. I am 99% sure this is something wrong with the RH server. I have been a Debian user for about 5 years now and hate having to ever touch a RH server. I just don't know where anything is... I don't understand the organization. Is there anyone out there that could help me shed some light on this? Should I scratch the RPM's and simply recompile my own amanda version from source? Are there known problems with this version? Pardon me if I forgot to include any relevant data. It is wy past my bed time and I'm afraid I don't have my full wits about me. Thank you for your time. Michael P.S. - As a side note. The largest problem I had when installing was getting the "chg-zd-mtx" configuration to work. Only after inspecting the source for this script was I easily able to configure using the author's instructions. Perhaps you should include a sample configuration with your docs... or do you? and I was just too tired to see? Until tomorrow...
Re: Problem with amflush
> As Paul assumed in another branch of this thread, you might have more > than one AMANDA-installation on your machine. > > Have you tried several installations and maybe failed to remove one? No. It was installed via RPM and it one and only amanda installation I have on that machine. > What does a simple "find / -name amflush -type f" give you? # find / -name amflush -type f find: /proc/4059/fd: No such file or directory find: /proc/10993/fd: No such file or directory /usr/sbin/amflush /var/lib/amanda/DailySet1/amflush > If you find more than one amflush, it is very likely that you call > "the wrong one". Maybe it was compiled with different directories and > such. Looks like not. > Check if the directories contain something useful or if the contain > something that does not belong there. What is the "windows"-dir there? There is one more non-amanda directory called "windows". I use this directory to backup windows servers [non amanda backup process - manual] > In a properly configured holdingdisk there should not exist anything > else than files created by amdump. > > "There shall not be anything beside me!", if you like it that way ;) Ok. Can I create one more directory under /backup, set permissions, move all dumps from /backup into the new directory and run amflush again? Will that be okay? > Also check permissions and stuff. Checked that. You can refer to my post in reply to Paul's post. I gave some details there. > If the s-option of amflush does not work, check your amanda-logdir for > files like amflush.log (I assume it would be called like that as I > currently have no access to my testbox). This file should contain > useful information about what happens and how far the flush gets. Here are the contents of amflush: amflush: datestamp 20040205 driver: pid 7545 executable driver version 2.4.3 driver: send-cmd time 0.098 to taper: START-TAPER 20040205 taper: pid 7546 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400d5000 taper: buffer[01] at 0x400dd000 taper: buffer[02] at 0x400e5000 taper: buffer[03] at 0x400ed000 taper: buffer[04] at 0x400f5000 taper: buffer[05] at 0x400fd000 taper: buffer[06] at 0x40105000 taper: buffer[07] at 0x4010d000 taper: buffer[08] at 0x40115000 taper: buffer[09] at 0x4011d000 taper: buffer[10] at 0x40125000 taper: buffer[11] at 0x4012d000 taper: buffer[12] at 0x40135000 taper: buffer[13] at 0x4013d000 taper: buffer[14] at 0x40145000 taper: buffer[15] at 0x4014d000 taper: buffer[16] at 0x40155000 taper: buffer[17] at 0x4015d000 taper: buffer[18] at 0x40165000 taper: buffer[19] at 0x4016d000 taper: buffer structures at 0x40175000 for 240 bytes taper: read label `Set-1-08' date `20040108' taper: wrote label `Set-1-08' date `20040205' driver: adding holding disk 0 dir /backup size 572408 reserving 572408 out of 572408 for degraded-mode dumps driver: start time 6317.511 inparallel 4 bandwidth 2000 diskspace 572408 dir OBSOLETE datestamp 20040205 driver: drain-ends tapeq LFFO big-dumpers ttt driver: result time 6317.515 from taper: TAPER-OK driver: state time 6317.515 free kps: 2000 space: 572408 taper: idle idle-dumpers: 4 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 6317.515 if : free 600 if ETH0: free 400 if LOCAL: free 1000 driver: hdisk-state time 6317.515 hdisk 0: free 572408 dumpers 0 driver: QUITTING time 6317.533 telling children to quit driver: send-cmd time 6317.533 to taper: QUIT taper: DONE [idle wait: 6316.544 secs] taper: writing end marker. [Set-1-08 OK kb 0 fm 0] driver: FINISHED time 6340.968
