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
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
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.
--
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
* 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
[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
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,
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
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
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
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
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
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
[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
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
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
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
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.
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?
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:
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
* 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
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
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
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
...
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
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
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
28 matches
Mail list logo
