Hi,
AFAIK the portrange settings have to be applied identically at the
server and the client. You have recompiled the client with the same
settings for portrange, correct?
Christoph
Dean Pullen schrieb:
Hi all.
I have compiled Amanda using the following options:
./configure --with-user=aman
hello,
I'm a newbie to amanda and mtx. I'm running solaris 2.6(sprac). Want to
know how to configure the DDS3 autoloader to do backingup. I don't use any
commercial software. I need to use the 6 slots of the cartridge for
different filesystem backups. Also does amanda support resuming or
cont
In a message dated: Tue, 06 Apr 2004 12:12:05 BST
"William Hargrove" said:
>I was thinking I could do the incremental backups to a hard disk area on the tape
>server each night and then run Amanda once a week to archive the full backups plus
>the HDD incremental ones.
I did this once, way back w
Here's a strategy that I implemented about a month ago that is working
pretty well so far:
1. run amdump every night to large RAID w/o tape, mix of full and incr
2. run script to separate images to amanda-incr and amanda-full
3. when amanda-full exceeds size of tape, run amflush
4. when RAID appr
On Tue, Apr 06, 2004 at 12:12:05PM +0100, William Hargrove wrote:
> Hello All,
>
> I would like to ask a general Amanda backup 'strategy' question here, given
> by backup 'goals' below. I have a configured and working Amanda set-up but I
> want to try and fit a backup policy that I believe is best
Hi all.
I have compiled Amanda using the following options:
./configure
--with-user=amanda \
--mandir=/usr/share/man
\
--prefix=/usr
\
--infodir=/usr/share/info
\
--sysconfdir=/etc
\
Hello All,
I would like to ask a general Amanda backup 'strategy' question here, given
by backup 'goals' below. I have a configured and working Amanda set-up but I
want to try and fit a backup policy that I believe is best suited to our
site around Amanda.
I have an 8-tape (DLT 35/70gb each) auto
ing disk /dumps: 17528692 KB disk space available, using 17016692
KB
amcheck-server: slot 0: date 20040111 label DailySet1-13 (active tape)
amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape)
amcheck-server: slot 2: date 20040111 label DailySet1-12 (exact label
match)
NOTE: skipping tap