Re: personal request - no need for double mail
I, as a culprit, Agree. Trevor. - Original Message - From: Jon LaBadie [EMAIL PROTECTED] To: Jon LaBadie [EMAIL PROTECTED] Sent: Wednesday, September 11, 2002 4:00 PM Subject: personal request - no need for double mail I'm moderately active on the list, both posting and through private emails. In addressing replies and follow-ups, I kindly request either a list posting or a private email. Both are unnecessary. Others may have vastly differing opinion. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: win32
On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang, A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag archive that seems to be read by Amanda exactly like the Unix executable flag. Now I am backuping some W2K servers, in production. Everything goes well :) -- Jean-Christian SIMONETTI email: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France --
Newbie HOWTO
Hallo all As mentioned earlier I am busy writing a newbie HOWTO. Will anybody mind if I post it to the list ? I want evereybody to look it to check if I didn't make any major mistakes ;-) I have only done the prelimenary setup procedures sofar (no config files) If anybody minds please let me know Mozzi
Re: Working with multiple tape drives----- Ammended
Reply With History On the library, sometimes due to transportation (and the library was not Park properly), the robot arm tends to miscalculate its Y position. That is when you need to re-calibrate. By re-calibrate I meant accessing the menu on the library and manually calibrate. On the units that we (Tandberg Data) sell, there is a special menu where you can select to manually calibrate the robot arm. This menu is NOT for normal user use, therefore its need a combinations of keys presses to make it appeared. What I would suggest for you to do is to get the manual for the library you have, maybe there is a section in there that tell you how to recalibrate. If not then you need to contact the support section. Regards Tien
raw device permissions
Hi This is my stupid question of the week ;-) Sorry but my brain has deflated. Please bear with me for when my newbie howto is finished I hope it will stop questions like this. This is a direct quote from the INSTALL file B. Set up your raw disk devices so that the dumpuser can read them, and /etc/dumpdates so that the dumpuser can write to it. Normally this is done by making the disk devices readable by (and dumpdates read/writable by) group `operator', and putting the dumpuser into that group. Now my problem: Getting dumpuser to read the raw devices. I see in Red-Hat the default group is disk [root@backupserver docs]# ls -ahl /dev/hda brw-rw1 root disk 3, 0 Apr 11 16:25 /dev/hda I can't just put dumpuser into group disk as that wil give it full read write access. I don't think it wil be a good idea to revoke write privelages from disk ;-)and it will not be a good idea to change the group.So what now ? This is what stumps me. Tnx all Mozzi
A nightmare of failures
I'm wondering if someone could have a look at this log file, and give me
an idea of what to do here. Almost half of my backups are failing. I
either get FAIL planner mur3.lb.backbone /usr 0 [Request to
mur3.lb.backbone timed out.] on some partitions, or FAIL dumper
fido.lb.backbone /var/www 0 [/bin/tar returned 2] Why is amanda so
temperamental
[root@lon-backup Execulink]# tail -f log
INFO planner Adding new disk fido.lb.backbone:/var/www.
INFO planner Adding new disk fido.lb.backbone:/usr/ppp1.
INFO planner Adding new disk fido.lb.backbone:/usr/ppp2.
INFO planner Adding new disk mur3.lb.backbone:/home.
INFO planner Adding new disk mur3.lb.backbone:/home2.
INFO planner Adding new disk mur3.lb.backbone:/home3.
INFO planner Adding new disk mur3.lb.backbone:/var.
INFO planner Adding new disk mur3.lb.backbone:/usr.
START driver date 20020911
START taper datestamp 20020911 label Execulink10 tape 0
FAIL planner mur3.lb.backbone /usr 0 [Request to mur3.lb.backbone timed
out.]
FAIL planner mur3.odyssey.on.ca /var 0 [Request to mur3.lb.backbone
timed out.]
FAIL planner mur3.odyssey.on.ca /home3 0 [Request to mur3.lb.backbone
timed out.]
FAIL planner mur3.odyssey.on.ca /home2 0 [Request to mur3.lb.backbone
timed out.]
FAIL planner mur3.odyssey.on.ca /home 0 [Request to mur3.lb.backbone
timed out.]
FINISH planner date 20020911
STATS driver startup time 36001.665
SUCCESS dumper gatekeeper.lb.backbone /usr/lib/perl5/execulink 20020911
1 [sec 0.030 kb 32 kps 1044.1 orig-kb 10]
SUCCESS taper gatekeeper.lb.backbone /usr/lib/perl5/execulink 20020911 1
[sec 1.547 kb 64 kps 41.4 {wr: writers 2 rdwait 0.000 wrwait 0.017
filemark 1.530}]
SUCCESS dumper gatekeeper.lb.backbone /var/www/htdocs 20020911 1 [sec
0.048 kb 32 kps 653.2 orig-kb 80]
SUCCESS taper gatekeeper.lb.backbone /var/www/htdocs 20020911 1 [sec
1.583 kb 64 kps 40.4 {wr: writers 2 rdwait 0.000 wrwait 0.017 filemark
1.565}]
SUCCESS dumper gatekeeper.lb.backbone /home/jg 20020911 1 [sec 0.066 kb
32 kps 478.4 orig-kb 160]
SUCCESS taper gatekeeper.lb.backbone /home/jg 20020911 1 [sec 1.618 kb
64 kps 39.5 {wr: writers 2 rdwait 0.000 wrwait 0.016 filemark 1.601}]
FAIL dumper fido.lb.backbone /var/www 0 [/bin/tar returned 2]
sendbackup: start [fido.lb.backbone:/var/www level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? gtar: ./logs/access_log: file changed as we read it: No such file or
directory
? gtar: ./logs/error_log: file changed as we read it: No such file or
directory
| Total bytes written: 1926533120
? gtar: Error exit delayed from previous errors
sendbackup: error [/bin/tar returned 2]
SUCCESS dumper fido.lb.backbone /usr/ppp2 20020911 0 [sec 2875.789 kb
5141824 kps 1788.0 orig-kb 6067090]
SUCCESS taper fido.lb.backbone /usr/ppp2 20020911 0 [sec 348.020 kb
5141856 kps 14774.6 {wr: writers 160683 rdwait 0.216 wrwait 344.642
filemark 1.984}]
FAIL dumper fido.lb.backbone /usr/ppp1 0 [data timeout]
sendbackup: start [fido.lb.backbone:/usr/ppp1 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
INFO taper tape Execulink10 kb 5142048 fm 4 [OK]
FINISH driver date 20020911 time 41481.691
--
Jason Greenberg, CCNP
Re: Tape technology
First off, thanks to all for the info; I at least now have a base from which to start. the small business with say 5-10 major machines to backup, a dedicated software raid server with a rack of big drives, running rsync, also has a cost and speed advantage. I know of one such setup with a capacity of 320 gigs in 4 160 gig drives that does its Hell, you might as well start talking Coda to me. Which is another possibility. about 1600 USD at the time. Is it as dependable as tape? Time will tell. Can you take it offsite? In a sense, yes, by cycling enough drives thru each slot in the array and letting the raid rebuild I'm not really keen on this idea. Although relative to the price of a DDS drive it is affordable (for just one or two harddrives). My main problem is that the drives will be handled by average users. Hrm. ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Tape DDS-3 values
Hello,
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
Thanks in advance.
___
Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
Re: Tape DDS-3 values
On Thu, 12 Sep 2002, Kablan BOGNINI wrote:
Hello,
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Nope, they are not correct. The reason is that you probably have hardware
compression on which actually expands the data Amanda uses to determine
tapesize which in turn gives a smaller length.
However, you are in good company since, even though I have only been on
this list for a short time, this seems to be one of the most frequent
questions here.
I had the same problem and I solved it by removing the drive from it's
drivebox and changing a dip-switch. Some OS:s seems to allows you to
change if the drive should use compression with the mt command (I have not
found it in Solaris 8 though).
Also, tar+gnuzip gives you alot better compression than the internal
hardware of the drive, at least from what I've read on this list.
Could someone give me more accurate values for this
tape or point me to doc ?
I use the following tapetype:
define tapetype HP-C1554a {
comment just produced by tapetype program
length 10075 mbytes
filemark 0 kbytes
speed 872 kps
}
Perhaps the length could be a bit larger, but better safe than sorry. If
you change the drive to default to hardware compression off you can rerun
tapetype to get more accurate values.
Hope it helps!
--
Conny Gyllendahl
Don't try to have the last word -- you might get it.
-- Lazarus Long
Re: Tape technology
On Thursday 12 September 2002 04:28, Brian Jonnes wrote: First off, thanks to all for the info; I at least now have a base from which to start. the small business with say 5-10 major machines to backup, a dedicated software raid server with a rack of big drives, running rsync, also has a cost and speed advantage. I know of one such setup with a capacity of 320 gigs in 4 160 gig drives that does its Hell, you might as well start talking Coda to me. Which is another possibility. about 1600 USD at the time. Is it as dependable as tape? Time will tell. Can you take it offsite? In a sense, yes, by cycling enough drives thru each slot in the array and letting the raid rebuild I'm not really keen on this idea. Although relative to the price of a DDS drive it is affordable (for just one or two harddrives). My main problem is that the drives will be handled by average users. Hrm. ..Brian We at first were going to use some removable drive bays, but had trouble with the ata-133 settings and the extra cabling, so the removeable kits are still on the shelf. They work fine with ata100 stuff though as we're doing that with video drives for program delay and transport now. But thats temporary since the mpeg-2 standard doesn't do closed captioning which gets us phone calls from the hard of hearing folks. We only do that when the real dvc-pro machine is down for service, its our program backup. Now if we could figure out how to automate the removal and replacement of several hundred surface mounted electrolytic capacitors when one of them starts pixelizing. Its hell on one's back, sitting at the bench working under a magnifying lamp doing that, takes 3 or 4 days to go all the way thru one of those $3k-$7k+ machines. Thats the major failure mechanism for a dvc-pro tape machine. :-( -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Tape DDS-3 values
--On Thursday, September 12, 2002 15:54:43 +0200 Kablan BOGNINI [EMAIL PROTECTED]
wrote:
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
You probably have compression enabled on your drive, and
it is making tapetype's data bigger. Try turning off the
compression and re-running tapetype.
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Newbie HOWTO
Mozzi wrote: Hallo all As mentioned earlier I am busy writing a newbie HOWTO. Will anybody mind if I post it to the list ? I want evereybody to look it to check if I didn't make any major mistakes ;-) I don't mind. I want to see where I messed up on configurating Amanda. *grin* I have only done the prelimenary setup procedures sofar (no config files) If anybody minds please let me know -- Eric
Re: Tape DDS-3 values
On Thu, Sep 12, 2002 at 05:13:53PM +0300, Conny Gyllendahl wrote: Also, tar+gnuzip gives you alot better compression than the internal hardware of the drive, at least from what I've read on this list. This is true but as a friend pointed out to me recently when I was having some tape reading problems - if you get some bit errors reading a tar file from a tape, most likely asll you will lose is the affected file. If OTOH you get bit errors reading a gzipped tar file, you most likely will not be able to read anything after the bit errors. Just something to be aware of. Kindest regards, Niall O Broin
Correction to SOLVED: amlabel: Operation not permitted
Hi, everyone, Correction: that should read /dev/nst0, not /dev/st0 I changed the device to /dev/st0 and everything worked, including amlabel. Apparently the problem is with vxaTool reporting the wrong device and not amanda. I'll report the bug to Exabyte. Thanks again, Caity
SOLVED: amlabel: Operation not permitted
Hi, everyone, I changed the device to /dev/st0 and everything worked, including amlabel. Apparently the problem is with vxaTool reporting the wrong device and not amanda. I'll report the bug to Exabyte. Thanks
Re: Tape DDS-3 values
Kablan BOGNINI wrote:
Hello,
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
Thanks in advance.
___
Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
I'm gonna go out on a limb and say you have hardware compression turned
on...as any search through the archives will state, turn if off and
leave it off. Software compression will most likely give you more than
the tape advertises (just ask Gene). If you are running linux, run mt
-f /dev/tapedevice compression 0 . If you still get the same result
you may have to play with data density settings for the drive which will
require perusing the manuals.
=G=
Re: Tape DDS-3 values
On Thursday 12 September 2002 09:54, Kablan BOGNINI wrote:
Hello,
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
Thanks in advance.
That looks as if you have the drives hardware compression enabled,
which for amanda is a Bad Thing(tm).
When you run tapetype, the source of the data is /dev/urandom. This
is not generally compressable data because there is little
removable redundancy in such data. And in most cases, the rll
encoder in the drive will actually expand such data, hence the
apparent short tape.
This also places an unknown into amanda's idea of what the tape will
hold as amanda counts bytes sent to the tape *after* any software
compression has been applied.
So turn off the hardware compression and leave it off forever. Then
re-run the tapetype.
Software compression is usually much more effective anyway. Last
nights run here put 8370k of real data out to the tape as 3780k on
a DDS2 120 meter tape, the first time I've actually had a tape 100%
used. And its a 46 gig system.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Tapetype
Hi Watch out for tapetype!!! I have a Tandberg VS80 DLT 40/80 Gig drive I gave it the command #./tapetype -e 40960 -f /dev/nst0 -t TandbergVS80 It has been going for 26 hours now,and no end in sight. Mozzi
HOWTO-here it is !!!!
Hi all
Please note this is just phase 1 basis for discussion ;-)
It should cover all setups to be done on the server prior to the final
amanda setup.
So hopefully ;-) If you have done this you can just edit your amnda
config files and off you go !!!
Please look the following.
Is evereything in logical order? (I wrote as I went along)
Have I left enything out?
Have you got something to add ?
All contributions are welcome
Tnx
Mozzi
building and installing amanda for network backups
---
Please remember this is a newbie quickdirty setup HOWTO
a)Thanx
Firstly thanx to the amanda users mailing listand evereybody there who
answered my questions so
patiently,without you guys I wouldn't have been able to do this.
b)Disclaimer
This worked for me.If you machie starts smoking or bursts into
flames,sorry I cannot do anything about it.
Should this happen please post to the list as I am sure evereyone would
like to hear about it,include a full
bugreport please ;-)
c)Setup
I use the following here
user=amanda
group=backup
profile=test
index machine=tapehost
I use Red-Hat 7.3 on x86
I have:
two ide harddrives
scsi Tandberg VS80 DLT tapedrive (internal)
Subsystem: Adaptec 29160 Ultra160 SCSI Controller
Make sure your kernel supports your scsi cotroller,how to setup that
is way beyond the scope of this document.
Use the link below to test your tapedrive.It is for DLT scsi.
If you use auto changers or robotics Sorry I do not have one to test
on ;-)
When you can use the mt utility on the tapedrive you are ready for
primetime!!!
To setup the DLT Tapedrive I found this link verey handy
http://www.quantum.com/NR/rdonlyres/6ayrpuorsal7nrdypfpq456w2ehie6zr7zubapbcq5marehyanix5v7xoovfrhjmtteqpm73zygud
/dlt8000linux.pdf
---
d)On index machine (where tape device is)
adduser amanda
groupadd backup
./configure --with-user=amanda --with-group=backup
make
make install
this point I like to switch off hardware compression
#mt -t /dev/nst0 -compression 0
I actually put that into my rc.local file to make sure.
As someone mentioned on the list amanda measures the output after
compression so you should score a lot
by doing this
Put the Amanda services into your /etc/services file on the tapehost
Add entries like so:
amanda 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
I just added them right the top
Add the following to your xinetd.d directory
vi amanda
cutpaste the following
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = backup
groups = yes
server = /usr/local/libexec/amandad
}
--
vi amandaidx
cutpaste the following
---
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = backup
groups = yes
server = /usr/local/libexec/amindexd
}
-
vi amidxtape
cutpaste the following
--
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = backup
groups = yes
server = /usr/local/libexec/amidxtaped
}
-
now we must get our config directory ready
mkdir /usr/local/etc/amanda/test
In the above test is the name of my profile stick to it for now but when
you setup your own
you can use whatever you want.
Now we copy the files we need into the config directory
cd ~/amanda-2.4.2p2/example/
cp amanda.conf config.site disklist
Make amanda the owner
chown amanda:backup /usr/local/etc/amanda/test
Now create the log directory
mkdir /usr/local/var/amanda
mkdir /usr/local/var/amanda/test
mkdir /usr/local/var/amanda/test/curinfo
mkdir /usr/local/var/amanda/test/index
mkdir /usr/local/var/amanda/test/tapelist
Make amanda the owner
chown -R amanda:backup /usr/local/var/amanda/test/
We will later edit the amanda.conf file to reflect this.
Now let's setup our holding area for images while they are waiting to be
written to tape
mkdir /var/dump
Make amanda the owner
chown -R amanda:backup /var/dump
We will later edit the amanda.conf file to reflect this.
Re: win32
Care to share what you went through? I remember there's an exe you have to run to turn any program into a service (anyserv.exe?) as I've had to do it for a perl script before. Would be nice to get it all under the same backup system. On 9/12/02 2:35 AM, JC Simonetti [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang, A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag archive that seems to be read by Amanda exactly like the Unix executable flag. Now I am backuping some W2K servers, in production. Everything goes well :) -- Jean-Christian SIMONETTI email: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France --
Re: Tape DDS-3 values
On Thursday 12 September 2002 10:43, Galen Johnson wrote:
Kablan BOGNINI wrote:
Hello,
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
Thanks in advance.
___
Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
I'm gonna go out on a limb and say you have hardware compression
turned on...as any search through the archives will state, turn
if off and leave it off. Software compression will most likely
give you more than the tape advertises (just ask Gene). If you
are running linux, run mt -f /dev/tapedevice compression 0 .
If you still get the same result you may have to play with data
density settings for the drive which will require perusing the
manuals.
=G=
While you can use mt to turn it off, on most drives is a switch that
will turn it off, a bit more dependable than remembering to do it
with mt, if your platforms mt even has that ability.
Which brings me to the next subject regarding compression.
Most modern drives can autoswitch, and will switch it back on if it
finds, in the tapes own, you can't read it, header, that the
compression is on for that individual tape. So basicly it doesn't
do you any good to turn it off if the *(% tape itself turns it
back on during the tape recognition as each tape is inserted into
the drive.
What I've found to be a way to fix that is to rewind the tape, then
dd the amanda label block out to a scratch file, then rewind the
tape again, use mt to shut the compression off and write 20 megs or
so of data from /dev/zero to it using dd. Rewind it and rewrite
the scratch file back to restore the label.
By doing this long garbage data write, you are going to force the
drive to flush its buffers. When this is done, the drive will
re-write those hidden headers, doing it with the compression flag
now set to off. If such a flush operation is not forced, the drive
doesn't update those headers and you're stuck with xx gig tapes
that only hold less because the compression is on regardless of
your wishes. Sometimes much less when you feed the drives rll
compressor with a few gigs worth of bz2 files.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Re: win32
On Thu, Sep 12, 2002 at 09:35:57AM +0200, JC Simonetti wrote: On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002, Galen Johnson wrote: I downloaded this package but have been unable to get it to work - anyone using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag archive that seems to be read by Amanda exactly like the Unix executable flag. Now I am backuping some W2K servers, in production. Everything goes well :) Important follow-ups: Can you also amrecover/amrestore? Have you, or will you, put the changes out for others? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tapetype
On Thursday 12 September 2002 10:48, Mozzi wrote: Hi Watch out for tapetype!!! I have a Tandberg VS80 DLT 40/80 Gig drive I gave it the command #./tapetype -e 40960 -f /dev/nst0 -t TandbergVS80 It has been going for 26 hours now,and no end in sight. Mozzi It will get done at some point. It has to write the tape completely full twice, and a slow writing big tape will take a while. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: SOLVED: amlabel: Operation not permitted
Hi, sorry to correct you, but you must not use /dev/st0 with amanda, the correct device for amanda is /dev/nst0, as this device does not rewind when it is closen. /dev/st0 rewinds the tape at close which is a nono with amanda. vxa tools are reporting a correct device for your tape, but not for the use with amanda. the /dev/sg[0-9] devices are for generic acces to scsi-devices, they offer another interface. If you want to operate a changer for example you'll have to use the sg-device. Christoph Caitlyn M. Martin schrieb: Hi, everyone, I changed the device to /dev/st0 and everything worked, including amlabel. Apparently the problem is with vxaTool reporting the wrong device and not amanda. I'll report the bug to Exabyte. Thanks
Output of tapetype
Hello,
Im learning amanda so thanks for your time.
What does this mean when running tapetype:
# ./tapetype -f /dev/rmt/1ln
wrote 2266437 32Kb blocks in 6931 files in 28845 seconds (short write)
wrote 1826089 32Kb blocks in 11203 files in 27217 seconds (short
write)
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 93147 mbytes
filemark 3298 kbytes
speed 2330 kps
}
Should I really use that?
We have a :
SONY SDX-500C with a 15 slot stacker SPECTRA 215 1019
Thanks.
Rob
Re: Too many taper retries
On Tuesday 28 April 2020 05:33, Gene Heskett wrote: I just noted that my clock was foobar, set for something in april 2020! As I have a daily rdate, is there any way to ascertain that the rdate request to the server returns a sane result before it blindly resets everything? It happened yesterday morning on cron executing my setibatch -uploads script which includes this rdate command as it finishes up. Sort of embarrasing that I missed it for nearly 2 days. On Wednesday 11 September 2002 23:03, Alvin Ko wrote: I used amanda 2.4.2p2 with a DDS-3 tape drive to do a full backup of my Linux last night. In the amanda.conf file, I used chg-manual as the changer with 3 tapes. My /export/home folder has 23GB data. I had labeled three tapes (Tape-01, Tape-02, Tape-03) and then start the backup. 3 hours later, she asked me to insert backup tape into slot 1. When amdump completed, I got the following report. --- These dumps were to tapes Tape-01, Tape-02, Tape-03. The next 3 tapes Amanda expects to used are: a new tape, a new tape, a new tape. FAILURE AND STRANGE DUMP SUMMARY: localhost /export/home lev 0 FAILED [too many taper retries] ... NOTES: planner: Adding new disk localhost:/boot. planner: Adding new disk localhost:/usr. planner: Adding new disk localhost:/. planner: Adding new disk localhost:/export/home. planner: Adding new disk localhost:/home. planner: Adding new disk localhost:/var. planner: Adding new disk localhost:/opt. taper: tape Tape-01 kb 12013824 fm 7 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-02 kb 12004832 fm 1 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-03 kb 0 fm 0 [OK] driver: Could not rmdir /mnt/hdc1/20020911: Directory not empty --- She could not backup my /export/home folder into multiple tapes. Anybody knows why? Best Regards, Alvin K. T. Ko How big is /export/home? If its bigger than your DDS3 tape, you will have to break that entry up into even smaller pieces. Basicly, amanda cannot span more than one tape with a single filesystem, and probably never will. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
HELP : amlabel - no tape online
Hi,
I am a newbie to Amanda. I have set up version
2.4.2.p2 on a RedHat
Linux 7.3 system with a HP SureStore 24x6 external
drive (HP C1557A).
Installation of amanda went on fine. Here are relevant
portions from
the amanda.conf file :
**
*
runtapes 1 # number of tapes to be used in a single
run of amdump
tpchanger /etc/amanda/daily/chg-zd-mtx# the
tape-changer glue
script
tapedev /dev/nst0 # the no-rewind tape device to be
used
rawtapedev /dev/nst0 # the raw device to be used
(ftape only)
changerfile /etc/amanda/mtx-changer
changerdev /dev/sg0
tapetype HP1557A# what kind of tape it is (see
tapetypes below)
labelstr ^DailySet1-[0-9][0-9][0-9] # label
constraint regex: all
tapes must match
[]
define tapetype HP1557A {
comment HP SureStore DAT24x6e tape drive
# data provided by Ivo Clarysse
length 12000 mbytes
filemark 111 kbytes
speed 3000 kbytes
}
**
I have tried using the mtx-changer command, and can
eject and load
individual tapes using it. However, when after all
configuration was
done, and I wanted to label a tape using the command:
su amanda -c amlabel daily DailySet1
I get this error:
*
labeling tape in slot /etc/amanda/daily/chg-zd-mtx:
([: too many
arguments):
rewinding
amlabel: no tape online
*
I used info from this URL for tape changer
configuration :
http://www.soti.org/~soggie/linux/hw/hp-surestore-24x6/
And for other Amanda installation and general
configuration, I
followed the guide at:
http://www.frankenlinux.com/guides/amandaserver.html
I have also tested my tape drive using tar commands,
and it works well
with the device file /dev/nst0. The changer device
file shows up as
/dev/sg1.
Here is the output of the mt status command:
**
SCSI 2 tape drive:
File number=0, block number=0, partition=0
Tape block size 0 bytes. Density code 0x25 (DDS-3).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
**
Any help in resolving this problem will be much
appreciated!
Thanks,
Vivek
__
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
RE: Working with multiple tape drives----- Ammended
Tien, if recalibration is what I need then, looking at my manual, it'd seem that this might be what I wanna do: Uncal Drive Target Allows the operator to uncalibrate a drive target. The next time a tape mount operation is called for that drive, the library recalibrates the target automatically as, for example, when a drive has been physically removed and replaced while the library is operating (hot swapped-only for qualified service personnel). Do you agree? -Original Message- From: Tien That Ton [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 3:35 AM To: [EMAIL PROTECTED] Subject: Re: Working with multiple tape drives- Ammended Reply With History On the library, sometimes due to transportation (and the library was not Park properly), the robot arm tends to miscalculate its Y position. That is when you need to re-calibrate. By re-calibrate I meant accessing the menu on the library and manually calibrate. On the units that we (Tandberg Data) sell, there is a special menu where you can select to manually calibrate the robot arm. This menu is NOT for normal user use, therefore its need a combinations of keys presses to make it appeared. What I would suggest for you to do is to get the manual for the library you have, maybe there is a section in there that tell you how to recalibrate. If not then you need to contact the support section. Regards Tien
Re: win32
I'll post here a little howto as soon as I find time. Don't hesitate to remind me of that if I forget. (one week could be a correct timeout for me I think if I have not too any problems...) On Thu, 12 Sep 2002 09:01:18 -0500 Tony Shadwick [EMAIL PROTECTED] wrote: Care to share what you went through? I remember there's an exe you have to run to turn any program into a service (anyserv.exe?) as I've had to do it for a perl script before. Would be nice to get it all under the same backup system. On 9/12/02 2:35 AM, JC Simonetti [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang, A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag archive that seems to be read by Amanda exactly like the Unix executable flag. Now I am backuping some W2K servers, in production. Everything goes well :) -- Jean-Christian SIMONETTI email: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France --
Re: win32
On Thu, 12 Sep 2002 11:16:11 -0400 Jon LaBadie [EMAIL PROTECTED] wrote: On Thu, Sep 12, 2002 at 09:35:57AM +0200, JC Simonetti wrote: On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary [EMAIL PROTECTED] wrote: On Wed, 11 Sep 2002, Galen Johnson wrote: I downloaded this package but have been unable to get it to work - anyone using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag archive that seems to be read by Amanda exactly like the Unix executable flag. Now I am backuping some W2K servers, in production. Everything goes well :) Important follow-ups: Can you also amrecover/amrestore? amrecover is possible. You extract the tarball archive on your backup server and upload it to the Windows box, and there you untar it with the WinTar provided with Win32 Amanda (different of course from the GNU tar, due to NT file rights...). amrestore is possible, but I don't like the ability of the client to log in as root without password on the backup server, so I tested the solution but did not put it in production. amrestore is also helped by a GUI written in Python (need to install a Python interpreter on your Windows box, easy way but not so easy to automatically deploy). Have you, or will you, put the changes out for others? Will be done. See my previous mail ;)
Re: Output of tapetype
On Thu, Sep 12, 2002 at 08:28:29AM -0700, rmckeever wrote:
Hello,
Im learning amanda so thanks for your time.
What does this mean when running tapetype:
# ./tapetype -f /dev/rmt/1ln
wrote 2266437 32Kb blocks in 6931 files in 28845 seconds (short write)
wrote 1826089 32Kb blocks in 11203 files in 27217 seconds (short
write)
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 93147 mbytes
filemark 3298 kbytes
speed 2330 kps
}
It means you got VERY different results than 2 others who put
their results into the Faq-O-Matic.
You got twice the capacity, half the speed, and a substantial
waste of space between files compared to their results.
Should I really use that?
We have a :
SONY SDX-500C with a 15 slot stacker SPECTRA 215 1019
1) is it reproducible?
2) are you certain compression was turned off?
3) do the numbers (capacity, speed) seem reasonable?
4) can you explain the difference between your results
and the previously listed ones? (tape size, eg longer,
technology, eg. xyz-2 vs xyz-1, slow, narrow scsi)
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: HELP : amlabel - no tape online
On Thursday 12 September 2002 11:35, Vivek Singh wrote:
Hi,
I am a newbie to Amanda. I have set up version
2.4.2.p2 on a RedHat
Linux 7.3 system with a HP SureStore 24x6 external
drive (HP C1557A).
Installation of amanda went on fine. Here are relevant
portions from
the amanda.conf file :
**
*
runtapes 1 # number of tapes to be used in a single
run of amdump
tpchanger /etc/amanda/daily/chg-zd-mtx # the
tape-changer glue
script
tapedev /dev/nst0# the no-rewind tape device to be
used
rawtapedev /dev/nst0 # the raw device to be used
(ftape only)
changerfile /etc/amanda/mtx-changer
changerdev /dev/sg0
tapetype HP1557A # what kind of tape it is (see
tapetypes below)
labelstr ^DailySet1-[0-9][0-9][0-9] # label
constraint regex: all
tapes must match
[]
define tapetype HP1557A {
comment HP SureStore DAT24x6e tape drive
# data provided by Ivo Clarysse
length 12000 mbytes
filemark 111 kbytes
speed 3000 kbytes
}
**
I have tried using the mtx-changer command, and can
eject and load
individual tapes using it. However, when after all
configuration was
done, and I wanted to label a tape using the command:
su amanda -c amlabel daily DailySet1
DailySet1 is the group name thats the default in amanda.conf, and
you need to also supply a trailing 1 or 2 digit number to complete
the unique label for each tape, like -1, -2, ... -20.
I get this error:
**
***
labeling tape in slot /etc/amanda/daily/chg-zd-mtx:
([: too many
arguments):
rewinding
amlabel: no tape online
**
***
I used info from this URL for tape changer
configuration :
http://www.soti.org/~soggie/linux/hw/hp-surestore-24x6/
And for other Amanda installation and general
configuration, I
followed the guide at:
http://www.frankenlinux.com/guides/amandaserver.html
I have also tested my tape drive using tar commands,
and it works well
with the device file /dev/nst0. The changer device
file shows up as
/dev/sg1.
Here is the output of the mt status command:
**
SCSI 2 tape drive:
File number=0, block number=0, partition=0
Tape block size 0 bytes. Density code 0x25 (DDS-3).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
**
Any help in resolving this problem will be much
appreciated!
Thanks,
Vivek
__
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Output of tapetype
On Thursday 12 September 2002 11:28, rmckeever wrote:
Hello,
Im learning amanda so thanks for your time.
What does this mean when running tapetype:
# ./tapetype -f /dev/rmt/1ln
wrote 2266437 32Kb blocks in 6931 files in 28845 seconds (short
write) wrote 1826089 32Kb blocks in 11203 files in 27217 seconds
(short write)
The above is normal output just so you know that tapetype hasn't
gone to vegas to play the slots with your money. :-)
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 93147 mbytes
filemark 3298 kbytes
speed 2330 kps
}
Looks good if its supposed to be a 10 gig tape. If not, then check
to see if the hardware compression is on, which for amanda is a
no-no. See my other recent messages about getting it turned off
and kept off.
Should I really use that?
We have a :
SONY SDX-500C with a 15 slot stacker SPECTRA 215 1019
Thanks.
Rob
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Re: win32
JC Simonetti wrote: amrecover is possible. You extract the tarball archive on your backup server and upload it to the Windows box, and there you untar it with the WinTar provided with Win32 Amanda (different of course from the GNU tar, due to NT file rights...). amrestore is possible, but I don't like the ability of the client to log in as root without password on the backup server, so I tested the solution but did not put it in production. amrestore is also helped by a GUI written in Python (need to install a Python interpreter on your Windows box, easy way but not so easy to automatically deploy). Have you, or will you, put the changes out for others? Will be done. See my previous mail ;) Can I assume from what you've been saying that you've actually gotten the amanda-win32 project from sourceforce to compile properly? What about the selfcheck bug? Or sendsize crashes that were reported? these questions assume you are using amanda-win32. I've tried contacting the current maintainer with no success. All the source files are about 18 months old and CVS hasn't been touched in as long. Also, what version of amanda have you gotten it to work with? There was a previous response from someone who couldn't get it to work on the more recent code. =G=
Re: raw device permissions
On Thu, Sep 12, 2002 at 12:42:57PM +0200, Mozzi wrote: Hi This is my stupid question of the week ;-) Sorry but my brain has deflated. Please bear with me for when my newbie howto is finished I hope it will stop questions like this. This is a direct quote from the INSTALL file B. Set up your raw disk devices so that the dumpuser can read them, and /etc/dumpdates so that the dumpuser can write to it. Normally this is done by making the disk devices readable by (and dumpdates read/writable by) group `operator', and putting the dumpuser into that group. Now my problem: Getting dumpuser to read the raw devices. I see in Red-Hat the default group is disk [root@backupserver docs]# ls -ahl /dev/hda brw-rw1 root disk 3, 0 Apr 11 16:25 /dev/hda I can't just put dumpuser into group disk as that wil give it full read write access. I don't think it wil be a good idea to revoke write privelages from disk ;-)and it will not be a good idea to change the group.So what now ? This is what stumps me. Does linux (i.e. your RH version) support ACL's (access control lists). If so, they allow much finer granularity. Like, amanda if they are presently in group backup can read this file. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Tape technology
[ On Thursday, September 12, 2002 at 10:28:13 (+0200), Brian Jonnes wrote: ] Subject: Re: Tape technology about 1600 USD at the time. Is it as dependable as tape? Time will tell. Can you take it offsite? In a sense, yes, by cycling enough drives thru each slot in the array and letting the raid rebuild Well it wouldn't work well that way, though with a mirror of a pair of mirrors you could remove either underlying pair of mirrored drives, then add a new pair of mirrored drives and re-construct the outer mirror. That way you'd have two copies of the data -- one could go off-site for reduncancy and disaster recovery purposes and one could stay on-site for quick retrieval. Maxtor announced low-priced 320GB drives just the other day I'm not really keen on this idea. Although relative to the price of a DDS drive it is affordable (for just one or two harddrives). My main problem is that the drives will be handled by average users. Hrm. Put the drives in canisters. Good ones add to the cost, but that's the only way you'll be easily able to hot-swap ATA drives anyway. By this point I probably wouldn't be using amanda though -- unless I had disk-full clients that couldn't run rsync. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
Re: HELP : amlabel - no tape online
On Thu, Sep 12, 2002 at 08:35:16AM -0700, Vivek Singh wrote:
Hi,
I am a newbie to Amanda. I have set up version
2.4.2.p2 on a RedHat
Linux 7.3 system with a HP SureStore 24x6 external
drive (HP C1557A).
Installation of amanda went on fine. Here are relevant
portions from
the amanda.conf file :
**
*
runtapes 1# number of tapes to be used in a single
run of amdump
tpchanger /etc/amanda/daily/chg-zd-mtx # the
tape-changer glue
script
tapedev /dev/nst0 # the no-rewind tape device to be
used
rawtapedev /dev/nst0# the raw device to be used
(ftape only)
changerfile /etc/amanda/mtx-changer
changerdev /dev/sg0
tapetype HP1557A # what kind of tape it is (see
tapetypes below)
labelstr ^DailySet1-[0-9][0-9][0-9] # label
constraint regex: all
tapes must match
[]
define tapetype HP1557A {
comment HP SureStore DAT24x6e tape drive
# data provided by Ivo Clarysse
length 12000 mbytes
filemark 111 kbytes
speed 3000 kbytes
}
**
I have tried using the mtx-changer command, and can
eject and load
individual tapes using it. However, when after all
configuration was
done, and I wanted to label a tape using the command:
su amanda -c amlabel daily DailySet1
Note:
labelstr ^DailySet1-[0-9][0-9][0-9] # label
Your label string says each tape must be labeled with a unique
string after the word DailySet1 consisting of a dash and 3 digits.
I get this error:
*
labeling tape in slot /etc/amanda/daily/chg-zd-mtx:
([: too many
arguments):
rewinding
amlabel: no tape online
*
Note that this error is being brought to you by the chg-zd-mtx command.
Almost always, the chg-* scripts will need some tuning for the local
environment. One mtx version does not print the same string, for the
same type of drive, as the next.
For debugging you can (as amanda-user) cd to the config dir (?daily?).
The run chg-zd-mtx directly to manipulate the changer.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Output of tapetype
On Thursday 12 September 2002 12:07, Gene Heskett wrote:
On Thursday 12 September 2002 11:28, rmckeever wrote:
Hello,
Im learning amanda so thanks for your time.
What does this mean when running tapetype:
# ./tapetype -f /dev/rmt/1ln
wrote 2266437 32Kb blocks in 6931 files in 28845 seconds (short
write) wrote 1826089 32Kb blocks in 11203 files in 27217 seconds
(short write)
The above is normal output just so you know that tapetype hasn't
gone to vegas to play the slots with your money. :-)
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 93147 mbytes
filemark 3298 kbytes
speed 2330 kps
}
Looks good if its supposed to be a 10 gig tape. If not, then
check to see if the hardware compression is on, which for amanda
is a no-no. See my other recent messages about getting it turned
off and kept off.
Darn, I have got to get my eyes recalibrated. 93 GIGS doesn't sound
right.
Should I really use that?
We have a :
SONY SDX-500C with a 15 slot stacker SPECTRA 215 1019
Thanks.
Rob
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
DEBRA Wagy/St Louis/IBM is out of the office.
I am out of the office from 09/06/2002, returning 09/23/2002. You will receive only this notification of my absence prior to my return, at which time I will respond. I am out of the office from9/02/2002 thru 9/20/2002. I will be returning on 9/23/2002. I will respond to your message when I return. If you need immediate help Contact one of the following: LInda Seeba - 45190 or Karla Ross - 29964.
Re: amverify only on most recent set
Hi Andrew,
I include a patch to amverify that add a third argument, the number of tape
you want to verify, it will take runtapes if the argument is absent.
I also include a new program (amverifyrun) which verify the tape
written in the latest run (amdump or amflush), this script grep
the log file to find the first slot to verify and the number of
tape use, it then call amverify with the appropriate parameters.
The third attachment is a patch for configure and Makefile to compile
and install amverifyrun.
I only did a few test, I'm using runtapes=1. Could you test it and
tell me if it works in your configuration.
Jean-Louis
On Wed, Sep 11, 2002 at 08:33:16AM -0700, Andrew Williams wrote:
Is there a way to get amverify to only check tapes from the most recently
completed backup? I currently have runtapes set to 3 (to allow for new hosts
I'm going to be adding in the next few weeks) however the current backup only
takes one tape. amverify is currently scanning it's 3rd tape (from a backup 2
days ago) This takes a ton of time to scan tapes that have already been
scanned. Any way around this other than writing a script to check the output
of amtape show and run amverify per slot on the newest tapes only? Also, if
you specify a slot with amverify does it then ignore the runtapes option?
- andrew
__
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.4.3b4.orig/server-src/amverify.sh.in
amanda-2.4.3b4.new/server-src/amverify.sh.in
--- amanda-2.4.3b4.orig/server-src/amverify.sh.in Thu Sep 12 15:05:31 2002
+++ amanda-2.4.3b4.new/server-src/amverify.sh.inThu Sep 12 15:26:03 2002
@@ -269,7 +269,7 @@ if [ X$TPCHANGER = X ]; then
else
CHANGER_SLOT=${2:-current}
$Echoe Tape changer is $TPCHANGER...
- SLOTS=`getparm runtapes`
+ SLOTS=${3:-`getparm runtapes`}
[ X$SLOTS = X ] SLOTS=1
if [ $SLOTS -eq 1 ]; then
p=
#!/bin/sh
#
prefix=@prefix@
exec_prefix=@exec_prefix@
sbindir=@sbindir@
libexecdir=@libexecdir@
PATH=$sbindir:$libexecdir:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ucb
export PATH
USE_VERSION_SUFFIXES=@USE_VERSION_SUFFIXES@
if [ $USE_VERSION_SUFFIXES = yes ]; then
SUF=-@VERSION@
else
SUF=
fi
getparm() {
$AMGETCONF $CONFIG $1 2/dev/null | grep -v BUGGY
}
CONFIG=$1
libexecdir=$libexecdir
sbindir=$sbindir
AMGETCONF=$sbindir/amgetconf$SUF
AMVERIFY=$sbindir/amverify$SUF
LOGDIR=`getparm logdir`
AMDUMPLOG=${LOGDIR}/amdump.1
AMFLUSHLOG=${LOGDIR}/amflush.1
if [ -e $AMDUMPLOG ]; then
if [ -e $AMFLUSHLOG ]; then
if [ $AMDUMPLOG -nt $AMFLUSHLOG ]; then
AMLOG=$AMDUMPLOG
else
AMLOG=$AMFLUSHLOG
fi
else
AMLOG=$AMDUMPLOG
fi
else
if [ -e $AMFLUSHLOG ]; then
AMLOG=$AMFLUSHLOG
else
echo Nothing to verify
exit 1;
fi
fi
FIRST_SLOT=`grep taper: slot $AMLOG | sed 1q | sed 's/://g' | awk '{print $3}'`
NBTAPES=`grep -c taper: wrote label $AMLOG`
$AMVERIFY $CONFIG $FIRST_SLOT $NBTAPES
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.4.3b4.orig/configure.in amanda-2.4.3b4.new/configure.in
--- amanda-2.4.3b4.orig/configure.inFri Sep 6 10:00:39 2002
+++ amanda-2.4.3b4.new/configure.in Thu Sep 12 14:28:44 2002
@@ -2720,6 +2720,7 @@ AC_OUTPUT( \
server-src/amoverview.plserver-src/amrmtape.sh \
server-src/amtoc.pl server-src/amverify.sh \
server-src/Makefile server-src/amstatus.pl \
+ server-src/amverifyrun.sh \
\
tape-src/Makefile \
\
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.4.3b4.orig/server-src/Makefile.am amanda-2.4.3b4.new/server-src/Makefile.am
--- amanda-2.4.3b4.orig/server-src/Makefile.am Sun Mar 24 18:06:44 2002
+++ amanda-2.4.3b4.new/server-src/Makefile.am Thu Sep 12 14:25:09 2002
@@ -27,7 +27,7 @@ libexec_PROGRAMS =amindexdamlogroll am
sbin_SCRIPTS = amcheckdb amcleanup amdump \
amoverview amrmtapeamtoc \
- amverifyamstatus
+ amverifyamverifyrun amstatus
libamserver_la_SOURCES=amindex.c changer.c \
conffile.c diskfile.c driverio.c \
Pics for you
GET FREE ACCESS TO XXX PORN!INSTANT ACCESS... 100% FREE HARDCORENote: If you would would like to be removed from our list, please reply to this email with the word REMOVE as the subject j6fwkdud10q
Re: samba dumps no worky
Galen Johnson wrote: Hi folks, I'm moving forward with backing up my windows machines amanda. I've gotten samba talking to my windows boxes and can run 'smbclient -Uamanda%herpasswd -L windows_host' just fine.. .I see all the shares, etc...I can also see my samba server on the windows boxes. However, whwne I run 'amdump daily' I get the following: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to fwpilot timed out. fwpilot//pdc_circ/c$ RESULTS MISSING fwpilot//pdc_circ/d$ RESULTS MISSING I think I have tracked it down to the fact that I can only see what's shared on the server but not actually access them. Any hints would be helpful...I've added amanda to the group which should give her enough permissions for everything (full control under windows perms). I'm at my wits end...any input, leads, places to look...you get the idea...anecdotes are welcome. =G= Issue was resolved by including the optional domain field in /etc/amandapass. I'd recommend that this field be upgraded to 'recommended' instead of 'optional'. Thanks to Jon LaBadie for his ever insightful suggestions. They really helped since I wasn't thinking straight (too much work, too little sleep). =G=
Re: Tapetype
Not so sure about this. I had a Travan-4 tape whizzing away for 24 hours. Now, I've had full tapes before, and the dump time... lemme pull out the reports: Output Size (meg)3863.3 3829.7 33.6 ... Tape Time (hrs:min)2:15 2:05 0:10 Tape Size (meg) 3864.1 3830.0 34.1 Tape Used (%) 101.7 100.80.9 (level:#disks ...) So for a tapetype run it should take 4h30... Give it 5 hours. I gave up on it and went to the FAQO. ..Brian On Thu 12 Sep 02 17:15, Gene Heskett wrote: On Thursday 12 September 2002 10:48, Mozzi wrote: Hi Watch out for tapetype!!! I have a Tandberg VS80 DLT 40/80 Gig drive I gave it the command #./tapetype -e 40960 -f /dev/nst0 -t TandbergVS80 It has been going for 26 hours now,and no end in sight. Mozzi It will get done at some point. It has to write the tape completely full twice, and a slow writing big tape will take a while. -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Re: Tape DDS-3 values
On Thu 12 Sep 02 16:38, Niall O Broin wrote: This is true but as a friend pointed out to me recently when I was having some tape reading problems - if you get some bit errors reading a tar file from a tape, most likely asll you will lose is the affected file. If OTOH you get bit errors reading a gzipped tar file, you most likely will not be able to read anything after the bit errors. Just something to be aware of. So... when, and how much work is it to get bzip2 used. Apparently it doesn't suffer from this problem? If I were to replace (by hook or by crook) the COMPRESS_PATH to bzip2 would that work? And what is the opinion of the Right Way to do this? Regards, Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
