RE: I'm back!

2003-10-20 Thread Dana Bourgeois
Actually as of (I think) about 1986 when the copyright laws were overhauled,
you don't have to state a copyright to have one.  Prior to that if you
didn't state your work was copyrighted, you forfeited copyright.  Since
then, you have an implicit copyright on everything you produce that is
copyrightable although the lawyers will tell you that putting the copyright
notice on it is still a good idea.

Thus, if you can show that you created the material and they later possessed
it in the act of transmitting it for you, (headers ought to suffice), I
would expect you would have no problem in showing that you, not they, are
copyright holder.  Now, if you signed over to them, as part of your account
creation, your copyrights to all your mail that might be different.

Hopefully this information is not wrong due to the Digital Millenium
Actso much sh*t slid through in that bill I think even the special
interests were surprised.


Dana Bourgeois
Not a lawyer, don't play one on TV

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Gene Heskett
> Sent: Monday, October 20, 2003 5:55 PM
> To: Galen Johnson
> Cc: [EMAIL PROTECTED]
> Subject: Re: I'm back!
> 
> 
> On Monday 20 October 2003 13:53, Galen Johnson wrote:
> >Gene Heskett wrote:
> >>I think, some jet lag though...
> >
> >OK Gene...I have to ask...Why are you copyrighting your email?
> >
> >=G=
> 
> Because of yahoo's TOS. (of a couple of years ago, I don't know their 
> current TOS)  Someone had emailed me a copy quite some time ago after 
> I was discussing something that if developed, might have been 
> meagerly profitable.  He was attempting to show me that according to 
> that TOS, they could take my idea and there wasn't anything I could 
> do about it.  Their TOS at the time attempts to pre-empt your rights, 
> trying to put a blanket copyright on every message that passes thru 
> their hardware.
> 
> Yahoo has an attitude reminiscent of a Mr. Gates product EULA.  So I 
> figure if I have a stated prior copyright, maybe I can catch them 
> with their legal drawers at half mast someday.  I'd enjoy that I 
> think.
> 
> But its more related to principles than any profit related motives as 
> I realisticly view it as more of a method to harrass some dingleberry 
> attorney than anything else.  All based of course on that old saw 
> about "first we kill all the lawyers" which I believe is a quote from 
> a Shakespear play, so its not even remotely close to current.
> 
> But I am in favor of that solution vis-a-vis lawyers anyway...
> 
> IIRC C-Net also has such a TOS rider.
> 
> -- 
> Cheers, Gene
> AMD [EMAIL PROTECTED] 320M
> [EMAIL PROTECTED]  512M
> 99.27% setiathome rank, not too shabby for a WV hillbilly 
> Yahoo.com attornies please note, additions to this message by 
> Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, 
> all rights reserved.
> 
> 




Re: I'm back!

2003-10-20 Thread Gene Heskett
On Monday 20 October 2003 13:53, Galen Johnson wrote:
>Gene Heskett wrote:
>>I think, some jet lag though...
>
>OK Gene...I have to ask...Why are you copyrighting your email?
>
>=G=

Because of yahoo's TOS. (of a couple of years ago, I don't know their 
current TOS)  Someone had emailed me a copy quite some time ago after 
I was discussing something that if developed, might have been 
meagerly profitable.  He was attempting to show me that according to 
that TOS, they could take my idea and there wasn't anything I could 
do about it.  Their TOS at the time attempts to pre-empt your rights, 
trying to put a blanket copyright on every message that passes thru 
their hardware.

Yahoo has an attitude reminiscent of a Mr. Gates product EULA.  So I 
figure if I have a stated prior copyright, maybe I can catch them 
with their legal drawers at half mast someday.  I'd enjoy that I 
think.

But its more related to principles than any profit related motives as 
I realisticly view it as more of a method to harrass some dingleberry 
attorney than anything else.  All based of course on that old saw 
about "first we kill all the lawyers" which I believe is a quote from 
a Shakespear play, so its not even remotely close to current.

But I am in favor of that solution vis-a-vis lawyers anyway...

IIRC C-Net also has such a TOS rider.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.



Re: Question about new client setup

2003-10-20 Thread Eric Siegerman
On Mon, Oct 20, 2003 at 11:53:34AM -0700, Dana Bourgeois wrote:
>   alta   / lev 0 FAILED [disk / offline on alta?]

I hate that message; it's extremely misleading.  Besides what it
says, it can also mean that sendsize was unable to parse the
output of whatever subcommand it ran.  That in turn can be
because it used the wrong subcommand entirely (e.g.
/usr/ccs/bin/dump instead of ufsdump on a Solaris box).  Only
rarely, it seems, does "disk foo offline" actually mean that disk
foo was offline :-(

Try looking in the "amdump" file and the various debug files
(especially the sendsize* ones on the clients in question).

> I'm wondering if it's the mismatch between
> client version and server.

Unknown, but docs/UPGRADE doesn't mention it (and it does mention
an earlier incompatibility, so that'd be the place to look).  I'd
try to rule out other problems first.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
When I came back around from the dark side, there in front of me would
be the landing area where the crew was, and the Earth, all in the view
of my window. I couldn't help but think that there in front of me was
all of humanity, except me.
- Michael Collins, Apollo 11 Command Module Pilot



Re: recommendation needed

2003-10-20 Thread Eric Siegerman
On Fri, Oct 17, 2003 at 06:43:40PM -0400, Jon LaBadie wrote:
> I tried some throughput checks today.  Test one was a "cp -r"
> of a directory tree with 8.5GB (only a few large files) and
> test two was a ufsdump of a 1GB partition.  Both gave between
> 3 and 3.5MB/sec rates to the NFS device.  That certainly is
> higher than the 1MB/sec I get to tape, but quite a bit lower
> than the rate to a local disk.

NFS-2 write performance is lousy, since the server needs to
effectively fsync() on every write() call before it returns
status to the client.  (I suspect that one tends to notice this
with large files more than with small ones, because we expect
lots-of-small-file performance to be worse in any case.)

NFS-3 is supposed to be better, as is FreeBSD's "nqnfs" (the "nq"
stands for "not quite"), but I've never tried either.

Here's a test, in addition to the ones Tony suggested:
  - Try copying a single large file from local disk to the
NFS-mounted drive
  - Try copying the same large file, to the same partition on the
NFS server, using FTP (if you use scp instead, turn off
compression to keep it from becoming CPU-bound and confusing
things)

Comparing the length of time for those two tests will tell you
how much of the problem is in NFS itself, and how much is in the
lower layers of the networking subsystem.

Also, if you can sit beside the Snap Server when doing those
tests, listen to it.  If its disks make noise when they seek, I
bet you'll hear a *lot* more of that during the NFS test than
during the FTP one.  If there's a disk-activity LED, you might
see a difference there too.  (I don't know how this manifests in
more scientific measurements like iostat results, if it does at
all...  The completely unscientific seek-rattle is more
viscerally convincing anyway; at least I found it so :-)

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
When I came back around from the dark side, there in front of me would
be the landing area where the crew was, and the Earth, all in the view
of my window. I couldn't help but think that there in front of me was
all of humanity, except me.
- Michael Collins, Apollo 11 Command Module Pilot



Re: tape type for HP DDS3 C5708A

2003-10-20 Thread Eric Siegerman
On Sat, Oct 18, 2003 at 03:29:13PM -0400, Jon LaBadie wrote:
> On Sat, Oct 18, 2003 at 11:24:05PM +0530, Rohit Peyyeti wrote:
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   localhost  /h lev 0 FAILED [dumps too big, but cannot incremental dump new disk]
> >   [plus three more of the same]
> 
> This suggests to me that the DLE's are each larger than your tape.

I don't think so.  In that case, the message would have been
"dump larger than tape, but cannot yada yada" (Phase 1 of
delay_dumps()).

The "dumps too big" variant comes from Phase 2, when a full dump
is due, but planner wants to postpone it and do an incremental
instead, to fit all the DLEs onto the tape.  In the case of a new
disk, as you pointed out, the do-an-incremental-instead option
isn't possible, so planner's only choice is to skip the DLE
entirely.

Rohit:

The answer, as Jon said, is to add DLEs a few at a time -- or, in
your case, it looks like *one* at a time :-(, so as not to ask
Amanda to put more on a tape than will fit.

Or else just don't worry about it; leave all of the DLEs in there
and let them fight it out for tape space :-)  Sooner or later,
they'll all make it onto tape, as //windows/UsersG3 did this
time.  I doubt that it'll happen any faster if you follow the
usual advice and only add them slowly.  The only advantages of
doing it that way are:
  - you won't get Amanda shouting at you that YOUR BACKUPS
FAILED!!

  - if some DLEs are more important to back up than others, you
get to put those into the backup system first, rather than
letting Amanda choose randomly which one(s) to add in any
given run


> > --> some NT_STATUS_OBJECT_NAME_NOT_FOUND errors <--

Someone recently posted a solution to that, I think.  Couldn't
hurt to check the archives for it.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
When I came back around from the dark side, there in front of me would
be the landing area where the crew was, and the Earth, all in the view
of my window. I couldn't help but think that there in front of me was
all of humanity, except me.
- Michael Collins, Apollo 11 Command Module Pilot



Re: How to control which tape is next?

2003-10-20 Thread Mads Pultz
Hi.

Thanks for all your replies. I'm not through my tapecycle yet so that is
probably the reason.

Regards
Mads

On Mon, 2003-10-20 at 21:34, Frank Smith wrote:
> --On Monday, October 20, 2003 20:39:45 +0200 Mads Pultz <[EMAIL PROTECTED]> wrote:
> 
> > Hi.
> > 
> > I have the following settings.
> > 
> > dumpcycle 3 days 
> > runspercycle 3 days
> > tapecycle 8 tapes
> > 
> > runtapes 1
> > tapedev "/dev/nst0"
> > 
> >> From the backup report that is sent to me every day everything seems to
> > be fine. However, there is one thing that bugs me. The report begins
> > like this
> > 
> > These dumps were to tape Daily006.
> > The next tape Amanda expects to use is: a new tape.
> > 
> > However, I would like AMANDA to only accept the immediate subsequent
> > tape (in this case tape Daily007). In this at all possible? If so what
> > am I doing wrong. I messed around with the chg-manual script for a while
> > but without any luck.
> 
> I'm guessing that all your tapes aren't in your tapelist, so all
> Amanda knows is that its not yet time to reuse any of the ones it knows
> about, so its asking for a new tape.
>Once your tapelist is as long or longer than your tapecyle Amanda
> will ask for the oldest one in the tapelist (oldest meaning the tape
> last written to the longest time ago). 
> 
> Frank
> 
> > 
> > Any help would be appreciated.
> > 
> > Mads
-- 
Mads Pultz
Systems Architect

Nordija A/S
Gladsaxevej 382
DK - 2860 Søborg
Denmark

Email: [EMAIL PROTECTED]

Phone Office: +45 70 20 25 10
Phone Mobile: +45 30 94 58 63





Re: How to control which tape is next?

2003-10-20 Thread Frank Smith
--On Monday, October 20, 2003 20:39:45 +0200 Mads Pultz <[EMAIL PROTECTED]> wrote:

> Hi.
> 
> I have the following settings.
> 
> dumpcycle 3 days 
> runspercycle 3 days
> tapecycle 8 tapes
> 
> runtapes 1
> tapedev "/dev/nst0"
> 
>> From the backup report that is sent to me every day everything seems to
> be fine. However, there is one thing that bugs me. The report begins
> like this
> 
> These dumps were to tape Daily006.
> The next tape Amanda expects to use is: a new tape.
> 
> However, I would like AMANDA to only accept the immediate subsequent
> tape (in this case tape Daily007). In this at all possible? If so what
> am I doing wrong. I messed around with the chg-manual script for a while
> but without any luck.

I'm guessing that all your tapes aren't in your tapelist, so all
Amanda knows is that its not yet time to reuse any of the ones it knows
about, so its asking for a new tape.
   Once your tapelist is as long or longer than your tapecyle Amanda
will ask for the oldest one in the tapelist (oldest meaning the tape
last written to the longest time ago). 

Frank

> 
> Any help would be appreciated.
> 
> Mads



-- 
Frank Smith  [EMAIL PROTECTED]
Systems Administrator   Voice: 512-374-4673
Hoover's Online   Fax: 512-374-4501



Re: How to control which tape is next?

2003-10-20 Thread Paul Bijnens
Mads Pultz wrote:

I have the following settings.

dumpcycle 3 days 
runspercycle 3 days
tapecycle 8 tapes

runtapes 1
tapedev "/dev/nst0"
From the backup report that is sent to me every day everything seems to
be fine. However, there is one thing that bugs me. The report begins
like this
These dumps were to tape Daily006.
The next tape Amanda expects to use is: a new tape.
Amanda takes the next tape found in your tapelist file, the one last in
the file, unless there are not yet enough tapes, i.e. less than
tapecycle, in the file. When you run amlabel, amanda adds the tape with 
date "0" to the list (usually to the top).
If you have already 8 tapes in your tapelist file, then amanda will
ask for the next tape, just as you expect.  (At least on the version
I use: 2.4.4p1.)


However, I would like AMANDA to only accept the immediate subsequent
tape (in this case tape Daily007). In this at all possible? If so what
am I doing wrong. I messed around with the chg-manual script for a while
but without any luck.
What has this to do with chg-manual actually?

--
Paul @ Home


Re: rename amanda clients

2003-10-20 Thread Michael Evans
I recognice the problem. Among other things I needed to switch 
from localhost to the correct host name :-(

Two reservations:
1. I am no shell script expert. There is only a little error checking, 
so this could bite you.

2. The technique is not based on any official Amanda 
documentation. It worked for me when I needed it with 2.4.2p1 and 
RedHat 8.0.

Please feel free to comment, correct or ignore
/Mike


From:   Thomas Franz <[EMAIL PROTECTED]>
Organization:   DSS Incore Service GmbH
To: [EMAIL PROTECTED]
Subject:rename amanda clients
Date sent:  Mon, 20 Oct 2003 14:50:03 +0200

> Hello, 
> 
> sometimes, I have to rename a server(amanda client) in this case: 
> server.domain1 -> server.domain2
> ( a server is moving into another zone)
> 
> Now, I have changed the disklist , the directories in "index-dir" and all
> occurances in "log.*" . But, if I want to restore a file with amrecover,
> it does not work, because on the tape  there is still the old name ( of
> course !).
> 
> -debug-file--
> amidxtaped: time 0.073: amandahosts security check passed
> amidxtaped: time 0.073: > CONFIG=DailySet1
> amidxtaped: time 0.073: > LABEL=DailySet1-077
> amidxtaped: time 0.073: > FSF=16
> amidxtaped: time 0.073: > HEADER
> amidxtaped: time 0.073: > DEVICE=/dev/nsa0
> amidxtaped: time 0.073: > HOST=^server.domain2$
> amidxtaped: time 0.073: > DISK=^/home$
> amidxtaped: time 0.073: > DATESTAMP=20031011
> amidxtaped: time 0.073: > END
> amidxtaped: time 0.075: amrestore_nargs=0
> amidxtaped: time 0.075: Ready to execv amrestore with:
> path = /usr/local/sbin/amrestore
> argv[0] = "amrestore"
> argv[1] = "-p"
> argv[2] = "-h"
> argv[3] = "-l"
> argv[4] = "DailySet1-077"
> argv[5] = "-f"
> argv[6] = "16"
> argv[7] = "/dev/nsa0"
> argv[8] = "^server.domain2$"
> argv[9] = "^/home$"
> argv[10] = "20031011"
> amrestore:  16: skipping server.domain1._home.20031011.0
> amrestore:  17: skipping 1.domain1._etc.20031011.0
> .
> amrestore:  35: reached end of tape: date 20031013
> amidxtaped: time 163.109: amrestore terminated normally with status: 1
> amidxtaped: time 163.109: rewinding tape ... amidxtaped: time 206.223:
> done amidxtaped: time 206.223: pid 18486 finish time Mon Oct 20 11:12:21
> 2003 end of debug-file--
> 
> Is there any workaround to keep the database before renaming a server ?
> 
> 
> best regards
> 
> Thomas Franz


-- 
Michael Evans [EMAIL PROTECTED]


mv-disk.zip
Description: Zip archive


Question about new client setup

2003-10-20 Thread Dana Bourgeois
I'm on 2.4.1 over Solaris 2.5.1 (maybe 2.6 - I didn't write it down).
Anyway, I have several new Suse 8.1 clients to backup.  Suse came with 2.4.2
already installed so I configured the client and ran amcheck.  Finished fine
and clients responded.  However, when it came time to run the backup, these
clients were not successful.  I'm wondering if it's the mismatch between
client version and server.  For some reason I was thinking at the time that
a later client would be OK but now I'm thinking that a new server should be
backwards compatible with an older client but not necessarily the other way
'round.  Alta, tahihiti and london have been 'adding new disk' several times
now (see the NOTES).  Is that a clue?


Dana Bourgeois

# Possibly relevant amdump
report...

These dumps were to tape daily02.
Tonight's dumps should go onto 1 tape: daily03.

FAILURE AND STRANGE DUMP SUMMARY:
  alta   / lev 0 FAILED [disk / offline on alta?]
  tahiti / lev 0 FAILED [disk / offline on tahiti?]
  london / lev 0 FAILED [disk / offline on london?]


STATISTICS:
  Total   Full  Daily
      
Dump Time (hrs:min)   11:48  10:26   0:03   (0:14 start, 1:04
idle)
Output Size (meg)   10099.3 9771.8  327.6
Original Size (meg) 22932.222183.7  748.5
Avg Compressed Size (%)44.0   44.0   43.8
Tape Used (%)  94.4   91.33.1   (level:#disks ...)
Filesystems Dumped   36 12 24   (1:23 2:1)
Avg Dump Rate (k/s)   322.0  336.0  143.8
Avg Tp Write Rate (k/s)   273.7  266.2 1732.0
NOTES:
  planner: Adding new disk alta:/.
  planner: Adding new disk tahiti:/.
  planner: Adding new disk london:/.
  taper: tape daily02 kb 11315392 fm 37 [OK]

DUMP SUMMARY:
  DUMPER STATS  TAPER
STATS
HOSTNAME  DISK   L  ORIG-KB   OUT-KB COMP%  MMM:SS   KB/s  MMM:SS
KB/s
-- --
--
alta  /  0   FAILED

london/  0   FAILED

tahiti/  0   FAILED


(brought to you by Amanda version 2.4.1p1)




How to control which tape is next?

2003-10-20 Thread Mads Pultz
Hi.

I have the following settings.

dumpcycle 3 days 
runspercycle 3 days
tapecycle 8 tapes

runtapes 1
tapedev "/dev/nst0"

>From the backup report that is sent to me every day everything seems to
be fine. However, there is one thing that bugs me. The report begins
like this

These dumps were to tape Daily006.
The next tape Amanda expects to use is: a new tape.

However, I would like AMANDA to only accept the immediate subsequent
tape (in this case tape Daily007). In this at all possible? If so what
am I doing wrong. I messed around with the chg-manual script for a while
but without any luck.

Any help would be appreciated.

Mads



Re: I'm back!

2003-10-20 Thread Galen Johnson
Gene Heskett wrote:

I think, some jet lag though...

 

OK Gene...I have to ask...Why are you copyrighting your email?

=G=



Samba 3.0 and Amanda 2.4.4p1

2003-10-20 Thread Stefan G. Weichinger
Hi, amanda-users,

I am planning to upgrade my customers server to Samba 3.0 this week.
I would also like to upgrade their Amanda-server to Samba 3.0, to be
up-to-date.

As I noticed on Sept. 25th, Amanda did not work with Samba 3.0.
I was on vacation for two weeks now and had disabled my
amanda-users-subscription for this time ...

Has Gregor already sent his patch? ;-)
Has someone else a patch?

--

Another question:

Does anyone know if I can disable the eject button on a HP-DAT-drive?
It´s one of those HP Surestore 20/40 GB things, I don´t know the exact
number know, but can look it up if needed.

Thank you,
Stefan G. Weichinger

mailto:[EMAIL PROTECTED]




RE: backups stopped after upgrade to redhat 9?

2003-10-20 Thread Amanda Admin
Maybe I'm off base, but haven't there been some recent threads about changes
in signal handling in RH 9? I think a patch to amanda 2.4.4 was posted to
fix the problem.

Search the archives for redhat 9, or SIG -- should be within the last two
months.

Note that I don't have RH9, so I haven't had this problem nor had to apply
the patch.

Doug

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of C.Scheeder
> Sent: Sunday, October 19, 2003 11:35 PM
> To: dwtrusty
> Cc: [EMAIL PROTECTED]
> Subject: Re: backups stopped after upgrade to redhat 9?
>
>
> Hi,
> check your local firewall-settings.
> Even if you didn't change them or set them up there may be some.
> RH has decided around V8 to implement restrictive firewallrules
> as default, without asking for confirmation for doing it.
> That problem bit many other amanda-users before you.
> Christoph
>
> dwtrusty schrieb:
> > Thanks for the tips.
> >
> > All the low-level commands seem to be in order.
> >
> > I can use ammt, mt, amtape, mtx successfully.  I can use tar to write
> > to the tape, and read the contents back.  Amcheck shows no errors.
> >
> > I'm using version 2.4.3.
> >
> > What else should I check?
> >
> > Thanks,
> >
> > David
> >
> >
> >
> >
> > --- In [EMAIL PROTECTED], Jon LaBadie <[EMAIL PROTECTED]> wrote:
> >
> >>On Sat, Oct 18, 2003 at 10:21:21PM -0500, David Trusty wrote:
> >>
> >>>Hi,
> >>>
> >>>After I upgraded my system to redhat 9, the backups have quit working.
> >>>
> >>>The file "/var/lib/DailySet1/amdump" ends with this line:
> >>>  taper: stream_accept: timeout after 120 seconds
> >>>
> >>
> >>Step back.  After the upgrade:
> >>
> >>Can you write to your tape with things like dd?
> >>Do mt commands work with your tape drive?
> >>How about ammt?
> >>If it is a changer, can you manipulate it with mtx?
> >>Do amtape commands work?
> >>What does amcheck say?
> >>
> >>--
> >>Jon H. LaBadie  [EMAIL PROTECTED]
> >> JG Computing
> >> 4455 Province Line Road(609) 252-0159
> >> Princeton, NJ  08540-4322  (609) 683-7220 (fax)
> >
> >
>



Re: rename amanda clients

2003-10-20 Thread Jon LaBadie
On Mon, Oct 20, 2003 at 02:50:03PM +0200, Thomas Franz wrote:
> Hello, 
> 
> sometimes, I have to rename a server(amanda client) in this case: 
> server.domain1 -> server.domain2
> ( a server is moving into another zone)
> 
> Now, I have changed the disklist , the directories in "index-dir" and 
> all occurances in "log.*" .
> But, if I want to restore a file with amrecover, it does not work, because
> on the tape  there is still the old name ( of course !).
...
> Is there any workaround to keep the database before renaming a server ?

Just a thought about workarounds outside of amanda.

On the unix systems with which I'm familiar, a single NIC can service
multiple IP's.  Each system seems to have its one administration technique
to implement this.  But for example, the system I'm writing this on is
using a single NIC to represent itself X.Y.Z.60 and the network DNS server,
X.Y.Z.2.

Perhaps for a period, corresponding to how long the tapes current tapes
are valid, you could maintain two DNS entries and IP's for the client.
Then it could backup/restore under the new name, and restore old stuff
under the old one.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)


rename amanda clients

2003-10-20 Thread Thomas Franz
Hello, 

sometimes, I have to rename a server(amanda client) in this case: 
server.domain1 -> server.domain2
( a server is moving into another zone)

Now, I have changed the disklist , the directories in "index-dir" and 
all occurances in "log.*" .
But, if I want to restore a file with amrecover, it does not work, because
on the tape  there is still the old name ( of course !).

-debug-file--
amidxtaped: time 0.073: amandahosts security check passed
amidxtaped: time 0.073: > CONFIG=DailySet1
amidxtaped: time 0.073: > LABEL=DailySet1-077
amidxtaped: time 0.073: > FSF=16
amidxtaped: time 0.073: > HEADER
amidxtaped: time 0.073: > DEVICE=/dev/nsa0
amidxtaped: time 0.073: > HOST=^server.domain2$
amidxtaped: time 0.073: > DISK=^/home$
amidxtaped: time 0.073: > DATESTAMP=20031011
amidxtaped: time 0.073: > END
amidxtaped: time 0.075: amrestore_nargs=0
amidxtaped: time 0.075: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "-l"
argv[4] = "DailySet1-077"
argv[5] = "-f"
argv[6] = "16"
argv[7] = "/dev/nsa0"
argv[8] = "^server.domain2$"
argv[9] = "^/home$"
argv[10] = "20031011"
amrestore:  16: skipping server.domain1._home.20031011.0
amrestore:  17: skipping 1.domain1._etc.20031011.0
.
amrestore:  35: reached end of tape: date 20031013
amidxtaped: time 163.109: amrestore terminated normally with status: 1
amidxtaped: time 163.109: rewinding tape ...
amidxtaped: time 206.223: done
amidxtaped: time 206.223: pid 18486 finish time Mon Oct 20 11:12:21 2003
end of debug-file--

Is there any workaround to keep the database before renaming a server ?


best regards

Thomas Franz


I'm back!

2003-10-20 Thread Gene Heskett
I think, some jet lag though...

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.21% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.