Hi all!!
I'm having backups of this: file://adolfopa/amanda, a windows directory.
When I do amrecover, all data is ok, whithout corruptions, but the amreport
says this:
FAILURE AND STRANGE DUMP SUMMARY:
server file://adolfopa/amanda lev 0 STRANGE
What is the meaning?
Thanks.
FAILURE AND STRANGE DUMP SUMMARY:
server file://adolfopa/amanda lev 0 STRANGE
What is the meaning?
Since you didn't post the rest of the output involving this file system,
it's impossible to tell.
Look at the detailed output for this file system for lines that start
with a question mark
Hello Josh,
On Sat, Jan 13, 2001 at 06:09:37PM -0500, Josh Kuperman wrote:
All, I'm trying to figure out at the moment is the correct test config
and what I need to do to reset everything so I can run my DailySet in
production after running the test. It seems that there are certain
files
Hi,
I've finally taken the time to setup amanda fully and it seems to be
functioning well. Amanda works around the 2Gb file limitation on linux
quite well (with chunksize), but when I use amrestore to restore a file
from tape it tries to restore the fs dump as one big file. Am I supposed
to
On Jan 13, 2001, Josh Kuperman [EMAIL PROTECTED] wrote:
It seems that there are certain files which can't be separated out
in the configuration file. Specifically, the lists for the tar files
and others.
Yep
For me the ideal would be a test-mode where I could rerun repeatedly
with the
On Jan 14, 2001, Tony Magni [EMAIL PROTECTED] wrote:
I have put both entries in my .amandahosts
file, one for operator, one for root (just like on my sgi's), but on
the sgi's it works, on the linux boxes (both redhat 7) it doesn't.
IIRC, on Red Hat Linux 7, operator's home directory is
On Jan 14, 2001, Mike Cathey [EMAIL PROTECTED] wrote:
but when I use amrestore to restore a file from tape it tries to
restore the fs dump as one big file.
Use amrestore -p and pipe the results directly to restore/tar, or use
bsplit. If you don't have bsplit, the following script (not
So a few weeks ago, I finally got around to implementing (as recorded
either here in amanda-users or in -hackers; I forget) a separate
"Offsite" configuration that runs on Sundays, and does a full backup of
everything (with "no-record"). Since I had been able to (just barely!)
run amanda with a
I amchecked fine. there is no error. but when i tried to amdump, i got the
error below:
These dumps were to tape DailySet30.
The next tape Amanda expects to use is: DailySet30.
FAILURE AND STRANGE DUMP SUMMARY:
dirac /export/raid1/home/takaslo/document lev 0 FAILED [disk
I amchecked fine. there is no error. but when i tried to amdump, i got the
error below:
These dumps were to tape DailySet30.
The next tape Amanda expects to use is: DailySet30.
FAILURE AND STRANGE DUMP SUMMARY:
dirac /export/raid1/home/takaslo/document lev 0 FAILED [disk
On Sun, 14 Jan 2001, David Wolfskill wrote:
Well, as it happened, one of the file systems I back up is hovering right
around 12 GB. And as luck would have it, amanda would typically get about
30 - 35 GB on the first tape before this file system was ready to be taped.
Then taper would try to
On Jan 15, 2001, "Takayuki Murai" [EMAIL PROTECTED] wrote:
dirac /export/raid1/home/takaslo/document lev 0 FAILED [disk
/export/raid1/home/takaslo/document offline on dirac?]
What does dirac:/tmp/amanda/sendsize.debug say?
--
Alexandre Oliva Enjoy Guarana', see
12 matches
Mail list logo
