Greetings folks;
from /tmp/amanda-dbg/amandad/tonights file:
-
amandad: time 0.220: try_socksize: receive buffer size is 65536
amandad: time 0.220: stream_server: waiting for connection: ::.41697
amandad: time 0.220: sending REP pkt:
CONNECT DATA 44889 MESG 54361 INDEX
On 2007-06-25 22:43, Chris Hoogendyk wrote:
Jon LaBadie wrote:
On Mon, Jun 25, 2007 at 12:43:50PM -0400, Chris Hoogendyk wrote:
...
then I created a dumptype that was the same as my regular dumps but with
record no
strategy incronly
Instead of making it a different configuration, and
On 2007-06-26 09:17, Gene Heskett wrote:
Greetings folks;
from /tmp/amanda-dbg/amandad/tonights file:
-
amandad: time 0.220: try_socksize: receive buffer size is 65536
amandad: time 0.220: stream_server: waiting for connection: ::.41697
amandad: time 0.220: sending
On Tue, Jun 26, 2007 at 09:29:52AM +0200, Paul Bijnens wrote:
I'm not 100% certain, but I believe you may even erase (some of) the
holdingdisk files, without flushing. I think that Amanda will take into
account that the holdingdisk file disappeared, and schedule the same
incremental level
Fellow AMANDA users,
In the past, I remember seeing something about AMANDA having trouble
when there are a large number of disklist entries. First, am I
remembering correctly, and second what constitutes a large number
of entries? My current backup plan is to have about 1500-2000 entries
Kevin, thanks so much. You were right on the money. Disabling the
firewall completely allow amcheck to work correctly.
If you have some additional patience, I could use a hand trying to
configure the firewall rules correctly on my amanda client. I tried to
follow the directions at
On Tue, Jun 26, 2007 at 10:38:33AM -0400, Zembower, Kevin enlightened us:
Kevin, thanks so much. You were right on the money. Disabling the
firewall completely allow amcheck to work correctly.
If you have some additional patience, I could use a hand trying to
configure the firewall rules
Hi,
Is it possible to have 2 configs using 2 separate drives in a tape
robot, i.e. can they share the changer interface? I don't mean use of
RAIT.
I have successfully set up 1 config with chg-zd-mtx then tried
duplicating that to a 2nd config using chg-zd-mtx with a different set
of tapes in
On Tue, 26 Jun 2007 at 4:58pm, Weber, Philip wrote
Is it possible to have 2 configs using 2 separate drives in a tape
robot, i.e. can they share the changer interface? I don't mean use of
RAIT.
I have successfully set up 1 config with chg-zd-mtx then tried
duplicating that to a 2nd config
On Tuesday 26 June 2007 11:58:00 Weber, Philip wrote:
Is it possible to have 2 configs using 2 separate drives in a tape
robot, i.e. can they share the changer interface? I don't mean use of
RAIT.
The answer to your question is yes, but you must ensure that only one instance
of mtx is
Hello again.
In my struggle to get a working amanda config (working for my strange
setup :)
I reached the following decision:
I'll use two configs,
- Weekly, which does level-0 dumps to tape (using chg-zd-mtx)
- Daily, which does incrementals to a virtual tape on disk
(using chg-disk)
As it is
* Joshua Baker-LePain [EMAIL PROTECTED] [20070626 12:32]:
On Tue, 26 Jun 2007 at 4:58pm, Weber, Philip wrote
Is it possible to have 2 configs using 2 separate drives in a tape
robot, i.e. can they share the changer interface? I don't mean use of
RAIT.
I have successfully set up 1 config
On Tue, 26 Jun 2007 at 12:57pm, Jean-Francois Malouin wrote
I'll just add that you must also configure amanda such that both
configs use different ports with '--with-testing=config1' and
'--with-testing=config2' and add those to /etc/services like
amanda-config110080/tcp
amanda-config1
Hi Harald,
I'm going to ignore your details and key on the concept : you want to
have a weekly and a daily back up.
I wanted to do this too and went down the path of investigating multiple
configurations like you are doing. But it really bugged me that I have
to basically do 2 level-0
Matt, thank you for your help. I didn't think that I had
ip_conntrack_amanda, so I was trying to set it up without it. When I
tried your way, it worked like a charm.
Note to archive readers: I think it's important to insert the line:
-A INPUT -s 192.168.1.1 -d 192.168.1.30 -p udp -m udp --dport
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wanted to do this too and went down the path of investigating multiple
configurations like you are doing. But it really bugged me that I have
to basically do 2 level-0 backups a week, one for the weekly and one for
the daily (since the daily
16 matches
Mail list logo
