On Mon, Jan 14, 2002 at 10:53:29AM -0500, Pedro Aguayo wrote:
Could be that your holding disk space is to small, or you trying to backup a
file that is larger than 2 gigs?
Perhaps I misunderstand something here, but...
The holding disk afaik holds the entire dump of the filesystem you try
and
Hi everyone,
Amanda cans make backups for a directory or only file systems?
For example backup /export/home/amanda
Thanks
---
Javier Fernández Pérez
Servicio de Informática Corporativa
D.G. de Telecomunicaciones y
hi everyone again,
Does anybody know how can i use gnu tar to make incremental backups?
Is it posible?
Thanks.
---
Javier Fernández Pérez
Servicio de Informática Corporativa
D.G. de Telecomunicaciones y Transportes
On 15 Jan 2002 at 1:22pm, [EMAIL PROTECTED] wrote
Amanda cans make backups for a directory or only file systems?
For example backup /export/home/amanda
If you use dump as your backup program, then it can only do file systems.
If you use tar, then you can do directories.
--
Joshua
On Mon, 14 Jan 2002 at 8:51pm, Gene Heskett wrote
Humm, what I see is that you are using linux dump, specifically
built for the ext2 filesystem, on a XFS filesystem? Donnbesilly.
No. Amanda checks the fstab for filesystem type, and uses the appropriate
dump tool for each filesystem (given
On 15 Jan 2002 at 1:43pm, [EMAIL PROTECTED] wrote
Does anybody know how can i use gnu tar to make incremental backups?
Is it posible?
Just tell amanda to use 'program GNUTAR' in your dumptype. amanda will
take care of the rest.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Hello Everyone,
I have about 60 MS clients that AMANDA backs up. I had trouble figuring out
the best way to offer individual/small file recovery to the users until a
friend suggested that I install apache on the AMANDA server and do recovery
thru the web.
The apache web server has a
[EMAIL PROTECTED] wrote:
Hi everyone,
Amanda cans make backups for a directory or only file systems?
For example backup /export/home/amanda
It depends on the backup program selected. GNUTAR will backup starting
from any directory, while dump can only backup a complete filesystem.
DTS
[EMAIL PROTECTED] wrote:
hi everyone again,
Does anybody know how can i use gnu tar to make incremental backups?
Is it posible?
In the amanda.conf file there is a section called 'dumptype'. All the
different kind of dumps are defined. GNUTAR dumps usually have names
that include
On Tue, 15 Jan 2002, Joshua Baker-LePain wrote:
On 15 Jan 2002 at 1:22pm, [EMAIL PROTECTED] wrote
Amanda cans make backups for a directory or only file systems?
For example backup /export/home/amanda
If you use dump as your backup program, then it can only do file systems.
If you
On Tue, 15 Jan 2002 at 2:36pm, Matteo Centonza wrote
On Tue, 15 Jan 2002, Joshua Baker-LePain wrote:
Hmm, if I remember correctly, i've made subtree dump in the past with
amanda. BTW there's that's from ext2fs dump manpage:
*snip*
so it's possible (with some restrictions e.g. only
I'm here again,
When i execute amdump, the backup fails
FAILURE AND STRANGE DUMP SUMMARY:
sc01us0105 /software/amanda/share/ lev 0 FAILED [disk /software/amanda/share/offline
on sc01us0105?]
frostis.cf /export/home/setup/freeware/amanda-2.4.2p2/ lev 0 FAILED [disk
On Tue, 15 Jan 2002, Joshua Baker-LePain wrote:
On Tue, 15 Jan 2002 at 2:36pm, Matteo Centonza wrote
On Tue, 15 Jan 2002, Joshua Baker-LePain wrote:
Hmm, if I remember correctly, i've made subtree dump in the past with
amanda. BTW there's that's from ext2fs dump manpage:
*snip*
On 15 Jan 2002 at 2:47pm, [EMAIL PROTECTED] wrote
FAILURE AND STRANGE DUMP SUMMARY:
sc01us0105 /software/amanda/share/ lev 0 FAILED [disk
/software/amanda/share/offline on sc01us0105?]
frostis.cf /export/home/setup/freeware/amanda-2.4.2p2/ lev 0 FAILED [disk
That's a great Idea, I'm going to save this one.
But, I think Edwin doesn't have this problem, meaning he says he doesn't
have a file larger than 2gb.
Could be hidden, or maybe you mounted over a directory that had a huge file,
just digging here.
Pedro
-Original Message-
From: [EMAIL
On Tue, Jan 15, 2002 at 09:14:33AM -0500, Pedro Aguayo wrote:
But, I think Edwin doesn't have this problem, meaning he says he doesn't
have a file larger than 2gb.
I had none, either, but the filesystem was dumped into a file as a
whole, leading to a huge file, same with tar. The problem only
Ahh! I see said the blind man.
Pedro
-Original Message-
From: Adrian Reyer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 9:24 AM
To: Pedro Aguayo
Cc: Rivera, Edwin; [EMAIL PROTECTED]
Subject: Re: [data write: File too large]
On Tue, Jan 15, 2002 at 09:14:33AM -0500, Pedro
In a message dated: Mon, 14 Jan 2002 18:41:04 EST
Brandon D. Valentine said:
On Mon, 14 Jan 2002, Joshua Baker-LePain wrote:
Hmmm, you did 'rpm -e' the RPM version, right? Pre-build amanda=bad.
Word. Especially the moronic way in which RedHat has decided to build it.
I'm glad I'm not the
I see! said the blind carpenter, who picked up his hammer and saw.
-My ninth grade science teacher, Brother Paul, a terrible
punner.
-Kevin
Pedro Aguayo [EMAIL PROTECTED] 01/15/02 09:45AM
Ahh! I see said the blind man.
Pedro
-Original Message-
From: Adrian Reyer
On 15-Jan-2002 Adrian Reyer wrote:
No holding-disk - no big file - no problem. (well, tape might have
to stop more often because of interruption in data-flow)
Why not define a chunksize of 500 Mb on your holdingdisk? That's what
I did. Backups go faster and there's less wear and tear on
I have got an email from OnStream support today. They say that they
are *not* planning to release a new firmware for the ADR50 or the
ADR30 at the moment. Thus, no support for amanda.
They claim that their new generation drives, the ADR2 series, do not
have this problem.
Moritz
Ok, I didn't but think I do now.
Basically when amanda write to the holding disk, it rights it to a flat file
on the file system, and if that flat file is larger than 2gb then you might
encounter a problem if your filesystem has a limitation where it can only
support files 2gb.
But if you write
Good afternoon,
Well, when i execute dump... i receive the next e-mail
FAILURE AND STRANGE DUMP SUMMARY:
sc01us0105 /software/amanda/share/ lev 0 FAILED [disk /software/amanda/share/
offline on sc01us0105?]
DUMP SUMMARY:
DUMPER STATS
And yes, I have read the FAQ.
On my RedHat 7 server, Amrecover invariably dies with an Unexpected server
end of file error. All other amanda functions (amdump, acheck, alabel) work
great. I have the sneaking suspicion that xinetd is somehow to blame, mainly
because of this error message
Pedro Aguayo wrote:
Ok, I didn't but think I do now.
Basically when amanda write to the holding disk, it rights it to a flat file
on the file system, and if that flat file is larger than 2gb then you might
encounter a problem if your filesystem has a limitation where it can only
support
hello,
I encounter a trouble when trying to configure
my Amanda server to backup NT hosts through
the Samba suite:
* Amanda index/tape server: Linux RH7.1
(the server is also an Amanda client)
* Amanda version : 2.4.2p2,
compiled with --with-smb-client=/full/path/...
* Samba version : 2.2
Help, please.
I had been running amanda 2.4.2p2 on a SunSparc Ultra 2
backing up to a DLT2000 drive.
HD in system has crashed, and now I can't access my backup tape.
Have installed amanda again, and think I have things config'd same as
before. (but I don't have my original amanda.conf
answering my own question:
* Amanda version : 2.4.2p2,
compiled with --with-smb-client=/full/path/...
I tried to recompile again, and checked the
configure output:
$ ./configure ... --with-smblient=/usr/local/samba/bin/smbclient ...
(...)
checking for smbclient... no
(...)
but,
$
Looks to me like xinetd is working correctly. If xinetd was refusing
the connection you wolkd never see the 220 prompt.
Some sugesstions:
1. Does amandahome/.amandahosts on the tape server have a line like:
localhostroot
my.serverroot
2. It may be necessary to add the server
I am trying to restore an NT partition from backup. Naturally one has to
use GNUTAR to be able to backup the filesystem.
However is there an interactive method to restore from tar, or must I
untar to a holding disk first, then grab the files I need.
Also a while back there was mention of
On Tue, 15 Jan 2002 at 1:08pm, Brad Groshok wrote
I had been running amanda 2.4.2p2 on a SunSparc Ultra 2
backing up to a DLT2000 drive.
amverify ody shows:
Using device /dev/rmt/0bn
** Error reading label on tape
Errors found:
0+0 records in
0+0 records out
amrestore
Ah, the beauty of amanda.
Use the no-rewind device and issue:
mt -t no-rewind device fsf 1
That will skip the label header. Then you can use dump, GNUTAR or whatever
backup utility you used and restore or list the tape using the no-rewind
device. For GNUTAR that might be:
tar xvf
One more thing:
As a normal NT server, usually the hard drives are shared automagically,
via a $ sign.
therefore if you have C, D and E drive, they are shared respectively by
//host/c$, //host/d$, and //host/e$. Assuming you got administrative
privledge access.
So i got lucky and was able to
amrestore ody shows:
amrestore: could not open tape ody: No such file or directory
That's not the proper syntax to amrestore. It needs to know the tape
device, i.e. 'amrestore /dev/rmt/0bn'. It doesn't care about a config
file.
[2:20pm chip]# mt rewind
[2:20pm chip]# amrestore
I have been using amanda-2.4.2p2-4 (RPM) on linux (redhat 7.2) for
some time with good results. Now they have moved my equipment so that
there is a firewall between my clients and server. After the move I
am getting data timeouts. I can't figure out what's the problem.
Here is what the client
On Tuesday 15 January 2002 12:13 pm, you wrote:
Looks to me like xinetd is working correctly. If xinetd was refusing
the connection you wolkd never see the 220 prompt.
Some sugesstions:
1. Does amandahome/.amandahosts on the tape server have a line like:
localhost root
my.server
I'm having some trouble setting up an Amanda client sitting in a DMZ
of a firewall to talk to an Amanda server sittin inside a firewall.
I've tried to follow the answer in the FAQ and also read the various
posts on amanda-users. However, I can't get it to work and some
questions till linger:
Wow, you and I are at almost the exact same place with the same problem.
I too am getting errors about port numbers that I didn't set up in the
configuration, when I compiled amanda.
I've been assuming that my firewall was translating port addresses in
addition to IP addresses, but this doesn't
Here's how I did this.
The relevant portions of my configure line:
./configure --with-udpportrange=850,855 --with-portrange=32800,32850
I used this on both client and server
And my firewall (linux) looks like this: (IP numbers are not real)
Internet firewall
This makes sense because when I ran my initial Amanda dump on that host, I
had no holding-disk defined, and it did backup the filesystem at level 0,
and that filesystem has over 24GB of data on it, albeit, they are all small
.c files and the such. I am left wondering then how chunksize fits into
is there a way, in the amanda.conf file, to specify *NOT* to use the
holding-disk for a particular filesystem?
for example, if i use amanda to backup 8 filesystems on one box and i want 7
to use the holding-disk, but one not to.. is that possible?
just curious..
-edwin
-Original
On Tuesday 15 January 2002 10:30 am, Moritz Both wrote:
I have got an email from OnStream support today. They say that
they are *not* planning to release a new firmware for the ADR50
or the ADR30 at the moment. Thus, no support for amanda.
They claim that their new generation drives, the ADR2
On Tuesday 15 January 2002 09:56 am, Rivera, Edwin wrote:
is there a way, in the amanda.conf file, to specify *NOT* to use
the holding-disk for a particular filesystem?
for example, if i use amanda to backup 8 filesystems on one box
and i want 7 to use the holding-disk, but one not to.. is
43 matches
Mail list logo
