Dustin J. Mitchell wrote:
On Fri, Mar 26, 2010 at 1:02 PM, Michael Mueskens wrote:
Well ok, we don't have to talk about backing up running databases, the best way
in my opinion to do a db-backup is to dump the databases (e.g. mysqldump) and
then backup these dumps via amanda.
Or, if
On Fri, Mar 26, 2010 at 3:23 PM, Chris Hoogendyk
wrote:
> Does that mean that the planner understands this and will arrange for fulls
> and incrementals in the same fashion as for ordinary partition backups with
> ufsdump or gnutar?
Yep!
> Now, what about MySQL? I know that starts to conflict wi
On Fri, Mar 26, 2010 at 2:40 PM, Michael Mueskens wrote:
>> Jean-Louis' suggestion is a good one for this case.
>
> So far I haven't had the time to take a look into 3.1, but it sounds very
> interesting.
>
>>
>> I had forgotten that ampgsql makes this easily configurable already,
>> using the STR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dustin J. Mitchell schrieb:
> On Fri, Mar 26, 2010 at 1:02 PM, Michael Mueskens wrote:
> Or, if you're using postgres, use ampgsql.
> http://code.v.igoro.us/archives/50-Whats-New-in-Amanda-Postgres-Backups.html
I'm sorry, but we're using that only
On Fri, Mar 26, 2010 at 12:36 PM, Valeriu Mutu wrote:
> I have Amanda setup and working successfully (thanks to the development
> team). Nevertheless, I can't restore files when 'amdump' is running. I'm
> using the 'chg-zd-mtx' tape changer.
>
> This is what I get from 'amrecover' when I try to
Hi,
I have Amanda setup and working successfully (thanks to the development team).
Nevertheless, I can't restore files when 'amdump' is running. I'm using the
'chg-zd-mtx' tape changer.
This is what I get from 'amrecover' when I try to do a recovery in such a
scenario:
/var/lib/amanda/Daily1/
On Fri, Mar 26, 2010 at 1:02 PM, Michael Mueskens wrote:
> Well ok, we don't have to talk about backing up running databases, the best
> way
> in my opinion to do a db-backup is to dump the databases (e.g. mysqldump) and
> then backup these dumps via amanda.
Or, if you're using postgres, use amp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dustin J. Mitchell schrieb:
> Amdump's exit statuses are here, by the way:
> http://wiki.zmanda.com/man/amdump.8.html
>
> We've kept the strange messages as a distinct error because they *can*
> represent data loss. For example, if your accounts_re
With the amgtar application (in 3.1.0), an exit status of 1 from runtar
is not an error.
"file changed as we read it" will still result in STRANGE result, but
you can add a regex to turn it into a SUCCESS.
Jean-Louis
Toomas Aas wrote:
Hello!
I upgraded Amanda from 2.5.1p3 to 2.6.1p2 on my Fr
On Friday 26 March 2010, Michael Mueskens wrote:
>Gene Heskett schrieb:
>> On Friday 26 March 2010, Michael Mueskens wrote:
>>> how exactly did you do that? Did you change something in the
>>> amanda-source? Is this error output not from the client, so you have to
>>> patch something in the amanda-
On Fri, Mar 26, 2010 at 10:32 AM, Gene Heskett wrote:
> In bash, you can assign that error and process accordingly. Here is a
> snippet of that part of my wrapper script, with the language sanitized
> for the list:
>
> ${AM_SBIN_DIR}/amdump $CONFIGNAME $HOST $DLE >> $LOG
> SCS=$?
>
On Friday 26 March 2010, Dustin J. Mitchell wrote:
>On Fri, Mar 26, 2010 at 7:53 AM, Gene Heskett
wrote:
>> I just installed the amanda-3.1.0rc16-20100325 snapshot and amrecover
>> still fails:
>
>Gene, this is the bug you caught a few days ago. I only committed the
>fix to it about 5 minutes ag
On Fri, Mar 26, 2010 at 9:08 AM, Alan Bunch wrote:
> I am looking at Amanda as a new backup server. I have a two drive, 40 slot
> changer.
>
> Is the recommended setup to use two Amanda configurations, one for each tape
> drive, or have I missed something in the documentation ?
>
> Is this supp
On Fri, Mar 26, 2010 at 8:11 AM, Gene Heskett wrote:
> the 3.2alpha for 0325 also fails, but the 0319 version Just Works(TM)
And apologies for the short response previously. The bug has now been
reported a half-dozen times by our internal QA team, and 3 times by
you. :)
It does show that we're
On Fri, Mar 26, 2010 at 7:53 AM, Gene Heskett wrote:
> I just installed the amanda-3.1.0rc16-20100325 snapshot and amrecover still
> fails:
Gene, this is the bug you caught a few days ago. I only committed the
fix to it about 5 minutes ago, so I'm not surprised it's still
failing!
I was just g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gene Heskett schrieb:
> On Friday 26 March 2010, Michael Mueskens wrote:
>> how exactly did you do that? Did you change something in the
>> amanda-source? Is this error output not from the client, so you have to
>> patch something in the amanda-client-
On Friday 26 March 2010, Michael Mueskens wrote:
>Gene Heskett schrieb:
>> On Friday 26 March 2010, Toomas Aas wrote:
>> It has been a while since I visited my wrapper scripts, but ISTR I had
>> to train my scripts that an error return of 1 was perfectly ok.
>
>hello Gene,
>
>how exactly did you do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gene Heskett schrieb:
> On Friday 26 March 2010, Toomas Aas wrote:
> It has been a while since I visited my wrapper scripts, but ISTR I had to
> train my scripts that an error return of 1 was perfectly ok.
hello Gene,
how exactly did you do that? Di
I am looking at Amanda as a new backup server. I have a two drive, 40
slot changer.
Is the recommended setup to use two Amanda configurations, one for each
tape drive, or have I missed something in the documentation ?
Is this supported in a single configuration ?
Thanks in advance.
Alan
Greetings;
the 3.2alpha for 0325 also fails, but the 0319 version Just Works(TM)
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
He whom opens thee Windows invites the bugs in.
Greetings folks;
I just installed the amanda-3.1.0rc16-20100325 snapshot and amrecover still
fails:
[r...@coyote amanda]# amrecover
AMRECOVER Version 3.1.0rc16. Contacting server on coyote.coyote.den ...
220 coyote AMANDA index server (3.1.0rc16) ready.
Setting restore
On Friday 26 March 2010, Toomas Aas wrote:
>On 25.03.2010 08:03, Toomas Aas wrote:
>> So it seems that the FAILURE DUMP SUMMARY is incorrect about
>> listing this DLE as failed.
>
>As a workaround, I switched this DLE to "estimate calcsize". Tonight's run
>went fine.
>
>--
>Toomas
>
It has been a w
On 26/03/2010 13:40, Dustin J. Mitchell wrote:
On Thu, Mar 25, 2010 at 8:45 PM, Jobst Schmalenbach
wrote:
I think this is a DNS problem AND apache, further when typing
the IP address 216.34.181.97 it yiilds the same webpage (f5.txt).
At the moment, though, it looks li
23 matches
Mail list logo
