Re: amandahostsauth
Hi, permisions of .amandahosts? they have to be 0600 or amanda will reject it. Christoph janebackup wrote: Hi, I've recently installed and configured amanda 2.4.3b3 on my linux machine and I am trying to backup this one machine at the minute. When I run amcheck -c DailySet1 I get the following error message: ERROR: dataserv [access as root not allowed from root@dataserv] amandahostsauth failed I have a .amandahosts file with the following entry: dataservroot Has anyone else experienced this problem before? I would be grateful for any help! Thanks in advance! Jane.
Re: Sending mail from LAN.
Hello Stephen, I've done some work on our DNS server, but I am unfimiliar with a valid MX record. How do I go about this, or if you prefer, do you know of a nice doc on the subject. Thanks, Trevor. - Original Message - From: Stephen Carville [EMAIL PROTECTED] To: Trevor Fraser [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, July 30, 2002 7:27 PM Subject: Re: Sending mail from LAN. Set up your DNS server to return a valid MX record for systematic.lan. On Tue, 30 Jul 2002, Trevor Fraser wrote: - Hello all. - - I've managed to sort out sending mail message to [EMAIL PROTECTED] , - many thanks to all who replied. This mailling list is worth more than - gold...every tried getting support from the present leading software - developersfat chance you little drop in the ocean!!! Just give a - though for what we've got going here guys and girls. - - Sorry for the side track, I just rerealised how blessed Linux users are. - - The problem now is that our LAN domain doesn't exist on the internet, and - our mail-server only accepts mail from existing domains. How do I send mail - from an existing domain, or at least appear to be? - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Problem with GNUTAR or index files generated not correctly
Hello all. My index files generate not correctly. If I use DUMP progam in amanda.conf - all it's OK, if I use GNUTAR program in amanda.conf the special character (not english characters) in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) Is this bug in GNUTAR? How can I solve this problem? I need backup NT shares (not english characters) thats why I have to use GNUTAR - am I right? Is there any dump programs which i can use instead GNUTAR? Thank U. p.s. Sorry for my bad english. If I use DUMP progam the special characters on localhost in index files display correctly If I use GNUTAR progam the special characters on localhost in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) I am sure the problem in GNUTAR progam. p.s.s tar --version tar (GNU tar) 1.13.25
Re: Problem with GNUTAR or index files generated not correctly
On Wed, Jul 31, 2002 at 11:47:05AM +0400, Lishtovny Denis wrote: Hello all. My index files generate not correctly. If I use DUMP progam in amanda.conf - all it's OK, if I use GNUTAR program in amanda.conf the special character (not english characters) in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) Is this bug in GNUTAR? How can I solve this problem? I need backup NT shares (not english characters) thats why I have to use GNUTAR - am I right? Is there any dump programs which i can use instead GNUTAR? Thank U. p.s. Sorry for my bad english. If I use DUMP progam the special characters on localhost in index files display correctly If I use GNUTAR progam the special characters on localhost in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) Is that just /PRIWET TEST.doc with the eighth bit of each character turned on? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: DLT4500 on Linux RH 7.3
hi, i use this combination: Quantum DLT4700 D57A at scbus3 target 0 lun 0 (pass1,sa0) Quantum TZ Media Changer D57Aat scbus3 target 0 lun 1 (pass2) in my amanda.conf i use this configuration: tpchanger chg-zd-mtx # the tape-changer glue script changerfile /usr/local/etc/amanda/kdDaily/changer the changer script i use is the chg-zd-mtx and it is located under /usr/local/libexec/ . hmm, the os is a freebsd and the path may be different on other systems. the changerfile ist changer.conf in the directory where the amanda.conf is located. i hope this helps greets Patrick Schumacher | technical department phone +49 (0)4192-8794 -440 | fax -290 | easynet DV GmbH | Achtern Dieck 9 | 24576 Bad Bramstedt # easynet is part of the easynet group plc | www.easynetgroup.net -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Keith Clay Gesendet: Freitag, 26. Juli 2002 21:19 An: [EMAIL PROTECTED] Betreff: DLT4500 on Linux RH 7.3 Folks, I am having problems figuring out how to get the autochanger working. I can manipulate it with mtx but can't find the right changer config to get it working. I looked for chg-mtx in the conf dir but nothing is there. keith -- - Keith Clay, [EMAIL PROTECTED] Lead Programmer, Web Integration and Programming 286 Adams Center for Teaching Excellence Abilene Christian University Abilene, TX 79699 (915) 674-2187 (915) 674-2834 -
some strange error
Hi, I hope someone can help me with this problem. I am running weekly amanda backups on my IRIX 6.5 server, and I had no problems so far. Yesterday I made an extra backup using xfsrestore and not amanda at all. Once the xfsrestore was finished, I inserted back the weekly tape, and ran amcheck... Now I have this error message I don't understand: Amanda Tape Server Host Check - /usr/local/amanda/hold: 1582060 KB disk space available, using 1274860 KB. ERROR: /dev/rmt/tps1d3nr: reading label: Invalid argument. (expecting tape info.mi:Woche_1 or a new tape) NOTE: skipping tape-writable test. I am completely sure the tape I have inserted is labeled info.mi:Woche_1. I didn't change anything in amanda's configuration. Can anyone give me a hint? Thanx! carlos f. useche
Re: Problem with GNUTAR or index files generated not correctly
Hello all. My index files generate not correctly. If I use DUMP progam in amanda.conf - all it's OK, if I use GNUTAR program in amanda.conf the special character (not english characters) in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) Is this bug in GNUTAR? How can I solve this problem? I need backup NT shares (not english characters) thats why I have to use GNUTAR - am I right? Is there any dump programs which i can use instead GNUTAR? Thank U. p.s. Sorry for my bad english. If I use DUMP progam the special characters on localhost in index files display correctly If I use GNUTAR progam the special characters on localhost in index files display as octal (for example: /\320\322\311\327\305\324 \324\305\323\324.doc) Is that just /PRIWET TEST.doc with the eighth bit of each character turned on? Yes! U R Right ! but (/PRIWET TEST.doc) in russian characters. I'm sure problem in GNUTAR - what could U advice me to do. p.s By the way, do U know Russian?
sendmail
Hi, I'm using amanda 2.4.3b3 on my Linux server, I don't have the email option setup on this machine could you tell if it is ok to to use amanda without email setup as I know she uses it to send reports etc. Jane
Re: some strange error
On Wednesday 31 July 2002 06:17, carlos felipe useche wrote: Hi, I hope someone can help me with this problem. I am running weekly amanda backups on my IRIX 6.5 server, and I had no problems so far. Yesterday I made an extra backup using xfsrestore and not amanda at all. Once the xfsrestore was finished, I inserted back the weekly tape, and ran amcheck... Now I have this error message I don't understand: Amanda Tape Server Host Check - /usr/local/amanda/hold: 1582060 KB disk space available, using 1274860 KB. ERROR: /dev/rmt/tps1d3nr: reading label: Invalid argument. (expecting tape info.mi:Woche_1 or a new tape) NOTE: skipping tape-writable test. I am completely sure the tape I have inserted is labeled info.mi:Woche_1. I didn't change anything in amanda's configuration. Can anyone give me a hint? Thanx! carlos f. useche AFAIK, any tape can be identifed by the following sequence assuming that your tape 'device' is /dev/rmt/tps1d3nr. #mt -f /dev/rmt/tps1d3nr rewind #dd if=/dev/rmt/tps1d3nr count=1 The first makes sure the tape is rewound, and the second should output on the screen the first block of the tape containing the label. You didn't state what drive, but there might be a slim chance the xfsrestore put the drive into some other mode that it might take a powerdown reset to restore a mode amanda is familiar with. Also, OnStream drives seem to generate more than their fair share of poor-mouthing. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.09% setiathome rank, not too shabby for a WV hillbilly
installing Amanda
Hello, Actually I'm installing Amanda on HP-UX version 11 and I need some help. Is the version 2.4.2 compatible with hp-UX version 11? otherwise what's new version can I install. I read the install document and I saw plenty of things, could you please tell where can I get a simply document on how to buid Amanda on this operating system. I need all the step how to make this install properly on the server and client station. Thanks for your involvements Jean-Claude _ Affichez, modifiez et partagez gratuitement vos photos en ligne: http://photos.msn.com/support/worldwide.aspx
Re: installing Amanda
En réponse à Jean-Claude Ramsamy [EMAIL PROTECTED]: Hello, Actually I'm installing Amanda on HP-UX version 11 and I need some help. Is the version 2.4.2 compatible with hp-UX version 11? otherwise what's new version can I install. I read the install document and I saw plenty of things, could you please tell where can I get a simply document on how to buid Amanda on this operating system. I need all the step how to make this install properly on the server and client station. http://www.backupcentral.com/amanda.html is a good starting point for configuring amanda. Hery Zo Thanks for your involvements Jean-Claude _ Affichez, modifiez et partagez gratuitement vos photos en ligne: http://photos.msn.com/support/worldwide.aspx Hery Zo RAKOTONDRAMANANA Simicro Internet Tél: (261) 20 22 648 83 Fax: (261) 20 22 661 83 --
Re: Tapeless error with 2.4.3 (expecting a new tape)
But I am not using a tape. This is all backed up to the hard drive. Is the labelstr required in this case? - Original Message - From: John Koenig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 30, 2002 10:13 AM Subject: Re: Tapeless error with 2.4.3 (expecting a new tape) Hi John, Thanks for the response. I have also set it up the way that you are talking about but I still have the same problem. Could it be the directory names that you are using? What is your labelstr entry in your amanda.conf file set to? You may need to label your tape, next. This would not be related to labelstr, unless of course you are indeed doing the label step and the literal you are using does not match the pattern in the labelstr. --
amanda report
A few questions about my report. I have a cron set to force level 0 dumps
a minute or two before the actual backup goes into place so that I can get a
full level 0 on each tape.
I understand can't switch to incremental dump because it was forced to be
dump 0, right?
But why would the entire backup fail for this one machine? It is on and
available!
Thanks in advance,
-Michael Blinn
FAILURE AND STRANGE DUMP SUMMARY:
mail /configs lev 0 FAILED [can't switch to incremental dump]
mail /var/lib/mysql lev 0 FAILED [can't switch to incremental
dump]
mail /usr/local/apache lev 0 FAILED [can't switch to incremental
dump]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:12
Dump Time (hrs:min)0:12 0:00 0:12
Output Size (meg) 158.60.0 158.6
Original Size (meg) 607.40.0 607.4
Avg Compressed Size (%)26.1--26.1 (level:#disks ...)
Filesystems Dumped2 0 2 (1:2)
Avg Dump Rate (k/s) 221.6-- 221.6
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk mail:/usr/local/apache.
planner: Adding new disk mail:/var/lib/mysql.
planner: Adding new disk mail:/configs.
planner: Last full dump of localhost://ntserver/ppidocs on tape daily5
overwritten in 2 runs.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
localhost-sinesswork 1 19320 3968 20.5 0:54 73.7 N/A N/A
localhost-er/ppidocs 1 602623 158400 26.3 11:19 233.3 N/A N/A
mail /configs0 FAILED ---
mail -cal/apache 0 FAILED ---
mail -/lib/mysql 0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
Re: amanda report
On Wed, 31 Jul 2002 at 9:47am, Michael P. Blinn wrote A few questions about my report. I have a cron set to force level 0 dumps a minute or two before the actual backup goes into place so that I can get a full level 0 on each tape. Why do it that way? Just use 'dumpcycle 0' and it should do the same thing. I understand can't switch to incremental dump because it was forced to be dump 0, right? Sort of. You don't seem to be using a tape, so amanda was probably in degraded mode. What is your reserve set to in amanda.conf? If it's the default, there's no room saved in degraded mode for level 0s, and you're not letting it switch to incrementals, thus the FAILs. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amanda report
Hmm... Looks like you didn't have a (usable) tape in the drive.
Were the level 0 dumps of these new disks bigger than would fit on
your holding disk(s)?
-Mitch
On Wed, 31 Jul 2002, Michael P. Blinn wrote:
A few questions about my report. I have a cron set to force level 0 dumps
a minute or two before the actual backup goes into place so that I can get a
full level 0 on each tape.
I understand can't switch to incremental dump because it was forced to be
dump 0, right?
But why would the entire backup fail for this one machine? It is on and
available!
Thanks in advance,
-Michael Blinn
FAILURE AND STRANGE DUMP SUMMARY:
mail /configs lev 0 FAILED [can't switch to incremental dump]
mail /var/lib/mysql lev 0 FAILED [can't switch to incremental
dump]
mail /usr/local/apache lev 0 FAILED [can't switch to incremental
dump]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:12
Dump Time (hrs:min)0:12 0:00 0:12
Output Size (meg) 158.60.0 158.6
Original Size (meg) 607.40.0 607.4
Avg Compressed Size (%)26.1--26.1 (level:#disks ...)
Filesystems Dumped2 0 2 (1:2)
Avg Dump Rate (k/s) 221.6-- 221.6
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk mail:/usr/local/apache.
planner: Adding new disk mail:/var/lib/mysql.
planner: Adding new disk mail:/configs.
planner: Last full dump of localhost://ntserver/ppidocs on tape daily5
overwritten in 2 runs.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
localhost-sinesswork 1 19320 3968 20.5 0:54 73.7 N/A N/A
localhost-er/ppidocs 1 602623 158400 26.3 11:19 233.3 N/A N/A
mail /configs0 FAILED ---
mail -cal/apache 0 FAILED ---
mail -/lib/mysql 0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
Re: Sending mail from LAN.
The best doc IMO is DNS and Bind from O'Reilly. If you are goiung to be administering DNS suggest you buy it. I assume you have a server that does DNS for the zone called systematic.lan. If you are using Bind, add to the zone file after the ORIGIN statment (or the @ symbol) a record like: IN MX 10 mail then, if necessary, add an A record for the mail server. mail IN Aip.address.of.machine It will end up something like: $TTL3600 @ IN SOA dns.systematic.lan. domainadmin.systematic.co.za. ( 17 ; serial 3H ; refresh 15M ; retry 1W ; expire 3600 ) ; default IN NS dns IN MX 10 mail mailIN A192.168.12.69 etc... IF you are using Windoes, select New Mail Exchanger and fill in the values. Make sure there is an A record for the mail server. Do NOT point an MX name to a CNAME record (Alias on Windoes). You have been warned! On Wed, 31 Jul 2002, Trevor Fraser wrote: - Hello Stephen, - - I've done some work on our DNS server, but I am unfimiliar with a valid MX - record. How do I go about this, or if you prefer, do you know of a nice - doc on the subject. - - Thanks, Trevor. - - - Original Message - - From: Stephen Carville [EMAIL PROTECTED] - To: Trevor Fraser [EMAIL PROTECTED] - Cc: [EMAIL PROTECTED] - Sent: Tuesday, July 30, 2002 7:27 PM - Subject: Re: Sending mail from LAN. - - - Set up your DNS server to return a valid MX record for systematic.lan. - - On Tue, 30 Jul 2002, Trevor Fraser wrote: - - - Hello all. - - - - I've managed to sort out sending mail message to [EMAIL PROTECTED] - , - - many thanks to all who replied. This mailling list is worth more than - - gold...every tried getting support from the present leading software - - developersfat chance you little drop in the ocean!!! Just give a - - though for what we've got going here guys and girls. - - - - Sorry for the side track, I just rerealised how blessed Linux users are. - - - - The problem now is that our LAN domain doesn't exist on the internet, - and - - our mail-server only accepts mail from existing domains. How do I send - mail - - from an existing domain, or at least appear to be? - - - - -- - -- Stephen Carville - UNIX and Network Administrator - DPSI (formerly Ace USA Flood Services) - 310-342-3602 - [EMAIL PROTECTED] - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Incremental Vs. Full
Hi, Anyone have strong opinions on using amanda to do incremental backups versus doing full backups? Currently I have amanda doing full backups every night. The backups fit on the tape with ~90% tape to spare (small installation, big tapes). The full level 0 backups are working fine, but I wonder if there's any advantage to incremental backups, other than decreased backup and processor time. Any thoughts? -- Lalo Castro Programmer/Analyst McHenry Library (831) 459-5208
Re: Back up issues
On Wednesday 31 July 2002 11:44, support wrote:
Hi,
We've been using Amanda for sometime to handle our tape back
ups, but have recently encountered an issue. One of our servers
has a rather large home directory that will not fit onto a
standard 12gig tape, so for the most part, we have been
attempting to split the dump into two parts for this drive. The
format for the two part dumps in the amanda.conf when working
were slightly different than below, but it was not backing up
files properly, so have attempted the following. What we are
trying to do is to back up the first part of the dump excluding
any file or directory starting with letters a-l, and then on the
second dump, backing up files excluding m-z.
I believe I must have the exclude format incorrect, I was assuming
that /home/[a-l]* would do the trick, but is causing Amanda to
produce errors saying that the dumps failed, and that these two
disks are offline.
define dumptype part1dump {
comment Delta part 1
global
priority high
exclude /home/[a-l]*
}
define dumptype part2dump {
comment Delta part 2
global
priority high
exclude /home/[m-z]*
I'm trying to find out the proper way of splitting a dump into
two, and have it work right.
Anyone have any ideas? I was also trying to get amanda.conf to
write to 10 tapes instead of 8, and that failed miserably as
well. Changing the tape # from 8 to 10, Amanda would no longer
recognize any labelled tapes, and would keep asking for a new
tape. So I'm back to 8 tapes again.
Thanks,
Tim
[EMAIL PROTECTED]
First, you didn't specify the actual reader/writer program, beit
dump or tar. Dump does not support exclusions so I assume you are
using tar.
The format I use, rather than a whole list of excludes (I do use one
list, to exclude the holding disks) is to just name everything in
the disklist, breaking it down to pieces that will fit on a 4gig
dds2 tape. I realize this will make for small archives, all
stacked up on one tape in your case, but its one possibility.
The exclude files contents are a bit fussy, and according to the
docs, only work in this format:
---
./usr/dumps/*
./var/pacct
---
note the preceeding ./ in each line, which anchors it to the current
directory. In my case these happen to be off the root branch, but
this syntax I'm told is just as effective if I had a
/home/joetheblowfish/usr/dumps/*
in which case the trailing usr/dumps/* portion of that path would
be excluded.
Now, the tape problem. One must 'amlabel' the added tapes else they
probably won't be useable. This operation can also cause an out of
order useage by amanda, fixable by hand editing the tapelist after
the labeling operation to put the newly added tapes into their
proper place in the list, which, since amanda uses a circular
buffer, may or may not mean they would be at the top or bottom of
the list, but may be in some odd order resembling this tapelist:
20020730 DailySet1-15 reuse
20020729 DailySet1-14 reuse
20020728 DailySet1-13 reuse
20020726 DailySet1-12 reuse
20020725 DailySet1-11 reuse
20020724 DailySet1-10 reuse
20020723 DailySet1-09 reuse
20020722 DailySet1-08 reuse
20020720 DailySet1-07 reuse
20020719 DailySet1-06 reuse
20020718 DailySet1-05 reuse
20020717 DailySet1-04 reuse
20020716 DailySet1-03 reuse
20020715 DailySet1-02 reuse
20020713 DailySet1-01 reuse
20020712 DailySet1-19 reuse
20020711 DailySet1-20 reuse
20020710 DailySet1-18 reuse
20020709 DailySet1-17 reuse
20020708 DailySet1-16 reuse
As you can see, I have one tape out of order but its a very minor
detail. The last tape used, (or IIRC labeled) is at the top of the
list, and the next tape amanda wants is at the bottom of the list.
As long as you are aware that adding tapes will insert the new ones,
IIRC to the top of the list, not in a sorted order. Amanda doesn't
care about the order, just that the labels are used in *her* order
if you do not hand edit the list to restore order. I've never
bothered.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.09% setiathome rank, not too shabby for a WV hillbilly
Re: Back up issues
Using gnutar. We use a list to exclude the holding disk as well, and it
seems to work effectively, and is of a very similar exclude format: exclude
/data/[RH]*
However, bringing that sort of format of an exclude for the /home directory
fails. I believe what you are indicating is that if the disk that I am
splitting in two is the home directory, I should use this format:
exclude ./[a-l]*
As ./ on this disk will be the /home dir.
As for amlabel, yes, all 10 new tapes have been labeled according to what we
were previously using, just that there are two new tapes to the list. The
Amanda tapelist had managed to recognize/add the 9th tape, as it does show
in the tapelist. You are saying that I should modify the tapelist to add
tape #10? Here is our tapelist currently:
20020731 Daily05 reuse
20020730 Daily06 reuse
20020727 Daily04 reuse
20020726 Daily03 reuse
20020725 Daily02 reuse
20020724 Daily01 reuse
20020723 Daily08 reuse
20020722 Daily09 reuse
20020719 Daily07 reuse
So I presume I should be adding Daily10 above the Daily09 line, and I guess
bump the dates by one day as Daily10 would be 20020723 right? (seems to make
sense to me)
Thanks for your input Gene.
Tim
- Original Message -
From: Gene Heskett [EMAIL PROTECTED]
To: support [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, July 31, 2002 1:56 PM
Subject: Re: Back up issues
On Wednesday 31 July 2002 11:44, support wrote:
Hi,
We've been using Amanda for sometime to handle our tape back
ups, but have recently encountered an issue. One of our servers
has a rather large home directory that will not fit onto a
standard 12gig tape, so for the most part, we have been
attempting to split the dump into two parts for this drive. The
format for the two part dumps in the amanda.conf when working
were slightly different than below, but it was not backing up
files properly, so have attempted the following. What we are
trying to do is to back up the first part of the dump excluding
any file or directory starting with letters a-l, and then on the
second dump, backing up files excluding m-z.
I believe I must have the exclude format incorrect, I was assuming
that /home/[a-l]* would do the trick, but is causing Amanda to
produce errors saying that the dumps failed, and that these two
disks are offline.
define dumptype part1dump {
comment Delta part 1
global
priority high
exclude /home/[a-l]*
}
define dumptype part2dump {
comment Delta part 2
global
priority high
exclude /home/[m-z]*
I'm trying to find out the proper way of splitting a dump into
two, and have it work right.
Anyone have any ideas? I was also trying to get amanda.conf to
write to 10 tapes instead of 8, and that failed miserably as
well. Changing the tape # from 8 to 10, Amanda would no longer
recognize any labelled tapes, and would keep asking for a new
tape. So I'm back to 8 tapes again.
Thanks,
Tim
[EMAIL PROTECTED]
First, you didn't specify the actual reader/writer program, beit
dump or tar. Dump does not support exclusions so I assume you are
using tar.
The format I use, rather than a whole list of excludes (I do use one
list, to exclude the holding disks) is to just name everything in
the disklist, breaking it down to pieces that will fit on a 4gig
dds2 tape. I realize this will make for small archives, all
stacked up on one tape in your case, but its one possibility.
The exclude files contents are a bit fussy, and according to the
docs, only work in this format:
---
./usr/dumps/*
./var/pacct
---
note the preceeding ./ in each line, which anchors it to the current
directory. In my case these happen to be off the root branch, but
this syntax I'm told is just as effective if I had a
/home/joetheblowfish/usr/dumps/*
in which case the trailing usr/dumps/* portion of that path would
be excluded.
Now, the tape problem. One must 'amlabel' the added tapes else they
probably won't be useable. This operation can also cause an out of
order useage by amanda, fixable by hand editing the tapelist after
the labeling operation to put the newly added tapes into their
proper place in the list, which, since amanda uses a circular
buffer, may or may not mean they would be at the top or bottom of
the list, but may be in some odd order resembling this tapelist:
20020730 DailySet1-15 reuse
20020729 DailySet1-14 reuse
20020728 DailySet1-13 reuse
20020726 DailySet1-12 reuse
20020725 DailySet1-11 reuse
20020724 DailySet1-10 reuse
20020723 DailySet1-09 reuse
20020722 DailySet1-08 reuse
20020720 DailySet1-07 reuse
20020719 DailySet1-06 reuse
20020718 DailySet1-05 reuse
20020717 DailySet1-04 reuse
20020716 DailySet1-03 reuse
20020715 DailySet1-02 reuse
20020713 DailySet1-01 reuse
20020712 DailySet1-19 reuse
20020711 DailySet1-20 reuse
20020710 DailySet1-18 reuse
20020709 DailySet1-17 reuse
20020708 DailySet1-16 reuse
As you can see, I have one tape out of order but its a very minor
detail. The last
added gnutar after install
help... I added gtar after install and now I get an error [GNUTAR Program not available] can I setup gnutar after client install or do I have to reinstall? __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
Re: added gnutar after install
You'll have to recompile with the --with-gnutar=path to tar option Marvin Davenport wrote: help... I added gtar after install and now I get an error [GNUTAR Program not available] can I setup gnutar after client install or do I have to reinstall? __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504 (303) 682-7110 Phone (303) 682-7140 Fax
RE: added gnutar after install
You need to recompile...and for added umph, I'd use the --with-gnutar=/path/to/tar option with my .config file just in case my path is screwy or I have multiple versions of tar hanging around on that box. Make sure to make clean, make distclean and check that config.cache is empty. Then .config again... -Original Message- From: Marvin Davenport [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 2:45 PM To: [EMAIL PROTECTED] Subject: added gnutar after install help... I added gtar after install and now I get an error [GNUTAR Program not available] can I setup gnutar after client install or do I have to reinstall? __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
Windows XP
Dear Amanda Users,
I am trying to backup a Windows XP client (//hans/C$) with Amanda 2.4.2.
It seems to work except for a number of files which are listed as errors
below.
Is there any way to get the files in error backed up with amanda?
Thanks,
Dick Kreutzer
These dumps were to tape Daily2.
The next tape Amanda expects to use is: Daily3.
FAILURE AND STRANGE DUMP SUMMARY:
gorn.ameri //hans/C$ lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:05
Run Time (hrs:min) 4:07
Dump Time (hrs:min)3:52 3:17 0:35
Output Size (meg) 29733.625011.3 4722.3
Original Size (meg) 29733.625011.3 4722.3
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 24 10 14 (1:14)
Avg Dump Rate (k/s) 2191.9 2168.5 2324.6
Tape Time (hrs:min)3:40 3:13 0:27
Tape Size (meg) 29734.425011.6 4722.8
Tape Used (%) 80.5 67.6 12.8 (level:#disks ...)
Filesystems Taped24 10 14 (1:14)
Avg Tp Write Rate (k/s) 2306.8 2213.4 2970.1
FAILED AND STRANGE DUMP DETAILS:
/-- gorn.ameri //hans/C$ lev 1 STRANGE
sendbackup: start [gorn.americom.com://hans/C$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
| Added interface ip=192.168.2.1 bcast=192.168.2.255 nmask=255.255.255.0
? ERRDOS - ERRnoaccess opening remote file \Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson\user.dmp (\Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\All
Users\Application Data\Microsoft\Network\Downloader\qmgr0.dat (\Documents and
Settings\All Users\Application Data\Microsoft\Network\Downloader\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\All
Users\Application Data\Microsoft\Network\Downloader\qmgr1.dat (\Documents and
Settings\All Users\Application Data\Microsoft\Network\Downloader\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\Jeff Moss\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat (\Documents and Settings\Jeff
Moss\Local Settings\Application Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\Jeff Moss\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG (\Documents and
Settings\Jeff Moss\Local Settings\Application Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\Jeff
Moss\NTUSER.DAT (\Documents and Settings\Jeff Moss\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\Jeff
Moss\ntuser.dat.LOG (\Documents and Settings\Jeff Moss\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\LocalService\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat (\Documents and
Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and Settings\LocalService\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG (\Documents and
Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\LocalService\NTUSER.DAT (\Documents and Settings\LocalService\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\LocalService\ntuser.dat.LOG (\Documents and Settings\LocalService\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat
(\Documents and Settings\NetworkService\Local Settings\Application
Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\NetworkService\Local Settings\Application
Data\Microsoft\Windows\UsrClass.dat.LOG (\Documents and Settings\NetworkService\Local
Settings\Application Data\Microsoft\Windows\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\NetworkService\NTUSER.DAT (\Documents and Settings\NetworkService\)
? ERRDOS - ERRbadshare opening remote file \Documents and
Settings\NetworkService\ntuser.dat.LOG (\Documents and Settings\NetworkService\)
? ERRDOS - ERRbadshare opening remote file \hiberfil.sys (\)
? ERRDOS - ERRbadshare opening remote file \pagefile.sys (\)
? ERRDOS - ERRnoaccess opening remote file \WINDOWS\$NtUninstallQ309521$\dxmasf.dll
(\WINDOWS\$NtUninstallQ309521$\)
? ERRDOS - ERRnoaccess opening remote file \WINDOWS\$NtUninstallQ309521$\httpod51.dll
(\WINDOWS\$NtUninstallQ309521$\)
? ERRDOS - ERRnoaccess opening remote file \WINDOWS\$NtUninstallQ309521$\lsasrv.dll
(\WINDOWS\$NtUninstallQ309521$\)
? ERRDOS - ERRnoaccess opening remote file
Re: installing Amanda
On Wed, Jul 31, 2002 at 11:45:16AM +, Jean-Claude Ramsamy wrote: Hello, Actually I'm installing Amanda on HP-UX version 11 and I need some help. Is the version 2.4.2 compatible with hp-UX version 11? otherwise what's new version can I install. Should be compatible, many are using it on HP-UX, 11 and otherwise. Newer versions should also be compatible. I read the install document and I saw plenty of things, could you please tell where can I get a simply document on how to buid Amanda on this operating system. I need all the step how to make this install properly on the server and client station. Sorry to be a bit snarky here Jean-Claude, but the install document you said you read is THE Simple Step-By-Step How-To Document. You saw plenty of things because there are plenty of steps. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Windows XP
On Wed, Jul 31, 2002 at 08:48:44PM -, [EMAIL PROTECTED] wrote: Dear Amanda Users, I am trying to backup a Windows XP client (//hans/C$) with Amanda 2.4.2. It seems to work except for a number of files which are listed as errors below. Is there any way to get the files in error backed up with amanda? When I was engaged in my mighty struggle to conquor samba and windows 2k, I found just about all the errors were due to the amanda user not having permission. The exceptions were the system things like pagefile.sys and I think the $NtUninstall kinda thingies. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Windows XP
In this case, amanda is logging into Windows (via smbclient) as Administrator. Shouldn't that override any permission issues? I am trying to backup a Windows XP client (//hans/C$) with Amanda 2.4.2. It seems to work except for a number of files which are listed as errors below. Is there any way to get the files in error backed up with amanda? When I was engaged in my mighty struggle to conquor samba and windows 2k, I found just about all the errors were due to the amanda user not having permission. The exceptions were the system things like pagefile.sys and I think the $NtUninstall kinda thingies. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Back up issues
On Wednesday 31 July 2002 14:15, support wrote:
Using gnutar. We use a list to exclude the holding disk as well,
and it seems to work effectively, and is of a very similar
exclude format: exclude /data/[RH]*
You are using a syntax [RH], [a-l], that I'm not familiar with. I
suspect thats a regex expression that looks for matches in the
range specified within the []. But I'll leave that to wiser heads
to say if it will work or not.
However, bringing that sort of format of an exclude for the /home
directory fails. I believe what you are indicating is that if the
disk that I am splitting in two is the home directory, I should
use this format:
exclude ./[a-l]*
As ./ on this disk will be the /home dir.
As for amlabel, yes, all 10 new tapes have been labeled according
to what we were previously using, just that there are two new
tapes to the list. The Amanda tapelist had managed to
recognize/add the 9th tape, as it does show in the tapelist. You
are saying that I should modify the tapelist to add tape #10?
Here is our tapelist currently:
20020731 Daily05 reuse
20020730 Daily06 reuse
20020727 Daily04 reuse
20020726 Daily03 reuse
20020725 Daily02 reuse
20020724 Daily01 reuse
20020723 Daily08 reuse
20020722 Daily09 reuse
20020719 Daily07 reuse
The act of labeling them *should* have added them to the tapelist
without any further intervention from you, so I'm sitting here a
bit puzzled.
So I presume I should be adding Daily10 above the Daily09 line,
and I guess bump the dates by one day as Daily10 would be
20020723 right? (seems to make sense to me)
Don't muck with the dates as thats amanda's shorthand to use as a
lookup pointer and match the tape with the backup index kept on
disk. Or at least thats how I understand it.
Thanks for your input Gene.
Tim
- Original Message -
From: Gene Heskett [EMAIL PROTECTED]
To: support [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, July 31, 2002 1:56 PM
Subject: Re: Back up issues
On Wednesday 31 July 2002 11:44, support wrote:
Hi,
We've been using Amanda for sometime to handle our tape back
ups, but have recently encountered an issue. One of our servers
has a rather large home directory that will not fit onto a
standard 12gig tape, so for the most part, we have been
attempting to split the dump into two parts for this drive. The
format for the two part dumps in the amanda.conf when working
were slightly different than below, but it was not backing up
files properly, so have attempted the following. What we are
trying to do is to back up the first part of the dump excluding
any file or directory starting with letters a-l, and then on the
second dump, backing up files excluding m-z.
I believe I must have the exclude format incorrect, I was
assuming that /home/[a-l]* would do the trick, but is causing
Amanda to produce errors saying that the dumps failed, and that
these two disks are offline.
define dumptype part1dump {
comment Delta part 1
global
priority high
exclude /home/[a-l]*
}
define dumptype part2dump {
comment Delta part 2
global
priority high
exclude /home/[m-z]*
I'm trying to find out the proper way of splitting a dump into
two, and have it work right.
Anyone have any ideas? I was also trying to get amanda.conf to
write to 10 tapes instead of 8, and that failed miserably as
well. Changing the tape # from 8 to 10, Amanda would no longer
recognize any labelled tapes, and would keep asking for a new
tape. So I'm back to 8 tapes again.
Thanks,
Tim
[EMAIL PROTECTED]
First, you didn't specify the actual reader/writer program, beit
dump or tar. Dump does not support exclusions so I assume you are
using tar.
The format I use, rather than a whole list of excludes (I do use
one list, to exclude the holding disks) is to just name
everything in the disklist, breaking it down to pieces that will
fit on a 4gig dds2 tape. I realize this will make for small
archives, all stacked up on one tape in your case, but its one
possibility.
The exclude files contents are a bit fussy, and according to the
docs, only work in this format:
---
./usr/dumps/*
./var/pacct
---
note the preceeding ./ in each line, which anchors it to the
current directory. In my case these happen to be off the root
branch, but this syntax I'm told is just as effective if I had a
/home/joetheblowfish/usr/dumps/*
in which case the trailing usr/dumps/* portion of that path
would be excluded.
Now, the tape problem. One must 'amlabel' the added tapes else
they probably won't be useable. This operation can also cause an
out of order useage by amanda, fixable by hand editing the
tapelist after the labeling operation to put the newly added
tapes into their proper place in the list, which, since amanda
uses a circular buffer, may or may not mean they would be at the
top or bottom of the list, but may be in some odd order
resembling this tapelist: 20020730
Re: /etc/amandates locking bug with 2.4.3b3
Jon, You were right on the money with this one. I reviewed the config.h file, and HAVE_FLOCK was defined as existing, but no locking scheme was defined for use. So I added: #define USE_FLOCK 1 to the config.h file, recompiled, and now the backup is executing normally on the host. Thanks for your help on this one. regards, Steve Kelly On Tue, 2002-07-30 at 18:58, Jon LaBadie wrote: On Tue, Jul 30, 2002 at 01:39:28PM +0800, Stephen Kelly wrote: Hello, I have an issue that is very frustrating with one of my amanda client machines. I am implementing amanda and adding in live clients one by one in my datacenter. I have three client machines working nicely with amanda so far. They are backing up to a psuedo autochanger configured on a hard disk partition on my backup server. This is working nicely while i wait for my new VXA Autochanger backup device to arrive. I have compiled the client software on the troublesome machine. It runs under xinetd as amanda:disk. The client runs a 2.2.16-22smp kernel and is based on redhat 7.0 amcheck reports no problems. However, when I attempt to rum amdump this client fails with a problem locking /etc/amandates. The error from /tmp/amanda/*size* is. sendsize: debug 1 pid 28239 ruid 515 euid 515 start time Tue Jul 30 15:32:56 2002 /usr/local/amanda/libexec/sendsize: version 2.4.3b3 could not lock /etc/amandates: Invalid argument sendsize: pid 28239 finish time Tue Jul 30 15:32:56 2002 Was this self-compiled? I ask as locking is one of the few configure problems I have had. It seems that there are about 5 different file locking schemes from which amanda can choose. And the code in configure is quite complex in deciding if each scheme exists and which is should use. In fact, although I think solaris, my os, has all of the 5 different schemes available, configure occasionally reports there is no file locking mechanism available. Perhaps a scan of the configure results and config.h would reveal which scheme is being used. Or maybe a make distclean frollowed by a new run of configure and rebuild might cause it to select a different scheme. It was a long time ago so details escape me, but I recall manually editing config.h before compiling to force amanda on solaris to use a specific locking scheme. The permissions on /etc/amandates is as follows: -rw-rw1 amanda disk0 Jul 26 19:02 /etc/amandates I have even tried making this file 0666 to see if that would make a difference but the same problem occured. There is at least one locking scheme on solaris that requires the set group id bit be turned on, with no execute on, for that file to be lockable. That would be permissions of 2660, -rw-rwS--- (capital S = sgid on, x off). The same configuration works fine on an older RedHat based server (RH 6.x vintage) and on my newer RH 7.3 based servers The same scan of the cache/config files might show which locking schemes are being employed and probably they should all be the same. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- === Technical Manager Ilisys Internet Pty Ltd [EMAIL PROTECTED] === New! Ilisys discussion forums http://forums.ilisys.com.au
Mac OS X yet?
I'm running Amanda on a FreeBSD server to back up various Unix-like workstations and servers on a LAN. We recently bought an iMac running Mac OS X, and I'd like to add it to the disklist whenever possible. Has anyone had any luck doing such a thing?
Re: /etc/amandates locking bug with 2.4.3b3
Let me add to this one. I thought defining use_flock would fix it. However it did not. I then tried lockf, posix_fcntl, and finally lnlock. It looks like it finally works with lnlock. I suspect their is some glibc bug relating to the locking stuff wit this revision of redhat (7.0). Fingers crossed, but the signs that it will work are looking good. Jon pointed me in the right direction, and with a little bit of trial and error it looks like I will run. Thanks again, regards, Steve Kelly On Thu, 2002-08-01 at 11:23, Stephen Kelly wrote: Jon, You were right on the money with this one. I reviewed the config.h file, and HAVE_FLOCK was defined as existing, but no locking scheme was defined for use. So I added: #define USE_FLOCK 1 to the config.h file, recompiled, and now the backup is executing normally on the host. Thanks for your help on this one. regards, Steve Kelly On Tue, 2002-07-30 at 18:58, Jon LaBadie wrote: On Tue, Jul 30, 2002 at 01:39:28PM +0800, Stephen Kelly wrote: Hello, I have an issue that is very frustrating with one of my amanda client machines. I am implementing amanda and adding in live clients one by one in my datacenter. I have three client machines working nicely with amanda so far. They are backing up to a psuedo autochanger configured on a hard disk partition on my backup server. This is working nicely while i wait for my new VXA Autochanger backup device to arrive. I have compiled the client software on the troublesome machine. It runs under xinetd as amanda:disk. The client runs a 2.2.16-22smp kernel and is based on redhat 7.0 amcheck reports no problems. However, when I attempt to rum amdump this client fails with a problem locking /etc/amandates. The error from /tmp/amanda/*size* is. sendsize: debug 1 pid 28239 ruid 515 euid 515 start time Tue Jul 30 15:32:56 2002 /usr/local/amanda/libexec/sendsize: version 2.4.3b3 could not lock /etc/amandates: Invalid argument sendsize: pid 28239 finish time Tue Jul 30 15:32:56 2002 Was this self-compiled? I ask as locking is one of the few configure problems I have had. It seems that there are about 5 different file locking schemes from which amanda can choose. And the code in configure is quite complex in deciding if each scheme exists and which is should use. In fact, although I think solaris, my os, has all of the 5 different schemes available, configure occasionally reports there is no file locking mechanism available. Perhaps a scan of the configure results and config.h would reveal which scheme is being used. Or maybe a make distclean frollowed by a new run of configure and rebuild might cause it to select a different scheme. It was a long time ago so details escape me, but I recall manually editing config.h before compiling to force amanda on solaris to use a specific locking scheme. The permissions on /etc/amandates is as follows: -rw-rw1 amanda disk0 Jul 26 19:02 /etc/amandates I have even tried making this file 0666 to see if that would make a difference but the same problem occured. There is at least one locking scheme on solaris that requires the set group id bit be turned on, with no execute on, for that file to be lockable. That would be permissions of 2660, -rw-rwS--- (capital S = sgid on, x off). The same configuration works fine on an older RedHat based server (RH 6.x vintage) and on my newer RH 7.3 based servers The same scan of the cache/config files might show which locking schemes are being employed and probably they should all be the same. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- === Technical Manager Ilisys Internet Pty Ltd [EMAIL PROTECTED] === New! Ilisys discussion forums http://forums.ilisys.com.au -- === Technical Manager Ilisys Internet Pty Ltd [EMAIL PROTECTED] === New! Ilisys discussion forums http://forums.ilisys.com.au
HOWTOs
Hello guys, I never found any good documentation about amanda so I never continued it. But everytime i see good post here on the mailing list, I'm being convince to try it again. So is anyone kind enough to share his notes, howtos, documentation on setting up and using amanda? Thank you. Ronneil
