Stefan Noll wrote:
Paul Bijnens wrote:
Also interesting is the sendsize..debug file on the client.
Can you post that one?
Sorry it's about 220KBytes.
There are 100 different entries in the disklist for client neptun.
We had some offline conversation, and probably Stefan hit a bug
due to the lar
Hallo Paul,
thank you for your help.
I think, it would be good to document this at
http://www.amanda.org FAQ-O-Matic
Greetings
Stefan Noll
Paul Bijnens wrote:
Stefan Noll wrote:
Hallo from Germany,
OK.
I found the cause.
It is a bug that was solved only recently (dd. 14 april 2004):
http://cvs.sou
Stefan G. Weichinger wrote:
Hello, amanda-users,
-SNIP
MS Exchange seems to only be able to dump ONE BIG FAT dumpfile, from
which you can only recover ALL the server.
SNIP-
This is correct up to 5.5 and I think 2k.
The way the various windows backup software products get around this
Hi, Chris Lee,
on Donnerstag, 27. Mai 2004 at 12:46 you wrote to amanda-users:
CL> Stefan G. Weichinger wrote:
>> Hello, amanda-users,
>>
CL> -SNIP
>>
>> MS Exchange seems to only be able to dump ONE BIG FAT dumpfile, from
>> which you can only recover ALL the server.
>>
CL> SNIP--
Title: Problem backing up just a few machines
Hello all,
We currently have about 10 HP-UX 11 and 11i machines in our Amanda setup.
Our server is HP-UX 11i with Amanda version 2.4.4 installed on all clients
and server.
I have two systems (HP-UX 11) that give me issue about once a week. When
Henson, George Mr JMLFDC wrote:
logfun02 / lev 0 FAILED [Request to logfun02 timed out.]
Then the next day I had two hosts with the same error. In trying to fix the
issue I found if I removed the curinfo directories for these two hosts, the
backups would run the next time amdump was called. It is
Title: RE: Problem backing up just a few machines
> Henson, George Mr JMLFDC wrote:
>
> > logfun02 / lev 0 FAILED [Request to logfun02 timed out.]
> >
> > Then the next day I had two hosts with the same error. In
> > trying to fix the issue I found if I removed the curinfo directories
>
Hi, i install amanda on my computer, the backup is
run ok but when i try extract one file iin amrecover i have this
error:
[EMAIL PROTECTED] root]# amrecover DailyAMRECOVER Version 2.4.4p2. Contacting
server on tux2.employer.com.br ...220 tux2 AMANDA index server (2.4.4p2)
ready.200 Access
Henson, George Mr JMLFDC wrote:
> Increase etimeout. (probably)
Currently etimeout is 300. Should this be increased
Could be, but to find out how much, the sendsize.XXX.debug log helps a
lot. But see below.
planner: time 30.790: error result for host logfun02 disk /: Request to
logfun02 timed
Hello, Marcelo.
I suppose you must "be" in /backup and run amrecover from there if you want
to restore /backup files.
Regards,
Pipoli
>Hi, i install amanda on my computer, the backup is run ok but when i try
extract one file iin amrecover i have this error:
>Extracting files using tape drive /
Hello,
I got some "funny" problems using amrecover:
schatten:/etc# amrecover Weekly
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Work
Marcelo Leão Caffaro wrote:
Scanning /dumps/amanda...
tape01: skipping cruft directory, perhaps you should delete it.
tape02: skipping cruft directory, perhaps you should delete it.
Have been mixing up the holdingdisk and the file-driver virtual
tapes? What are the "tapeXX" directories doing in /d
Title: RE: Problem backing up just a few machines
> > planner: time 30.790: error result for host logfun02 disk
> > /: Request to logfun02 timed out.
> >
> >
> >
> > If I am reading the above messages correctly the timeout is
> > happening well within the etimeout window. And the 30 sec
Thorsten Bremer wrote:
schatten:/etc# amrecover Weekly
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
amr
The backup i run in a few minutes, first i run amcheck Daily, then i run
amdump Daily and the data is record in tape device, i check this in
amstatus, when i try restore one file i have this error.
[EMAIL PROTECTED] backup]# amrecover Daily
AMRECOVER Version 2.4.4p2. Contacting server on tux2.empl
Marcelo Leão Caffaro wrote:
The backup i run in a few minutes, first i run amcheck Daily, then i run
amdump Daily and the data is record in tape device, i check this in
amstatus, when i try restore one file i have this error.
You did rewind the tape, did you?
See the debug below
amrecover: debug 1
Moin Paul,
> Your localhost is actually called "schatten", and I guess that a
> dns lookup of "schatten" does not result in "localhost", nor in 127.0.0.1.
Hmm... you're right :-)
> Don't use "localhost" in disklist. It will bit you.
> If you don't believe me, just just got bitten...
OK, I begi
Thorsten Bremer wrote:
schatten:~# amrecover Weekly -s schatten.magnus
AMRECOVER Version 2.4.2p2. Contacting server on schatten.magnus ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date
This is my debug file amindexd debug
amindexd: debug 1 pid 12952 ruid 502 euid 502: start at Thu May 27 08:02:00
2004
amindexd: version 2.4.4p2
amindexd: time 0.000: < 220 tux2 AMANDA index server (2.4.4p2) ready.
amindexd: time 0.020: > SECURITY USER root
amindexd: time 0.021: bsd security: r
Hello,
I have been using amanda for nearly two years now. Most things seem pretty
easy to figure out... At least if you like source code and cscope... :)
I currently am running amanda-2.4.4p2 on both server and client, the server
being a redhat 7.x system.
The client is a recently added solar
[EMAIL PROTECTED] wrote:
Its /, /bybee1, and /var filesystems are using ufs. The filesystems
/bybee[2..10] are using vxfs. Amanda can back them up ok, but if I
mount their snapshots separately then try to backup the snapshots,
Amanda gets if fstype from the /etc/vfstab file, or defaults to
the DUMP
Problem found and fixed!
The problem was that when I ran amcheck (and amdump) manually it worked to a
client machine, but when run from crontab it failed.
The problem was caused when we upgraded our main server, which is the tape
server, to a new machine. As part of this upgrade, we gave the ol
Actually, I don't have those entries in /etc/vfstab. I will give that a
try.
For future reference, in order to handle transient filesystems such as this,
it might be better off evaluating the output of "mount" rather than the
filesystem table. Except I can't remember if it gives FS info.
Than
23 matches
Mail list logo