Re:amlabel problems
- Original Message - From: Trevor Fraser [EMAIL PROTECTED] To: Jon LaBadie [EMAIL PROTECTED] Sent: Friday, July 12, 2002 9:21 AM Subject: Re: amlabel problems Hi Jon, What device are you using? i.e. the one stipulated in the amanda.conf file under, I think, tape device. I don't know if anyone will be able to help you without the relevent info. Another thing is does the tape rewind when it says it does? It sounds like wrong device name. -Trevor. - Original Message - From: Jon LaBadie [EMAIL PROTECTED] To: amanda-users [EMAIL PROTECTED] Sent: Thursday, July 11, 2002 11:18 PM Subject: Re: amlabel problems On Thu, Jul 11, 2002 at 02:30:20PM -0600, Trevor Morrison wrote: ... . When I run amlabel I get this output: rewinding, reading label, no tape online I would interpret this as saying the system does not believe there is a tape in the drive. Why it is saying that I don't know. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
localhost request time-out error failure to load tape
Hi there, I am currently trying to configure Amanda version 2.4.2p2, using Linux Redhat 7.3. The storage device used is HP Surestore DLT8000, using tape HP DLT-IV. I ran "amcheck DailySet1/" as user amanda on the localhost and I encountered the following error message: "Self-check request to host 127.0.0.1 timed out. Host down?" May I know how I should solve this problem? Besides using devices /dev/st0 or /dev/nst0, can I access the tapes with any other device names in Redhat? This is because I have problems loading unloading tapes using the amtape command. I am using the chg-multi changer script and in chg-multi.conf, the following parameters were set as: "multieject 0" "gravity 0" "needeject 0" "ejectdelay 0" "statefile /etc/amanda/DailySet1/changer-status" "firstslot 1" "lastslot 1" "slot 1 /dev/nst0" "127.0.0.1 /var/lib/amanda nocomp-user" is also included in the disklist file, which specifies the directory to be backed up. Thank you very much. Regards, Dallas Chee Get a bigger mailbox -- choose a size that fits your needs.http://uk.docs.yahoo.com/mail_storage.html
Re: localhost request time-out error failure to load tape
I haven't used a multi-changer, but this sounds like your .amandahosts file isn't configured properly, most probably only contains "localhost 127.0.0.1" entry. This file occurs in the dump user's home directory. Remember its a (.) file so you must use ls -al to see it. "Look at ' # man amcheck' to see how you can run amcheck on only the client oronly the host." - Original Message - From: DALLAS CHEE To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 12:36 PM Subject: localhost request time-out error failure to load tape Hi there, I am currently trying to configure Amanda version 2.4.2p2, using Linux Redhat 7.3. The storage device used is HP Surestore DLT8000, using tape HP DLT-IV. I ran "amcheck DailySet1/" as user amanda on the localhost and I encountered the following error message: "Self-check request to host 127.0.0.1 timed out. Host down?" May I know how I should solve this problem? Besides using devices /dev/st0 or /dev/nst0, can I access the tapes with any other device names in Redhat? This is because I have problems loading unloading tapes using the amtape command. I am using the chg-multi changer script and in chg-multi.conf, the following parameters were set as: "multieject 0" "gravity 0" "needeject 0" "ejectdelay 0" "statefile /etc/amanda/DailySet1/changer-status" "firstslot 1" "lastslot 1" "slot 1 /dev/nst0" "127.0.0.1 /var/lib/amanda nocomp-user" is also included in the disklist file, which specifies the directory to be backed up. Thank you very much. Regards, Dallas Chee Get a bigger mailbox -- choose a size that fits your needs.http://uk.docs.yahoo.com/mail_storage.html
some questions that I can´t get the answers
Hi,
I read the documentation at the software source,
the FAQ at amanda.org and i didn´t get the answer to these
questions.
1) how do I know how logger does my backup it
takes? I know the start time, but I don´t know when it is
finishing.
2) why I get this at my log after backup is done?
Whats the difference between Success and Strange?
FAIL dumper piaui /mnt/backup/sn1/etc1 0 [/bin/gtar
returned 2]
sendbackup: start [piaui:/mnt/backup/sn1/etc1 level
0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f...
-
sendbackup: info end
? gtar: ./samba/private: Cannot savedir: Permission
denied
? gtar: ./samba/private: Warning: Cannot savedir:
Permission denied
| Total bytes written: 112640 (110kB,
193kB/s)
? gtar: Error exit delayed from previous
errors
sendbackup: error [/bin/gtar returned 2
SUCCESS taper piaui /etc 20020711 0 [sec 0.451 kb 1248 kps
2762.6 {wr: writers 39 rdwait 0.000 wrwait 0.443 filemark 0.007}]
STRANGE dumper piaui /mnt/backup/sn3/etc2 0 [sec 14.472 kb
192 kps 13.3 orig-kb 960]
sendbackup: start [piaui:/mnt/backup/sn3/etc2 level
0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f...
-
sendbackup: info end
? gtar: ./hosts.equiv: Warning: Cannot open: Permission
denied
? gtar: ./master.passwd: Warning: Cannot open: Permission
denied
? gtar: ./skeykeys: Warning: Cannot open: Permission
denied
? gtar: ./spwd.db: Warning: Cannot open: Permission
denied
? gtar: ./ssh_host_dsa_key: Warning: Cannot open:
Permission denied
? gtar: ./ssh_host_key: Warning: Cannot open: Permission
denied
? gtar: ./ssh_host_rsa_key: Warning: Cannot open:
Permission denied
? gtar: ./rc.d/snort: Warning: Cannot open: Permission
denied
| Total bytes written: 983040 (960kB,
296kB/s)
sendbackup: size 960
sendbackup: end
If anyone can help me with this I will be glad!!
;-)
ceva
Re: some questions that I can´t get the answers
On Fri, 12 Jul 2002 at 10:38am, Eduardo Ceva wrote 1) how do I know how logger does my backup it takes? I know the start time, but I don´t know when it is finishing. a) Look at the time at which the report email is sent b) In that email, look at the Run time. That's the amount of (wall clock) time for which amanda ran. 2) why I get this at my log after backup is done? Whats the difference between Success and Strange? STRANGE means the backup finished, but the backup program (tar, in your case) output some messages amanda wasn't expecting. FAIL dumper piaui /mnt/backup/sn1/etc1 0 [/bin/gtar returned 2] sendbackup: start [piaui:/mnt/backup/sn1/etc1 level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end ? gtar: ./samba/private: Cannot savedir: Permission denied ? gtar: ./samba/private: Warning: Cannot savedir: Permission denied *snip* STRANGE dumper piaui /mnt/backup/sn3/etc2 0 [sec 14.472 kb 192 kps 13.3 orig-kb 960] sendbackup: start [piaui:/mnt/backup/sn3/etc2 level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end ? gtar: ./hosts.equiv: Warning: Cannot open: Permission denied ? gtar: ./master.passwd: Warning: Cannot open: Permission denied ? gtar: ./skeykeys: Warning: Cannot open: Permission denied ? gtar: ./spwd.db: Warning: Cannot open: Permission denied ? gtar: ./ssh_host_dsa_key: Warning: Cannot open: Permission denied ? gtar: ./ssh_host_key: Warning: Cannot open: Permission denied ? gtar: ./ssh_host_rsa_key: Warning: Cannot open: Permission denied ? gtar: ./rc.d/snort: Warning: Cannot open: Permission denied So, you're having permissions errors. Amanda runs tar via a setuid root runtar wrapper, so you shouldn't be getting these. However, I see that these filesystems are in /mnt -- are they NFS mounted perchance? If that's the case, you need to set the no_root_squash option on the NFS server(s) for these exports. Otherwise, root on the NFS client (the one running amanda) gets mapped to nobody on the NFS server, and you get your permission denied errors. Is there a reason you can't install the amanda client bits on the NFS servers themselves? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
schg ...
Oops! I did my first real attempt at restoring data. I restored the / directory of a networked computer from a tape on the amanda server to my dump directory on my amanda server. Now I have some files with flag schg that I cannot get rid of. I have tried 'shutdown now' to get into single user mode, with no luck. (operation not permitted). I then tried rebooting with 'boot -s', this time I can't see any files in any directory that isnt in /. (I cant see below mounted drives, nor can I run the chflags command) I need some help with this problem, but more importantly, could someone please point me in a direction to some good amrestore/amrecover docs? I have several servers being backed up to my amanda server, and would really like to know the best procedure in the following situation: If /usr on server1 crashes (/usr is on it's own disk), what is the best policy to do a full restore to a new HD on server1 including lev 0 and up? What happens to symlinks and the like. Tks greatly, Steve Bertrand
Re: SMBCLIENT program not available
hello, Did you ever get this resolved? I just remembered also that if samba isn't setup correctly, this might produce this error. I believe in order for samba to work at all, it needs an smb.conf file in the appropriate location. --jason On Tue, Jun 25, 2002 at 11:25:26PM +0200, Martin Schmidt wrote: Hi, I am just testing amanda on my privat network before I will install it in the company. I have a SuSE-Linux 7.3 (rappelkasten) with samba, amanda and tape, and for testing a Win-Nt4 (rumpl). There is no problem running amanda on the linux. So I tried to backup a share from the NT. I created a user amanda on the NT with all privileges on one share. When I do a smbclient from commandline I can see the contents of that share. When I start amcheck, I get the messages: Amanda Backup Client Hosts Check ERROR: localhost: [This client is not configured for samba: //rumpl/lwd] ERROR: localhost: [SMBCLIENT program not available] Client check: 1 host checked in 0.084 seconds, 2 problems found (brought to you by Amanda 2.4.2p2) -- First i supposed, amanda is not configured with-smbclient when I install it from SuSE's CDs, so I got the file from source-forge and did a configure with --with-smbclient=/usr/bin/smbclient --with-user=amanda --with-group=disk (smbclient _is_ there, user and group I took from SuSE's default ). The messages are the same. There is no hint in the FAQs, the doc - directory, but several questions in the mailing list, but all unanswered. So I hope, I get an answer and wipe this problem off. Thanks Martin -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Re: Netapp dumps using Amanda
Yes you are right. I'm sorry we have indexing enabled. It is the record that we have disabled. Sorry bout that part. Ashwin. Jon LaBadie wrote: On Thu, Jul 11, 2002 at 01:56:04PM -0700, Ashwin Kotian wrote: Hi Paul, I think the reason we disabled indexing was because with indexing enabled, amanda was trying to use the u option try to update the dumpdates file was failing therein. Amanda wouldn't even do a dump it complained with it a cannot update dumpdates file error. Shouldn't that be the record parameter, not the index param? You can also compile amanda to use its own amandates file instead of the system dumpdates file.
Re: Archival tape backup configuration help
If I wanted to do something similar, but I didn't want to reuse the
tapes at all (I need to store each one for 7 years), how would I set
Amanda up to do that?
Thanks in advance!
Anthony
On Mon, 2002-07-08 at 12:53, Jon LaBadie wrote:
On Mon, Jul 08, 2002 at 04:57:07PM -0400, Cory Visi wrote:
Ok, I have my daily tape backup set configured and working perfectly.
Now I
want to setup an archival (available for offsite storage) backup
strategy.
Here is how I want it to work:
Week 1: Full backup to tapes 1 and 2
Week 3: Take tapes 1 and 2 offsite
Week 5: Full backup to tapes 3 and 4
Week 7: Replace tapes 1 and 2, take tapes 3 and 4 offsite
Week 9: Full backup to tapes 1 and 2
etc...
There will be 4 tapes total, 2 tapes per backup. amdump will be
run
every 4 weeks.
The difficulty is that a full backup of our disks do not fit on
one
tape. We can easily fit the excess in the holding space though.
The limitation is not the size of the total backup.
The limitation is the size of the largest disklist entry. No SINGLE
entry
in the disklist can span a tape. If you are using the same list (even
if
in a different file and config) you already know each individual
disklist
entry will fit onto a tape.
Aside from the weird crontab line, how would I configure Amanda to
handle
this strategy? This is what I have right now (I know it's wrong
because
it's not working at all):
dumpcycle 8 weeks
4 weeks
runspercycle 2
1
tapecycle 4 tapes
define dumptype comp-user-full {
comment Non-root partitions on reasonably fast machines (full
only)
record yes
Probably no so your dailies don't think a full was done and will
still do their own at the appropriate times.
index yes
skip-incr yes
Some suggest a dumpcycle of 0 to always force full.
compress client fast
priority medium
}
amdump email returns the following message:
driver: WARNING: got empty schedule from planner
and all the disks get SKIPPED.
I have a feeling skip-incr is not the right setting to use.
Anyone have any ideas?
Thank you for your help,
Cory Visi
End of included message
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Archival tape backup configuration help
amanda@tape$ amadmin MyConfig no-reuse MyOffsiteTapeLabel-1
Amanda will keep the record of the backup, but never ask for the tape again.
It is essentially read-only.
You should add another tape to your rotation (with a new name) to replace
it.
-Original Message-
From: Anthony Valentine [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 12, 2002 5:08 PM
To: Jon LaBadie
Cc: Amanda Users
Subject: Re: Archival tape backup configuration help
If I wanted to do something similar, but I didn't want to reuse the
tapes at all (I need to store each one for 7 years), how would I set
Amanda up to do that?
Thanks in advance!
Anthony
On Mon, 2002-07-08 at 12:53, Jon LaBadie wrote:
On Mon, Jul 08, 2002 at 04:57:07PM -0400, Cory Visi wrote:
Ok, I have my daily tape backup set configured and working
perfectly.
Now I
want to setup an archival (available for offsite storage) backup
strategy.
Here is how I want it to work:
Week 1: Full backup to tapes 1 and 2
Week 3: Take tapes 1 and 2 offsite
Week 5: Full backup to tapes 3 and 4
Week 7: Replace tapes 1 and 2, take tapes 3 and 4 offsite
Week 9: Full backup to tapes 1 and 2
etc...
There will be 4 tapes total, 2 tapes per backup. amdump will be
run
every 4 weeks.
The difficulty is that a full backup of our disks do not fit on
one
tape. We can easily fit the excess in the holding space though.
The limitation is not the size of the total backup.
The limitation is the size of the largest disklist entry. No SINGLE
entry
in the disklist can span a tape. If you are using the same list (even
if
in a different file and config) you already know each individual
disklist
entry will fit onto a tape.
Aside from the weird crontab line, how would I configure Amanda to
handle
this strategy? This is what I have right now (I know it's wrong
because
it's not working at all):
dumpcycle 8 weeks
4 weeks
runspercycle 2
1
tapecycle 4 tapes
define dumptype comp-user-full {
comment Non-root partitions on reasonably fast machines (full
only)
record yes
Probably no so your dailies don't think a full was done and will
still do their own at the appropriate times.
index yes
skip-incr yes
Some suggest a dumpcycle of 0 to always force full.
compress client fast
priority medium
}
amdump email returns the following message:
driver: WARNING: got empty schedule from planner
and all the disks get SKIPPED.
I have a feeling skip-incr is not the right setting to use.
Anyone have any ideas?
Thank you for your help,
Cory Visi
End of included message
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Remote Tape drive
I am trying to setup amanda on my test machine to act as the Amanda server I want it to use a tape drive on a remote machine. I know it would be practical advisable to install Amanda on the machine to which the tape drive is connected but I would like to test Amanda with some source modifications on my test machine have it dump to the tape drive connected to the remote machine. I have set up rsh access for user amanda on the machine with the tape drive. Now the only process remaining is to setup the tape device that my amanda server will use. What tape device do I need to specify in the amanda config if it involves using the RMT protocol, how do I go about setting up this device file on my local machine using which I can access the tape drive on the remote machine. Your co-operation suggestions are very much appreciated. Thanks, Ashwin.
Re: Gnutar not recognized
On Thursday 11 July 2002 17:41, Scott Sanders wrote: Hi all, I've got amanda up and running pretty well now with the local dump s/w. I'd like to have the GNUtar at my disposal as well but even after installing it and deleting the config.cache files, re-running configure amcheck still can't find it. will running make clean or make distclean solve this? distclean might, Scott. I was in error when I said it had to be findable by the configuration tool. Then someone else says you have to find tar and tell ./configure with an option line where its at. Or at least that was somebody elses advice, but I'm *not* doing that and I *am* using tar, so there seems to be some amount of room for 'interpretation' I guess. In any event, here is the script I use to run configure. I use it so there aren't any surprises when I migrate to the each new release of the 2.4.3b3 series as they come out. --- #!/bin/sh make clean rm -f config.status config.cache ./configure --with-user=amanda --with-group=disk \ --with-owner=amanda --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=192.168.1.3 --with-amandahosts \ --with-configdir=/usr/local/etc/amanda - In other words, I don't do ./configure but ./gh-cf which is the local name of that shell script above. From that, you can see that I'm not setting it with an option. tar-1.13-25 is in my PATH as root, or as user amanda. You should unpack it as root, then before cd'ing to the unoacked directory, do chown -R amanda:disk amanda-version, then su to amanda, build it, exit to root and instal. That way all the perms to run it are properly set. Thanks for all the great help everyone -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.06% setiathome rank, not too shabby for a WV hillbilly
Re: Remote Tape drive
On Fri, 12 Jul 2002, Ashwin Kotian wrote: Your co-operation suggestions are very much appreciated. man rmt man rdump -- pay attention to '-f' argument man rrestore -- ditto man tar -- pay attention to --file argument, GNUtar only Lather, rinse, repeat. Now you have the information necessary to ask smart questions[0]. I don't know of any current support for this in amanda but it should not be difficult to implement. If you're intersted then look at tape-src/tapeio.[ch] in the amanda source. Sounds to me like implementing that is overkill for your project though. Just install amanda on the machine with the tape drive; run two concurrent amandas on that machine if it's already running an amanda install until you get your testing done. If you're really worried about it, dig up an old QIC drive or something to test with. [0] - http://www.tuxedo.org/~esr/faqs/smart-questions.html -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
