Re: interestng developments
On Jul 3, 2001, Ben Hitz <[EMAIL PROTECTED]> wrote:
> If I use another Linux machine, instead of local host - I get the
> following from Amcheck. It looks like the same problem, but why would
> the connection be refused on Linux but not Irix?
Because GNU/Linux sends a packet back when it receives a UDP packet to
a port on which no process is listening, and another GNU/Linux machine
will report this back to the sender as a connection refused. It means
you haven't set up [x]inetd to run amanda on the client.
--
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: alternate recovery host?
On Jul 3, 2001, Bill Swingle <[EMAIL PROTECTED]> wrote:
> Is there a way to set this up so that the local machine has all the
> info needed to find/restore files without needing the remote
> machine?
Sure, just rsync the configuration and index directories over from the
remote machine into a closer index server, and tell amrecover to
use this index server, while still using the remote tape server (I
suppose).
--
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: help: problems building Amanda 2.4.2p2 on HP-UX v10.20
On Jul 2, 2001, "Rivera, Edwin" <[EMAIL PROTECTED]> wrote:
> /buildhp2/amanda-2.4.2p2# ./configure --with-user=amanda --with-group=amanda
2> &1 > tt.txt
> Invalid configuration `hpux10.20': machine `hpux10.20' not recognized
Seems like some config.site or config.cache is breaking the system
auto-detection.
--
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: amrecover and index record
On Jun 29, 2001, [EMAIL PROTECTED] wrote:
> amindexd is running as root. I have to do my dump as root because I use
> tar.
Amanda takes care of running GNU tar as root by itself, you don't have
to configure --with-user=root for GNU tar to work properly.
--
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: Building one one machine; using on another
On Jun 27, 2001, a blob of green gelatin <[EMAIL PROTECTED]> wrote:
> ld: fatal: file values-Xa.o: open failed: No such file or directory
This file is part of a development-installation of Solaris. You'll
definitely need to install some Solaris package to get anything at all
compiled on this system. Installing pre-compiled versions of GCC and
GNU binutils won't be enough: they'll still want this file to be
present.
--
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: amrecover problems
On Jun 26, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> Does it make the things run slower if a program is ALWAYS compiled with -g?
Not when using GCC. In fact, that's the reason why configure uses
CFLAGS="-O2 -g" by default, when the compiler is GCC. GCC generates
exactly the same code, regardless of -g, and you can always strip off
debugging information if you wish. Debugging information will only
take up disk space, but since it's not in loadable sections, it won't
even use additional memory when you run the program.
--
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: dds3 or dds4?
On Jun 27, 2001, Tom Strickland <[EMAIL PROTECTED]> wrote:
> total for HP SureStore DDS3i, SCSI card, 20 tapes, delivery, VAT: 998.52UKP
It doesn't look like we're talking lots of disk space here. Consider
buying one or two machines with loads of disk and do backup on disk
only, rsyncing the backups onto a backup of the backup or having the
backup disks on RAID 5, depending on how serious of a failure you're
willing to tolerate.
--
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: Too many filesystems to AMANDA?
On Jul 3, 2001, Enrique Rodríguez Lázaro <[EMAIL PROTECTED]> wrote:
> GNUTAR /xxx/r/ttt/ 0 1970:1:1:0:0:0 1 exclude-file=*bbb..es* *mmm*
^
You can't have whitespace in an exclude-file specification. This is
what breaks the request packet reader.
--
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: amcheck problem
On Jun 22, 2001, "John Holstein, IS" <[EMAIL PROTECTED]> wrote:
> "amanda.conf" line 0: default tape type EXABYTE not defined.
> amcheck: could not read amanda config file
> We didnt add any "EXABYTE" stuff in there at all.
Yep, but for some reason that's the default tapetype name, so you have
to override it with `tapetype NAME' in amanda.conf, and make sure to
`define tapetype NAME' too.
--
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: time_t?
On Jun 21, 2001, [EMAIL PROTECTED] wrote:
> Alexandre Oliva wrote:
>> On Jun 21, 2001, Lance Dillon <[EMAIL PROTECTED]> wrote:
>>
>> > The tar version is 1.13 (tar --version), from sunfreeware.com.
>>
>> 1.13 is broken. That's one of the symptoms.
>>
>> > I tried to compile 1.13.19 from the sources, but it would always hang up
>> > at a certain point (I determined where it would fail, but not why).
>>
>> Is this on Solaris/x86 or Solaris/sparc? Which compiler? Which linker?
> Solaris sparc. gcc 2.8.1 (also from sunfreeware.com), ld 2.9.1
Check the GNU tar 1.13.19 release notes. I believe somewhere it says
GCC 2.8.1 won't compile it properly.
--
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: tcp port
On Jun 17, 2001, "Wong Ching Kuen Frederick" <[EMAIL PROTECTED]> wrote:
> but they are running as setuid already.
Note that sendbackup (the one that binds the ports the server connects
to to get the backup data) is not (and should not be) setuid root.
So, client TCP ports should not be in the <1024 range, unless you
configured --with-user=root.
--
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: time_t?
On Jun 21, 2001, Lance Dillon <[EMAIL PROTECTED]> wrote:
> The tar version is 1.13 (tar --version), from sunfreeware.com.
1.13 is broken. That's one of the symptoms.
> I tried to compile 1.13.19 from the sources, but it would always hang up
> at a certain point (I determined where it would fail, but not why).
Is this on Solaris/x86 or Solaris/sparc? Which compiler? Which linker?
--
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: overwrite full with incremental?
On Jun 21, 2001, Pamela Miller <[EMAIL PROTECTED]> wrote:
> 0 20010615 DailySet112 3 1524850 1524864 788
> 3 20010621 DailySet112 3 252040 252064 218
You asked for one full backup per week (dumpcycle), and told Amanda to
use only 6 tapes (tapecycle), but it appears that you didn't run
Amanda 5 times during the week (runspercycle), which might explain why
it wouldn't have found enough space in the tape to run another full
backup of the disk, especially given that it wasn't due yet (since a
week hadn't passed).
It's strongly recommended that you have additional tapes ((2 *
runspercycle + 1) * runtapes) in the tapecycle in case a full backup
fails: then you can always go back to the other, without the risk of
having had it just overwritten.
Amanda probably made a lot of noise in the mail backups warning that
the last full backup of that disk was about to be overwritten, and
finally overwritten. This is a strong indication that your tapecycle
is too short, or your dumpcycle is too long, or that you aren't
following the runspercycle plan.
--
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: long term achieving with tar
On Jun 20, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> One possible workaround (some would say "hack" :-) if the runs might
> happen at the same time would be to add a trailing "/." to all the disk
> names in your disklist. For instance, if your daily run backs up "/home"
> have the archive run do "/home/.". That will do effectively the same
> thing but the file names will be different.
> I think.
FWIW, I had the same idea a few weeks ago to introduce an experimental
configuration in our set up (switching Amanda servers), and it's been
working beautifully.
--
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: Problem on amcheck: NACK error
On Jun 8, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
>> But hen the MULTITAPE documentation says:
>> "- a single dump file can straddle two tapes"
>> So who/what should I believe ?
> I unde4rstand it as: need to use DUMP (not tar) and have manual
> changer activated. Then it can spread.
Nope, not even then. Even though docs/MULTITAPE was written on 1994,
as a future enhancement place, this feature isn't available in any
official release of Amanda yet. There's a CVS branch in which JJ has
developed this feature, and last time I heard it was working
reliably. Perhaps you'd like to give it a try?
--
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: Problems with the tape.
On Jun 14, 2001, "Josep M. Marti" <[EMAIL PROTECTED]> wrote:
> I have a problem with the service and the xinetd. I have defined the
> service but I have disabled (option default) the xinetd.d/amanda
> xinetd.d/mandaidx and xinetd.d/amidxtape.
`chkconfig amanda on' (perhaps followed by `/etc/init.d/xinetd
reload'?) should get xinetd to start amandad whenever a request comes
up.
--
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: Cooling
On Jun 19, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> it makes about 10 degrees difference
Centigrade or Fahrenheit?
--
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: tcp port
On Jun 19, 2001, "Wong Ching Kuen Frederick" <[EMAIL PROTECTED]> wrote:
> for udp port, i could use <1024
> for tcp port, i should use ports > 1024.
> is this correct?
Yep.
--
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: dump larger than tape, but cannot incremental dump new disk
On Jun 18, 2001, "Arnar Gestsson" <[EMAIL PROTECTED]> wrote:
> the estimate, given by amstatus shows that a filesystem of 33.8 MB is
> 544758720k.
Are you using hardware compression? Is comprate set in the given
dumptype? What is the estimate printed by GNU tar in
/tmp/amanda/sendsize.debug on the client?
--
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: tar, latest vs star latest
On Jun 15, 2001, Gene Heskett <[EMAIL PROTECTED]> wrote:
> Has anyone done any tests to see if it will work as a tar substitute
> with amanda?
Probably not. I suppose start doesn't support --listed-incrementals
the same way GNU tar does.
It shouldn't be too hard to get Amanda to use star as soon as the
DUMPER API is implemented, though.
--
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: tcp port
On Jun 17, 2001, "Wong Ching Kuen Frederick" <[EMAIL PROTECTED]> wrote:
> ./configure --prefix=/usr/local/amanda --with-user=amanda --with-group=disk
>--with-portrange=800,830 --with-udpportrange=800,830
> however, after using tcpdump, i find out that it use udp port 800,830, but tcp port
>3. could somebody tell me why?! thanks.
Another issue is that a process must be running as root to get a
privileged (<1024) port. The Amanda server, when connecting to a
client port, is not running as root, so it can't get a privileged
port.
--
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: more errors
On Jun 15, 2001, Lance Dillon <[EMAIL PROTECTED]> wrote:
> backup fails because "the file changed while reading it", and it doesn't
> backup the system at all.
> Is there any way to ignore this error?
GNU tar 1.13.19 should not FAIL on this message, you'll just get a
STRANGE warning, which may be annoying, but I find it a good thing.
--
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: tcp port
On Jun 17, 2001, "Wong Ching Kuen Frederick" <[EMAIL PROTECTED]> wrote:
> however, after using tcpdump, i find out that it use udp port
> 800,830, but tcp port 3.
Did you use --with-portrange when building the client too?
--
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: pb lock "/etc/amandates", flock or fcntl problems??
On Jun 13, 2001, Henk Vandecasteele <[EMAIL PROTECTED]> wrote:
> I also tried to install rh7.1 amanda rpm on rh7.0 system.
> Changing the permission of /etc/amandates changes the
> behaviour, but I could never make it to work. Looks like
> the package is incompatible.
My understanding is that packages built for Red Hat Linux 7.1 use
features of glibc that are only enabled in the presence of a 2.4
kernel, so they won't work on Red Hat Linux 7. Note that the converse
is true: packages built on Red Hat Linux 7 will run on 7.1.
--
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: no-rewind?
On Jun 13, 2001, Aaron Smith <[EMAIL PROTECTED]> wrote:
> but amlabel constantly pukes on it with the same error listed below
Which version of amlabel? There was an embarrassing bug in 2.4.2 (or
some earlier snapshot?) that caused it to fail every time on some
platforms. It's most definitely fixed in 2.4.2p2.
--
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: Archiving.
On Jun 9, 2001, Grant Schofield <[EMAIL PROTECTED]> wrote:
> I am needing to archive data on a long term basis. If I I run one
> backup a week I will only get about 25gb of data which does not fill up
> my AIT(50gb) tape. Due to disk limitations (NetApp) I really can not
> let this one process take up more space on the netapp then 25gb. What
> is the best way to archive this data without wasting tapes?
Buy one of those relatively inexpensive 60GB-80GB disks, plug it in a
PC and use it as your holding disk.
--
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: amcheck response on slot
On Jun 7, 2001, "Howard Zhou" <[EMAIL PROTECTED]> wrote:
> When I ran amcheck, I got the following.
> amcheck-server: slot 0: not an amanda tape
Did you amlabel the tape?
--
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: Backup of Windows machine times out
On Jun 6, 2001, Albert Hopkins <[EMAIL PROTECTED]> wrote:
> The daily amcheck reports no errors however the nightly backup fails
> with [Request to localhost timed out.]
Perhaps the estimates took too long? Check /tmp/amanda/sendsize.debug
and compute the difference between the timestamps in the first and the
last lines, and make sure etimeout in amanda.conf is somewhat larger
than that.
--
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: dump to tape failed
On Jun 5, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
>> 2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
>> 2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump to
>> tape failed]
>> 2001-05-31 hermes hda1 0 --- 0 FAILED (dumper) ["data
>> write: Broken pipe"]
> Are you sure your files are not kept on the holding disk?
Since the message is `dump *to tape* failed', the dump was never
stored in the holding disk: it was a direct-to-tape dump.
Vicente, consider getting a larger holding disk, or specifying a
chunksize so that this disk gets dumped to the holding disk. Then, if
it turns out that it doesn't fit in the tape, you'll be able to flush
it to another tape on the next day.
--
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: amverify problem w/DLT
On Jun 5, 2001, "Jaehne, Richard S" <[EMAIL PROTECTED]> wrote:
> amrestore: could not open tape /dev/rmt/DLTlbn: Device busy
AFAICT, all this means is that the tape unit wasn't ready yet at the
time amverify started another amrestore on it. Nothing to be worried
about.
--
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: More info: Exabyte 220 / Solaris 7 x86
On Jun 4, 2001, Jason Tucker <[EMAIL PROTECTED]> wrote:
> So, two questions: Does anyone know what causes an "exit(33)" in gcc
> (cc1)?
The fact that it prints not only the warnings that can be ignored, but
also real errors. If cc1 finds actual errors, gcc won't run the
assembler at all.
--
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: Amcheck troubleshooting
On Jun 5, 2001, Denise Ives <[EMAIL PROTECTED]> wrote:
> can not access hdg1 (hdg1): No such file or directory
Looks like it's not looking for it as /dev/hdg1, assuming this device
name exists. Try /dev/hdg1 explicitly, if this is the case.
--
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: Listing tape content -- confusion
On Jun 5, 2001, Joseph Del Corso <[EMAIL PROTECTED]> wrote:
> amrestore $TAPE whatever
> And according to archived emails, this should list tape content...
> but according to the man page, this also extracts the contents of the
> tape.
As long as `whatever' matches some of your host names. The trick is
to give it a hostname that won't match any of the backups.
--
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-users] Re: several errors & I'm confused
On Jun 5, 2001, Eric Sproul <[EMAIL PROTECTED]> wrote:
> I have continued to experience problems with writing filemarks and
> getting 'bad file descriptor' errors on nightly Amanda runs as well as
> with amflush.
Sometimes, all this means is that you're reaching EOT. Does tape
usage match this assumption?
--
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: Problem on amcheck: NACK error
On Jun 5, 2001, Patrick Ellis <[EMAIL PROTECTED]> wrote:
> I just installed amanda version 2.4.2p2 on a FreeBSD node and I have
> amandad: version 2.3.0
Look, you're running 2.4.2p2's amcheck but the client is still running
2.3.0's amandad. The protocol was modified in release 2.4.0, and it's
no longer compatible with that of 2.3.0. You have to upgrade all the
clients to 2.4.* when you upgrade the server to 2.4.*.
--
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: broken gnutar
On Jun 5, 2001, <[EMAIL PROTECTED]> wrote:
> I understand that there are some versions of gnutar that do not correctly
> exclude data. Does anyone know which version(s) are affected?
Nope. GNU tar 1.13 restores data into directory names containing
numbers, but that's all. 1.12+patches and 1.13.1[79] work fine.
--
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: ununderstood error
On Jun 3, 2001, Paolo Supino <[EMAIL PROTECTED]> wrote:
> "*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]]."
> The tape was a brand new one that I labeled the same day the backup
> ran. It didn't report any problems while labeling it. Running `amcheck`
> a few minutes later didn't report any problems with the tape either.
Tape full? The error message is exactly what the OS told Amanda when
it asked the OS to write to the device.
--
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: core:
On Jun 1, 2001, Denise Ives <[EMAIL PROTECTED]> wrote:
> gdb ufsrestore
> This GDB was configured as "sparc-sun-solaris2.8"...(no debugging symbols
> found)...
> (gdb)
If it was ufsrestore that crashed, you should file a bug report to
Sun.
But first, make sure this particular filesystem was dumped with
ufsdump on the same version of Solaris. dump formats change from one
OS to another, and from one OS version to another.
--
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: Blanks in disklist entries
On May 31, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> U, I hope you put "/some/where/in/unix/land/." in disklist and not
> just "/some/where/in/unix/land". Without the trailing "/." GNU tar (I
> assume that's what you're using) will only back up the symlink itself,
> not the directory structure it points at.
You sure? Remember that we do
tar -C /some/where/in/unix/land -cf - .
not
tar -cf - /some/where/in/unix/land
which would indeed only archive the soft-link (but then, your backups
would be blazingly fast! :-D
--
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: Insufficient holding disk space
On May 31, 2001, Jason Henry Parker <[EMAIL PROTECTED]> wrote:
> This is all fine, except the holding disk is a 45GB disk, and the
> dumps from client `cray' take only 1.5GB. There is nothing else on
> the disk, and hdc1 on `hopper' is only 8GB.
The error message is certainly misleading, but I guess it has to do
with the fact that you haven't set a chunksize. IIRC, the default
setting in 2.4.1p1 tells Amanda not to use the holding for images
larger than 2Gb. Set chunksize to, say, 1 Gb, and all should be fine.
--
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: Antwort: Incremental Backup and Backup NT from Unix server
On May 31, 2001, "Howard Zhou" <[EMAIL PROTECTED]> wrote:
> I downloaded tar-1.13.tar.gz from http://www.gnu.org/directory/tar.html
> Is this the right version of gtar?
No, see docs/INSTALL.
> I found this package gives me tar instead of gtar executable.
This doesn't matter. Amanda's configure looks for gnutar, gtar and
tar.
--
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: Is Amanda what i want to use ?
On May 30, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> What would it be with Gnu tar?
It's easy enough to have multiple Amanda installations, each one
running with a different set of ports and gnutar-lists-directories, so
that backups with them are absolutely independent.
Also, since Arne was talking GNU/Linux, I suppose having multiple
builds of dump, each one using a different pathname for
/etc/dumpdates, wouldn't be too hard to do.
> And also consider that Amanda is designed to run on tape, the version
> to run on disk is only a development thing...
But a stable one, according to JJ, who has been working on it.
--
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: Incremental Backup and Backup NT from Unix server
On May 30, 2001, Mitch Collinsworth <[EMAIL PROTECTED]> wrote:
> One thing to note here is that the Amanda/Samba/gtar backups of windows
> shares will only perform level 0 and level 1 dumps. All incrementals
> are at level 1 until the next full.
And yet another thing to note here is that Cygwin has (recently?)
gained a program named cygrunsrv, that could be used to start a
Cygwin-built [x]inetd, that could then fire amandad natively on
Windows. I haven't got to the trouble of going down this path, but it
seems like someone with a lot of Windows machine to back up could
observe a significant speed up avoiding all of the SMB overhead,
gaining more levels of incremental backups meanwhile.
--
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: Antwort: Incremental Backup and Backup NT from Unix server
On May 30, 2001, [EMAIL PROTECTED] wrote:
> Yes. You need samba and gtar (use 1.13.18 or newer!).
Actually, 1.13.18 contains a very serious bug. 1.13.19 was released
one or two days after it, to fix the bug. 1.13.17 was ok, as far as
Amanda is concerned.
--
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: Out of tape??
On May 29, 2001, Aaron Levitt <[EMAIL PROTECTED]> wrote:
> The server is running redhat 6.2
Try `man mt'. Look for datcompress.
--
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 compile error on solaris
On May 28, 2001, "Howard Zhou" <[EMAIL PROTECTED]> wrote:
> Are these lines use by a parser? Or just comment lines?
They're mostly used to emit debugging information, so that the object
file points at the original file, as opposed to the generated file.
However, the preprocessor also uses these notes to look for headers
mentioned in `#include "header.h"' directives (compare with `#include
', that causes the preprocessor to search only the default
search path, not do relative search).
> What I did actually to get around this problem was to comment out all lines
> proceeding with "#line" with /* */.
> It compiled ok. Did I do the right thing?
Yep, that works.
--
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: Bug: xfsrestore -t insists on CWD being on a XFS filesystem
On May 28, 2001, "Bernhard R. Erdmann" <[EMAIL PROTECTED]> wrote:
> /usr/sbin/xfsrestore: ERROR: Current directory not XFS: /tmp/amanda
> I consider this being a bug: no actual restore is done, so CWD's
> filesystem doesn't matter.
I'd go even further: xfsrestore should be capable of restoring onto
non-XFS filesystems. What should matter is the format of the backup
image, not the underlying representation of data on the filesystem to
which files are being restored.
--
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: Out of tape??
On May 28, 2001, Aaron Levitt <[EMAIL PROTECTED]> wrote:
> How can I tell?? I know I am using software, since the dumptype has
> "compress server best". Any other pointers??
Check the leds in your tape drive. They often indicate whether
software compression is enabled or disabled. It's generally possible
to tell this in software too, but it depends on which OS the tape
server is running.
--
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 compile error on solaris
On May 26, 2001, "Howard Zhou" <[EMAIL PROTECTED]> wrote:
> /home/gandalf/u66/jrj/work/amanda/amanda-242/recover-src/uparse.y:32:
Edit uparse.c and remove all pathname components in any occurrences of
the filename above, leaving just `uparse.h'. This should fix the
problem.
JJ, this is yet another trick related with building release tarballs:
it's best done in a copy of the source tree after `make
maintainerclean' (I believe this will remove uparse.c and any other
lex/yacc-generated files).
--
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: disk offline
On May 20, 2001, "Bernhard R. Erdmann" <[EMAIL PROTECTED]> wrote:
>> #! /bin/sh
>> X=; export X
>> exec $0.exe ${1+"$@"}
> What is ${1+"$@"} good for? Never seen that construction before...
Some shells expand "$@" to "" when $# = 0.
--
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: disk offline
On May 20, 2001, Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> This appears to be a bug that triggers in a very particular
> condition: when the environment is empty. It doesn't trigger with
> 1.12 because it just doesn't depend on librt.so.
Nope. It didn't trigger on 1.12 because it wasn't linked with GNU ld.
The problem is that GNU ld sets the dynamic linker as
/usr/lib/libc.so.1, whereas Sun ld sets it to /usr/lib/ld.so.1. Even
though Sun officially supports both, according to a friend of mine at
Sun, the one chosen by GNU ld fails because it assumes the environment
contains at least one non-NULL entry. My friend is working on a fix
for Solaris/x86 libc; I'm not sure we (GNU developers) are going to
fix GCC or GNU ld, or both, or neither, since the work-around is
simple: just link the program using
`-Wl,--dynamic-linker,/usr/lib/ld.so.1', or use Sun ld, or make sure
the environment is never empty, or wait for a patch from Sun.
--
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: disk offline
On May 19, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> I have upgraded to tar 1.13.19 but when I try to activate amanda on a
> client machine, I get disk off line error:
> FAILURE AND STRANGE DUMP SUMMARY:
> oak/home/fidji lev 0 FAILED [disk /home/fidji offline on oak?]
> oak/home/hawai lev 0 FAILED [disk /home/hawai offline on oak?]
Is this on Solaris?
It seems that the environment clean-up that sendsize does before
running runtar is getting Solaris/x86' start-up code somewhat
confused. At least, I'm getting crashes very early in the program
execution, before ld.so gets to open librt.so (the first shared
library tar depends on). This appears to be a bug that triggers in a
very particular condition: when the environment is empty. It doesn't
trigger with 1.12 because it just doesn't depend on librt.so.
Anyway, I've managed to work around the bug by wrapping the tar
1.13.19 executable with a script that exports an environment variable
set to an empty string:
#! /bin/sh
X=; export X
exec $0.exe ${1+"$@"}
--
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: A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]]
On May 20, 2001, Sven Kirmess <[EMAIL PROTECTED]> wrote:
>> NOTES:
>> taper: tape daily26 kb 0 fm 0 writing filemark: Input/output error
> Sory for replaying to my own message. I found something in syslog:
> kernel: st0: Error with sense data: Info fld=0x1, Current st
> 09:00: sense key Medium Error
> kernel: Additional sense indicates Write error
> I think that means the tape is broken...?
Quite possibly. Try running tapetype on it and see how far it goes.
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>>> Looks like gcc 2.8.1.
>> Gee. That's dead broken. ...
> Yeah, yeah. But you're just a wee bit biased :-) :-).
FYI, I've just found this in GNU tar 1.13.19's README:
* Solaris issues.
GNU tar exercises many features that can cause problems with older GCC
versions. In particular, GCC 2.8.1 (sparc, -O1 or -O2) is known to
miscompile GNU tar. No compiler-related problems have been reported
when using GCC 2.95.2 or later.
And here's the patch for a crash I had mentioned I had found. It
would crash while doing --listed-incremental full or incremental
backups whenever it didn't have permission to enter a directory:
--- src/incremen.c~ Sat Jan 13 03:59:29 2001
+++ src/incremen.c Sun May 20 05:51:37 2001
@@ -183,7 +183,10 @@
enum children children;
if (! dirp)
- savedir_error (path);
+ {
+ savedir_error (path);
+ return 0;
+ }
errno = 0;
name_buffer_size = strlen (path) + NAME_FIELD_SIZE;
--
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: disk offline
On May 19, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> I wonder what is the tar command that is used to calculate the
> estimate.
It's printed in sendsize.debug, IIRC. And in runtar.debug.
It will reference a gnutar-list-dir .new file. It's created initially
empty for level 0 estimates, and a copy of the lower level for
incremental estimates.
FWIW, I've had similar results with GNU tar 1.13.19 on Solaris 7/x86.
I've started investigating, but didn't get very far, and ended up
downgrading back to 1.12+patches.
--
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: amverify 'not at start of tape' errors
On May 19, 2001, "Carey Jung" <[EMAIL PROTECTED]> wrote:
> we seem to get a lot of 'not at start of tape' errors
It's not an error, just a warning that the tape section numbers that
follow do not reflect the actual tape section numbers on tape, because
you hadn't started amrestore at the beginning of the tape. It has
absolutely nothing to do with what is actually on the tape. It has to
do with whether amrestore found a tape label in the beginning of the
first section it read or not, and this tape label is only written by
Amanda in the beginning of a tape.
--
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: A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]]
On May 18, 2001, Sven Kirmess <[EMAIL PROTECTED]> wrote:
> *** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
> Some dumps may have been left in the holding disk.
> /-- localhost /dev/md190 lev 1 FAILED ["data write: Broken pipe"]
> What does that mean? Is my tape broken?
It probably means you ran out of tape space during a direct-to-tape
backup.
--
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: amercover and indexes
On May 18, 2001, Ian Prowell <[EMAIL PROTECTED]> wrote:
> 07300354473/./etc/
Read docs/INSTALL. You should not have used GNU tar 1.13.
--
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: Problem with GNU tar 1.13
On May 18, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
> I am just starting to install Amanda and have a problem with GNU tar
> 1.13 (freshly downloaded from GNU ftp);
Read docs/INSTALL. You don't want to use GNU tar 1.13. Use
1.12+patches or 1.13.17 or newer.
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>> Do you know which compiler was used to build this version of GNU tar?
> Looks like gcc 2.8.1.
Gee. That's dead broken. First thing I'd do would be to get GNU tar
1.13.19 built with a newer compiler. But I can tell from personal
experience that, even when built with GCC 2.95.3, on Solaris 7/x86, it
wouldn't even be able to do estimates properly. So I stayed with 1.12
for now. Investigating the actual problem is in my to-do list.
I can also tell from personal experience that I haven't had trouble
with GNU tar 1.13.17 on GNU/Linux/x86, but I still haven't been able
to do backups reliably with 1.13.19 (it will generally abort part-way
through the back-up; I suspect a network problem, but a bug in GNU tar
still isn't ruled out)
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>> Did you try to read this tar-file with some other tar program? ...
... such as GNU tar 1.12?
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> Yeah, yeah. But you're just a wee bit biased :-) :-).
Me! No way! :-D
>> First thing I'd do would be to get GNU tar
>> 1.13.19 built with a newer compiler. ...
> So what's the recommended **stable** gcc these days?
2.95.3
> I'll try to scrounge up the 100+ MBytes and CPU hours it takes to
> build and give that a try.
I could build GNU tar 1.13.19 for you, to run on Solaris 2.6/sparc, if
that would help. Just let me know.
--
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: GNUTAR backup of VxFS fails
On May 17, 2001, David Carter <[EMAIL PROTECTED]> wrote:
> The gtar version is 1.11.8.
You need at least 1.12+Amanda's patches (but not 1.13 and, given JJ's
recent posting about 1.13.19 on Solaris, I'd stay away from it too, at
least for now).
> where --file becomes "/dev/null"
This is just how estimates are done.
sendsize.debug might say more about the reason it failed.
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> --listed-incremental /tmp/jrj/zli \
> This does what Amanda does for a full dump.
Just to make sure (and for the enlightenment of anyone else trying to
duplicate the problem): you have removed /tmp/jrj/zli before every tar
command, right? 'cause I can't seem to be able to duplicate this
problem on my machines. Do you know which compiler was used to build
this version of GNU tar?
> $ gtar tvf z.tar
> drwxr-xr-x jrj/pucc 62 1999-06-08 13:53:30 ./
> -rwxr-xr-x jrj/pucc 10412 1999-06-08 13:53:30 ./getMailHostName
> gtar: Unexpected EOF in archive
> gtar: Error is not recoverable: exiting now
Did you try to read this tar-file with some other tar program? Hmm, I
guess this doesn't matter much; it's pretty obvious tar didn't write
everything out to the tarball, given how small it is.
--
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: Linux and dump
On May 17, 2001, Dan Wilder <[EMAIL PROTECTED]> wrote:
> Is this an option amrecover can (or does) pass to tar?
Nope. amrecover explicitly tells tar which files to restore, so this
is not an issue.
--
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: Linux and dump
On May 17, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> Oh, shit.
I wouldn't have put it better :-)
> I tried GNU tar 1.12 (plus the Amanda patches) and it works fine.
Thanks God I'm still using that one, on most systems I've got. Talk
`conservative' regarding backups.
> But if'n I were you folks using this version of GNU tar, I'd start
> making damn sure your tapes had anything even faintly useful on them.
This is good advice, regardless of the backup tool you're using.
> Not to panic you or anything, of course. Have a nice day. :-)
:-)
--
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: switch to tar
On May 17, 2001, [EMAIL PROTECTED] wrote:
> could it be possible, that amanda can't overwrite tapes with "tar"
> that have been previously written with "dump" ?
Nope. The error message generally means tape full or media error.
Is there any message in the e-mail log specifying how much data taper
managed to get into the tape? Does it match your expectations?
--
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: Linux and dump
On May 17, 2001, "Anthony A. D. Talltree" <[EMAIL PROTECTED]> wrote:
>> But this is not a problem of linux, it's a problem of dump.
> Yeah yeah yeah. We've all heard that a million times before, and yet on
> real systems we've been happily using dump for years without
> consequences.
You've been lucky for years. Some day, it'll bite you, and you'll
regretfully remember this discussion. Or perhaps you'll keep on being
lucky.
Good luck :-)
> A more fitting analogy would be GM making cars out of cardboard and
> warning people to not leave them out in the sun because they might catch
> fire.
So your point is that dump should refuse to run on a mounted
filesystem? Yeah, that sounds reasonable to me. Then more people
would learn about its limitations and switch to some saner backup
tool.
--
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: Linux and dump
On May 17, 2001, "C. Chan" <[EMAIL PROTECTED]> wrote:
> I followed suggestions to remove ext2 dump so
> Amanda would detect xfsdump and recompiled, but I find this rather inelegant.
What is inelegant? Removing ext2 dump? You didn't have to do that.
You only need xfsdump available at configure time to get the xfsdump
supporting bits enabled; the existence of ext2 dump doesn't make a
difference.
--
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: Linux and dump
On May 17, 2001, Ron Stanonik <[EMAIL PROTECTED]> wrote:
> Sorry for the newbie question, but how can tar be configured so
> that after restoring a full and an incremental the filesystem has
> exactly the files at the time of the incremental, not any files
> which were present during the full but removed before the incremental.
Use -G at restore time. From the GNU tar manual:
`--incremental' (`-G') in conjunction with `--extract' (`--get',
`-x') causes `tar' to read the lists of directory contents previously
stored in the archive, _delete_ files in the file system that did not
exist in their directories when the archive was created, and then
extract the files in the archive.
This behavior is convenient when restoring a damaged file system from
a succession of incremental backups: it restores the entire state of
the file system to that which obtained when the backup was made. If
`--incremental' (`-G') isn't specified, the file system will probably
fill up with files that shouldn't exist any more.
--
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: .configure problem redhat 6.1
On May 8, 2001, Adam <[EMAIL PROTECTED]> wrote:
> --host=Linux
This is bogus. Let it guess itself, or specify at least the CPU type
in addition to the kernel name, i.e., something like i686-linux.
--
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: data encription
On May 7, 2001, Luke McKee <[EMAIL PROTECTED]> wrote:
> Quick question: Does AMANDA support media encryption?
Not directly. But someone came up with some scripts to get backups
encrypted with GnuPG. You may want to search the archives.
> Does the SECURITY-API cover this - or is it only limited to network
> security?
I believe it has to do with network security only.
--
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: host mozart.cefet-al.br: port 1038 not secure
On May 7, 2001, "Leandro Sales" <[EMAIL PROTECTED]> wrote:
> ERROR: mozart: [host mozart.mydomain.com: port 1038 not secure]
Check the FAQ at www.amanda.org. This usually means amcheck is not
setuid root.
--
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
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: 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
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: 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
Re: recover w/o index
On May 1, 2001, "Joseph McDonald" <[EMAIL PROTECTED]> wrote:
> indexing wasn't turned on.. any possible way to recover from the tapes?
Use amrestore.
--
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: RegEx within disklist?
On May 1, 2001, "Hanno 'Rince' Wagner" <[EMAIL PROTECTED]> wrote:
> I would like to use RegEx within the disklist and say one SaveSet is
> /path/to/save/[0-b] next one is /path/to/save/[c-n] and
> /path/to/save/[o-z] or something similar. Is this possible?
Yes. The trick is to use:
hostname /path/to/save {
theDumptype
exclude "./[^0-b]" # backup up only files starting with 0-b
}
hostname /path/to/save/. { # note the trailing dot
theDumptype
exclude "./[^c-n]"
}
hostname /path/to/save/./. { # note the trailing dots
theDumptype
exclude "./[^o-z]"
}
--
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: How amanda thinks
On Apr 30, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>> 1) When I run an amflush I notice that the dump are put on tape starting
>> with the smallest and working its way up to the largest last. Why is
>> this?
> I suspect the theory is to get as many images safely out to tape as
> quickly as possible.
My theory has to do with releasing holding disk space: since a small
image will be flushed more quickly than a large one, we flush the
small one first, and can release its disk space as soon as it
completes. Of course, in the long run (i.e., after everything is
flushed), you end up releasing the same amount of disk space, but, on
average over time, you get more free space flushing the small images
first.
--
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: Linus Torvald's opinion on Dump.
On Apr 28, 2001, Daniel David Benson <[EMAIL PROTECTED]> wrote:
>> It cuts 4 - 5 hours of my dumptimes.
> Tar definitely sucks in this respect. At my last job I had to use
> tar for some SAMBA backups. Definitely slowed things down a lot.
Samba backups are a completely different matter. GNU tar isn't even
involved in Samba backups (*); in retrospect, using it as the program
name to enable Samba backups was probably a mistake.
(*) even though it may be involved in index generation and in
restoring to Unix machines.
--
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: What is the purpose and location of /etc/amandates?
On Apr 27, 2001, Tom Schutter <[EMAIL PROTECTED]> wrote:
> 1) What is the current purpose of /etc/amandates?
To fill in a hole in our to-do list: to remove it some day :-)
It is totally unused.
> 2) Why is amandates in /etc? My guess is because it is close in
>functionality to /etc/dates, which is written by dump.
Guessed right.
--
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: amrecover: Unexpected server end of file
On May 2, 2001, Vicente Vives <[EMAIL PROTECTED]> wrote:
>> Does /tmp/amanda/amindexd*debug get updated on the server? If so,
>> what's in it?
> There isn't any amindexd*debug in the server.
That's because amrecover is contacting localhost. Specify the tape
and index server names in the amrecover command line.
--
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: could someone explain me this error?
On Apr 26, 2001, [EMAIL PROTECTED] wrote:
> i don't understand why amanda return "data timeout" because the other
> disk have been successfully backup ??
Unless you have modified dtimeout, this means the Amanda waited for
this filesystem to send data for 30 minutes and got nothing, so it
assumed the system was dead and aborted the backup. You may increase
dtimeout, if you have reasons to believe the backup is indeed making
progress. If you're using GNU tar, this is quite normal: it has a
very long start-up time: while it collects the directory tables it
outputs very little information.
--
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: Problem with device sg*
On Apr 26, 2001, Juergen Knott <[EMAIL PROTECTED]> wrote:
>> On Apr 26, 2001, Juergen Knott <[EMAIL PROTECTED]> wrote:
>> > Hm.with "mtx -f /dev/sg7 slot first" i haven't problems. The tape is
>> > changed. Also "mtx -f /dev/sg7 info" have no problems.
>>
>> But /dev/sg7 is not the tape device, it's the changer device.
> correct, the tape device is /dev/sg6
Huh? This looks very much like the name of a changer device too. Why
do you think it's a tape device?
> I don't understand that "mtx -f /dev/sg6 info" works fine.
This probably talks to the tape changer, not to the tape drive.
> And when i have loaded a tape manually and start "amcheck Daily", the loaded
> tape was unloaded and than comes the error messages in /tmp/amanda/*.debug
> It is an input-/output error.
Looks like your tape changer configuration file is not properly set
up. Which changer program are you using? How does its configuration
file look like?
--
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: Problem with device sg*
On Apr 26, 2001, Juergen Knott <[EMAIL PROTECTED]> wrote:
> Hm.with "mtx -f /dev/sg7 slot first" i haven't problems. The tape is
> changed. Also "mtx -f /dev/sg7 info" have no problems.
But /dev/sg7 is not the tape device, it's the changer device.
It is /dev/nst0, the tape device, that is not working. Are you sure
/dev/nst0 is what you're supposed to use to access the tape device
associated with that changer?
--
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: Problem with device sg*
On Apr 26, 2001, Juergen Knott <[EMAIL PROTECTED]> wrote:
> After 10 Minutes i send a break with ctrl-c because there is no operating.
It's waiting for the tape to get ready. Perhaps Amanda should print a
message after a while, and eventually time out.
> as user amanda and as user root after typing "mt-f /dev/nst0 rewind" this
> error message is displayed:
> mt: /dev/nst0: Input-/output error
Looks like you've got a problem accessing the tape device. Before you
fix this problem, Amanda won't be able to use it.
--
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: Tar, general, and amindexd questions
On Apr 25, 2001, Jason Brooks <[EMAIL PROTECTED]> wrote:
> 1) gnu tar version 1.13..*
> I can only find version 1.13. Where is gnu tar being developed
> that I may ensure I have the latest stable version?
docs/INSTALL (from 2.4.2p2) says:
gnutar 1.13.19 can be found at:
ftp://alpha.gnu.org/pub/gnu/tar
> 2) amanda.conf tweaking
> Over a period of time, I have tweaked amanda.conf. Sometimes
> needing to remove a backup from the disklist, other times
> noticing that "index" was set to no and changing it.
> Are there bad things to tweak in the config file that will make
> my backups unreliable?
Well, you can certainly break things if you leave a broken
configuration, but simply adding or removing disks from the disklist
or modifying index shouldn't break anything.
> is the index feature ONLY for gtar backups, or does it work with
> dump as well?
It works with dump.
> Is this a static compile time issue for
> amindexd?
Hmm... The configuration name given as argument to -C should have
been passed to the server. This is very odd. Which versions of
amrecover and amindexd?
--
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: upgraded tape server & a few clients to 2.4.2p2
On Apr 25, 2001, "Ben Hyatt" <[EMAIL PROTECTED]> wrote:
> I don't understand why it's looking for an amandapass, amandates
> locally when these exist on the tape server.
Because these files are looked at by client programs, not by server
programs. So they must exist on clients that need them.
--
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: "Cannot do /usr/sbin/vxdump dumps"
On Apr 23, 2001, "Mangala Gunadasa" <[EMAIL PROTECTED]> wrote:
> grep VX config/config.h
> #define VXDUMP "/usr/sbin/vxdump"
> #define VXRESTORE "/usr/sbin/vxrestore"
> amadmin xx version | grep VXDUMP did not show anything.
Did you rebuild the server binaries from scratch after this change in
config/config.h?
--
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: access to amrecover
On Apr 24, 2001, thing <[EMAIL PROTECTED]> wrote:
> "501 No index records for host: kascha. Invalid?
> Trying kascha...
> "501 No index records for host: kascha. Invalid?
> Trying kascha.thing.dyndns.org...
> 501 No index records for host:kascha.thing.dyndns.org. Invalid?
Did you have `index yes' in the corresponding dumptype at backup time?
--
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 client for HPUX 11?
On Apr 23, 2001, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> I cannot seem to build an amanda client with the compiler that comes
> with the OS.
Why not?
--
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 server behind linux ipchains firewall
On Apr 22, 2001, Dietmar Goldbeck <[EMAIL PROTECTED]> wrote:
> - _Everyone_ from inside firewall can run an amanda server and
> request backups from the outside machine. (This is often not a big problem
> if the outside machine has only "public" content (e.g. Webserver))
> - You have to tell Amanda Client outside firewall not to do reserved
> port checking, in common-src:
Err... Wouldn't it be better to disable masquerading for requests to
amandad? Or at least get them masqueraded into privileged ports?
Don't know if the latter is possible; the former should be, as long as
you're not using private subnets. Yet another alternative is to set
up a VPN from the backup server directly to the machines outside the
firewall.
--
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: Holding disks getting full ..
On Apr 20, 2001, Gerhard den Hollander <[EMAIL PROTECTED]> wrote:
> So it looks like amdump checks if there is enough space on the holding disk
> before it starts dumping,
Yep.
> and then simply continues dumping whitout checking if the holding disk
> becomes full, until it runs in a diskfull error and aborts the dump.
It would fall over to another holding disk, if you had one.
> The right thing (imo) would be to check every time a new chunk is written,
> and if the chunk to be written would fail the holding disk free space
> criteria, it should abort the dump.
And end up aborting the dump anyway? What's the advantage?
--
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: how do you backup up 5 days to a single tape?
On Apr 19, 2001, Patrick Presto <[EMAIL PROTECTED]> wrote:
> I was hoping I could use the tapes
> and just append to the last backup taken (somehow??).
And risk having a bus reset rewind the tape and getting a week's worth
of backups overwritten? No way!
> If I did backup five days to the holding disk and then flushed the data to a
> tape, would I be able to use amrecover to restore data from any of the last
> 5 days? Would I have to do anything special to recover?
I'd hope so, but you may have to position the tape manually for
amrestore (as called by amrecover) to find the right image in the
tape. But I've never tried anything like that (restoring from a
multi-run flush tape with amrecover, not positioning the tape :-)
myself.
--
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: want only full dumps (strategy noinc)
On Apr 18, 2001, Julian R C Briggs <[EMAIL PROTECTED]> wrote:
> How do others archive a set of large filesystems onto a set of small
> tapes?
If filesystems are larger than tapes, telling Amanda to back them up
as individual sub-directories with GNU tar.
--
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: error with amlabel
On Apr 18, 2001, Jason Jin <[EMAIL PROTECTED]> wrote:
> with Amanda 2.4.2.
> rewinding, writing label DailySet1-000
> amlabel: writing endmark: I/O error
IIRC, this is fixed with:
2000-04-09 Alexandre Oliva <[EMAIL PROTECTED]>
* server-src/amlabel.c (main): Check label *after* writing end mark.
that made it to 2.4.2p2, but not to 2.4.2
--
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: problem with amanda
On Apr 19, 2001, Vicente Vives <[EMAIL PROTECTED]> wrote:
> I run amcheck and it returns :
No ERRORs nor WARNINGs, that's good.
> If i run amrecover it returns : Error connecting to server: refused
> connection
Looks like you didn't enable the amidxtaped service. That's totally
separate from amandad.
--
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: compiling --with-db=gdbm
On Apr 19, 2001, Thomas Bahls <[EMAIL PROTECTED]> wrote:
> could anyone give me a hint what options I do have to use when compiling
> with a database format other than 'text'?
Probably the best option is to change your mind. Other database
formats only are (or used to be) supported for backward
compatibility. Don't use them any more. There will soon be features
that will require the text database.
--
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: Firewall woes
On Apr 19, 2001, Kaley Davis <[EMAIL PROTECTED]> wrote:
> I also recompiled amanda on the amanda server with:
> --with-portrange=850,854 --with-udpportrange=850,854
It's the client that is affected by --with-portrange, and it's always
the server that contacts the client to open the TCP connections.
--
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
