unsubscribe
Ummm!
added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
added interface ip=128.84.247.9 bcast=128.84.247.255
On Apr 2, 2001, verdon [EMAIL PROTECTED] wrote:
I wanted to perform a FULL dump each sunday during 10 weeks
Jason is correct that you want "dumpcycle 0" to force the full dumps.
I just wanted to add that if these clients are also being backed up
with another configuration (e.g. daily),
On Apr 2, 2001, Sandra Panesso [EMAIL PROTECTED] wrote:
? gtar: time_t value 18446744071597657311 too large (max=68719476735)
I used to get errors like this with GNU tar 1.13. If that's the one
you're using, don't. Use GNU tar 1.13.17 or newer, or go back to 1.12
plus the patch somewhere in
On Apr 2, 2001, David Lloyd [EMAIL PROTECTED] wrote:
Steve!
Can I just remove the holding disk directories that were created? I don't
particularly want to flush these to tape, but I also don't want to break
anything.
I wouldn't "just remove" them if I were you, especially if the dumps
On Apr 3, 2001, verdon [EMAIL PROTECTED] wrote:
on tape from the config 1 ?
or the last level 0 from config 1 ?
It will ask for the last level 0 from config 1, but it will fail,
because what it really needs is that last level 0 from either config.
Note that amandates doesn't play any role at
config 1 backup from monday to friday
config 2 backup on sunday
So evry client as it's own /etc/dumpdates and if i'll try to restore
data for thursday, (i suppose backup is a level 1)
amanda will need the level 0, ask /etc/amandates, and so ask for two
tape the last incremental tape and an
Now i suppose that i have to
- let amanda doing backup for the week , and i can make an external
script that will backup tar and gzip all my client during week-end...
or
-just use one configuration in which i force full dump during the
week-end and then use: "amadmin conf no-reuse
On Apr 3, 2001, verdon [EMAIL PROTECTED] wrote:
well i think i'm going to use the first, what do you think about it?
Just set the archive configuration to use `record no', as JJ and the
FAQ recommend, and all will be fine.
--
Alexandre Oliva Enjoy Guarana', see
so, i have tried to backup data last week so actually all my clients
/etc/amandates are wrong
if i want to correct all amandates i suppose i had to force a full dump
this evening !? right?
may i clear all amanda logs on the server to restart backing up client
as the first time?
Alexandre Oliva
On Mon, 2 Apr 2001, John R. Jackson wrote:
What's the recommended procedure for temporarily removing a disklist entry?
... My solution is to just comment out the disklist entry, but I'm
not sure what effect that has on indexing, amrecover, etc.
That's what I do. You won't be able to do an
Hi All,
my GNUTAR ist 'tar-1.13.tar.gz' for sparc Solaris 7
Is ther any second entry to make in amanda.conf or anywhere?
Amanda Backup Client Hosts Check
ERROR: daphne: [GNUTAR program not available]
Client check: 1 host checked in 0.896 seconds, 1 problem
Is ther any second entry to make in amanda.conf or anywhere?
Make sure gtar is in your path before running 'configure' - assuming you're
building from source.
Add gtar to your path, re-run configure, make and make install.
-Ben
unsubscribe [EMAIL PROTECTED]
winmail.dat
Has anyone used Amanda on OS X release? Given what I've heard about
OS X, I would expect the bulk of it to work with some unknown grief
level, modulo issues about how the Mac filesystem bits appear in the
BSD tree.
Thus, my real questions are:
Is Amanda on OS X a sufficient backup scheme for
my GNUTAR ist 'tar-1.13.tar.gz' for sparc Solaris 7
Type "/path/to/gnu/tar --version" and make sure it is at least 1.13.17.
Do **not** use anything earlier than that.
ERROR: daphne: [GNUTAR program not available]
Is ther any second entry to make in amanda.conf or anywhere?
As Ben said, just
I make a special dump-type, "skip" with the 'ignore' option. ...
Ahh, that's a good idea.
And with 2.4.2, you can build dumptypes "on the fly" in the disklist,
so it could be done like this without messing with amanda.conf:
client.my.domain /first/disk a-normal-dumptype
Well, I've looked through the archives and it appears that some
people are having success with this driver. I am not one of
them.
I'm currently running redhat 6.2 with a 2.2.16 kernel. I can get
the drive to work with the ide-tape module patched according to
onstream and access it as /dev/ht0
On Tue, 3 Apr 2001, Phil Stracchino wrote:
All mine reports is 1.13. No minor version.
What, hypothetically speaking, would happen if one used tar 1.13.17?
It won't work. I built a Slack 7 box with 1.13 and it just didn't work.
Okay, to be more specific, it didn't create the index files
... I've
noticed that amanda-2.4.2p1 doesn't like broadcasts at all and will fail
dismally even though smbclient will cope. ...
Huh? How can Amanda fail and smbclient work when Amanda is doing nothing
more than call smbclient? What, exactly, does "fail dismally" mean,
i.e. what kinds of
I am a beginner ...
Welcome!
I am trying to understand this file. ...
You might read http://www.backupcentral.com/amanda.html. It is an online
chapter specifically about Amanda from a book about backups in general.
There is also information at the main Amanda web site, www.amanda.org.
Has anyone used Amanda on OS X release? ...
I just spent some time with my local Mac wizard and he says getting
Amanda working is probably not too hard (he gave me an account on his
machine, but I haven't decide whether to thank or curse him for that :-).
Getting a backup program that Amanda
Does anyone know what is the error mean? Does it mean the tape is bad?
DUMP: Date of this level 0 dump: Fri Mar 30 23:45:28 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sda8 (/u1 (dir /app/apache/product/1.3.12)) to
standard output
| DUMP: Label: none
| DUMP:
Does anyone know what is the error mean? Does it mean the tape is bad?
Well, you're not using a tape, so no :-). At this point Amanda is
running dump to a socket back to the holding disk.
It probably means the file system was active and dump got confused.
Just let it try again.
John R.
The error I see is:
"Host is down or invalid password"
Essentially my guess is that Amanda via smbclient attempts to use a
local wins server to resolve the Netbios name which didn't work because
I didn't have a wins server configured. Hence, rather than wait for the
broadcast to function (it
David Lloyd wrote:
The error I see is:
"Host is down or invalid password"
In some sense, that is the final answer.
More explicitly (and has been stated in the FAQ, and on this mailing
list inumerable times): if smbclient can't get to the windows host,
Amanda is not involved. You must
Marty!
I suggest you put your asbestos, flame resistant suit on...
Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT!
You obviously cannot understand what I am saying, or you have not
followed this thread. If you cannot understand English I will have this
translated into any other
Hi, I'm using SUN StorEdge L9 ( DLT autochenger).
After installing Amanda, I execute amcheck then I got the following error
message.
I'm wandering it's amanda configuration problem or L9 hardware problem or
DLT tape error.
Is there anyone who had same error message?
Has anybody any experience with backing up LSM drives using Amanda?
I have configured the system so that amcheck is happy, but amdump
reports disk is offline.
I have set the device permissions like so:
brw-r root system /dev/vol/rootvol (logical volume)
crw-r root system
I have not been able to get amanda to back anything up.
amcheck is fine.
amdump hangs (days) and I get an email that has MISSING under the dumper
stats . I am just trying to back up /home on the local machine.
Any thoughts before I give up and just use dump.?
amanda-2.4.2p1
OpenBSD 2.8
unsubscribe amanda-users [EMAIL PROTECTED]
32 matches
Mail list logo
