Re: Error: can not access sda1: No such file or directory
ERROR: rajiv [can not access sda1 (sda1): No such file or directory] Your directory is /dev/sda1, it is NOT sda1 Olivier
Re: selfcheck request timed out.
since a reboot of the firewall, amanda reports selfcheck request timed out. for some (up to four) servers. some servers are never reported (they seem to repsond to the selfcheck request), the other servers change (i.e., servers a,b,c,d are reported to time out, 1 hour later servers c,d,e,f are reported to time out). I would suggest that the firewall had been reconfigured to allow amanda and the confg was not saved. When the firewall rebooted, the modifications were lost. Olivier
amcheck: permission denied
Hi I will appreciate if somebody can spare his/her time to help me making sure that the amanda-2.4.2p2 is working. I have configured amanda.conf by following the docs and FAQ. However running amcheck through crontab gives me this error. amcheck: could not open /tmp/amanda/amcheck.temp.1501: Permission denied permision on this folder is as follows. 1 drwx--S---2 amanda amanda 1024 Jul 10 09:27 . 1 drwxrwxrwt 13 root root 1024 Jul 10 09:27 .. 1 -rw---1 amanda amanda244 Jul 10 09:27 amcheck.20010710092 700.debug pls help. Sendoro
Amanda on RH7.1
Hi Sir, How do I backup my Samba server running on Redhat 7.1 using Amanda? There' s a part in the INSTALL which mentions about inetd.conf. But Redhat 7.1 don't use inetd.conf, is there a problem? Thanks. warmest regards, Desmond Lim System Administrator http://www.kikuze.com/ AP Co-ordinator Pte Ltd 6 Aljunied Ave 3 #01-02 Singapore 389932 Tel: 7460188#322 Fax: 7462550 HP: 94525736
Re: Amanda on RH7.1
On Tue, 10 Jul 2001 at 6:28pm, Desmond Lim wrote
How do I backup my Samba server running on Redhat 7.1 using Amanda? There' s
a part in the INSTALL which mentions about inetd.conf. But Redhat 7.1 don't
use inetd.conf, is there a problem?
Redhat 7.x uses xinetd rather than inetd. Config files are kept in
/etc/xinetd.d/. For amanda, just put a file called 'amanda' in there
with the following contents:
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
server = /usr/local/libexec/amandad
}
Then restart xinetd via '/etc/init.d/xinetd restart' -- ISTR that just
sending xinetd a SIGHUP is no longer sufficient.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: Redo amdump
On Sun, Jul 08, 2001 at 04:17:15PM +0100, Jose Manuel dos Santos Calhariz wrote: During this nigth, some machines crashed during the backup and I don't trust the backup that amanda have done. I think it could have taped garbage. How do I redo the amdump of this nigth, as it have never happened? Supose that it was labeled DailySet1-01 In trying to do that, I have amrmtape DailySet1-01. But whenever amdump started to run, it remember the backups it have done this nigth. So I deleted from the logs, the amdump and log files of this nigth. Now it forgets about the the backups of this nigth. It was not enough. It forgets the full backups, but not the incremental backups. So I have a filesystem that have bumped from level 1 to level 3 without level 2 on tape. It will force the full backup of that filesystem, and everything should be OK. What I am asking is: What I should have done, to redo the backup of the day, if for some motive I have lost it. It think the procedure to redo a backup is a good one to put in the FAQ. I am running version 2.4.2 Jose Calhariz -- --
Problems backing up
Hi, I still have problems backing up.. I backup more directories from one machine over the internet. I check the status as the process progresses and I found that one directory got dumped okay, but the next one hangs at 100.04% :-? The directories being backed up are cobalt01.somewhere.nl: /etc, /home and /var. I previously mailed my problems regarding a backup problem of the /home directory, while the others went fine.. but roght now, the /etc directory fails as well... I am very curious where to look for the problem... To find out, I made a second config for backing up (and send the dumps to /dev/null). so besides config hosting I use hosting2 for test purposes. checking the status with amcheck hosting2 tells me that the /var dir is backed up okay (first dir.), /etc hangs at 100.04% and /home is waiting for /etc to finish. The amounts to be backed up are : /etc 70Mb, /home 200Mb and /var 17Mb I must say I find it very strange that over time (it worked perfectly), more and more problems arise. With hosting2 I tried to clear en curinfo and index directories, to make a clean start, but no luck. I am using Amanda 2.4.2p1 on the server (A Sun Solaris 2.6 machine) And on the cobalt as well 2.4.2p1. After the process has stalled, the gtar program is still listed in the process list (ps) for a while, but it quits as well, after about 10 minutes. Can I clean some information on the client (cobalt) for amanda which makes it start from scratch? Or is information only stored on the server side (using the curinfo and index directories) ? Thanks.. Shakespeare: 2B|^2B=?
Re: Amanda on RH7.1
On Tue, 10 Jul 2001, Desmond Lim wrote: Hi Sir, We are a list, not a sir ;) How do I backup my Samba server running on Redhat 7.1 using Amanda? There' s a part in the INSTALL which mentions about inetd.conf. But Redhat 7.1 don't use inetd.conf, is there a problem? RH upgraded to xinetd and there's documentation about that. If not elsewhere, then in the mailinglist archives. Adding amanda there is quite trivial. Also, backing up a non-windows (or other crippled CIFS-only system) has nothing to do with samba, so you shouldn't need to worry about that.
Re: Amanda on RH7.1
If you use the amanda package that comes with RedHat 7.1, it will set itself up in xinetd automatically. You will need to edit the xinetd file for amanda to enable it. Note that if you are using high security, you will need to add rules to ipchains for the backup server. In particular, you need a rule that allows: IP: backup_server - backup_client, Port: any - 10080, Proto: UDP Also, Amanda will open up random TCP ports on the client for commands, data and indexing. This rule should should do the trick: IP: backup_server - backup_client, Port: any - any, Proto: TCP, SYN Packets (-y) Chris Desmond Lim [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: Sent by: Subject: Amanda on RH7.1 owner-amanda-users@ amanda.org 07/10/2001 06:28 AM Hi Sir, How do I backup my Samba server running on Redhat 7.1 using Amanda? There' s a part in the INSTALL which mentions about inetd.conf. But Redhat 7.1 don't use inetd.conf, is there a problem? Thanks. warmest regards, Desmond Lim System Administrator http://www.kikuze.com/ AP Co-ordinator Pte Ltd 6 Aljunied Ave 3 #01-02 Singapore 389932 Tel: 7460188#322 Fax: 7462550 HP: 94525736
Newbie neeed Help
I believe with this log file need for someone to be able to help me. The status report (below) looks like this when I attempt to run amdump and stays like this. I'm attempting to do a tapeless backup with version 2.4.2p2 of amanda. Thank you for your help. ekeely:/boot 0 730k wait for dumping SUMMARY part real estimated size size partition : 1 estimated : 1730k failed : 0 0k ( 0.00%) wait for dumping: 1730k (100.00%) dumping to tape : 0 0k ( 0.00%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 00k0k ( 0.00%) ( 0.00%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 00k0k ( 0.00%) ( 0.00%) all dumpers active taper idle Patrick Lanphier The Artemis Group http://www.artemisgroup.com email: [EMAIL PROTECTED] phone: 814-235-0444 fax: 800-582-9710 amdump: start at Tue Jul 10 09:06:12 EDT 2001 planner: pid 13776 executable /usr/libexec/planner version 2.4.2p2 planner: build: VERSION=Amanda-2.4.2p2 planner:BUILT_DATE=Mon Jul 9 14:49:53 EDT 2001 planner:BUILT_MACH=Linux c11030-a.scllg1.pa.home.com 2.4.4-pre8 #15 Sat Apr 28 10:14:26 EDT 2001 i686 unknown planner:CC=gcc planner: paths: bindir=/usr/bin sbindir=/usr/sbin planner:libexecdir=/usr/libexec mandir=/usr/man planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda planner:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ planner:RDEV_PREFIX=/dev/ DUMP=/sbin/dump planner:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient planner:GNUTAR=/bin/gtar COMPRESS_PATH=/bin/gzip planner:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail planner:listed_incr_dir=/usr/var/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=c11030-a.scllg1.pa.home.com planner:DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=c11030-a.scllg1.pa.home.com planner:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS planner:CLIENT_LOGIN=root FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc planner: dgram_bind: socket bound to 0.0.0.0.916 READING CONF FILES... startup took 0.009 secs SETTING UP FOR ESTIMATES... setting up estimates for ekeely:/boot ekeely:/boot overdue 11514 days for level 0 setup_estimate: ekeely:/boot: command 0, options: last_level -1 next_level0 -11514 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates took 0.001 secs GETTING ESTIMATES... taper: pid 13781 executable taper version 2.4.2p2 driver: pid 13780 executable /usr/libexec/driver version 2.4.2p2 driver: send-cmd time 0.069 to taper: START-TAPER 20010710 changer: opening pipe to: /usr/libexec/chg-manual -info got result for host ekeely disk /boot: 0 - 1460K, -1 - -1K, -1 - -1K getting estimates took 0.234 secs FAILED QUEUE: empty DONE QUEUE: 0: ekeely /boot ANALYZING ESTIMATES... pondering ekeely:/boot... next_level0 -11514 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 730 total size 970 total_lev0 730 balanced-lev0size 36 INITIAL SCHEDULE (size 970): ekeely /boot pri 11514 lev 0 size 730 DELAYING DUMPS IF NEEDED, total_size 970, tape length 4300800 mark 48 delay: Total size now 970. PROMOTING DUMPS IF NEEDED, total_lev0 730, balanced_size 36... analysis took 0.000 secs GENERATING SCHEDULE: ekeely /boot 11514 0 1970:1:1:0:0:0 730 24 dumper: dgram_bind: socket bound to 0.0.0.0.923 dumper: pid 13783 executable dumper version 2.4.2p2, using port 923 driver: started dumper0 pid 13783 dumper: dgram_bind: socket bound to 0.0.0.0.928 dumper: pid 13787 executable dumper version 2.4.2p2, using port 928 driver: started dumper1 pid 13787 dumper: dgram_bind: socket bound to 0.0.0.0.930 dumper: pid 13789 executable dumper version 2.4.2p2, using port 930 driver: started dumper2 pid 13789 dumper: dgram_bind: socket bound to 0.0.0.0.932 dumper: pid 13791 executable dumper version 2.4.2p2, using port 932 driver: started dumper3 pid 13791 driver: adding holding disk 0 dir /home/amanda size 19414028 reserving 9707014 out of 19414028 for degraded-mode dumps driver: start time 0.460 inparallel 4 bandwidth 3000 diskspace 19414028 dir OBSOLETE datestamp 20010710 driver: drain-ends tapeq LFFO big-dumpers 1 changer: got exit: 0 str: 0 99 1 changer: opening pipe to: /usr/libexec/chg-manual
Re: Amanda on RH7.1
How do I backup my Samba server running on Redhat 7.1 using Amanda? There' s a part in the INSTALL which mentions about inetd.conf. But Redhat 7.1 don't use inetd.conf, is there a problem? Don't use Linux :) Why those people always want to do things diferently? Well I think it is called xinetd.conf under Linux. Olivier
Re: Multiple tape drives config
Matteo Centonza [EMAIL PROTECTED] writes: Hi all, I'm trying to set up a backup server with two tape drives: - Tandberg SLR 100 - Sony SDT-5000 (DDS-2 DAT Tape Drive) is it possible to force the planner in order to use smallest tape to perform incrementals and SLR for full dumps, without tricky FAQ suggestions (holding disk et al.)? Has anyone tried similar two drives configuration? Matteo, Before messing with this stuff, get Amanda running in two standard configurations (one for each tape drive). After that I'd have a look at the man page for the strategy parameter. strategy string Default: standard. Strategy to use when planning what level of backup to run next. Values are: standard The standard Amanda schedule. nofull Never do full backups, only level 1 incre mentals. noinc Never do incremental backups, only full dumps. skip Never do backups (useful when sharing the disklist file). incronly Only do incremental dumps. `amadmin force' should be used to tell Amanda that a full dump has been performed off-line, so that it resets to level 1. It is similar to skip- full, but with incronly full dumps may be scheduled manually.Unfortunately, it appears that Amanda will perform full backups with this configuration, which is probably a bug. The developers will tell you if the incronly bug still exists. Another bug: Is there a parameter strategy skip-full? The trick is to use strategy incrony for the small tape and have the full backups started by an external skript. OTOH is it worth it to reuse old DDS2 tapes over and over? I'd make restore tests as soon as possible and tell the boss that DDS tapes can be used only about 10-20 times before they get unreliable. HTH, Johannes Nieß
tapetype for hp surestore dat 40x6
hello all
i am new to this list and i just finished tapetype on an hp dat40x6
here is the result :
define tapetype SureStore-DAT40x6 {
comment HP SureStore DAT 40x6 autoloader
length 17004 mbytes
filemark 399 kbytes
speed 1584 kps
}
regards
Paolo Borsa
IT Manager
Promelit S.p.A.
20, Via Modigliani
I-20092 Cinisello Balsamo (MI)
Phone +39 02 66087 1
Fax +39 02 66087 302
e-mail : [EMAIL PROTECTED]
web : http://www.promelit.it
unsubscribe
Title: unsubscribe unsubscribe ~~~ The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. ~~~
No Subject
question: multi DLT drive Linux (RH v7.1)
hello all, i have a PowerStor L200 DLT tape-changer unit connected via an Adaptec 29160 controller, and am running my amanda server (v2.4.2p2) on a Linux RH v7.1 box. i can read/label/write to a tape in the drive, and if i use 'amtape conf eject', my L200 automatically unloads the tape currently in the drive and grabs the next one in the magazine. however, if i run an 'amcheck conf' i get slot is empty errors for every slot in the magazine, even though they all have tapes in them (i.e.): Amanda Tape Server Host Check - Holding disk /backup: 74779256 KB disk space available, using 65342072 KB amcheck-server: slot 6: reading label: Input/output error amcheck-server: slot 7: slot is empty amcheck-server: slot 0: slot is empty amcheck-server: slot 1: slot is empty amcheck-server: slot 2: slot is empty amcheck-server: slot 3: slot is empty amcheck-server: slot 4: slot is empty amcheck-server: slot 5: slot is empty ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 40.692 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.037 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) here's a copy of my chg-multi.conf: multieject 0 gravity 0 needeject 1 ejectdelay 20 statefile /var/log/amanda/csd/changer-status firstslot 0 lastslot 7 orget to specify the no-rewind version of the device. slot 0 /dev/nst0 slot 1 /dev/nst1 slot 2 /dev/nst2 slot 3 /dev/nst3 slot 4 /dev/nst4 slot 5 /dev/nst5 slot 6 /dev/nst6 slot 7 /dev/nst7 also, what's the easiest way to sync/alter amanda so that it reads tapes sequentially from 0-7? it seems as though every time i run amcheck it increments the slot number it thinks its reading +1, even though the tape in the drive came from slot0 ? thanks in advance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799 [EMAIL PROTECTED]
Re: Redo amdump
What I am asking is: What I should have done, to redo the backup of the day, if for some motive I have lost it. My guess (but I have not thought this through entirely) would be to leave the tape alone (do not do the amrmtape) but use force-no-bump with amadmin for all the clients. I think that would force Amanda to redo the same level for each one as the failed run. Jose Calhariz John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Error: can not access sda1: No such file or directory
ERROR: rajiv [can not access sda1 (sda1): No such file or directory] I think what Olivier was suggesting is that you change that to /dev/sda1. Or, what I would do, is use the mount point, /. What does the / entry look like in /etc/fstab? Is the client also running 2.4.1p1 or is it running something newer? What OS and version is the client running? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Change Amanda Client
I am running amanda-2.3.0.4. ... You're probably going to have a tough time finding help with such an ancient release. Hint, hint :-). Does anyone who knows how to change amanda clients. Such as delete an existing client and add another new client. This is all purely guesswork, but I'd think on the server side it would not take anything more than deleting the entries from the disklist for the client going away and adding the new ones. As far as the software on the client, since they are both Solaris Sparc, I'd try copying the pieces from the client or server to the new client. Even though the OS version is different, I expect 2.8 will be able run the 2.6 Amanda binaries. Make sure you keep permissions and ownership exactly the same (don't lose any setuid-root stuff, for instance). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: changer problems
Hi, On Tue, Jul 10, 2001 at 04:41:12AM -, [EMAIL PROTECTED] wrote: The chg-scsi in 2.4.2p2 and 2.5.0 cvs does not work right with this changer - after loading 10th tape won't do anything else Huh, if have an EXB library here as my development equipment and it works great. (yes, I have gravity set to 0) - Hmm there is no option gravity for chg-scsi, could it be that your setup ist wrong. Can you send me your amanda.conf and changer config file to see whats wrong, and if there is something wrong in chg-scsi i will fix it :-)... Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Re: Samba
I am new to amanda back up ... Then welcome to the Amanda mailing list! I heard that Loading Samba on win2k unix boxes, and configuring amanda will enable to take backup of both win2k and unix servers.. It doesn't quite work this way (but close). Samba is a package that runs on Unix machines and talks the Windows file sharing protocols. So what you'll do is install Samba on one of your Unix machines, and then tell Amanda to use that Unix machine to reach out to the Windows boxes. So the first thing to do is pick a Unix machine and install Samba on it. Once you have that working and can connect to the Windows machines with smbclient (which is described in the Samba documentation), then you can add in the Amanda parts. Take a look at docs/SAMBA that comes with the Amanda distribution. There is also some discussion in: http://www.backupcentral.com/amanda.html And if you get stuck, don't hesitate to post here again. Rajesh. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problems backing up
I check the status as the process progresses and I found that one directory got dumped okay, but the next one hangs at 100.04% :-? As Olivier said, the value being larger than 100% is not a problem. The hang, of course, is :-). To find out, I made a second config for backing up (and send the dumps to /dev/null). ... That was a good idea. You did set record no in the dumptypes, right? Otherwise, this testing will interfere with the real backups. checking the status with amcheck hosting2 tells me that the /var dir is backed up okay (first dir.), /etc hangs at 100.04% and /home is waiting for /etc to finish. So the next thing to do is find out what part is hanging. After the process has stalled, the gtar program is still listed in the process list (ps) for a while, but it quits as well, after about 10 minutes. Is the sendbackup process still there as well? Hangs are notoriously hard problems to debug, especially with lots of processes connected in a complex manner like Amanda sets up. You'll need to build everything with debugging enabled (-g on the cc/gcc lines), and both gdb and lsof tools available on client and server. After watching one of your backups that behaves to see how things normally move, do the same to the one that hangs and try to figure out what's different, where the data is jammed up, etc. The first thing I'd try is turning indexing off (note that these are just debugging tips -- I'm not suggesting you'll have to run production this way). That will simplify the connections between processes. What do you have maxdumps set to? Try setting it to one. Can I clean some information on the client (cobalt) for amanda which makes it start from scratch? Or is information only stored on the server side (using the curinfo and index directories) ? The only information clients store/update is the listed incremental files if you're using GNU tar or /etc/dumpdates for dump. If you've set record no, they are not a factor. Everything that controls Amanda is on the server. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie neeed Help
I believe with this log file need for someone to be able to help me. The status report (below) looks like this when I attempt to run amdump and stays like this. I'm attempting to do a tapeless backup with version 2.4.2p2 of amanda. ... In the log it says this: changer: opening pipe to: /usr/libexec/chg-manual -slot current That means it's sitting there waiting for you to mount the tape. How did you try to set up Amanda to run tapeless? Normally that would be done by *not* defining a tape changer and setting tapedev to something like /no-such-device. Patrick Lanphier John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck: permission denied
amcheck: could not open /tmp/amanda/amcheck.temp.1501: Permission denied permision on this folder is as follows. 1 drwx--S---2 amanda amanda 1024 Jul 10 09:27 . Are you sure you ran amcheck as user amanda? That temp file is built by amcheck itself (as compared to something amandad runs for it on the client, for instance). There is a test to make sure you're running amcheck as the Amanda user, but unfortunately it's after this temp file is created (which is a bug). Sendoro John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
supported libraries database?
Is there a section in the FAQ-O-Matic that I didn't see containing lists of tape libraries known to work (or known not to work) with Amanda? Something along the lines of the linuxprinting.org database of how well various models of printers work with linux (http://www.linuxprinting.org/printer_list.cgi). It could be done similarly to the tateptypes, with notes of which changer script was used, modifications needed, or whether it wouldn't work at all. I'm in the market for a new library, and I'd prefer to narrow my search to only those that are known to work well with Amanda, without having to post to the list every few days asking 'what about the foo.com model X?'. In the meantime, anyone have any recommendations for a 2 drive 20-40 slot AIT library? Thanks, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
amcheck bug(?)
Hello, amcheck is reporting an incorrect number of hosts checked for windows backups, though the backups themselves operate correctly. I am running amanda 2.4.2p1 on a linux redhat 7.0 system (streak). In addition to unix, I am also backing up windows servers. I have a test configuration called Test which I use to verify my client setups before I add them to the main system. My problem isn't whether backups succeed or fail. It is what amcheck -c Test reports. Currently, in my test disklist config, I have two entries for two hosts: # trask (Gabi's pc) streak //trask/d$ windows # pond (core server) streak //pond/c$ windows windows is the backup type and is defined in my amanda.conf file. Amcheck only reports: Amanda Backup Client Hosts Check Client check: 1 host checked in 1.482 seconds, 0 problems found (brought to you by Amanda 2.4.2p1) Why? or does it only check the client streak as shown in the disklist? if amcheck only shows the machine that smbclient is run on, should there be additional info showing that the actual connection to the windows hosts succeeeded? again, the backups themselves are running just fine. --jason -- ~~~ 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: upgrading from DAT to DLT
Hello, i'm sorry as this is definitely a newbie question, however, i don't have much experience with backup devices. I understand. I recommend you pick up the book unix backup and restore. this book also has a HUGE section on amanda. This is the same section online whose link can be found at http://www.amanda.org. i was recently appointed as UNIX admin here (no previous admins) and i began using my workstation with a 20/40 GB DAT drive as an amanda server to do simple network backups for a few of the mission-critical boxes (just to get something going). S, Thinking about giving that dat drive away? I probably can manage with one... :) however, now i'd like to get serious and plug in the PowerStor L200 drive (8 DLT Tapes) someone here bought over a year ago that's just been sitting around and start doing some real backup stuff. my question is, however, what would be the device name for the multi-tape changer under linux. will it remain /dev/[n]st0 or will it change to something else? Seriously, it depends. I assume both the new and old drives are scsi. if you plug in the new drive onto the scsi chain with the old one, /dev/[n]st0 will point to the drive with the lowest scsi id number. /dev/[n]st1 will point the higher scsi device id. If you replace the old drive entirely with the new one, (same id perhaps), then /dev/[n]st0 will point for certain at the new drive. the bootup messages, messages logfile, and dmesg will show you what device the kernel has assigned to your tape drives. Here's the output from my dmesg command: st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0 I would be tempted to put the new drive on the chain with the old one and set its scsi device id higher than the old one. this way you can still run backups on the old drive without changing your current configuration. After that, build an entirely new amanda configuration for the new drive. Remember the value of if it ain't broke, don't fix it. again, sorry this is so basic. This is not basic. it is a relatively painless process, however. After you install the new drive, spend some time testing it, including scripts to change to different tapes, what device settings turn off and on compression etc. does anyone else have an L200 that would possibly be willing to post their chg-multi settings (or not)? the tapetype settings for your particular tape cartridges should be pretty easy to find on the tapetype list in the faq-o-matic. I do hope someone here has that tape drive type for controlling the more advanced features of your drive. thanks in advance for any assistance. You are welcome. I hope this helps... Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799 [EMAIL PROTECTED] -- ~~~ 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: amcheck bug(?)
... does it only check the client streak as shown in the disklist? ... Yes, hence the count of one. Amanda on the server side doesn't distinguish between that machine doing itself (if it did that) or it reaching out to one or more PC's. if amcheck only shows the machine that smbclient is run on, should there be additional info showing that the actual connection to the windows hosts succeeeded? No news is good news :-). You'd see complaints if it had problems connecting to one of the PC's. If you're really concerned, look at the /tmp/amanda/selfcheck*debug file on the client. I'm not positive but I think it logs stuff about each smbclient call. --jason John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
2.5 chg-scsi now part of 2.4.2 CVS
For those of you mixing the 2.5 chg-scsi changer into your 2.4.2* Amanda build, the 2.5 chg-scsi code has been back-ported into the various 2.4.2 CVS branches. This means it will be in the next 2.4.2 based release (if there is one), and it also means that if you work from CVS you can build a 2.4.2 (stable) system with the newer chg-scsi in one step without messing around with the main (development) branch. As improvements are made to chg-scsi, all the branches will be updated with the same changes. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck bug(?)
Why? or does it only check the client streak as shown in the disklist? if amcheck only shows the machine that smbclient is run on, From amanda point of view, there is only one client: streak On streak you have two disks: \\pond\c$ and \\trask\d$ remember in disklist, first field is machine name and second is disk name. So you have only one machine. That this client is a bit special and access windows disks, is unknown from the server where you run the check. Olivier
RE: Amanda on RH7.1
How do I backup my Samba server running on Redhat 7.1 using
Amanda? There' s
a part in the INSTALL which mentions about inetd.conf. But
Redhat 7.1 don't
use inetd.conf, is there a problem?
Don't use Linux :) Why those people always want to do things diferently?
Well I think it is called xinetd.conf under Linux.
You are right. Modify the following to match your amanda user, amanda group
and the paths to server files and copy in appropriate files. Once done you
have to reinitialise xinetd (kill -SIGUSR1 xinetd PID)
Good Luck!
Srdjan
This goes in: /etc/xinetd.d/amanda
-- CUT HERE --
# default: on
#
# description: Part of the Amanda server package
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= operator
group = disk
server = /usr/local/libexec/amandad
}
-- CUT HERE --
This goes in: /etc/xinetd.d/amandaidx
-- CUT HERE --
# default: on
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= yes
user= operator
group = disk
server = /usr/local/libexec/amindexd
}
-- CUT HERE --
This goes in: /etc/xinetd.d/amidxtape
# default: on
#
# description: Part of the amanda server package
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= operator
group = disk
server = /usr/local/libexec/amidxtaped
}
-- CUT HERE --
Re: Problems backing up
I check the status as the process progresses and I found that one directory got dumped okay, but the next one hangs at 100.04% :-? Dn't worry about the 100.04 %, it just means that the estimate was a bit over optimistic. So when it comes to transfer real data, there are more than what it thought it should be. Or new data have been created since the estimate (for /etc, it is not uncommon that some system tables grow there all the time). Now do you have any message about the hang? What are you using as a firewall? Cobalt system? I would be quite catious on putting too much load on such a firewall (OK I have only 8 hours experience with such system :) I run back-up by GB without any trouble... Olivier
backing up to blockdevs?
I have this Jaz drive and a stack of 10 disks for it. I'd like to use this as my tape drive, and am wondering if amanda supports strange strategies like this. It's just my home network, so I'm quite willing to use code from experimental CVS branches. I'd rather not do something kludgey/hamstrung, like using the Jaz drive as a holding disk and /dev/null as the tape device, and purposefully letting backups fail. That just defeats the purpose of using amanda in the first place ;). But if there's even semi-working code that either causes the blockdev to look like a chardev (this would be sort of neat), or just uses the blockdev as the backup device natively, I'd love to give it a go. Thanks, Dan D. -- Dan Debertin [EMAIL PROTECTED] www.nodewarrior.org
