On Thursday, 03.04.2008 at 09:29 -0400, Matthew Moffitt wrote:
I've been through this but still don't have it working. On the
particular disk entry (backing up with gtar) encryption doesn't run
during amdump. amcheck reports the error:
WARNING: testhost:/disk1/user/srl does not support
Hi All,
this is what I see when I type amstatus DailySet1
isisrv1:/ getting estimate
isisrv1:/boot getting estimate
isisrv1:/data0 getting estimate
isisrv1:/var/loggetting estimate
isisrv2:/ getting
Hi All,
I receive the following message from amreport. Everyday!
FAILURE AND STRANGE DUMP SUMMARY:
server5/data lev 7 FAILED [dumps way too big, 88524660 KB, must skip
incremental dumps]
server3/data0/data lev 5 FAILED [dumps way too big, 70851612 KB, must
skip incremental dumps]
On 4/4/2008 4:00 AM, Dave Ewart wrote:
On Thursday, 03.04.2008 at 09:29 -0400, Matthew Moffitt wrote:
I've been through this but still don't have it working. On the
particular disk entry (backing up with gtar) encryption doesn't run
during amdump. amcheck reports the error:
WARNING:
On Fri, Apr 4, 2008 at 10:31 AM, Matthew Moffitt
[EMAIL PROTECTED] wrote:
I think an alternate informational message would help, or at least better
documentation on the requirement for using encryption. I wonder what the
client requirement check is for, perhaps it's a vestige of a previous
Greetings.
We have been running Amanda on Solaris for about 4 years.
About 3 months ago, we added a Linux system to the disklist.
Last week, there was a power outage and that host has not been
backed up since.
It is the only host that is not (or WAS not at the time :-) on a UPS.
(All my other
Since I've been this deep (holds hand above head) in trying to get encryption to
work, I've been reading and re-reading documentation and man pages. I noticed a
small typo in the amanda.conf page for the section detailing encryption in
dumptypes. Basically, for encrypt client it says to look
With all the problems I've had doing client side encryption on FreeBSD I wanted
to make sure amanda worked without any fancy options. I tried two
variations on backups:
1. No compression, no encryption, ssh authentication
2. No compression, SERVER-side encryption, ssh authentication
I'm
I've solved the problem, and I'd like to answer myself in case
someone in the future comes across the same problem. The solution was
to add the LANG=en_US env variable in the crontab before running
amdump. Although LANG=en_US in the user shell, it is not so in the
crontab environment.
Thanks -- I fixed it on the wiki, and I'll patch the codebase in a bit.
Dustin
On Fri, Apr 4, 2008 at 3:37 PM, Oscar Ricardo Silva
[EMAIL PROTECTED] wrote:
Since I've been this deep (holds hand above head) in trying to get
encryption to work, I've been reading and re-reading documentation and
10 matches
Mail list logo
