?
Presently, it is out of the box, and we run ./configure before the
make.
On Thu, 2008-05-22 at 12:38 -0400, Dustin J. Mitchell wrote:
On Wed, May 21, 2008 at 2:07 PM, Freels, James D. [EMAIL PROTECTED] wrote:
/-- aixclient hd3 lev 0 FAILED [missing size line from sendbackup]
sendbackup: start
for AMANDA and AIX. Not many folks still using AIX
these days ...
On Thu, 2008-05-22 at 15:35 -0400, Dustin J. Mitchell wrote:
On Thu, May 22, 2008 at 3:26 PM, Freels, James D. [EMAIL PROTECTED] wrote:
We took a look at uustat and the only locked files were some batch jobs
we had running
For the could not unlock /etc/amandates: Bad file number problem:
What is looking amanda choose to use? Look for LOCKING= in 'amadmin
config version' output.
Can you upgrade your client to 2.6.0p1?
Jean-Louis
Freels, James D. wrote:
We have a linux amanda server that is working fine
We have a linux amanda server that is working fine for linux boxes
connected as clients. However, we are trying to connect two additional
IBM AIX clients to this server, and having difficulty. One AIX client
is at version 5.2 of AIX, while the second is at version 5.3 of AIX.
Both AIX clients
On another system with a smaller tape drive (limited to about 4-5 GB),
I have been using the new capability in 2.5.x for manual tape changers
and spanning tapes to more than one tape per backup. This has been
working great and as expected except for the split size. Within my
dumptype statement,
Hello, I am running amanda-server 2.5.1p1-2.1 on several clients of the
same version; all under linux/debian/stable (etch). This new version
(from debian/sarge of v2.4.x vintage, have been using AMANDA for years)
has a few new features, including different messages, so I need help
interpreting
+0200, Geert Uytterhoeven wrote:
On Fri, 13 Apr 2007, Freels, James D. wrote:
I discovered today that my tape drive was dirty and did not realize it.
What happened was the drive sent a scsi error to the kernel/OS and
somehow the root (/), home (/home), and holding disk area recognized
I discovered today that my tape drive was dirty and did not realize it.
What happened was the drive sent a scsi error to the kernel/OS and
somehow the root (/), home (/home), and holding disk area recognized by
AMANDA was changed from rw access to ro access. I believe this change
was made by
I have a new set of X23 tapes from Exabyte (now Tandberg) that I want to
make sure I get the most out of with my AMANDA backup system. The tapes
are rated at 80/160 GB (uncompressed/compressed) for my VXA-2 drive. A
few questions:
1) compresstion
I read where hardware compression in the tape
:
Stefan G. Weichinger wrote:
Freels, James D. wrote:
The problem I had started at kernels greater than 2.6.12.x (starting
at 2.6.13.0) and was finally cleared at 2.6.15.0.
Interesting ... I am using that module with kernel 2.6.13 and have no
problems. Maybe this related
Do you happen to be using the aic7xxx driver ? If so, I had the same problem until the new kernel 2.6.15.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
http://www.comsol.com/stories/hfir/
---BeginMessage---
I hope this is not a
---
--On January 10, 2006 3:43:56 PM -0500 Freels, James D.
[EMAIL PROTECTED] wrote:
Do you happen to be using the aic7xxx driver ? If so, I had the same
problem until the new kernel 2.6.15.
I'm having problems in debian 2.6.8 related to aic7xxx as well...I use an
aic7xxx HVD SCSI connected
I have one machine that uses the aic7xxx driver of linux 2.6.15
and amanda and the tape driver are working fine. There is a fix in
2.6.15 to this driver that allowed this to happen that has been a bug
since the 2.6.12.x kernels (starting at 2.6.13, the bug showed up)
A similar bug on a second
have occurred in other machines.
On Sun, 2003-07-20 at 23:23, Gene Heskett wrote:
On Sunday 20 July 2003 18:31, Freels, James D. wrote:
OK. I am learning from this. The number of 1k blocks on the first
stored file on this tape is actually 384 and not 352. I should have
looked
OK. I can do this. Let me summarize:
I have a tape labeled fea12. This tape like all the tapes if all filesystems were backed up should contain 40 filesystems + front end + back end.
I issued the command
mt -f /dev/tape_norewind fsf 1
42 times before the end of tape occured and I received
Gregor,
Thanks for responding. I also responded back to Gene Heskett with his suggestion and a little more information.
I would like to try this idea. How can I determine from the amanda log files ? Once I output the data from the tape to the drive, how do I conver it back to a .tar
, James D. wrote:
Gregor,
Thanks for responding. I also responded back to Gene Heskett with his suggestion and a little more information.
I would like to try this idea. How can I determine from the amanda log files ? Once I output the data from the tape to the drive, how
OK. I am learning from this. The number of 1k blocks on the first stored file on this tape is actually 384 and not 352. I should have looked at the taper output and not the dumper output. I issue the following multiple times:
mt rewind
mt -f=/dev/tape_norewind fsf 1
dd if=/dev/tape_norewind
Hello I have used amanda for a long time and have used the amrecover command to recover files/directories in the past without problems. Recently, I accidently deleted a large chunk of my home directory (you don't really want to know how this happened do you--long story). Normally, if something
19 matches
Mail list logo
