tapetype definition question
I ran the tapetype util on two drives and below are the definitions that I
received. My question is, why did the filemarks both return 0? I believe
that I followed the instructions and I used the non-rewinding device. I am
new to amanda and looking for a solution so that I can convert 3 of my
offices to Linux and get rid of Novell and NT. Any help making this work is
greatly appreciated.
Thanx,
Brian W.
define tapetype HP-T20e {
comment "HP SureStore T20e"
length 9749 mbytes
filemark 0 kbytes
speed 748 kbytes
}
define tapetype AIWA-TD-8000 {
comment "Aiwa TD-8000"
length 4104 mbytes
filemark 0 kbytes
speed 386 kbytes
}
Re: tapetype definition question
Hi,
these values look all okay.
modern streamer integrate the filemarks in the datastream,
or only need a few byte for a filemark and cause of that
you get 0 for the size of them.
As i said no problem.
Christoph
Brian Whitehead schrieb:
>
> I ran the tapetype util on two drives and below are the definitions that I
> received. My question is, why did the filemarks both return 0? I believe
> that I followed the instructions and I used the non-rewinding device. I am
> new to amanda and looking for a solution so that I can convert 3 of my
> offices to Linux and get rid of Novell and NT. Any help making this work is
> greatly appreciated.
>
> Thanx,
> Brian W.
>
> define tapetype HP-T20e {
> comment "HP SureStore T20e"
> length 9749 mbytes
> filemark 0 kbytes
> speed 748 kbytes
> }
>
> define tapetype AIWA-TD-8000 {
> comment "Aiwa TD-8000"
> length 4104 mbytes
> filemark 0 kbytes
> speed 386 kbytes
> }
running as user "amanda" instead of "operator"?
Hi. I configured Amanda with --with-user=amanda and am running all of the am* programs under the amanda username. When running amcheck, I get: Amanda Backup Client Hosts Check ERROR: running as user "amanda" instead of "operator" What gives here? Of course it's running as user "amanda"! Ben
A question about performance
Scenario: I have a machine with a bunch of 18G disks and one raid5 arrray of 420G [1] I have hooked up an LTO ultrium tapedrive to that machine (100G uncompressed, 30Mbit/s transfer rate (that's 10G per hour uncompressed)) if I ufsdump [2] the raid array to that LTO drive, I get indeed almost 10G per hour. I was using amanda, with some space on that disk allocated as holding space. And I was getting arund 6-7000 kps Xfer rate. since all disks were local to my machine, I changed amanda.conf to have - only 1 dumper - not use any holding space The next amanda run took over 18 hours to complete (a Xfer rate of less than 1G per hour (350 - 400 kps) Now I switched it back to - multiple dumpers - use holding disk (accept for the RAID array itself) and it looks im getting 6 - 7000 kps again. Can anyone explain this to me ? I was expecting that since all disks are local disks, I would be getting roughly the same results in both setups. [1] raid 5 and 1 hotspare, disks hotswappable .. had one disk die in there, replaced it whitout having to shut down the machine or the diskpack .. [2] Yup, Im using solaris (2.6 and up ) On a related note: I was trying to use gnutar iso ufsdump to backup the raidarray , so that I could use exclude files , and the tar estimate takes easily over an hour , the ufsdump based estimates are done much sooner (30-ish minutes). Any clue ;) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: running as user "amanda" instead of "operator"?
On Jan 17, 2001, Ben Elliston <[EMAIL PROTECTED]> wrote:
> Amanda Backup Client Hosts Check
>
> ERROR: running as user "amanda" instead of "operator"
Looks like it is the client that is complaining. Maybe xinetd is
still running an older version of amandad, that wants to be started as
user operator?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: running as user "amanda" instead of "operator"?
oliva wrote: > Amanda Backup Client Hosts Check > > ERROR: running as user "amanda" instead of "operator" Looks like it is the client that is complaining. Maybe xinetd is still running an older version of amandad, that wants to be started as user operator? xinetd is running /usr/local/libexec/amandad, which I just re-installed to be certain. It's from a build tree whose config.status reads: # ../amanda-2.4.2/configure --with-fqdn --with-user=amanda --with-group=disk Any other ideas? Ben
temporary skip a tape
Hi, I have six tapes in my tape cycle and according to amanda, tonight's dumps should go to the tape "daily-0". However, exactly that tape isn't available at the moment, and I don't want to wait with the backup until I have access to that particular tape again. Can I somehow tell amanda to skip that tape and use "daily-1" just for this time instead? Is this a faq? / Erik -- erik eriksson; [EMAIL PROTECTED]; +4613203202(work); +46705228912(cell)
Re: running as user "amanda" instead of "operator"?
On Jan 17, 2001, Ben Elliston <[EMAIL PROTECTED]> wrote:
> xinetd is running /usr/local/libexec/amandad, which I just re-installed to
> be certain. It's from a build tree whose config.status reads:
> # ../amanda-2.4.2/configure --with-fqdn --with-user=amanda --with-group=disk
> Any other ideas?
Have a look at /tmp/amanda/amandad.debug
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: temporary skip a tape
On Jan 17, 2001, erik eriksson <[EMAIL PROTECTED]> wrote:
> Can I somehow tell amanda to skip that tape and use "daily-1" just
> for this time instead?
Reduce tapecycle by one, so that Amanda will accept daily-1. You may
also want to mark daily-0 as no reuse with amadmin.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: running as user "amanda" instead of "operator"?
no, go to the top of your amanda.conf file, and change the "run as
operator" to "run as amanda".
Alexandre Oliva wrote:
> On Jan 17, 2001, Ben Elliston <[EMAIL PROTECTED]> wrote:
>
> > Amanda Backup Client Hosts Check
> >
> > ERROR: running as user "amanda" instead of "operator"
>
> Looks like it is the client that is complaining. Maybe xinetd is
> still running an older version of amandad, that wants to be started as
> user operator?
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist*Please* write to mailing lists, not to me
tar 1.12
The docs/INSTALL file says to use GNU tar 1.12 -- is there any reason why a later version, such as 1.13, could not be used (with the provided patches)? Ben
Re: Index server error?
"John R. Jackson" wrote: > >> SCNF DailySet1 > > Is "DailySet1" the name of your Amanda configuration? Amrecover > (amindexd) is known to mis-behave when given a bad config name (it's on > my TODO list). > > If that doesn't help, run amindexd by hand, **as the Amanda user**, > with the "-t" option, e.g.: > > $ su > # su "/.../amindexd -t" > > Then enter these commands: > > SECURITY USER root > DATE 2001-01-16 > SCNF DailySet1 > > and see if it has anything more interesting to say. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] It did have something more interesting, actually. I needed to add root access to .amandahosts from the host, and then add the correct name of the Amanda configuration. All now works very well. Thanks again!! Eric
Re: Diagnosing client-side errors
>Date: Tue, 16 Jan 2001 18:45:43 -0500 >From: "John R. Jackson" <[EMAIL PROTECTED]> >>i thought you needed to use >>/dev/sdan where n is the number of the partition >No, you don't. You may use one of these forms, give the above comments >about system configuration are taken into account: > sda (the block device name) > rsda (the "raw"/character device name) > /dev/sda (full path to the block device name) > /dev/rsda (full path to the "raw"/character device name) > /the/mount/point (file system mount point) >The exact syntax depends on the OS. And I encourage folks who are in the position of deciding which form(s) to use to consider the issue from the perspectives they are likely to have when (note lack of conditional) they need to perform a restore. For me, the answer was to use names that denote function, vs. implementation -- in the case in point, I use mount points (now; I had started with device names). And that's probably a Good Thing in my case, because some of the device names have changed with changing OS (FreeBSD) levels. Cheers, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391
Re: A question about performance
Well, all I can do is confirm the 6000-7000KB/sec transfer rate. I'm using Solaris 2.5.1 with an IBM LTO ultrium (I'm still trying to get Amanda to work with the autoloader) and I get the same performance you do. I have one holding disk big enough to hold a dump of any other disk I'm trying to back up. Regards, Scott On Wed, 17 Jan 2001, Gerhard den Hollander wrote: > Date: Wed, 17 Jan 2001 11:55:31 +0100 > From: Gerhard den Hollander <[EMAIL PROTECTED]> > Reply-To: Gerhard den Hollander <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: A question about performance > > Scenario: > > I have a machine with a bunch of 18G disks and one raid5 arrray of 420G [1] > > I have hooked up an LTO ultrium tapedrive to that machine > (100G uncompressed, 30Mbit/s transfer rate (that's 10G per hour > uncompressed)) > if I ufsdump [2] the raid array to that LTO drive, I get indeed almost 10G > per hour. > > I was using amanda, with some space on that disk allocated as holding > space. And I was getting arund 6-7000 kps Xfer rate. > > since all disks were local to my machine, I changed amanda.conf to have > - only 1 dumper > - not use any holding space > > The next amanda run took over 18 hours to complete (a Xfer rate of less > than 1G per hour (350 - 400 kps) > > Now I switched it back to > - multiple dumpers > - use holding disk (accept for the RAID array itself) > and it looks im getting 6 - 7000 kps again. > > Can anyone explain this to me ? > > I was expecting that since all disks are local disks, I would be getting > roughly the same results in both setups. > > [1] raid 5 and 1 hotspare, disks hotswappable .. had one disk die in there, > replaced it whitout having to shut down the machine or the diskpack .. > > [2] Yup, Im using solaris (2.6 and up ) > > On a related note: > > I was trying to use gnutar iso ufsdump to backup the raidarray , so that I > could use exclude files , and the tar estimate takes easily over an hour , > the ufsdump based estimates are done much sooner (30-ish minutes). > > Any clue ;) > > Kind regards, > -- > Gerhard den Hollander Phone +31-10.280.1515 > Technical Support Jason Geosystems BV Fax +31-10.280.1511 > (When calling please note: we are in GMT+1) > [EMAIL PROTECTED] POBox 1573 > visit us at http://www.jasongeo.com 3000 BN Rotterdam > JASON...#1 in Reservoir CharacterizationThe Netherlands > > This e-mail and any attachment is/are intended solely for the named > addressee(s) and may contain information that is confidential and privileged. >If you are not the intended recipient, we request that you do not > disseminate, forward, distribute or copy this e-mail message. > If you have received this e-mail message in error, please notify us >immediately by telephone and destroy the original message. >
Changing OS of amanda server
Hi folks For various reasons, I've decided to change the OS on my amanda server from RH Linux to Solaris 8 x86. I'm not changing any hardware, just the OS. After the OS change, I want amanda to resume operation as normal. Am I correct in thinking that all the files I need to keep are in /etc/amanda and /var/amanda ? I've only had to amrestore a couple of times so ~root/.amandahosts on this server is sparse. Thanks! Michael
Re: tar 1.12
On Thu, Jan 18, 2001 at 12:46:11AM +1100, Ben Elliston wrote: > The docs/INSTALL file says to use GNU tar 1.12 -- is there any reason why a > later version, such as 1.13, could not be used (with the provided patches)? You can use tar-1.13.18 with the patch from http://www.amanda.org/patches.html The docs/INSTALL file need an update. Jean-Louis -- 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
No Subject
I want to run a backup of our 2 servers and a few windows clients. I want to do a 2 week cycle which does 2 backups of the whole system in those 2 weeks. How should i label my tapes and what are the settings for amanda.conf ? thanx in advance Nicky Haan Unix/Linux Sysadmin / Systems Engineer NetCASE Interactive Solutions Dr. Nolenslaan 140 6136 GV Sittard Netherlands Tel: +31(0)46 420 1880 Fax: +31(0)46 420 1881 E-Mail: [EMAIL PROTECTED] Web: www.netcase.nl
Re: amrecover failure
Okay, I see. amrecover is trying to put the files back to baboquivari, the NT machine that crashed. What I was trying to do was restore the specified files to a local drive on navajo (my amanda server) because baboquivari isn't going to be coming back, and there were just a couple of files that needed to be retieved. How does one tell amrecover to place the restored files elsewhere? I did an lcd to where I wanted them to appear, but apparently this isn't sufficient? --- Eric Wadsworth On Tue, 16 Jan 2001, John R. Jackson wrote: > >Now it gives this error: > >added interface ip=10.0.2.20 bcast=10.0.2.255 nmask=255.255.255.0 > >Connection to failed > >extract_list - child returned non-zero status: 1 > > Take a look at /tmp/amanda/amrecover*debug on navajo.hq.consys.com. > It should list the smbclient command used. I'm guessing that command is > failing to connect to the PC (note the "Connection to failed" message), > or it is badly formatted (note the " " in the error message). > > >Eric Wadsworth > > JJ >
Re: amrecover failure
On Jan 17, 2001, [EMAIL PROTECTED] wrote:
> How does one tell amrecover to place the restored files elsewhere? I
> did an lcd to where I wanted them to appear, but apparently this
> isn't sufficient?
This isn't possible with Amanda 2.4.1p1's amrecover. With 2.4.2's,
the default (IIRC) is to restore to local files, but there's a new
command to switch to/from SMB/local restores.
In case you're using 2.4.1p1, you'll be able to get the tar-file into
the local disk (or into a pipe to tar) using amrestore.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Changing OS of amanda server
On Jan 17, 2001, Michael Peterson <[EMAIL PROTECTED]> wrote:
> change the OS on my amanda server from RH Linux to Solaris 8 x86.
Bad move :-) :-)
> Am I correct in thinking that all the files I need to keep are in
> /etc/amanda and /var/amanda?
Yep. As long as you didn't configure Amanda to use different areas,
of course.
You might also want to restore all of `/' and get back to the one true
operating system :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amcheck with gnutar
Takayuki Murai wrote: > > my client's /etc/group: > --- > operator:*:5:root,amanda > amanda:*:1000:amanda > ... > > > The files of permissions are: > > > > > > -rwsr-x--- 1 rootamanda 52300 Jan 15 17:06 runtar > > > drw-rw-rw- 2 amanda amanda 512 Jan 16 15:58 gnutar-lists > > > Since amanda is in the operator group on your client, runtar, at least, should be owned by group operator, not group amanda. I see that you have a user amanda (on the client and the server), a group amanda (on the client, as seen on the files permissions above), a group operator (on the client) and a group disk (on the server). Of course, you can do it that complicated, but you must know what you are doing ;-) I suggest you stick to *one* AMANDA user and *one* group with disk access rights for both server and client. I have decided for "amanda" as the AMANDA user and "disk" for the disk access group where amanda belongs. It is then enough to change the *group* ownership to the disk group. So I have: -rwsr-xr-- 1 root disk21344 Dec 10 16:42 /usr/lib/amanda/runtar > Please give me some advice!! > > taka > > Takayuki Murai -'o^a?@-2"V- > [EMAIL PROTECTED] > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of > > [EMAIL PROTECTED] > > Sent: Tuesday, January 16, 2001 5:45 PM > > To: [EMAIL PROTECTED] > > Subject: Re: amcheck with gnutar > > > > > > taka murai hath declared on Tuesday the 16 day of January 2001 :-: > > > > > > ERROR: dirac: [can not execute /usr/local/libexec/runtar: > > Permission denied] > > > ERROR: dirac: [can not read/write /usr/local/var/amanda/gnutar-lists/.: > > > Permission denied] > > > > > > How can I do to get Permission allowed? > > > > First off, what user are you running amandad as on the client? > > In /etc/inetd.conf: > > > > amanda dgram udp waitamanda /usr/local/libexec/amandad amandad > > ^^ > > > > Next, is this user in the amanda group to be able to run runtar, > > it it possibly operator (Freebsd) or disk (linux), you could just > > add amanda to the amanda group in /etc/group as you want amanda to > > stay in the group that has read access to the disks (operator/disk) > > > > /etc/group: > > amanda:*:6:amanda (or something similar...) > > > > As for gnutar-lists... *shrug* > > check the permission to the directories under it, /usr/local/var/, > > /usr/local/var/amanda. Also it is a bad idea to have write permission > > to all other groups on the system, someone could be nasty! > > > > -- > > Robert "bobb" Crosbie. > > System Administrator, Internet Ireland. > > -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Will amanda do what I need?
Ed Troy wrote: > > I have a small peer to peer network with several windows 95 machines and a > windows 2000 machine and a linux machine. Ideally, what I would like to be > able to do is to backup everything, on a regular, to a very large (and > prehaps removable) ata hard drive on the linux box. ... > Is Amanda what I am > looking for? AMANDA can do what you want, just leave the files that AMANDA creates on your "very large" drive. Depending on the version you will use, she might not "trust" those files (trust, that is, that they really have made it to some tape ultimately), so you might have to use some trick. As far as Windows is concerned you will not be able to backup the registry, or swap file, or such active or system files, so a separate measure has to taken for them. You will experience problems in the estimates of incrementals for the vfat filesystems (not an AMANDA problem per se, rather a tar/kernel issue): sometimes they will be as large as full ones. To get around this, you will need to hack AMANDA a little (but really only just a bit) and recompile (I will post a report on this soon, whatever soon means...). You will need SAMBA on you Linux box to back the Windows boxes with AMANDA. And you will need to be fluent in commands like dd, tar, gzip and basic Linux administration. Now the good news: After having gone around all the pitfalls above, backups will never be an issue for you again! AMANDA will take care of everything (Linux _and_ Windows hosts) and you will be free for more creative tasks! Never again having to think "Hmm... shall I do a full backup on that host today, and an incremental level 2 for that one, or did I already do it yesterday - and which backups are due for the other one?". All backups with one method, with a stable system :-), with classic, standard tools, with a sophisticated strategy (one that really deserves this name). Configure and forget. Period. PS: You don't need (portable) backup media that are so large. The important thing is that each medium has enough space for a full backup of some (configurable in the disklist) portion of your filesystem plus the incrementals for the rest (the increment level is decided by AMANDA, so what really matters is the daily rate of change of your systems). Read http://www.backupcentral.com/amanda.html for the details. -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Changing OS of amanda server
>> change the OS on my amanda server from RH Linux to Solaris 8 x86. >Bad move :-) :-) I've never had to set up a cron job on a SunOS 5 machine that runs every minute, ifconfig'ing down and up the ethernet interface and re-adding the default route. This is what I have to do on my laptop when running RH Linux to keep the ethernet working.
Tried 3 different ways to restore, none work
Amanda has been backing up the network for a couple of months now, and we had an NT box crash. I need to restore the contents of it's C drive. When it was rebuilt yesterday, its name was changed from baboquivari to cerbat (baboquivari is a pain to spell), so amrecover wouldn't work. So we scrapped that, and I decided to do it manually. The level 0 dump is on tape 001, but for some reason there are two lvl one dumps. (?) I did this command, and these are the relevant portion of the results: amadmin DailySet1 find | grep babo 2001-01-09 navajo.hq.consys.com //baboquivari/c_backup 1 DailySet1-000 36 OK 2001-01-10 navajo.hq.consys.com //baboquivari/c_backup 0 DailySet1-001 38 OK 2001-01-11 navajo.hq.consys.com //baboquivari/c_backup 1 DailySet1-002 33 OK 2001-01-12 navajo.hq.consys.com //baboquivari/c_backup 1 DailySet1-003 35 OK I copied three files from the tapes 001 002 and 003 to a large hard drive on my UNIX box (navajo, which also happens to be the amanda host, samba server, etc). Here are the files: navajo.hq.consys.com.__baboquivari_c__backup.20010110.0 navajo.hq.consys.com.__baboquivari_c__backup.20010111.1 navajo.hq.consys.com.__baboquivari_c__backup.20010112.1 Then I tried using the UNIX restore command to rebuild the directory tree so I can pull the needed files from it. All I can get restore to give me is this error message: Tape is not a dump tape After reading the man page for restore about a dozen times, I think I've tried every reasonable combination of parameters. It refuses to read these files from disk. I've read the whole chapter 11 "backups" from the UNIX System Administrators Handbook also, but still nothing helpful. So, it must need the files on tape, right? So I tried sticking the tape 001 back in there, which holds the level 0 dump, but it still doesn't work. Just just tells me that the tape is not a dump tape. What am I doing wrong??? Any advice is appreciated. My failure to restore is resulting in fingers beginning to point. :(
Re: Tried 3 different ways to restore, none work
Eric Wadsworth <[EMAIL PROTECTED]> writes: > Then I tried using the UNIX restore command to rebuild the directory tree > so I can pull the needed files from it. All I can get restore to give me > is this error message: > Tape is not a dump tape Wouldn't that be tar-files? I think that is the only format that can be used for dumping Windows machines? Jens Bech Madsen -- Jens Bech Madsen The Stibo Group, Denmark
Re: Tried 3 different ways to restore, none work
Ah, yes, this was the answer. I untarred the lvl 0 dump first, then the others, assuming they would over-wright the files from the lvl 0 dump. I guess the only difference between the backed-up directory tree and this one I just created is that files that any files that were deleted will be maintained. This is fine, as the user is going to use this directory tree to get whatever he wants. Thanks! --- Eric On 17 Jan 2001, Jens Bech Madsen wrote: > Eric Wadsworth <[EMAIL PROTECTED]> writes: > > Then I tried using the UNIX restore command to rebuild the directory tree > > so I can pull the needed files from it. All I can get restore to give me > > is this error message: > > Tape is not a dump tape > > Wouldn't that be tar-files? I think that is the only format that can be > used for dumping Windows machines? > > Jens Bech Madsen > -- > Jens Bech Madsen > The Stibo Group, Denmark >
Re:
Nicky Haan wrote:
>
> I want to run a backup of our 2 servers and a few windows clients.
> I want to do a 2 week cycle which does 2 backups of the whole system in
> those 2 weeks.
> How should i label my tapes and what are the settings for amanda.conf ?
> thanx in advance
There are no restrictions on labelling, unless *you* pose one in
amanda.conf ("labelstr" parameter).
Two backups of the whole system in two weeks means one full backup of
the system per week (I'am still good at mathematics ;-) ) => dumpcycle =
1 week. (Of course, striktly speaking, this is not necessary, because to
get 2 full backups in two weeks there are more possibilities than just
the suggested "one full backup per week" way, but I doubt you could
achieve this in AMANDA otherwise).
The rest is up to you:
- How often do you want to run AMANDA - once per week, every day...? =>
runspercycle.
- How many tapes do you want to use each time you run it - 1, 10...? =>
runtapes. But be careful: you could choose runtapes to be 1, but if you
choose runspercycle to be 1 (meaning AMANDA should run only once per
dumpcycle), then runtapes should be enough tapes to backup all your
system on one run!
- How many tapes do you want to commit to this operation - 15, 20...? =>
tapecycle. But you are not totally free here either: tapecycle should be
*at least* runspercycle times runtapes plus a few tapes more (for
unforseeable events). There is no upper limit however - except your
budget :-)
For the rest of the settings, read the comments in amanda.conf. If you
still don't come through, read http://www.backupcentral.com/amanda.html,
study the FAQ and search this lists's archives.
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: running as user "amanda" instead of "operator"?
>xinetd is running /usr/local/libexec/amandad, which I just re-installed to >be certain. It's from a build tree whose config.status reads: > ># ../amanda-2.4.2/configure --with-fqdn --with-user=amanda --with-group=disk That was not the question. The question was, what user is the xinetd config file running amandad as? That's set up by hand by you, not by the Amanda installation process. >Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: running as user "amanda" instead of "operator"?
>xinetd is running /usr/local/libexec/amandad, which I just re-installed to
>be certain. It's from a build tree whose config.status reads:
>
># ../amanda-2.4.2/configure --with-fqdn --with-user=amanda --with-group=disk
That was not the question. The question was, what user is the xinetd
config file running amandad as? That's set up by hand by you, not by
the Amanda installation process.
service amanda
{
socket_type = dgram
wait= no
user= amanda
server = /usr/local/libexec/amandad
}
Re: running as user "amanda" instead of "operator"?
Sorry. I should have looked at where that message came from in the first place. Sharon England had it right. The error comes from amcheck itself, not the client. It says amcheck looked up "dumpuser" in amanda.conf and found "operator", but you are trying to run it as user "amanda". One of those is going to have to give :-). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Reusing tapes
I am in the process of debugging my Amanda setup and wish to reuse the same tape over and over. Short of using `mt erase' to completely erase the tape, is there a way I can prevent Amanda from aborting because it thinks I'm overwriting a tape from the backup set? Thanks, Ben
Re: Reusing tapes
>I am in the process of debugging my Amanda setup and wish to reuse the same >tape over and over. Short of using `mt erase' to completely erase the tape, >is there a way I can prevent Amanda from aborting because it thinks I'm >overwriting a tape from the backup set? Erasing the tape won't help. Try "amrmtape". >Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Reusing tapes
[amanda@tape /]$man amrmtape :) -Original Message- From: Ben Elliston [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 17, 2001 5:14 PM To: [EMAIL PROTECTED] Subject: Reusing tapes I am in the process of debugging my Amanda setup and wish to reuse the same tape over and over. Short of using `mt erase' to completely erase the tape, is there a way I can prevent Amanda from aborting because it thinks I'm overwriting a tape from the backup set? Thanks, Ben
Re: Reusing tapes
>Date: Thu, 18 Jan 2001 09:14:10 +1100 (EST) >From: Ben Elliston <[EMAIL PROTECTED]> >I am in the process of debugging my Amanda setup and wish to reuse the same >tape over and over. Short of using `mt erase' to completely erase the tape, >is there a way I can prevent Amanda from aborting because it thinks I'm >overwriting a tape from the backup set? When I was doing something similar, I found "amrmtape" sufficient. (And "mt erase" would not affect what amanda believes about the tape; it would merely disguise the fact that the tape is one that amanda had seen before.) Cheers, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391
running amverify
amverify was taking forever so I aborted it is there ayway to find out if amverify was hung or if it was just taking a long time to do its thing? amverify daily Wed Jan 17 17:08:13 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 ** results - amanda report * Subject: daily AMANDA VERIFY REPORT FOR daily119 Tapes: daily119 Errors found: aborted! amverify daily Wed Jan 17 17:08:13 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 aborted!
what tape device does amanda support?
Hello all, I am considering to get tape drive "SONY TSL-A500", and wondering if amanda supports it. Takayuki Murai -$BB<0f!!N4G7(B- [EMAIL PROTECTED]
Re: Weird illustration of peculiar interactions :-}
On Mon, 15 Jan 2001, Martin Apel wrote: >I implemented some changes in the driver that cause it to gather dumps >until a certain threshold is reached. Afterwards it will always write >the biggest dump still fitting on the tape. This works quite nicely for me >and improves tape utilization a lot. Unfortunately it also increases the >total dump time a bit, if your tape is slow. >I haven't released it yet, because I implemented it in Amanda 2.4.1p1 >and didn't come around to porting it to 2.4.2. >But if you like I can post the patches for 2.4.1p1. I have a perl script which will go through my holding disk and spit out a list of backup sets to select to best pack tapes. here's an example: [amanda@joi amanda]$ pack -C OffSite 138530/140906 ( 98%) /home/amanda/mnt/holdingdisk/OffSite/20010106 /home/amanda/mnt/holdingdisk/OffSite/20010114 116784/140906 ( 82%) /home/amanda/mnt/holdingdisk/OffSite/20010107 /home/amanda/mnt/holdingdisk/OffSite/20010108 114088/140906 ( 80%) /home/amanda/mnt/holdingdisk/OffSite/20010111 99327/140906 ( 70%) /home/amanda/mnt/holdingdisk/OffSite/20010112 Nothing left to pack! I amflush these to tapes to send to offsite storage. I've already done two tapes from this batch, I have four left to do. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: what tape device does amanda support?
On Thu, 18 Jan 2001, Takayuki Murai wrote: >Date: Thu, 18 Jan 2001 10:39:21 +0900 >From: Takayuki Murai <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: what tape device does amanda support? > >Hello all, > >I am considering to get tape drive "SONY TSL-A500", and wondering if amanda >supports it. It's not up to amanda. Check your platform's own list of supported scsi tapes and go from there. Amanda will use either gnu tar, samba, or your platform's native dump utility. It's those items which have to talk to your tape. Robots are a slightly different story. Amanda comes with a number of scripts you can adapt for use with your particular robot. As long as you can get a robot control script going, you're all set. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amandad not executing correctly
>The results from this are attached but I suspect that the extra output >you (John) were fishing for is: Yup. And in case anyone can't "read between the lines" :-), it said: ld.so.1: /usr/local/libexec/amanda/1.2.1p1/amandad: fatal: relocation error: file /usr/local/lib/libamanda-2.4.1p1.so.0: symbol open64: referenced symbol not found This looks to me like some kind of build problem, like Amanda was built on a system with large file support (64 bit file offsets, i.e. "open64") but is trying to be run on one without it. >Paul John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amanda hacks
Wed Jan 17 23:57:38 EST 2001 Hi All, We have been using amanda for years and are very happy with it. We recently purchased a new machine whose only purpose was to be a backup server. We purchased a lot of hard disk space with the hope of storing a weeks worth of backups on the machine, as well as going nightly to tape. This would allow us to do restores for data lost during the week (We have a 7 day dumpcycle) without having to retrieve the tapes from off-site. Great plan, but currently not possible (as far as I know) with amanda. Hence we came up with a neat plan to monitor the amdump log file and once the dump of one filesystem started our script would spawn a monitor process to wait until the dump was complete, as soon as it was done, it would copy the file from the holding disk into our weekly archive area. Not being C coders, this is implemented in perl, hence I am worried of the race condition where the file is dumped and removed from the holding disk before we get a chance to copy it over. Does anyone out there have a C hack that can do this? If anyone is interested in having a look at the perl code (Its not brilliant, or efficient, but it does the job) I would be happy to show it to those interested. Any FreeBSD users know of a hack using kqueue? Any other info would be appreciated. Andrew.
Re: running amverify
>... is there ayway to find out >if amverify was hung or if it was just taking a long time to do its thing? Look for blinking lights on the drive is the first thing that pops to mind :-). Next, I'd get a ps listing of what was running, "ps -fu ". If you see it sitting on "sleep" repeatedly with no more output, it's probably hung waiting on the drive to go ready or something like that. If it's sitting on GNU tar or dd, it's probably skipping though an image (i.e. doing what it's supposed to). Next, I'd get "lsof": ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/lsof.tar.gz This will let you see what offset various file descriptors are at (among a bajillion other things), so you can run it on whatever processes have the tape open and see if they are moving. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda hacks
>Not being C coders, this is implemented in perl, hence I am worried of >the race condition where the file is dumped and removed from the >holding disk before we get a chance to copy it over. I'd create another directory in the holding disk area parallel to the real holding disk, then hard link to the holding disk image. Use the hard link to do your copy. If Amanda removes it's link before you are done, no big deal. When both links are gone, the space will be released. See the "mkdir" and "link" Perl calls. Watch out for holding disk chunking, if you're using that. It will create multiple files and you'll need to deal with all of them (and they are not listed in the amdump log file). >Andrew. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda hacks
Thu Jan 18 00:43:47 EST 2001
Thanks for the quick reply.
With amanda 2.4.2 files that go to the holding disk first have a .tmp
appended to them. The file is then renamed to what it appears as in
the amdump file. What I currently do is :
while ($true) {
unless (-e $from) {
sleep ($nap);
next;
}
$true = 0;
}
using Time::HiRes qw(sleep); which allows me to set $nap to 0.15
seconds. Hence, I wait for the file renaming to take place. Without
using this sleep, is there a better way of monitoring the holding disk
directory, so as to link any new files to the archive directory. I
heard that in FreeBSD kqueue(2) could be used to monitor a directory,
so that one would be notified of any new files created. Is there
something along these lines that could be done.
My main worry is that small change done to one small file, hence a
very tiny level 1, that gets dumped, written to tape, and removed from
the holding disk, before it ever shows up in the amdump log.
Is my above concern warranted?
Andrew.
On Thu, Jan 18, 2001 at 12:29:48AM -0500, John R. Jackson wrote:
> >Not being C coders, this is implemented in perl, hence I am worried of
> >the race condition where the file is dumped and removed from the
> >holding disk before we get a chance to copy it over.
>
> I'd create another directory in the holding disk area parallel to the
> real holding disk, then hard link to the holding disk image. Use the
> hard link to do your copy. If Amanda removes it's link before you are
> done, no big deal. When both links are gone, the space will be released.
>
> See the "mkdir" and "link" Perl calls.
>
> Watch out for holding disk chunking, if you're using that. It will
> create multiple files and you'll need to deal with all of them (and they
> are not listed in the amdump log file).
>
> >Andrew.
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Only one dumper running
I'm doing a test run with about 8 entries in my disklist and Amanda is only running one dumper. When I run `amstatus' I see: 3 dumpers idle : no-diskspace taper idle network free kps: 1984 holding space : 806496k ( 76.91%) What does `no-diskspace' mean here? I seem to have free network capacity, so why aren't up to 4 dumpers (as I've configured) running? Ben
Re: Weird illustration of peculiar interactions :-}
On Wed, 17 Jan 2001, Joi Ellis wrote: > I have a perl script which will go through my holding disk and spit > out a list of backup sets to select to best pack tapes. > > here's an example: > > [amanda@joi amanda]$ pack -C OffSite > 138530/140906 ( 98%) > /home/amanda/mnt/holdingdisk/OffSite/20010106 > /home/amanda/mnt/holdingdisk/OffSite/20010114 > > 116784/140906 ( 82%) > /home/amanda/mnt/holdingdisk/OffSite/20010107 > /home/amanda/mnt/holdingdisk/OffSite/20010108 > > 114088/140906 ( 80%) > /home/amanda/mnt/holdingdisk/OffSite/20010111 > > 99327/140906 ( 70%) > /home/amanda/mnt/holdingdisk/OffSite/20010112 > > Nothing left to pack! > > I amflush these to tapes to send to offsite storage. > I've already done two tapes from this batch, I have four > left to do. That's a nice idea, but I have more data to back up than fits on the holding disk, so I have to flush some dumps to tape in order to dump all filesystems completely. Martin Martin Apel, Dipl.-Inform.t e c m a t h A G Group Manager Software Development Human Solutions Division phone +49 (0)6301 606-300Sauerwiesen 2, 67661 Kaiserslautern fax +49 (0)6301 606-309Germany [EMAIL PROTECTED] http://www.tecmath.com
Re: Only one dumper running
3 dumpers idle : no-diskspace A bit of simple arithmetic shows me that there is no room in the holding disk. :-) Sorry, Ben
