dump failed: Request to callisto timed out.
Hi,
It looks like I have the same problem as Rob Flory (unfortunately I couldn't
extract his email address from the Amanda archives at Yahoo).
I use Amanda to backup 3 machines on my local network: callisto (PPC, Amanda
server, with DDS1 tape drive), cassandra (m68k) and leia (AXP). All of them are
running Debian Linux.
I'm no longer able to backup callisto. It always fails with:
| FAILURE AND STRANGE DUMP SUMMARY:
| callisto sda8 lev 0 FAILED [Request to callisto timed out.]
| callisto sda5 lev 0 FAILED [Request to callisto timed out.]
| callisto sda1 lev 0 FAILED [Request to callisto timed out.]
| callisto sdb8 lev 0 FAILED [Request to callisto timed out.]
| callisto sdb7 lev 0 FAILED [Request to callisto timed out.]
| callisto sdb6 lev 0 FAILED [Request to callisto timed out.]
| callisto sdb5 lev 0 FAILED [Request to callisto timed out.]
| callisto sdb1 lev 0 FAILED [Request to callisto timed out.]
The other machines can be backed up fine.
Amcheck doesn't show any errors (except for the missing tape when I ran the
check):
| Amanda Tape Server Host Check
| -
| WARNING: /amanda: only 307732 KB free (656384 KB requested).
| ERROR: /dev/nst0: rewinding tape: No medium found.
|(expecting tape DAILY08 or a new tape)
| NOTE: skipping tape-writable test.
| Server check took 30.114 seconds.
|
| Amanda Backup Client Hosts Check
|
| Client check: 3 hosts checked in 2.381 seconds, 0 problems found.
|
| (brought to you by Amanda 2.4.1p1)
I've been using Amanda to backup my machines since more than 2 years.
First I thought the problem could be related to a problem with the network
configuration (A while ago leia (my firewall machine) had hardware problems so
I reconfigured callisto to connect directly to the outside world. When leia was
resurrected, I reverted to the old situation), but
- /etc/resolv.conf is the same on all machines
- /etc/hosts is the same on all machines (127.0.0.1 localhost only)
- /etc/hosts.* is the same on all machines
- all machines have valid forward and reverse DNS entries (leia is the local
DNS server)
- callisto:/etc/inetd.conf has
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
- {cassandra,leia}:/etc/inetd.conf has
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad
- all machines are running amanda 2.4.1p1-12 from Debian.
- all machines have in /var/backup/.amandahosts:
callisto.of.borgbackup
Anyone with a clue?
_Many_ thanks in advance!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: amdump error
Hello,
First thing this morning:
The problem repeated itself. I even copied the configuration to a test configuration
and amdump ran just fine.
1500:
I just ran amdump by hand and got a good backup while at a doctor's office. I had
changed one thing: I commented out of my disk list all
entries with the following dumptype used:
define dumptype nocomp-root-incr {
nocomp-root
comment incremental only
skip-full
}
Is there anything obviously wrong about this?
2335:
Wait! the cron job just failed! Yikes!
Is there any chance the run from the night before hasn't finished?
There are no leftover processes, and amcleanup run as my amanda user shows nothing to
recover from
[streak : bv-amanda]$ amcleanup Daily
amcleanup: no unprocessed logfile to clean up.
Scanning /amanda1...
lost+found: skipping cruft directory, perhaps you should delete it.
[streak : bv-amanda]$
I am running amanda version 2.4.2p1 on both server and all clients. The server is a
redhat linux 7.0 machine running a distclean compile of
kernel 2.2.19 (not redhat's version). I have not patched amanda with anything (yet),
but the fstab issues I mentioned in a previous post,
do not exist here. (that is, I have removed the label scheme used in redhat 7.0's
/etc/fstab).
I am running linux's version of dump, although that's irrelevant here.
Was the machine possibly rebooted while the previous run was still
going and amcleanup was not run during the boot sequence?
It was rebooted several times during the day (the day after the first failure), but no
amanda sequences were being run at the time. I have
also updated my rc.local with the following script exerpt:
echo cleaning up any amanda dumps left in the lurch...
for i in `ls /usr/local/etc/amanda |grep -v ^lbl`
do
echo $i
su -l bv-amanda -c /usr/local/sbin/amcleanup ${i}
done
If the above ideas don't help, you could add a couple of lines to the
script right before it exits:
ls -l $errfile $logdir/log 12
ps -fu AMANDA 12
Here's the ouput, but it just worked when I ran amdump by hand as my amanda user. the
cron entry is in my amanda user's crontab...
start jason's debug
ls: /var/amanda/DailySet1/amdump: No such file or directory
ls: /var/amanda/DailySet1/log: No such file or directory
UIDPID PPID C STIME TTY TIME CMD
1160021886 21885 0 Apr30 pts/000:00:00 -bash
11600 2050 2049 0 11:36 pts/300:00:00 -bash
11600 2805 2050 0 11:46 pts/300:00:00 sh /usr/local/sbin/amdump Daily
11600 2810 2805 0 11:46 pts/300:00:00 ps -fu bv-amanda
I guess I will see what happens tonight...
--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: dump failed: Request to callisto timed out.
On May 3, 2001, Geert Uytterhoeven [EMAIL PROTECTED] wrote:
| callisto sda8 lev 0 FAILED [Request to callisto timed out.]
The other machines can be backed up fine.
See how long the estimation took in /tmp/amanda/sendsize.debug* on the
client, then bump etimeout up accordingly.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
possibillity to verify a backup?
Hi there, after a period successfully using amanda on our lan, I think about the possibillity to verify the contents on an amanda tape (before removing the files from holding disk). From my point of view: Making backups is necessary, but how to enshure that the data would be read from the tape once a data loss on any client? Exist there a regular way to make a veryfy. If not, exist there any plan to implement one? bye mike
Re: Estimate request timed out - FAILED QUEUE - planner: FAILED
* John R. Jackson [EMAIL PROTECTED] (Wed, May 02, 2001 at 03:52:46PM -0500)
sendsize: debug 1 pid 377632 ruid 5 euid 5 start time Fri Apr 13 20:45:54 2001
...
sendsize: pid 377632 finish time Sat Apr 14 01:39:08 2001
Notice the duration was almost three hours. Amanda gave it 60 minutes
(two disks times 30 minutes per disk). It didn't answer within that
period, so Amanda thought it was dead.
You need to crank up etimeout in amanda.conf.
Or you need to use the modified sendsize that uses calcsize to calculate
the sizes ..
calcsize can do estimates at about 500G per hour (and that's full dump,
incremantal current level and incremental next level).
Tar does about 150G per hour, but that's only for one level .. so it has to
do it 3 times.
So doing 500G estimate with tar takes well over 9 hours.
with calcsize it's done in an hour ..
Attached my modified sendsize.c
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
/*
* Amanda, The Advanced Maryland Automatic Network Disk Archiver
* Copyright (c) 1991-1998 University of Maryland at College Park
* All Rights Reserved.
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that
* copyright notice and this permission notice appear in supporting
* documentation, and that the name of U.M. not be used in advertising or
* publicity pertaining to distribution of the software without specific,
* written prior permission. U.M. makes no representations about the
* suitability of this software for any purpose. It is provided as is
* without express or implied warranty.
*
* U.M. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL U.M.
* BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Authors: the Amanda Development Team. Its members are listed in a
* file named AUTHORS, in the root directory of this distribution.
*/
/*
* $Id: sendsize.c,v 1.97.2.13 2000/10/11 02:08:26 martinea Exp $
*
* send estimated backup sizes using dump
*/
#include amanda.h
#include pipespawn.h
#include amandates.h
#include getfsent.h
#include version.h
#ifdef SAMBA_CLIENT
#include findpass.h
#endif
#ifdef HAVE_SETPGID
# define SETPGRP setpgid(getpid(), getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgid(%ld,%ld) failed: %s\n, \
(long)getpid(), (long)getpid(), strerror(errno)));\
} while(0)
#else /* () line 0 */
#if defined(SETPGRP_VOID)
# define SETPGRP setpgrp()
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp() failed: %s\n, strerror(errno))); \
} while(0)
#else
# define SETPGRP setpgrp(0, getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp(0,%ld) failed: %s\n,\
(long)getpid(), strerror(errno)));\
} while(0)
#endif
#endif
typedef struct level_estimates_s {
time_t dumpsince;
int estsize;
int needestimate;
} level_estimate_t;
typedef struct disk_estimates_s {
struct disk_estimates_s *next;
char *amname;
char *dirname;
char *exclude;
char *program;
int spindle;
level_estimate_t est[DUMP_LEVELS];
} disk_estimates_t;
disk_estimates_t *est_list;
#define MAXMAXDUMPS 16
int maxdumps = 1, dumpsrunning = 0;
char *host; /* my hostname from the server */
/* local functions */
int main P((int argc, char **argv));
void add_diskest P((char *disk, int level, char *exclude, int spindle, char *prog));
void calc_estimates P((disk_estimates_t *est));
void free_estimates P((disk_estimates_t
Re: possibillity to verify a backup?
[EMAIL PROTECTED] writes: Hi there, after a period successfully using amanda on our lan, I think about the possibillity to verify the contents on an amanda tape (before removing the files from holding disk). From my point of view: Making backups is necessary, but how to enshure that the data would be read from the tape once a data loss on any client? Exist there a regular way to make a veryfy. If not, exist there any plan to implement one? bye mike amverify? (But afaik it reads back the tape only)
Re: Setting up Sun L280
Thanks once again for your help John. You provided plenty of food for thought. On Wed, 2 May 2001, John R. Jackson wrote: So far I have tried the following : - built and installed sst form the 2.4.2p2 source. I have a /dev/rsst1 and running sstest '/dev/rsst1 rew' I get 'Device rewound, status = 0x0'. ... You tried to rewind a tape changer? I'm surprised it didn't stick its tongue out at you and drop all the tapes on the floor. :-) I should have been paying a bit more attention ;) You might grab: ftp://gandalf.cc.purdue.edu/pub/amanda/atl_op Got it. That's a little test program I use to exercise my ATL robot through the sst interface. After you chmod +x it, try these things: atl_op -h # to see the help message atl_op -f /dev/rsst1 -v inquiry But there are other problems you need to look at first ... - I have built the latest mtx from sourceforge : # mtx -f /dev/rsst1 inquiry Product Type: Disk Drive Ummm, that would seem to be a very bad thing. You're talking to a disk drive, not your changer. :-) That, in turn, implies /dev/rsst1 is not pointing where you want it to. Were any other /dev/rsst* devices created? What does rsst1 point to? Only /dev/rsst1 was created which as you say points to the drive not the changer. I tried to change the sst.conf file as follows : name=sst parent=/pci@1f,2000/scsi@1/sst@1,0:character target=1 lun=0;A but this caused a kernel panic ! I created the link by hand : ln -s ../devices/pci@1f,2000/scsi@1/sst@1,0:character rsst2 and now I can : # ./atl_op -f /dev/rsst2 inquiry atl_op: device typeCHANGER atl_op: removeable atl_op: vendor HP atl_op: productC6280-7000 atl_op: revision_level 2.10 but still get : # ./mtx -f /dev/rsst2 status mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=0 (Unknown?!) mtx: Request Sense: Sense Key=No Sense mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 00 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no READ ELEMENT STATUS Command Failed but doing an inquiry produces the same results as atl_op and inventory causes some changer activity but nothing to stdin. The following gets logged to /var/adm/messages : unix: WARNING: /pci@1f,2000/scsi@1/sst@1,0 (sst2) Error for Command: undecoded cmd 0xb8Error Level: Fatal unix: Requested Block: 0 Error Block: 0 unix: Vendor: HP Serial Number: 99255B9697 unix: Sense Key: Illegal Request unix: ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 What do you get if you do this: find /devices -name 'sst*' # find /devices -name 'sst*' /devices/pci@1f,4000/scsi@3/sst@1,0:character /devices/pci@1f,2000/scsi@1/sst@1,0:character The top one is an internal disk drive (I think) and the bottom one is the changer. What did the system reboot say (e.g. /var/adm/messages) when it scanned the devices, in particular about your changer or the sst devices? unix: sst0:found Direct Access device at tgt1, lun0 unix: sst0:Vendor/Product ID = IBM DDRS34560SUN4.2G unix: sst0 at glm0: unix: target 1 lun 0 unix: sst0 is /pci@1f,4000/scsi@3/sst@1,0 unix: sst1:No response from target 1, lun 0 unix: sst2:found Changer device at tgt1, lun0 unix: sst2:Vendor/Product ID = HP C6280-7000 unix: sst2 at glm2: unix: target 1 lun unix: sst2 is /pci@1f,2000/scsi@1/sst@1,0 unix: sst3:No response from target 1, lun 0 What do I need to do ?? Thanks once again John. Cheers, Adam.
Re: Re: possibillity to verify a backup?
Hi there, after a period successfully using amanda on our lan, I think about the possibillity to verify the contents on an amanda tape (before removing the files from holding disk). From my point of view: Making backups is necessary, but how to enshure that the data would be read from the tape once a data loss on any client? Exist there a regular way to make a veryfy. If not, exist there any plan to implement one? bye mike amverify? (But afaik it reads back the tape only) It could be a solution. But amverify runs amrestore on each file on the tape, pipes the output to the appropriate restore program and discard all than the return codes. Therefore it reports only the readability of an amanda tape. I think if the verify contains a binary comparison on each file in the archive, it will be more secure. bye mike
Re: Problem with device sg*
Hi! Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: QUANTUM Model: DLT8000 Rev: 0119 Type: Sequential-AccessANSI SCSI revision: 02 Here's a thought. Are you sure everything on that bus is wide SCSI? yes, i'm shure, because the system was running before i installed a new scsi hard drive. BYe Juergen -- Dies ist eine Microsoft freie Mail!
Re: IPSec for safety?
Hello, I am not using IPsec but there is a way to use tar and gpg to encrypt the data. Check out http://security.uchicago.edu/tools/gpg-amanda/ for instructions. I use this system and it works great. I have not had any problems restoring data. Hope this helps. Andrew Hall On Wed, 2 May 2001, Charles Sprickman wrote: Hi, I looked at amanda some time ago, and everything looked really great except for lack of encryption/authentication (who wants their password files flying unencrypted all over the network?)... I'm discounting Kerberos, as that is another project to set up. One thing that has changed is that IPSec now ships on FreeBSD... That seems to solve both problems. Anyone doing this? Everything work as expected? Any hints? Thanks, Charles | Charles Sprickman | Internet Channel | INCH System Administration Team| (212)243-5200 | [EMAIL PROTECTED] | [EMAIL PROTECTED]
Re: Problem with device sg*
On Thu, 3 May 2001, Juergen Knott wrote: Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: QUANTUM Model: DLT8000 Rev: 0119 Type: Sequential-AccessANSI SCSI revision: 02 Here's a thought. Are you sure everything on that bus is wide SCSI? yes, i'm shure, because the system was running before i installed a new scsi hard drive. Are both the first and second harddisks (at SCSI ID 0 and 1) wide SCSI ?? Narrow devices don't have the 4th address line and thus can't see the difference between for instance ID 1 (0001) and 9 (1001). So if your first SCSI disk (sda at SCSI ID=0) is a narrow device, it will (try to) respond to all commands addressed to device 8. If the rest of the SCSI bus is the same as in your original email, I would suggest setting the ID of the tapedrive to 6 and the tape changer to 14 (or vice versa). -- Tot ziens, Bart-Jan
setting up multi configurations
hello, I'm configuring my tape server to run different configurations (e.g., daily backups and periodic archival runs on the same filesystems, plus different configurations on separate filesystems) The FAQ says to set the record no option for archival runs : I guess it has no effect on the amrecover features and capabilities, provided that the index yes option is set in each configurations. True or false?! Would you also recommend to separate the indexdir infofile directories for each configurations, or should I leave them into the same subdirectories ? thanks Pierre.
Amanda amdump mail report question
Hello Amanda Users, I've looked in the FAQ-O-MATIC but can't find the explaination for the following. [Report below was mostly deleted] In the following report the second entry is abriviated, I believe that I read in the amanda-user's mailing list that this was just because of field width and that all was well. I'm just trying to confirm that. Also - I believe that I'd read that there was a formatting variable that I could change to shift the display - something that I'd now find useful with some of the larger disk drives (partitions in the 10s of gigabytes) where the display fields are running together. Was that field variable in the code or an environmental variable or ??? Are there instructions handy on how to reset it ? Thanks, Brian DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- -- knick /dev/root 1 2269 288 12.71:134.00:02 140.0 knick -sr/local/view 1 124 32 25.80:103.20:02 29.5 (brought to you by Amanda version 2.4.1p1) - End of forwarded message from Super-User - Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Amanda amdump mail report question
[EMAIL PROTECTED] (Brian Cuttler) writes: Also - I believe that I'd read that there was a formatting variable that I could change to shift the display - something that I'd now find useful with some of the larger disk drives (partitions in the 10s of gigabytes) where the display fields are running together. Was that field variable in the code or an environmental variable or ??? It's in amanda.conf Are there instructions handy on how to reset it ? man amanda Look for columnspec Jens Bech Madsen -- Jens Bech Madsen The Stibo Group, Denmark
Re: setting up multi configurations
On May 3, 2001, Pierre Volcke [EMAIL PROTECTED] wrote:
The FAQ says to set the record no option for archival runs :
I guess it has no effect on the amrecover features and
capabilities, provided that the index yes option is set
in each configurations. True or false?!
True.
Would you also recommend to separate the indexdir infofile
directories for each configurations, or should I leave them
into the same subdirectories ?
If it's really a separate archive configuration (with record no),
better keep them separate, just for sanity. Some people that use a
full-only record-yes configuration for archiving and full backups, and
an incremental-only configuration for incrementals, should generally
keep them together.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Amanda amdump mail report question
On May 3, 2001, [EMAIL PROTECTED] (Brian Cuttler) wrote:
In the following report the second entry is abriviated, I believe that
I read in the amanda-user's mailing list that this was just because of
field width and that all was well.
That's correct.
Also - I believe that I'd read that there was a formatting variable
that I could change to shift the display - something that I'd now find
useful with some of the larger disk drives (partitions in the 10s of
gigabytes) where the display fields are running together. Was that
field variable in the code or an environmental variable or ???
It's columnspec in amanda.conf.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Segmentation Fault at getservbyname
Well, I've almost got Amanda working, but I'm haning problems. Here's the system setup: Solaris 7 11/99 NIS+ EXB-220 (I've modified scsi-changer-driver.c to handle it) Exabyte Mammoth 2 tape drive (same as above) compiled Amanda 2.4.2p2 with gcc Here's where I am: For now I am only trying to backup one disk on the host. I've got Amanda talking to the library and the tape drives, and all seems well there. I've got the Amanda background tasks working, and all seems well there. Here's the problem: The estimate planner is not working. I get a segmentation fault when trying to run the planner (I had to experiment to find the problem). The problem is in one of the calls to getservbyname in planner.c (it doesn't really matter which). I've tried various versions of gcc, but get the fault every time. I've tried the Sun cc compiler and I don't get the fault, the planner appears to be working. My problem is this, I don't have access to the Sun cc compiler on all my systems. How do I get around this segmentation fault, when using the gcc compiler? Has anyone else had this problem? Is there a solution? I am going to continue on using the Sun cc compiler, but I eventually will need to be able to use the gcc compiler. I hope someone will point me in the right direction. -- [EMAIL PROTECTED] LAN Engineer/Administrator RS Information Systems, Inc. (405)366-6545 ext. 3249 begin:vcard n:Cole;Russell tel;fax:(405)366-2961 tel;work:(405)366-6545 ext.3221 x-mozilla-html:FALSE url:http://www.noaa.gov org:RS Information Systems, Inc.;Engineering - Software adr:;;3200 Marshall Avenue, Suite 100;Norman;OK;73072;USA version:2.1 email;internet:[EMAIL PROTECTED] title:LAN Engineer/Administrator fn:Russell C. Cole end:vcard
trouble (?) with amrecover
hello again, I'm trying to am-recover some datas, and I get the following problem when I run amrecover : [tape-server]$ amrecover -C conf -s tape-server amrecover sethost backup-client amrecover setdisk /the/disk Scanning /the/holdingdisk ... 20010328: found Amanda directory. (*) 20010416: found Amanda directory. 200 Disk set to /the/disk amrecover ls (*) these directories are empty. problem: the 'ls' command only shows me a very small part of what is supposed to be backed up, I mean only a few directories files out of hundreds. more details: - the directories files that are shown do not seem to have something special or common attributes. - amanda report didn't show anything wrong, it even shows a good full backup yesterday. - problem is the same if I run amrecover from the backup client - the backup server also backs up some disks that it owns; I get no trouble when using amrecover on these disks. - I think that the 'hidden' files are indeed on the tape: the gnutar-lists on the client do show them fully, and the following command : [tape-server]$ ./amadmin conf info backup-client /the/disk Dumps: lev datestmp tape file origK compK secs 0 20010502 TAPE4 4 2172930 2172960 1666 1 20010503 TAPE5 3 24980 24992 20 ... shows well-filled tape for level 0. So, why is amrecover hiding files? thanks, Pierre.
Re: Estimate request timed out - FAILED QUEUE - planner: FAILED
Or you need to use the modified sendsize that uses calcsize to calculate the sizes .. calcsize can do estimates at about 500G per hour (and that's full dump, incremantal current level and incremental next level). Gerhard, what is calcsize? Is it a part of Amanda?
[amrestore] file too large
hello, I get the following message when restoring one of my full dumps with amrestore: [tape-serveur]# /usr/local/amanda/sbin/amrestore /dev/nst0 planeto amrestore: 0: skipping start of tape: date 20010502 label TAPE4 amrestore: 1: skipping jupiter._home_zone1.20010502.2 amrestore: 2: skipping jupiter._home_zone2.20010502.1 amrestore: 3: skipping jupiter._home_zone3.20010502.0 amrestore: 4: restoring planeto._home_zone10.20010502.0 amrestore: write error: File too large The target disk is big enough to handle the whole taped archive. According to the mail reports, the amount of datas saved on this tape is 17.8Gb. I use 20Gb/40Gb DLT Tapes. Could it be a problem with my tapetype config or with the tape hardware itself? Of course, a tar xvf on this archive will fail at the end of file: [tape-server]#cat planeto._home_zone10.20010502.0 | tar xvf - ... tar: 511 garbage bytes ignored at end of archive tar: Unexpected EOF in archive tar: Error exit delayed from previous errors ... any advice? thanks! Pierre.
Re: amlabel not seeing tape
The below got amlabel working, thanks. I'm not done, but i'm making progress. I'll post another question if i get stuck. I didn't realize when i started on the Amanda install that i could just use nfs to mount my second PC, and back up both my PCs at once with tar. Any reason not to do it this way, besides the security issue of having to load nfsd on my internet-connected PC? thx alot, george herson John R. Jackson wrote: (/usr/adm/amanda/changer-status-clean: No such file or directory): The Amanda changers now want to store three state files. All the file names are based on the changerfile variable in your amanda.conf. My guess is you have not set that variable, it's defaulting to /usr/adm/amanda/changer and directory /usr/adm/amanda does not exist. This is not your fault -- I think some new ideas slipped in without fully comprehending their impact. Sorry. Try setting changerfile to someplace Amanda can write, such as the directory that holds your tapelist file. Make sure the name ends in /changer because the other names add a suffix on to that. For instance, if tapelist is in directory /usr/local/etc/amanda/xxx, add this to amanda.conf: changerfile /usr/local/etc/amanda/xxx/changer This will cause these files to be created: /usr/local/etc/amanda/xxx/changer-clean /usr/local/etc/amanda/xxx/changer-access /usr/local/etc/amanda/xxx/changer-slot Or you can pick some other directory. Just as long as the Amanda user has write access to it. george herson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Estimate request timed out - FAILED QUEUE - planner: FAILED
* Bernhard R. Erdmann [EMAIL PROTECTED] (Thu, May 03, 2001 at 07:34:01PM +0200) Or you need to use the modified sendsize that uses calcsize to calculate the sizes .. calcsize can do estimates at about 500G per hour (and that's full dump, incremantal current level and incremental next level). Gerhard, what is calcsize? Is it a part of Amanda? calcsize is amandas alternative way of calculating dumpestimates. Im not sure what the status of it is (I think it's no longer officially supported) but it rules. John, Alexandre Is there any chance of getting calcsize actively supprted in 2.5 ? With a configure option to determine whether you want to: - always use dump/tar - use dump for dump estimates, calcsize for tar estimates - use tar for tar estimates, calcsize for dump estimates - always use calcsize Im using calcsize for a couple of months (half a year ? longer ?) and never had any problem with it (Solaris ufsdump and tar, linux tar only). SGI's xfsdump is incredibly fast, so Im using that iso calcsize. I only have one SunOS box, and that has so little disk to backup taht calcsize would be a few minutes faster than dump so I didn;t bother with that. I did some extensive testign way back when, and found that calcsize wa within 1% of the estimates given by ufsdump/tar (on quiet filesystems) on busy filesystems the difference between calcsizes estimate and dump was the same as ebtween two succesive dumpestimates. The moment a ufsdump/tar estimate takes more than 3 hours, the estimated size will not refelct the actual size anyway. Currently listening to: the hum of my computer Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: [amrestore] file too large
On May 3, 2001, Pierre Volcke [EMAIL PROTECTED] wrote:
amrestore: 4: restoring planeto._home_zone10.20010502.0
amrestore: write error: File too large
You seem to be bumping into file size limits of the host filesystem.
You may want to pipe the output of amrestore -p directly to tar, or to
bsplit.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
RE: [amrestore] file too large
Perhaps your operating system cannot handle files over 2Gb? Most Linuxes can't. I don't know about *BSD or Solaris/SunOS. -Original Message- From: Pierre Volcke [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 3:01 PM To: [EMAIL PROTECTED] Subject: [amrestore] file too large hello, I get the following message when restoring one of my full dumps with amrestore: [tape-serveur]# /usr/local/amanda/sbin/amrestore /dev/nst0 planeto amrestore: 0: skipping start of tape: date 20010502 label TAPE4 amrestore: 1: skipping jupiter._home_zone1.20010502.2 amrestore: 2: skipping jupiter._home_zone2.20010502.1 amrestore: 3: skipping jupiter._home_zone3.20010502.0 amrestore: 4: restoring planeto._home_zone10.20010502.0 amrestore: write error: File too large The target disk is big enough to handle the whole taped archive. According to the mail reports, the amount of datas saved on this tape is 17.8Gb. I use 20Gb/40Gb DLT Tapes. Could it be a problem with my tapetype config or with the tape hardware itself? Of course, a tar xvf on this archive will fail at the end of file: [tape-server]#cat planeto._home_zone10.20010502.0 | tar xvf - ... tar: 511 garbage bytes ignored at end of archive tar: Unexpected EOF in archive tar: Error exit delayed from previous errors ... any advice? thanks! Pierre.
Re: Setting up Sun L280
So, if I understand correctly, /dev/rsst2 is now correctly pointing at the proper device and works when doing a simply inquiry, both from atl_op and mtx. But doing other things with mtx does not work. My guess, then, is that you need to post to the mtx mailing list (see the instructions on the mtx project page at www.sourceforge.net), tell them what version you're using and ask what's going on and how to debug it. FWIW, I've got pretty much the latest mtx and cannot get it to work on my Solaris system, either, although I think the symptoms are different. But it is reportedly supposed to work on Solaris, so the developers probably just need to work with you (and me, for that matter) a bit to find out what's wrong. Adam. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Segmentation Fault at getservbyname
... compiled Amanda 2.4.2p2 with gcc ... I get a segmentation fault when trying to run the planner (I had to experiment to find the problem). The problem is in one of the calls to getservbyname in planner.c (it doesn't really matter which). I've tried various versions of gcc, but get the fault every time. Were all the versions of gcc built for the version of the OS you're running? Gcc is notorious for being picky about that. For instance, running gcc built for Solaris 2.5 may not work when building binaries for 2.6. You can tell what version of gcc you used and what OS it was built for with gcc -v. Did you remove config.cache between each attempted rebuild? Are you sure you used the newly built planner and didn't accidentally get one built with a previous compiler? About the only other idea I have is to set up ./configure to not optimize (i.e. do not use -O with gcc). That's always the first guess at a compiler problem. This won't matter too much to Amanda because it (at least the actual Amanda parts) are not CPU bound. My problem is this, I don't have access to the Sun cc compiler on all my systems. How about building Amanda on one of them and pushing the binaries? An easy way to do this is use --prefix on ./configure so Amanda gets put into its own separate area, e.g. /opt/amanda-2.4.2p2 (or whatever). [EMAIL PROTECTED] John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: trouble (?) with amrecover
Scanning /the/holdingdisk ... 20010328: found Amanda directory. (*) 20010416: found Amanda directory. ... (*) these directories are empty. Just for my own curiosity, why are they still there if they are empty? the 'ls' command only shows me a very small part of what is supposed to be backed up, I mean only a few directories files out of hundreds. I take it you're using GNU tar? What version? If it's older than 1.13.17 (even better, 1.13.19), the index files may be corrupt. Go to your index directory and look at one of the files. If each line has a very large number on it, that's a symptom of a broken tar. Pierre. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Breece Hill Q2.15 tape changer
I'm attempting to get a Breece Hill Q2.15 (with DLT7000 drives) tape changer working with amanda (under Linux). I've noted in the docs that it has been configured to work with chg-scsi. To assist me in getting it up and running (I have amanda working for several machines writing to a single VXA tape drive currently), has anyone out there already accomplished a successful configuration of amanda to work with the Q2.15? If so, would you mind sending me the changer config and amanda config you're using. I'd greatly appreciate it! It would be a great starting point. Thanks and regards, -- PG.. Philip Greer Visa DPS [EMAIL PROTECTED] WK:303-486-7443 CL:303-638-5991 PG:303-206-3534 E-PG:[EMAIL PROTECTED] Your mouse cursor has moved. You must reboot for changes to take affect.
