Sun storEDGE L280
Hi, Searching the archives, I found messages from Don Potter concerning using the L280 on a Sun and that he had it working. I am attempting to use an L280 on a Linux system. The hardware is recognized by the OS and I am able to load/unload tapes manually at the console and using mtx. However, I am having a problem when I attempt to run amcheck. For some reason, I suspect configuration errors on my part, amcheck will load/unload a couple of tapes and then I get a hardware error indicating the drive is empty (it is not) and the device fails to operate at all. I end up removing the DLT drive and manually removing the tape. After this, system checks on the library report OK. Any ideas as to what may be causing this, or what I need to change/ modify in the amanda configuration? Thank you. Lee
Re: Compiler errors
Conor, Do you have the GNU binutils installed? Some projects compile on Solaris better using the GNU binutils as opposed to Sun's native implementation. The error message indicates Sun's 'as' assembler is choking on the assembler files. If you do have GNU binutils installed, try checking your PATH variable to ensure that /usr/local/bin ( or where you have these tools installed) proceeds /usr/ccs/bin. On Tue, 2002-04-30 at 18:17, Conor Casey wrote: Hi, I've been trying to install Amanda on a machine running Solaris 8 and i'm having compile issues. Below is a copy of where the compile breaks down. I have seen recommendations on some documentation to try using gmake, but while i go looking for and installing it I though i might throw this out there and see if anyone has had a similar problem? If so I would greatly appreciate any help or suggestions you might have. Thanks Conor $ make Making all in config Making all in common-src /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c fileheader.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c fileheader.c -o fileheader.o /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2638: error: unknown opcode .subsection /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2638: error: statement syntax /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2647: error: unknown opcode .previous /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2647: error: statement syntax /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2808: error: unknown opcode .subsection /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2808: error: statement syntax /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2817: error: unknown opcode .previous /usr/ccs/bin/as: /var/tmp/ccHNSqRc.s, line 2817: error: statement syntax *** Error code 1 make: Fatal error: Command failed for target `fileheader.lo' Current working directory /opt/amanda-2.4.2p2/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' $
Backup up to files
Hi folks. I would like to back up several Linux servers RedHat/Slackware to an NFS-mounted partition on the amanda server using files instead of tapes. It seems to me that gtar should support this... has anyone tried it and how did they go about it? thanks, john.
DLT 8000 on Linux
Hi, We are trying here to make backups of a Linux File Server on a DLT 8000 tapedrive, but we can not get it to streaming mode. We tried everything we could think of, but it only streams when running 'dd if=/dev/zero of=/dev/st0 bs=64k'. It also streams with other block sizes, but as soon as we replace /dev/zero by anything else, it will not stream. Strange thing is that if we dd to disk and then to tape, it streams... But if we dd /dev/urandom to disk and then to tape, it doesn't. It's really baffling. Since I see a lot of you are running Amanda with DLT drives, does someone have any idea how to get the drive streaming with real data ? Our configuration: - Siemens F200F server, 1Ghz PIII - Adaptec I2O SCSI Raid controller with Raid-5 set and a seperate disk with its own filesystem - Symbios SYM53c1010-66 SCSI controller, with only the DLT attached. - Linux RedHat 7.1 with 2.4.18 kernel - All filesystems are still ext2 Does anyone have a clue ? Thanx in advance Elmar Kolkman
Re: Backup up to files
On Wed, 1 May 2002 at 9:48am, John D. Bickle wrote I would like to back up several Linux servers RedHat/Slackware to an NFS-mounted partition on the amanda server using files instead of tapes. Version 2.4.3 (still in beta) supports this via the file: tapedrive. Look in the amanda(8) man page included with 2.4.3b3 for all the gory details. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: DLT 8000 on Linux
* Elmar Kolkman [EMAIL PROTECTED] (Wed, May 01, 2002 at 04:43:49PM +0200) We are trying here to make backups of a Linux File Server on a DLT 8000 tapedrive, but we can not get it to streaming mode. We tried everything we Does anyone have a clue ? to get the obvious out of the way, are you using a spooldisk or are you dumping directly to tape ? If the latter, Im not surprised you do not get streaming mode. Currently listening to: CD Audio Track 1 Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: Invalid Argument with amlabel
On Tue, 2002-04-30 at 21:28, Cory Visi wrote:
I searched the list archives and read all the documentation and I cannot
find this error anywhere.
$ amlabel gcs DailySet1
insert tape into slot 0 and press return
labeling tape in slot 0 (/dev/nst0):
rewinding, reading label, not an amanda tape
rewinding, writing label DailySet1
amlabel: writing label: Invalid argument
Notice the Invalid argument.
That would be an Invalid argument error number (errno) coming back from
the write to the tape drive. Perhaps the system tape driver is
configured for some obtuse fixed block size or something? Or maybe
the tapes are just write protected?
Marc
I have a Seagate Python 04687 SCSI tape backup drive.
I am using Amanda 2.4.2p2 which I compiled myself on the same machine,
which is Linux 2.4.13 and glibc 2.2.2.
The backup user is backup. I am using nst0 as my tape device and
backup has permission to read/write:
# ls -l /dev/nst0
crw-rw1 root disk 9, 128 Apr 14 2001 /dev/nst0
# cat /etc/passwd | grep backup
backup:x:417:6:Amanda Backup:/root/amanda-data:/bin/false
# cat /etc/group | grep backup
disk:x:6:root,backup
Here is some of my amanda.conf:
tpchanger chg-manual
tapedev /dev/nst0
changerfile /root/amanda-data/changer-status
changerdev /dev/null
tapetype DAT
labelstr ^DailySet[0-9][0-9]*$
infofile /root/amanda-data
logdir /var/log/amanda
indexdir /root/amanda-data
tapelist /root/amanda-data/tapelist
define tapetype DAT {
comment Archive Python 04687-XXX
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}
amcheck returns no errors except that the current loaded tape has no label:
$ amcheck gcs
Amanda Tape Server Host Check
-
Holding disk /mnt/spare/var/amanda/: 1731365 KB disk space available,
that's plenty
insert tape into slot 1 and press return
amcheck-server: slot 1: not an amanda tape
I obviously need to label my tapes. Anyone have any ideas?
Thanks,
Cory Visi
amrestore problem
Hello, Is there a limit on the length of the path when using amrestore? I attempted to restore a partition but kept getting errors. When I went down a few subdirectories the restore worked. Amrestore seems to fail to restore files when the path is over 80 characters long. Soo
Re: DLT 8000 on Linux
On Wed, 1 May 2002, Elmar Kolkman wrote: Hi, We are trying here to make backups of a Linux File Server on a DLT 8000 tapedrive, but we can not get it to streaming mode. We tried everything we could think of, but it only streams when running 'dd if=/dev/zero of=/dev/st0 bs=64k'. It also streams with other block sizes, but as soon as we replace /dev/zero by anything else, it will not stream. Strange thing is that if we dd to disk and then to tape, it streams... But if we dd /dev/urandom to disk and then to tape, it doesn't. It's really baffling. Since I see a lot of you are running Amanda with DLT drives, does someone have any idea how to get the drive streaming with real data ? Have you tried looking at some of the module parameters for st? Try adding something like this to /etc/modules.conf (or pass on command line when loading module): options st buffer_kbs=128 write_threshold_kbs=126 max_buffers=32 max_sg_segs=16 See the st docs for info on what all that does and tune to taste. Later, Bill Carlson -- Systems Programmer[EMAIL PROTECTED] | Anything is possible, Virtual Hospital http://www.vh.org/ | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. |
Re: need AIT-3 tapetype entry
* Grant Basham [EMAIL PROTECTED] (Wed, May 01, 2002 at 11:31:56AM -0400) I would like a tapetype entry for a Sony AIT3 tape drive. I can just modify an AIT2 entry, but would like to see the results of a run of the tapetype utility on an AIT-3 drive. S Do you have an AIT-3 ? If so, you can simply run tapetype yourself. fROm the docs | Amanda provides a utility to calculate the size of a tape, to generate | a `tapetype' entry for your amanda.conf. However, this utility is | neither built nor installed by default. You can build it by entering | the tape-src directory in the build tree (after running configure) and | typing `make tapetype'. What platform are you on ? Currently listening to: CD Audio Track 2 Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Invalid Argument with amlabel
I have checked an double-checked and the tapes I use are not write-protected. In fact, when I attempt to label a write-protected tape, I receive the error Read-only device
As for the block size, the Linux SCSI tape driver is very flexible. Here are some exerpts from the README.st included with the kernel source:
The system manager (root) can define default values for some tape parameters, like block size and density using the MTSETDRVBUFFER ioctl. These parameters can be programmed to come into effect either when a new tape is loaded into the drive or if writing begins at the beginning of the tape.
The driver supports fixed and variable block size (within buffer limits).
In variable block mode, the byte count in write() determines the size of the physical block on tape. When reading, the drive reads the next tape block and returns to the user the data if the read() byte count is at least the block size. Otherwise, error ENOMEM is returned.
In fixed block mode, the data transfer between the drive and the driver is in multiples of the block size. The write() byte count must be a multiple of the block size. This is not required when reading but may be advisable for portability.
MTSETBLK Set the drive block size. Setting to zero sets the drive into variable block mode (if applicable).
Grepping through the Amanda source code, I do not see MTSETBLK or MTSETDRVBUFFER being used. I know that Amanda may use some external programs though, so maybe this block size issue is handled elsewhere?
In any case, I still have no idea why I'm getting an Invalid Argument. Please help!
Thanks,
Cory Visi
Marc Mengel [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/01/2002 11:10 AM
To:Cory Visi [EMAIL PROTECTED]
cc:[EMAIL PROTECTED], (bcc: Cory Visi/Mazescape)
Subject:Re: Invalid Argument with amlabel
On Tue, 2002-04-30 at 21:28, Cory Visi wrote:
I searched the list archives and read all the documentation and I cannot
find this error anywhere.
$ amlabel gcs DailySet1
insert tape into slot 0 and press return
labeling tape in slot 0 (/dev/nst0):
rewinding, reading label, not an amanda tape
rewinding, writing label DailySet1
amlabel: writing label: Invalid argument
Notice the Invalid argument.
That would be an Invalid argument error number (errno) coming back from
the write to the tape drive. Perhaps the system tape driver is
configured for some obtuse fixed block size or something? Or maybe
the tapes are just write protected?
Marc
I have a Seagate Python 04687 SCSI tape backup drive.
I am using Amanda 2.4.2p2 which I compiled myself on the same machine,
which is Linux 2.4.13 and glibc 2.2.2.
The backup user is backup. I am using nst0 as my tape device and
backup has permission to read/write:
# ls -l /dev/nst0
crw-rw 1 root disk9, 128 Apr 14 2001 /dev/nst0
# cat /etc/passwd | grep backup
backup:x:417:6:Amanda Backup:/root/amanda-data:/bin/false
# cat /etc/group | grep backup
disk:x:6:root,backup
Here is some of my amanda.conf:
tpchanger chg-manual
tapedev /dev/nst0
changerfile /root/amanda-data/changer-status
changerdev /dev/null
tapetype DAT
labelstr ^DailySet[0-9][0-9]*$
infofile /root/amanda-data
logdir /var/log/amanda
indexdir /root/amanda-data
tapelist /root/amanda-data/tapelist
define tapetype DAT {
comment Archive Python 04687-XXX
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}
amcheck returns no errors except that the current loaded tape has no label:
$ amcheck gcs
Amanda Tape Server Host Check
-
Holding disk /mnt/spare/var/amanda/: 1731365 KB disk space available,
that's plenty
insert tape into slot 1 and press return
amcheck-server: slot 1: not an amanda tape
I obviously need to label my tapes. Anyone have any ideas?
Thanks,
Cory Visi
Re: Invalid Argument with amlabel
On Wed, 2002-05-01 at 14:19, Cory Visi wrote: I have checked an double-checked and the tapes I use are not write-protected. In fact, when I attempt to label a write-protected tape, I receive the error Read-only device Well, I was thinking more along the lines of: bldlinux71 mt -f /dev/nst0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 1024 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN If yours said something like Tape block size 9177 bytes or such like you would get an error 'cause a 32k write (which is what amanda generally does) would not be a multiple of the blocksize. You probalby want to do mt -f /dev/nst0 setblk 0 for variable block mode. There may be some other parameters that are keeping that drive from writing a label. At any rate, you may want to ask a Linux user list rather than amanda-users as I don't think the problem you are having is an amanda configuration issue, but rather a system one.
Re: Incremental and Full backups
John R. Jackson wrote: You can also just tell Amanda not to do full dumps during the period you just want to be using DDS2's. How would you tell amanda to do this? Would you change the disklist file? Would you use strategy no-full? Then do a SDLT run once in a while and tell it to do lots of fulls to get back in sync. Would you use amadmin force? Here is what I want to do, sorry it is not a very specific set of questions, but perhaps it will be interesting as a starting point for discussions. I want to do something similiar to the above. I have a DDS4 changer (playing the role of the SDLT above) and a spare hard disk for disk-only runs (playing the role of the DDS2 above). It is hard for me to get more tapes, and so I want to avoid using a tape per night, I would rather use a couple of tapes per week. (a set of fulldumps would probably fit on 3 cartridges). I want to make sure that the tape runs never depend on a dump that is disk-only, so I am anticipating making the disk-only runs not record into dumpdates. The tape runs would use the standard strategy. I was thinking of creating a new strategy that does only something like a level 8 dump which would hopefully be higher than the the backup levels recorded into dumpdates by the tape runs. so, i would probably want to recycle the disk-only tapes about once a week, but the real-tape tapes i would keep much longer. so they would need different dump-cycles, so I would need to have two versions of amanda.conf and disklist, and i would put the ones i want to run into place before running amdump. I am hoping that the index database will be able to cope with some of the tapes getting recycled before other (real) tapes in the cycle. any hints or kinks would be appreciated! --James Ganong
runtape question, probably a FAQ
Is there a way to configure amanda so that runtapes is calculated dynamically to fit in that partciular amdump? Using two or more tapes for a dump is wasteful when there's only 10% of tape used for that dump. -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: runtape question, probably a FAQ
On Thu, May 02, 2002 at 10:49:00AM +1000, Robert Kearey wrote: Is there a way to configure amanda so that runtapes is calculated dynamically to fit in that partciular amdump? Using two or more tapes for a dump is wasteful when there's only 10% of tape used for that dump. The runtapes parameter is an upper bound on the number of tapes amanda _may_ use in a single run, not the number that will be used. If all of the data for a particular run fits on one tape, then only that one tape is used. -- Mike Delaney [EMAIL PROTECTED] ...Microsoft follows standards. In much the same manner that fish follow migrating caribou. Now I have this image in my mind of a fish embracing and extending a caribou. -- Paul Tomblin and Christian Bauernfeind in the SDM
Re: ./configure error with amanda 2.4.2
Make sure you also have the readline 'development' package installed, as Amanda needs to find the header files so it can properly link to the libraries. Also, if it is installed in an odd place configure won't find it, so you would need to add some configure options. Frank --On Thursday, May 02, 2002 02:38:25 +0200 [EMAIL PROTECTED] wrote: Hi :-) I am trying to install Amanda 2.4.2 on my SuSE 7.2 Linux with kernel 2.4.18 but got stopped right away when running ./configure --with-user=amanda --with-group=disk. It tells me: Checking in readline in -lreadline--- (cached) No configure: warning: ***No readline library, no history and command line editing in amrecover ! configure: warning: ***vtblc headers not found - no QIC volume table support*** I have readline installed - when I enter rpm -q readline it returns readline-2.05-21 What's wrong ? -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
