We need excellent and well-written documentation for linux backup software

[Turritopsis Dohrnii Teo En Ming]

Subject: We need excellent and well-written documentation for linux
backup software

Good day from Singapore,

Our company, which is a Systems Integrator (SI) in Singapore, is
evaluating more than 30 different backup software for linux systems.

We need excellent and well-written documentation for your linux backup
software. Please provide us with links on how to setup your linux
backup software.

We are looking forward to your replies. Thank you very much for your
kind assistance.

Mr. Turritopsis Dohrnii Teo En Ming, 43 years old as of 28 August
2021, is a TARGETED INDIVIDUAL living in Singapore. He is an IT
Consultant with a System Integrator (SI)/computer firm in Singapore.
He is an IT enthusiast.





-BEGIN EMAIL SIGNATURE-

The Gospel for all Targeted Individuals (TIs):

[The New York Times] Microwave Weapons Are Prime Suspect in Ills of
U.S. Embassy Workers

Link:
https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html



Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's
Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts
at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan
(5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020):

[1] https://tdtemcerts.wordpress.com/

[2] https://tdtemcerts.blogspot.sg/

[3] https://www.scribd.com/user/270125049/Teo-En-Ming

-END EMAIL SIGNATURE-

Upload of amanda 3.5.1-8 to Debian with new documentation about auth=ssh.

[Jose M Calhariz]

Hi,

I just upload a new package of amanda 3.5.1-8 to Debian.  The NEWS is:

  * That I have updated the README.Debian with instructions for
auth=ssh and more simple examples.

  * Added to a patch to build amanda with a new libc6, this patch came
from Fedora and maybe interesting to merge unto 3.5.1 github repo.

  * I expect in a new upload to add the systemd units for auth=bsdtcp.

I am not dropping the support for bsdtcp authentication, just making a little
harder by not doing some automatic tasks on installation.

Kind regards
Jose M Calhariz

-- 
--

A fama é boa até consegui-la

--Tostão


signature.asc
Description: PGP signature

Re: Documentation

[Stefan G. Weichinger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am 2017-02-20 um 00:00 schrieb J Martin Rushton:
> Hi,
> 
> For some years now I've been running Amanda on my home network
> (CentOS 6 & 7 machines, + 1 Raspberry Pi).  I was wanting to make a
> couple of changes and realised that my documentation was out of
> date.  I've been using "The Official Amanda Documentation" by
> Weichinger et al dated July 11, 2007.  It deals with version 2.5.0.
> I note that my actual version is 3.3.3-17.el7.  I've spent a
> fruitless couple of hours chasing around the website to try and
> find the full doc set.  Is it only available online or is there a
> downloadable PDF?

good question ;-)

Speaks for amanda if you didn't need to look up docs for ~10 years!

;-)

- -

Back then when I did the conversion of all the docs and manpages to
docbook-xml (I would have to look up the year) it was the intention
that one would be able to generate various output formats from the
amanda-docs inside the tarball:

pdf, html, manpages, ascii text ... everything from the same
source-files (in xml)

Your pdf is one of these generated files from back then.

- -

The xml-manpages went into the releases, other xml-files not.
Might be reasonable in some cases as there has been no real update
process in the last years for some parts of the "amanda-docs" from my
old project (the manpages in the main project-repo have been
maintained by JLM and others, sure).

Although I still am allowed to use that shiny @amanda.org email
address, I am not involved into current documentation anymore due to
various reasons.

One could ask now "who is then?"

As far as I know, the wiki at

https://wiki.zmanda.com/index.php/Main_Page

is the main spot to consult for amanda related issues.

Please correct me if necessary, but I think it's not as up to date as
it could be, especially since amanda-3.4.x releases came out with some
rather substantial changes/enhancements (which I am learning by trial
and error, not by reading docs or examples -> there should be more).

Regarding your original question: I don't know of any current version
of that pdf somewhere.

One of my intentions back then was to provide a base to build on ...
to get amanda-users into contributing and sharing knowhow, tricks and
tips in a way I think modern open-source projects should be run like.

Seems it needs another effort.

Stefan

Documentation

[J Martin Rushton]

Hi,

For some years now I've been running Amanda on my home network (CentOS 6
& 7 machines, + 1 Raspberry Pi).  I was wanting to make a couple of
changes and realised that my documentation was out of date.  I've been
using "The Official Amanda Documentation" by Weichinger et al dated July
11, 2007.  It deals with version 2.5.0.  I note that my actual version
is 3.3.3-17.el7.  I've spent a fruitless couple of hours chasing around
the website to try and find the full doc set.  Is it only available
online or is there a downloadable PDF?

Thanks,
Martin



signature.asc
Description: OpenPGP digital signature

Re: poor documentation

[Stefan G. Weichinger]

Joshua Baker-LePain wrote:

On Thu, 15 Sep 2005 at 2:20pm, Clive Galway wrote



Is there any documentation other than the official manual ?
The one I have (dated june 26 2005, so I presume it is recent) is
woefully poor and has in some cases made the install harder, not
easier.



Err, how many OSS projects do *you* know that have 350+ page manuals?  
Now, what are the sizes of the development teams for those projects?  For 
a project the size of amanda, that manual is nothing short of a wonder, 
and I applaud those who took the time to put it together.


(Used the wrong sender again, so my reply was swallowed by majordomo 
silently ...)


Thanks, Joshua, for defending the AMANDA-docs. Many things are already 
done, many are still to be done 


--
Stefan G. Weichinger
AMANDA core team member
mailto://[EMAIL PROTECTED]
--
oops! linux consulting & implementation
http://www.oops.co.at
--

Re: poor documentation

[Graeme Humphries]

[EMAIL PROTECTED] wrote:


I must agree that the current documentation does little to minimize
pain.  I started to get into Amanda a year or two ago, and eventually
dropped the ball after reading 60% of the documentation before I even
began to touch the software.  The amount of work required before being
able to see something work makes it risky in terms of time.

I just thought I'd interject here, since I've had a relatively painless 
time implementing Amanda. Due in large part to the help of this list, I 
had a working setup in a week, and a debugged setup in two - three. That 
doesn't seem like such a huge time investment for something as critical 
as backups. ;)


Graeme

--
Graeme Humphries ([EMAIL PROTECTED])
(306) 955-7075 ext. 485

My views are not the views of my employers.

Re: poor documentation

[Jon LaBadie]

On Fri, Sep 16, 2005 at 10:58:01AM +0100, Clive Galway wrote:
> 
> I would like to help out on the docs, but am currently very busy
> writing my own open source project and just don't have much time.
> Once I have set up our amanda system (which is a basic one linux server
> setup with a DDS4 tape) I will have to document it.
> 
> Seeing as I work for a hospital and not a for-profit company, I see no
> reason why I could not make that document public. That would seem to
> benefit others (I see people here agreeing that some form of quick-start
> would be a good idea) and the hospital (If we made a mistake, it is more
> likely to be corrected by others and we can feed that correction back
> into our system)

You know your employer better than I, but most
hospitals I'm familiar with are 'for-profit' corporations.
Best check with your legal-beagles before releasing it.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: poor documentation

[Rick Parola]

More power to you. I don't consider myself a network admin (other than for my 
own networks) But seriously, if you want to call yourself a network admin, it 
would help to know the basics... In linux, NIS _IS_ part of the basics, it is 
not "flavor" dependent, like samba, LDAP, and and NFS.

Tells me you wasted your money on that certification. Any linux book will at 
least mention and cover some of those.

While I do agree with you that generally speaking linux documentation should 
be better, I think a rant about it especially on the Amanda list (They do 
better than many others) was uncalled for. Something to keep in mind is that 
all this is created mostly by individual's efforts, people who have a need 
for an application, geek enough to start it open-source to get the help of 
others In most cases all they're concerned with is what they do best: 
programming, code, features, make it better. Docs are low on priority in 
their minds. that's where folks that don't necessarily have the tech skills 
to help programming can help by pushing the documentation... That rarely 
happens though does it?

Something else I learned about the way of open source (that is actually a 
great thing once you understand it) is that an application is almost never a 
stand alone. An example: in windows you can burn CD's with different apps: 
Windows comes with it's own crappy basic CD burning capabilities, you got 
Nero, Easy Cd Creator and others Each of those apps comes with it's own 
library to interface with the actual burner, no code is common between the 
applications. They are commercially developed applications, "No you're not 
using my code to make your own cd burning software...". I'm sure you at some 
point went through hell trying to uninstall one to install the other, or 
maybe discovered how badly these programs conflict if you try to have 
different ones installed. of course, speaking of documentation, each of them 
needs to come with their own set.

In the open source is a little different, the tendency is to not reinvent the 
weel: K3b, Xcdroast, the webmin cd burning module, gnomebaker, cdrtoaster the 
list could go on, ALL use the same libraries and a number of programs to 
burn, normalize, rip etc. there is no point rewriting something that's 
already there unless it's not good enough and it's developers don't agree it 
should be improved. The same goes for the docs. They're already written for 
certain things people aren't going to rewrite it.

To sum it up, things are "different" for good reasons in my opinion and while 
some documentation is poor, the biggest part of it is understanding how 
things work and getting used to the way. Amanda merely mentions NIS and tells 
you amanda specific things about NIS, Really as a network administrator you 
should know at least if you are using NIS, if you are you probably go it 
down, amanda docs are not the place to tell you all about it.

Things are explained sometimes to depts that go beyond your needs... try 
looking at the Samba unleashed sams book!! Great book by the way, 1100 + 
pages! Do we think it needs to be read and understood cover to cover in order 
to set up simple file sharing with a windows computer?

In most cases, what you do is take a moment to write a few bullet points, the 
scope of your project: what are you trying to do? what does it involve? over 
the network or not? and go look for information pertaining to just what you 
need. Then use the documentation as you would use a 1100 pages book: get what 
you need out of it. If it sais "If you're using the magic orbital widget..." 
and you never heard of that, chances are you're not using it and you can 
forget that section exists (I'd be curious enough to google it and see what 
the magical thing can do for me).

100 + men hours If you value those man hours any, you realize that it 
would have costed a lot less to hire a Linux consultant... Perhaps the very 
same people that are developing amanda... They'd get it done, secured and 
tweaked in just a few "You-wouldn't-care-how-expensive" hours.

... That is unless you want to learn things and that's the value of the 100+ 
hours in which case you should have a different attitude towards it all.

I hope this helps you and others in some way. 

Rick


On Friday 16 September 2005 06:01, you wrote:
> No, I did not know what NIS was for sure. Yes, a quick google confirmed
> my suspision that it was Network Info Serv, but with so many TLAs around
> these day, you can't be sure. Expand the acronym, maybe also say that if
> you dont know you most probably arent or whatever.
> When I said I was a LPI certified, I wasn't trying to blow my own
> trumpet, I was merely trying to indicate that I am not an utter newb. I
> am by no means an expert, but I kn

Re: poor documentation

[Joshua Baker-LePain]

On Thu, 15 Sep 2005 at 8:45pm, Gavin Henry wrote

> 
> > Is there any documentation other than the official manual ?
> > The one I have (dated june 26 2005, so I presume it is recent) is
> > woefully poor and has in some cases made the install harder, not
> > easier.
> 
> You can always offer to help?
> 
> Here is something I put together:
> 
> http://fedoranews.org/ghenry/amanda/

That looks good.  Also, download an older version of amanda, and have a 
look at docs/INSTALL.  That's all I needed to get going, back in the day.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: poor documentation

[Clive Galway]

Thanks for the link, I already found
http://www.harkness.co.uk/services/backup.html which appears to be
basically the same thing.
It was very helpful.

I would like to help out on the docs, but am currently very busy
writing my own open source project and just don't have much time.
Once I have set up our amanda system (which is a basic one linux server
setup with a DDS4 tape) I will have to document it.

Seeing as I work for a hospital and not a for-profit company, I see no
reason why I could not make that document public. That would seem to
benefit others (I see people here agreeing that some form of quick-start
would be a good idea) and the hospital (If we made a mistake, it is more
likely to be corrected by others and we can feed that correction back
into our system)

Maybe a smart idea would be to have the docs on a wiki so we could
suggest changes easier, certainly if there is going to be a
collaborative effort to get some kind of quick start doc going, that
would be best done on a wiki.



>>> "Gavin Henry" <[EMAIL PROTECTED]> 09/15/05 8:45 pm >>>

> Is there any documentation other than the official manual ?
> The one I have (dated june 26 2005, so I presume it is recent) is
> woefully poor and has in some cases made the install harder, not
> easier.

You can always offer to help?

Here is something I put together:

http://fedoranews.org/ghenry/amanda/ 



Paid support available:

http://www.amanda.org/support/commercial.php 

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED] 

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/

___
Disclaimer: Great Ormond Street Hospital for Children NHS Trust

SECURITY WARNING RE: PATIENT OR OTHER CONFIDENTIAL DATA. Please note
that Internet E-mail is simply not a secure communication medium.
We strongly advise that you understand & observe this lack of security
when e-mailing us.

FREEDOM OF INFORMATION ACT 2000: The information contained in this e-mail
may be subject to public disclosure under this Act.  Unless the information
is legally exempt from disclosure, the confidentiality of this e-mail and
your reply cannot be guaranteed.

This email and any files transmitted with it are intended solely for
the use of the individual to whom they are addressed.  If you have
received this email in error please notify your email administrator.

Any views or opinions are solely those of the author of this email
and do not represent those of Great Ormond Street Hospital for
Children NHS Trust unless specifically stated.

VIRUSES: This email message has been checked for the presence of
computer viruses by Sophos antivirus software.  However, this does
not guarantee that this email is free of viruses, and the recipient
should perform their own check. 

Re: poor documentation

[mindfuq]

* Clive Galway <[EMAIL PROTECTED]> [2005-09-15 22:09]:
> 
> Why is it that all linux documentation seems to be like this ? I
> know catering to the lowest common denominator sucks, but at least
> catering for the user with medium experience would be nice.
> 
> 100+ man-hours and counting to set up AMANDA for just backing up one
> server... And I have a bloody LPI cert in linux so I am not a
> drooling newbie... This is ridiculous.

I must agree that the current documentation does little to minimize
pain.  I started to get into Amanda a year or two ago, and eventually
dropped the ball after reading 60% of the documentation before I even
began to touch the software.  The amount of work required before being
able to see something work makes it risky in terms of time.  Although
the other part of the reason for dropping Amanda was due to the
difficulty of using it for an unsupported purpose -> to backup to an
array of optical drives.

Now with Blu-ray coming, I'm planning to make another go at it.  I've
noticed that the docs have not been simplified.

Comprehensive guides are great, but I think a quick-start doc with
baby steps would be *very* useful.  I just want that immediate
satisfaction of seeing Amanda in action, even if it's just one small
directory being dumped to a small image.  I don't even want to bring
cron into the picture until I see it do something useful.

The scalability of Amanda is magnificent, however, I would much prefer
to start small and scale up.  It seems the documentation out there
expects us to start off with a gimungus 1000 user installation.  I
would think the typical user would rather start drinking from the
faucet before turning on the information firehose.

At first glance, I have a feeling Gavin Henry's tutorial may be right
on the money for filling this need.  I'll soon take a closer look at
it.  In the meantime, I certainly welcome any suggestions for other
lightweight documention that will get new users off the ground
quickly.

Re: poor documentation

[Gene Heskett]

On Thursday 15 September 2005 09:49, Joshua Baker-LePain wrote:
[...]
>Myself, given your, err, complaints, I think that perhaps a
>quick-start chapter may be in order.  Now where did I put those
>circular tuits?

'Circular tuits'

Chuckle, Thats classic Joshua.  Gotta love it. :-)

Yup, I'm back from a month of trying to keep a junkyard tv on the
air.  I'll have to go back of course.  Too much left to do. And with
well over 10,000 emails to go over, I'm plumb out of those circular
tuits.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: poor documentation

[Gavin Henry]

> Is there any documentation other than the official manual ?
> The one I have (dated june 26 2005, so I presume it is recent) is
> woefully poor and has in some cases made the install harder, not
> easier.

You can always offer to help?

Here is something I put together:

http://fedoranews.org/ghenry/amanda/



Paid support available:

http://www.amanda.org/support/commercial.php

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED]

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/

Re: poor documentation

[Joshua Baker-LePain]

On Thu, 15 Sep 2005 at 2:20pm, Clive Galway wrote

> Is there any documentation other than the official manual ?
> The one I have (dated june 26 2005, so I presume it is recent) is
> woefully poor and has in some cases made the install harder, not
> easier.

Err, how many OSS projects do *you* know that have 350+ page manuals?  
Now, what are the sizes of the development teams for those projects?  For 
a project the size of amanda, that manual is nothing short of a wonder, 
and I applaud those who took the time to put it together.

> Some examples:
> Chapter 2.2.1 - last line of page 33, start of page 34:
> it talks about the $prefix dir and the various command-line parameters
> that use the $prefix variable. If users have to change some things,
> then, like me, they will be lulled into thinking they should use
> something like --llibdir=/etc/amanda/lib
> This would cause a problem though because then some things would be
> installed under the prefix dir and some would not.

Isn't that the point of mucking about with configure parameters -- putting 
some things in one place and some things in others?

> For god's sake, just list the --prefix= command.
> If users are advanced enough to want dirs scattered all over the place,
> let them dig for the information in the ./configure --help pages.

So, here you're complaining that the documentation is *too* comprehensive?  

> Chapter 2.3.1 - top of page 36:
> "If you are running NIS (aka YP) ..."
> Yeah. Right. Cause we all know what that is and whether we are running
> it.

NIS isn't one of those services that automagically run in the background 
without your knowledge.  It won't be running unless you set it up.  And 2 
min with google would let you know what it is.

> Why is it that all linux documentation seems to be like this ? I know
> catering to the lowest common denominator sucks, but at least catering
> for the user with medium experience would be nice.

To my eye, the manual looks to cater to folks of all experience levels.  

> 100+ man-hours and counting to set up AMANDA for just backing up one
> server... And I have a bloody LPI cert in linux so I am not a drooling
> newbie... This is ridiculous.

Then offer some *concrete suggestions* as to what could make it better.  
Just coming in and ranting at a group of volunteers rarely is helpful.

Myself, given your, err, complaints, I think that perhaps a quick-start 
chapter may be in order.  Now where did I put those circular tuits?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

poor documentation

[Clive Galway]

Is there any documentation other than the official manual ?
The one I have (dated june 26 2005, so I presume it is recent) is
woefully poor and has in some cases made the install harder, not
easier.

Some examples:
Chapter 2.2.1 - last line of page 33, start of page 34:
it talks about the $prefix dir and the various command-line parameters
that use the $prefix variable. If users have to change some things,
then, like me, they will be lulled into thinking they should use
something like --llibdir=/etc/amanda/lib
This would cause a problem though because then some things would be
installed under the prefix dir and some would not.
For god's sake, just list the --prefix= command.
If users are advanced enough to want dirs scattered all over the place,
let them dig for the information in the ./configure --help pages.


Chapter 2.3.1 - top of page 36:
"If you are running NIS (aka YP) ..."
Yeah. Right. Cause we all know what that is and whether we are running
it.

Why is it that all linux documentation seems to be like this ? I know
catering to the lowest common denominator sucks, but at least catering
for the user with medium experience would be nice.

100+ man-hours and counting to set up AMANDA for just backing up one
server... And I have a bloody LPI cert in linux so I am not a drooling
newbie... This is ridiculous.

___
Disclaimer: Great Ormond Street Hospital for Children NHS Trust

SECURITY WARNING RE: PATIENT OR OTHER CONFIDENTIAL DATA. Please note
that Internet E-mail is simply not a secure communication medium.
We strongly advise that you understand & observe this lack of security
when e-mailing us.

FREEDOM OF INFORMATION ACT 2000: The information contained in this e-mail
may be subject to public disclosure under this Act.  Unless the information
is legally exempt from disclosure, the confidentiality of this e-mail and
your reply cannot be guaranteed.

This email and any files transmitted with it are intended solely for
the use of the individual to whom they are addressed.  If you have
received this email in error please notify your email administrator.

Any views or opinions are solely those of the author of this email
and do not represent those of Great Ormond Street Hospital for
Children NHS Trust unless specifically stated.

VIRUSES: This email message has been checked for the presence of
computer viruses by Sophos antivirus software.  However, this does
not guarantee that this email is free of viruses, and the recipient
should perform their own check. 

Re: vtapes documentation

[Gavin Henry]

Doh!!!

Been one of those days already, and it's only 11:30am here ;-)

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED]

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/


> Gavin Henry wrote:
>> Hi Guys,
>>
>> Been a while, but that's due to Amanda being so rock solid!!!
>>
>> I am about to try a new setup using vtapes, as a new client won't be
>> getting a tape drive for about 5 weeks, but would like Amanda setup now.
>> Then when it arrives, we will be moving on to tapes.
>>
>> However, I can't seem to find anything in the main docs about vtapes?
>>
>> If there is and I have missed it, then sorry, if there isn't, then I
>> could
>> work on whatever we have and then speak to Stefan to work with him to
>> get
>> them added to the core docs?
>
> What about
>
> http://www.amanda.org/docs/howto-filedriver.html
>
> ?
>
> This is where the term "vtape" originates ...
>
> --
> Stefan G. Weichinger
> AMANDA core team member
> mailto://[EMAIL PROTECTED]
> --
> oops! linux consulting & implementation
> http://www.oops.co.at
> --
>

Re: vtapes documentation

[Stefan G. Weichinger]

Gavin Henry wrote:

Hi Guys,

Been a while, but that's due to Amanda being so rock solid!!!

I am about to try a new setup using vtapes, as a new client won't be
getting a tape drive for about 5 weeks, but would like Amanda setup now.
Then when it arrives, we will be moving on to tapes.

However, I can't seem to find anything in the main docs about vtapes?

If there is and I have missed it, then sorry, if there isn't, then I could
work on whatever we have and then speak to Stefan to work with him to get
them added to the core docs?


What about

http://www.amanda.org/docs/howto-filedriver.html

?

This is where the term "vtape" originates ...

--
Stefan G. Weichinger
AMANDA core team member
mailto://[EMAIL PROTECTED]
--
oops! linux consulting & implementation
http://www.oops.co.at
--

vtapes documentation

[Gavin Henry]

Hi Guys,

Been a while, but that's due to Amanda being so rock solid!!!

I am about to try a new setup using vtapes, as a new client won't be
getting a tape drive for about 5 weeks, but would like Amanda setup now.
Then when it arrives, we will be moving on to tapes.

However, I can't seem to find anything in the main docs about vtapes?

If there is and I have missed it, then sorry, if there isn't, then I could
work on whatever we have and then speak to Stefan to work with him to get
them added to the core docs?

Thanks,

Gavin.

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED]

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/

RE: Questions re: the chg-scsi documentation

[Scott R. Burns]

I had the core dump problem with chg-scsi as well. I am on NetBSD/i386
V2.0.2. I did a couple of things, of the two I am not sure if both were
required but:

I am running a HP SureStore DAT24x6 changer.

The first was:

I set my changerident to: "C1553A". (The closest value defined in chg-scsi
to my changer/drive).
I see "FastStor DLT" is defined. Have you tried that in your chg-scsi.conf ?

I looked through changer-src\sense.c and I see the following special entries
for changers.

ADIC DAT AutoChanger
L500 ATL
HP 1553A
HP 1537A
Tandberg TDS 1420
DLT8000
DLT7000
AIT VLS DLT Library
AIT VLS SDX Library
Exabyte 85058
Exabyte 10e Library
Exabyte 210 Library
Exabyte 230D Library
Spectra Treefrog Library

It would appear that the sense.c structure is defining inquiry results and
defining how to interpret them.
Your changer may require some entries in there.


Here is the chg-scsi.conf that I use that works for me on my HP changer. My
changer device on NetBSD
is "/dev/ch0". "dev /dev/nrst0" is my no-rewind tape drive device,
"scsitapedev /dev/rst0" I added
so that my "tapestatus /usr/pkg/etc/amanda/st0-status" file gets update with
error status values
after a run. My changer did not seem to require the "eject" value to be set
so I left it at 0.

"scsitapedev" may also be key as I think it changes how it talks to the
drive/changer.

With "debug 9:0" I get lots of detail in chg-scsi* files I find in
/tmp/amanda.

number_configs  1
eject   0   # Tapedrives need an eject command
sleep   5   # Seconds to wait until the tape gets ready
cleanmax50  # How many times could a cleaning tape get used

changeridentC1553A
changerdev  /dev/ch0
debug   9:0
#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/nrst0  # the device that is used for the tapedrive 0
scsitapedev /dev/rst0
startuse0   # The slots associated with the drive 0
enduse  4   #
statfile/usr/pkg/etc/amanda/st0-slot  # The file where the actual slot 
is
stored
cleancart   5   # the slot where the cleaningcartridge for drive 0 is 
located
cleanfile   /usr/pkg/etc/amanda/st0-clean # The file where the cleanings are
recorded
usagecount  /usr/pkg/etc/amanda/totaltime
tapestatus  /usr/pkg/etc/amanda/st0-status

# This is the end


There is a command documented as: "chg-scsi -genconf". What does that do in
your case ? I have never tried it
on my machine.


Can you make some of those available after performing some of the commands
that work and ones that don't ?

Under chgscsi.txt in the docs directory of 2.4.5 there are lots of notes on
chg-scsi.

Scott...




Scott R. Burns
NETCON Technologies Inc.
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Marcus
Sent: Saturday, August 13, 2005 2:34 PM
To: amanda-users@amanda.org
Subject: Questions re: the chg-scsi documentation


I was going through those pages a bit this morning and
had a few questions..;

Firstly, at the Configuration Notes it says I should
be able to get the changer value with modprobe sg.
That command returns nothing; which doesn't seem
right? But if I do a modprobe sg -l then I get:
/lib/modules/2.6.8-24-default/kernel/drivers/scsi/sg.ko
So have I got the right module loaded for sg devices?

Secondly, what does -status do? what is the param you
have to pass it?

Thirdly, around the changerident section, it lists
Faststor DLT which is what I run. It's listed as an
"other value". Does that mean chg-scsi supports my
drive w/o the changerident argument? Whenever I try to
add it, chg-scsi just gets cross at me.

Thanks for any help. I'm getting so close to this tape
drive working that I'm almost sick; chg-scsi will now
pick a tape and load it! :} But it still segfaults on
-scan, and it will "eject" the tape but doesn't know
how to unload it (I have to follow up with mtx -f
/dev/sg1 unload)


Good weekend to everyone..!


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Questions re: the chg-scsi documentation

[Marcus]

I was going through those pages a bit this morning and
had a few questions..;

Firstly, at the Configuration Notes it says I should
be able to get the changer value with modprobe sg.
That command returns nothing; which doesn't seem
right? But if I do a modprobe sg -l then I get:
/lib/modules/2.6.8-24-default/kernel/drivers/scsi/sg.ko
So have I got the right module loaded for sg devices?

Secondly, what does -status do? what is the param you
have to pass it?

Thirdly, around the changerident section, it lists
Faststor DLT which is what I run. It's listed as an
"other value". Does that mean chg-scsi supports my
drive w/o the changerident argument? Whenever I try to
add it, chg-scsi just gets cross at me.

Thanks for any help. I'm getting so close to this tape
drive working that I'm almost sick; chg-scsi will now
pick a tape and load it! :} But it still segfaults on
-scan, and it will "eject" the tape but doesn't know
how to unload it (I have to follow up with mtx -f
/dev/sg1 unload)


Good weekend to everyone..!


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Error in the documentation (Installation) ?

[Stefan G. Weichinger]

Hi, Guy,

on Freitag, 06. Mai 2005 at 14:20 you wrote to amanda-users:

GD> 2005/5/6, Stefan G. Weichinger <[EMAIL PROTECTED]>:

>> Please point out which part of the docs you refer to so I can look
>> that up and correct things.

>>> GD> The doc mentions /usr/local/bin/amcheck and /usr/local/bin/amdup in
>>> GD> crontab. This CANNOT work as the binaries ar in /usr/local/bin

GD> Section 2.3.1 (crontab entries, replace bin by sbin)

Edited that in the xml-docs.

>> GD> Also, the install doc mentions to create/edit
>> GD> /usr/local/etc/amanda/confname file.

GD> section 2.3.1 also.

GD> It should be mentionned at the start of the installation, that the
GD> $prefix/etc/amanda directory is not created by the make file (or the
GD> make file should create it)

The file already says "Create the config directory (eg.
/usr/local/etc/amanda/confname) [...]".

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Error in the documentation (Installation) ?

[Guy Dallaire]

2005/5/6, Stefan G. Weichinger <[EMAIL PROTECTED]>:

> Please point out which part of the docs you refer to so I can look
> that up and correct things.

>> GD> The doc mentions /usr/local/bin/amcheck and /usr/local/bin/amdup in
>> GD> crontab. This CANNOT work as the binaries ar in /usr/local/bin

Section 2.3.1 (crontab entries, replace bin by sbin)

> GD> Also, the install doc mentions to create/edit
> GD> /usr/local/etc/amanda/confname file.

section 2.3.1 also.

It should be mentionned at the start of the installation, that the
$prefix/etc/amanda directory is not created by the make file (or the
make file should create it)

Thanks

Re: Error in the documentation (Installation) ?

[Stefan G. Weichinger]

Hi, Guy Dallaire,

on Donnerstag, 05. Mai 2005 at 22:19 you wrote to amanda-users:

GD> According to the amanda doc (www.amanda.org) amanda is supposed to
GD> install binaries in /usr/local/bin.

GD> I have NO amanda binaries there. I used the standard configuration
GD> build. Most binaries are in /usr/local/sbin or /usr/local/libexec

GD> Is this NORMAL ?

GD> The doc mentions /usr/local/bin/amcheck and /usr/local/bin/amdup in
GD> crontab. This CANNOT work as the binaries ar in /usr/local/bin

GD> Also, the install doc mentions to edit
GD> /usr/local/etc/amanda/confname file. 

GD> The /usr/local/amanda directory was NOT created upon installation
GD> (with root user doing the make install) is this NORMAL ?


Please point out which part of the docs you refer to so I can look
that up and correct things.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Error in the documentation (Installation) ?

[Jon LaBadie]

On Thu, May 05, 2005 at 04:19:14PM -0400, Guy Dallaire wrote:
> According to the amanda doc (www.amanda.org) amanda is supposed to
> install binaries in /usr/local/bin.
> 
> I have NO amanda binaries there. I used the standard configuration
> build. Most binaries are in /usr/local/sbin or /usr/local/libexec
> 
> Is this NORMAL ?
> 
> The doc mentions /usr/local/bin/amcheck and /usr/local/bin/amdup in
> crontab. This CANNOT work as the binaries ar in /usr/local/bin
> 
> Also, the install doc mentions to edit /usr/local/etc/amanda/confname file. 
> 
> The /usr/local/amanda directory was NOT created upon installation
> (with root user doing the make install) is this NORMAL ?
> 

All seems normal.  The docs should probably be modified to read
under "/usr/local".  And the crontab examples adjusted.
-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Error in the documentation (Installation) ?

[Guy Dallaire]

According to the amanda doc (www.amanda.org) amanda is supposed to
install binaries in /usr/local/bin.

I have NO amanda binaries there. I used the standard configuration
build. Most binaries are in /usr/local/sbin or /usr/local/libexec

Is this NORMAL ?

The doc mentions /usr/local/bin/amcheck and /usr/local/bin/amdup in
crontab. This CANNOT work as the binaries ar in /usr/local/bin

Also, the install doc mentions to edit /usr/local/etc/amanda/confname file. 

The /usr/local/amanda directory was NOT created upon installation
(with root user doing the make install) is this NORMAL ?

Thanks

Re: Dump ordering optimisation documentation

[Stefan G. Weichinger]

Hi, Jon,

on Dienstag, 31. August 2004 at 23:30 you wrote to amanda-users:

JL> On Tue, Aug 31, 2004 at 02:14:40PM -0700, Mike Fedyk wrote:
>> Is there any chance we can get this in the documentation?
>> 
>> http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2
>> 

JL> I don't know of any email messages included with the amanda docs.

This does not mean that there won't be messages included in the
future. But the docs should definitely more than just a bunch of
pasted emails.

JL> Perhaps you could use that as the basis for a HOW-TO using the
JL> taperalgo and dumporder params.

Yes.

I would suggest a new and shiny amanda.conf-HOWTO.
This could be a part of it.

Just take the current example/amanda.conf and make a HOWTO of it.
I will be glad to help it getting done.

This could also go into some kind of Tuning-HOWTO ...
As always, suggestions are welcome 
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Dump ordering optimisation documentation

[Mike Fedyk]

Jon LaBadie wrote:
On Tue, Aug 31, 2004 at 02:14:40PM -0700, Mike Fedyk wrote:
 

Is there any chance we can get this in the documentation?
http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2
   

I don't know of any email messages included with the amanda docs.
Perhaps you could use that as the basis for a HOW-TO using the
taperalgo and dumporder params.
Oh sorry, it looks like I wasn't specific enough.  I meant to ask if 
something like this could be added to the current documentation that has 
been posted on the list lately, and maybe a parring down for the man 
page.  Not including this email itself within the sources.

Mike

Re: Dump ordering optimisation documentation

[Jon LaBadie]

On Tue, Aug 31, 2004 at 02:14:40PM -0700, Mike Fedyk wrote:
> Is there any chance we can get this in the documentation?
> 
> http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2
> 

I don't know of any email messages included with the amanda docs.

Perhaps you could use that as the basis for a HOW-TO using the
taperalgo and dumporder params.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Dump ordering optimisation documentation

[Mike Fedyk]

Is there any chance we can get this in the documentation?
http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2

Re: AMANDA Documentation at www.oops.co.at

[Stefan G. Weichinger]

Hi, Kevin,

on Dienstag, 24. August 2004 at 22:56 you wrote to amanda-users:

KZ> Stefan, thank for taking the time to do this. In the spirit
KZ> of bug-finding, I am unable to print page 93 of today's version of
KZ> the postscript file.

Errm, you mean, PDF instead of PostScript, don't you?
I haven't put the ps-file online yet ...

KZ> Don't know if this is related to the error
KZ> below. I'm using Adobe Acrobat 6.0 inside of IE 6.0 on a Windows
KZ> XP platform (no flames; required on the organization's LAN).

Thanks for the report, until now I have never tried to print anything
out of the AMANDA-pdf.

I assume that this is due to the fact that currently the pagenumbers
in the pdf are in roman style, not arabic. This is an issue I am
trying to track down for quite a while.

If I try to print page 93 by specifying the (arabic) pagenumber in the
MS Windows print-dialog, my Adobe Reader crashes --- bad thing.

If I try to print the same page by placing the cursor in that page and
specify "Current Page" (or whatever the english Windows says, I only
have the german release at hand) in the dialog, it prints fine.

One more reason to get those pagenumbers correct ...

Thanks,
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: AMANDA Documentation at www.oops.co.at

[KEVIN ZEMBOWER]

Stefan, thank for taking the time to do this. In the spirit of bug-finding, I am 
unable to print page 93 of today's version of the postscript file. Don't know if this 
is related to the error below. I'm using Adobe Acrobat 6.0 inside of IE 6.0 on a 
Windows XP platform (no flames; required on the organization's LAN).

Thanks, again.

-Kevin

>>> [EMAIL PROTECTED] 08/24/04 10:30AM >>>
Hi, Paul,

on Dienstag, 24. August 2004 at 15:34 you wrote to amanda-users:

papc> In a message dated: Tue, 24 Aug 2004 00:15:31 +0200
papc> "Stefan G. Weichinger" said:

>>Just get the file at:
>>
>>http://www.oops.co.at/AMANDA-docs/index.html 

papc> Hmmm, ghostscript seems to have trouble converting this to postscript:

papc> $ pdf2ps amanda.pdf amanda.ps
papc> Unknown operator: '.
papc> Error: /syntaxerror in --token--
papc> Operand stack:
papc>365361   2546   0   4   --dict:9/9(ro)(G)--   --nostringval--

Errm, you're right, I have no clue why this happens, have to dig that
up.

Fortunately I am able to generate ps straight with my buildtree. You
said, you want a pdf, so I gave you pdf ;-)

So you would like me to put the ps-file online, too, am I right ?

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED] 

Re: AMANDA Documentation at www.oops.co.at

[Stefan G. Weichinger]

Hi, Paul,

on Dienstag, 24. August 2004 at 15:34 you wrote to amanda-users:

papc> In a message dated: Tue, 24 Aug 2004 00:15:31 +0200
papc> "Stefan G. Weichinger" said:

>>Just get the file at:
>>
>>http://www.oops.co.at/AMANDA-docs/index.html

papc> Hmmm, ghostscript seems to have trouble converting this to postscript:

papc> $ pdf2ps amanda.pdf amanda.ps
papc> Unknown operator: '.
papc> Error: /syntaxerror in --token--
papc> Operand stack:
papc>365361   2546   0   4   --dict:9/9(ro)(G)--   --nostringval--

Errm, you're right, I have no clue why this happens, have to dig that
up.

Fortunately I am able to generate ps straight with my buildtree. You
said, you want a pdf, so I gave you pdf ;-)

So you would like me to put the ps-file online, too, am I right ?

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: AMANDA Documentation at www.oops.co.at

[pll+amanda]

In a message dated: Tue, 24 Aug 2004 00:15:31 +0200
"Stefan G. Weichinger" said:

>Just get the file at:
>
>http://www.oops.co.at/AMANDA-docs/index.html

Hmmm, ghostscript seems to have trouble converting this to postscript:

$ pdf2ps amanda.pdf amanda.ps
    Unknown operator: '.
Error: /syntaxerror in --token--
Operand stack:
   365361   2546   0   4   --dict:9/9(ro)(G)--   --nostringval--
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2  
 %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   
%stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   
--nostringval--   94   1   206   --nostringval--   %for_pos_int_continue   
--nostringval--   --nostringval--   --nostringval--   %array_continue   
--nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   
--nostringval--   %loop_continue   --nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1049/1123(ro)(G)--   --dict:0/20(G)--   --dict:74/200(L)--   
--dict:74/200(L)--   --dict:100/127(ro)(G)--   --dict:230/230(ro)(G)--   
--dict:20/24(L)--   --dict:4/6(L)--   --dict:22/31(L)--
Current allocation mode is local
GPL Ghostscript 8.01: Unrecoverable error, exit code 1


-- 
Seeya,
Paul

GPG Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

 If you're not having fun, you're not doing it right!

Re: AMANDA Documentation at www.oops.co.at

[pll+amanda]

In a message dated: Tue, 24 Aug 2004 00:15:31 +0200
"Stefan G. Weichinger" said:

>I would prefer to just put the current pdf online, as I want to put
>the xml-stuff online in early september. I want to avoid the
>side-effects of distributing stuff per email ...
>
>I am very busy with other things these days, but I hope to get back to
>the AMANDA-docs in september.
>
>Just get the file at:
>
>http://www.oops.co.at/AMANDA-docs/index.html

For some reason I didn't see that huge link staring me in the face 
yesterday pointing at the PDF :)  That's all I wanted, I didn't 
realize you had already generated the PDF.  Thanks!

>And note: this is still heavily ALPHA-stuff.
>Notes/corrections/additions welcome.

That's what we're all here for, to make it as ready as amanda is :)
(Thanks for getting this started)

>btw, the AMANDA-manpages will be added soon ...

And I notice they already have been.  Excellent!  I'll be reading 
this on my commute tomorrow morning (It's tough to read on a bicycle, 
which is how I commuted today :)
-- 
Seeya,
Paul

GPG Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

 If you're not having fun, you're not doing it right!

Re: AMANDA Documentation at www.oops.co.at

[Gavin Henry]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday 23 Aug 2004 23:58, Stefan G. Weichinger wrote:
> Hi, Gavin Henry,
>
> on Dienstag, 24. August 2004 at 00:26 you wrote to amanda-users:
>
> GH> -BEGIN PGP SIGNED MESSAGE-
> GH> Hash: SHA1
>
> >> btw, the AMANDA-manpages will be added soon ...
>
> GH> Me or you?
>
> GH> It will only take a hour if you provide your CSS or I can use mine?
>
> Didn't understand at first, now I do:
>
> Have a look at the manpages at
>
> http://www.oops.co.at/AMANDA-docs/index.html
>
> As always, corrections are welcome (and necessary).

Excellent.

>
> Thanks,
> Stefan
>
> Stefan G. Weichinger
> mailto:[EMAIL PROTECTED]

- -- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1467 624141
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED]

Open Source. Open Solutions.

http://www.suretecsystems.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBKufDeWseh9tzvqgRAn1+AKCbQlrn4LVXFi0jDjrg/+1Pz3mvDQCfX2lj
JCdk3S0Tw3CFljS6+db9o8s=
=i2cz
-END PGP SIGNATURE-

Re: AMANDA Documentation at www.oops.co.at

[Stefan G. Weichinger]

Hi, Gavin Henry,

on Dienstag, 24. August 2004 at 00:26 you wrote to amanda-users:

GH> -BEGIN PGP SIGNED MESSAGE-
GH> Hash: SHA1

>> btw, the AMANDA-manpages will be added soon ...

GH> Me or you?

GH> It will only take a hour if you provide your CSS or I can use mine?

Didn't understand at first, now I do:

Have a look at the manpages at

http://www.oops.co.at/AMANDA-docs/index.html

As always, corrections are welcome (and necessary).

Thanks,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: AMANDA Documentation at www.oops.co.at

[Gavin Henry]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> btw, the AMANDA-manpages will be added soon ...

Me or you?

It will only take a hour if you provide your CSS or I can use mine?

- -- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1467 624141
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E [EMAIL PROTECTED]

Open Source. Open Solutions.

http://www.suretecsystems.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBKm8neWseh9tzvqgRAsgFAJ0XjKws2yFVwDmtBfIDgHJNFyInJQCfUO/q
HiiLE++s2R/Q2qu+VJOmtjE=
=MpQs
-END PGP SIGNATURE-

Re: AMANDA Documentation at www.oops.co.at

[Stefan G. Weichinger]

Hi, Paul,

on Montag, 23. August 2004 at 15:58 you wrote to amanda-users:

>>>>>> On Wed, 4 Aug 2004, "Stefan" == Stefan G. Weichinger wrote:

papc>   Stefan> about one month has gone now, since I put a pre-release
papc>   Stefan> of "The Official AMANDA Documentation" online at
papc>   Stefan> http://www.oops.co.at/AMANDA-docs/index.html

papc> Very nice!

Thanks a lot ...

papc> I must have been on vacation when you first put this up.
papc> Is there away I can get the raw docbook source (I'd like to print out
papc> a PDF so I can read this during my commute on the train :)

papc> If so, I'll gladly provide assitance with edits/corrections, etc.

I would prefer to just put the current pdf online, as I want to put
the xml-stuff online in early september. I want to avoid the
side-effects of distributing stuff per email ...

I am very busy with other things these days, but I hope to get back to
the AMANDA-docs in september.

Just get the file at:

http://www.oops.co.at/AMANDA-docs/index.html

And note: this is still heavily ALPHA-stuff.

Notes/corrections/additions welcome.

btw, the AMANDA-manpages will be added soon ...

-- 
best regards,
Stefan.

Re: AMANDA Documentation at www.oops.co.at

[pll+amanda]

>>>>> On Wed, 4 Aug 2004, "Stefan" == Stefan G. Weichinger wrote:

  Stefan> about one month has gone now, since I put a pre-release
  Stefan> of "The Official AMANDA Documentation" online at
  Stefan> http://www.oops.co.at/AMANDA-docs/index.html

Very nice!  I must have been on vacation when you first put this up.
Is there away I can get the raw docbook source (I'd like to print out 
a PDF so I can read this during my commute on the train :)

If so, I'll gladly provide assitance with edits/corrections, etc.
-- 
Seeya,
Paul

GPG Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

 If you're not having fun, you're not doing it right!

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Stefan G. Weichinger]

Hi, Luc ,

on Freitag, 06. August 2004 at 03:23 you wrote to amanda-users:

LL> Hello Stefan,

LL> No not the email.   There are a few corrections in the text I resent
LL> you.   You changed the format of the text and I corrected the wording to
LL> ajust to your changes...

LL> Thanks.

LL> Stefan G. Weichinger wrote:

>>Hi, Luc,
>>
>>on Donnerstag, 05. August 2004 at 15:59 you wrote to amanda-users:
>>
>>LL> Hello Stefan,
>>
>>LL> Here's a few corrections (in blue):

The email was the only blue thing in my email-reader.
I will cutnpaste your latest text.
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Luc Lalonde]

Hello Stefan,
No not the email.   There are a few corrections in the text I resent 
you.   You changed the format of the text and I corrected the wording to 
ajust to your changes...

Thanks.
Stefan G. Weichinger wrote:
Hi, Luc,
on Donnerstag, 05. August 2004 at 15:59 you wrote to amanda-users:
LL> Hello Stefan,
LL> Here's a few corrections (in blue):
LL> Cut Here**
LL> Luc Lalonde <[EMAIL PROTECTED]
LL> > 

You mean the email-adress?? The format is pretty strict in my XML-DTD.
Or do I miss the point again?
best regards,
Stefan.
 

--
Luc Lalonde, analyste
-
Département de génie informatique:
École polytechnique de Montréal
(514) 340-4711 x5049
[EMAIL PROTECTED]
-
War is good for business, invest your son!
- 

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Luc Lalonde]

I think that it should go into the SGI-Irix section...
Stefan G. Weichinger wrote:
Hi, Luc Lalonde,
on Donnerstag, 05. August 2004 at 04:09 you wrote to amanda-users:
LL> Hello Stefan,
LL> Thanks for the enormous work that you've done putting together this
LL> document.
Thank you ...
LL> I've to some Irix (6.5.x) notes:
LL> 1)  If you use a jukebox, you must set the ownership of the 
LL> robot-changer device to the Amanda operator:group in "/etc/ioperms".
LL> Here's my configure:

LL> /etc/ioperms: /dev/scsi/sc8d6l0 0600 amanda backup
LL> Otherwise the ownership:group is changed to root:sys after each reboot.
LL> 2)  When you do upgrades, check the file /var/sysgen/master.d/scsi to
LL> see if it has changed.   Otherwise your jukebox could be rendered 
LL> unuseable.   In particular, check if it has been replaced by a new
LL> version and renamed to 'scsi.O'.

LL> If you use the Amanda package provided by freeware.sgi.com, you are not
LL> affected by the first question since at compile time the Amanda operator
LL> is root:sys.
You have already thought about where one would prefer to find that
infos?
I assume this should go into the current chapter 9 "AMANDA Tape
Changer Support" ...
 

--
Luc Lalonde, analyste
-
Département de génie informatique:
École polytechnique de Montréal
(514) 340-4711 x5049
[EMAIL PROTECTED]
-
War is good for business, invest your son!
- 

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Luc Lalonde]

Hello Stefan,
Thanks for the enormous work that you've done putting together this 
document.

I've to some Irix (6.5.x) notes:
1)  If you use a jukebox, you must set the ownership of the 
robot-changer device to the Amanda operator:group in "/etc/ioperms".   
Here's my configure:

/etc/ioperms: /dev/scsi/sc8d6l0 0600 amanda backup
Otherwise the ownership:group is changed to root:sys after each reboot.
2)  When you do upgrades, check the file /var/sysgen/master.d/scsi to 
see if it has changed.   Otherwise your jukebox could be rendered 
unuseable.   In particular, check if it has been replaced by a new 
version and renamed to 'scsi.O'.

If you use the Amanda package provided by freeware.sgi.com, you are not 
affected by the first question since at compile time the Amanda operator 
is root:sys.

Bye.
Stefan G. Weichinger wrote:
Hello, amanda-users,
about one month has gone now, since I put a pre-release of "The
Official AMANDA Documentation" online at
http://www.oops.co.at/AMANDA-docs/index.html
This was just meant as a ground for discussion (for
amanda-core-members), but it seems to hit the needs of several more
people:
The hits at www.oops.co.at have risen since then, and still rise.
No problem with that, just some thoughts:
- The current info is just equivalent to the infos in the (in some
parts outdated and incorrect :-( ) AMANDA-docs.
- The current formatting is far from being complete, there is much
potential for improvement (think XML-tags, indexing, ...)
Given the fact that I am more than busy with other
documentation-related tasks I just want to tell all of you that:
- every kind of correction is welcome.
- every kind of addition is welcome.
Feel free to express your thoughts, I will try the best to transform
your input into contributions to AMANDA.
best regards,
Stefan G. Weichinger
 

--
Luc Lalonde, analyste
-
Département de génie informatique:
École polytechnique de Montréal
(514) 340-4711 x5049
[EMAIL PROTECTED]
-
War is good for business, invest your son!
- 

AMANDA Documentation at www.oops.co.at

[Stefan G. Weichinger]

Hello, amanda-users,

about one month has gone now, since I put a pre-release of "The
Official AMANDA Documentation" online at
http://www.oops.co.at/AMANDA-docs/index.html

This was just meant as a ground for discussion (for
amanda-core-members), but it seems to hit the needs of several more
people:

The hits at www.oops.co.at have risen since then, and still rise.

No problem with that, just some thoughts:

- The current info is just equivalent to the infos in the (in some
parts outdated and incorrect :-( ) AMANDA-docs.

- The current formatting is far from being complete, there is much
potential for improvement (think XML-tags, indexing, ...)

Given the fact that I am more than busy with other
documentation-related tasks I just want to tell all of you that:

- every kind of correction is welcome.
- every kind of addition is welcome.

Feel free to express your thoughts, I will try the best to transform
your input into contributions to AMANDA.

best regards,
Stefan G. Weichinger

Re: Good Documentation anywhere?

[Stefan G. Weichinger]

Hi, Gene Heskett,

on Donnerstag, 03. Juni 2004 at 23:52 you wrote to amanda-users:

GH> There was at one time a site called frankenlinux.something that had a
GH> somewhat expanded set of manpages/docs.  I used them to get started
GH> with years ago.  They might be somewhat dated in that any new stuff
GH> might not be in there, but what they ahve should be 100% compatible.

yes, I knew that site.

Google says they're down. It's mirrored here:

http://people.web.psi.ch/bearpark/mirror/frankenlinux.com/guides/amandaintro

I have NOT read that now ;-)

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Good Documentation anywhere?

[Gene Heskett]

On Thursday 03 June 2004 17:33, Stefan G. Weichinger wrote:
>Hi, Ivan,
>
>on Donnerstag, 03. Juni 2004 at 22:52 you wrote to amanda-users:
>
>IP> Stefan G. Weichinger a e'crit:
>>> There is no such thing as "The Official AMANDA HOWTO And
>>> Reference Guide".
>
>IP> Is anybody working on it?
>
>I don't know of any current project, no.
>But I think about doing it myself.
>Currently I am far too busy to work on that.
>
>A good and current Guide would not hurt, AFAIK.
>
>Suggestions welcome.

There was at one time a site called frankenlinux.something that had a 
somewhat expanded set of manpages/docs.  I used them to get started 
with years ago.  They might be somewhat dated in that any new stuff 
might not be in there, but what they ahve should be 100% compatible.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.23% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: Good Documentation anywhere?

[Stefan G. Weichinger]

Hi, Ivan,

on Donnerstag, 03. Juni 2004 at 22:52 you wrote to amanda-users:

IP> Stefan G. Weichinger a e'crit:

>> There is no such thing as "The Official AMANDA HOWTO And Reference
>> Guide".

IP> Is anybody working on it?

I don't know of any current project, no.
But I think about doing it myself.
Currently I am far too busy to work on that.

A good and current Guide would not hurt, AFAIK.

Suggestions welcome.

-- 
best regards,
Stefan

Re: Good Documentation anywhere?

[Ivan Petrovich]

Stefan G. Weichinger a e'crit:

> There is no such thing as "The Official AMANDA HOWTO And Reference
> Guide".

Is anybody working on it?

Re: Good Documentation anywhere?

[Stefan G. Weichinger]

Hi, Kris,

on Donnerstag, 03. Juni 2004 at 21:46 you wrote to amanda-users:

KV> Does anyone know of a book or some online docs that explain
KV> in detail how AMANDA works, how to use all of its tools, and how
KV> to optimize / tweak it for a particular environment? The online
KV> chapter of Unix Backup and Recovery doesn't quite do it for me.
KV> Thx!

Errrmmm ...

What exactly do you want to know that can't be found in the
AMANDA-docs, the amanda-users-ml-archive and the web in general?

There is no such thing as "The Official AMANDA HOWTO And Reference
Guide".

Yet.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Good Documentation anywhere?

[Kris Vassallo]

Does anyone know of a book or some online docs that explain in detail how AMANDA works, how to use all of its tools, and how to optimize / tweak it for a particular environment? The online chapter of Unix Backup and Recovery doesn't quite do it for me. Thx!

documentation

[Marc Cuypers]

Hi,

Is there somewhere a schematic overview what the different programs do?

--
Best regards,
Marc.

Re: Q: amanda documentation / soft links vs backups

[Paul Bijnens]

Raúl Wild-Spain wrote:
Hi!

I've found into the amanda documentation (FAQ.gz) various ways to perform a backup. I've some doubts because my english is a little bad ( I'm spanish and my alternative language is french) and I would like to make some questions about this. The FAQ says the following:

--   

 You may create short-named links in some directory
closer to the root (/) so as to reduce the length of names.  I.e.,
instead of backing up /usr/home/foo and /usr/home/bar, create the
following links:
 /.foo -> /usr/home/foo
 /.bar -> /usr/home/bar
then list /.foo and /.bar in the disklist.
This case works because the toplevel symlink (/.foo) is resolved
by amanda before starting the dump/gnutar program.  This is similar to 
the way amanda fill in disknames (/dev/hda7) or mountpoints (/home), 
depending on what program does the backujp

Symlinks inside /usr/home/foo are not resolved.

   Another approach is to group sub-directories in backup sets,
instead of backing up them all separately.  For example, create
/usr/home/.bkp1 and move `foo' and `bar' into it, then create links so
that the original pathnames remain functional.  Then, list
/usr/home/.bkp1 in the disklist.  You may create as many `.bkp'
directories as you need.
--

then, my doubt is the following: if I create a hidden directory /.furvbackup and into this a make some soft-links to the areas I want to backup, does it will work right? and another, I suppose there isn't problem to backup directories ( not partitions or disks) with amanda, is it right?, example, into disk list  ->mypc/path/to/directory always-full
If your disklist contains

	mypc/.furvbackupalways-full

then symlinks INSIDE /.furvbackup are NOT resolved, and your backup
will contain only a few Kbytes.
Best regards,

Raúl
[EMAIL PROTECTED]


--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Q: amanda documentation / soft links vs backups

[Raúl Wild-Spain]

Hi!

I've found into the amanda documentation (FAQ.gz) various ways to perform a backup. 
I've some doubts because my english is a little bad ( I'm spanish and my alternative 
language is french) and I would like to make some questions about this. The FAQ says 
the following:

--   

 You may create short-named links in some directory
closer to the root (/) so as to reduce the length of names.  I.e.,
instead of backing up /usr/home/foo and /usr/home/bar, create the
following links:
 /.foo -> /usr/home/foo
 /.bar -> /usr/home/bar
then list /.foo and /.bar in the disklist.

   Another approach is to group sub-directories in backup sets,
instead of backing up them all separately.  For example, create
/usr/home/.bkp1 and move `foo' and `bar' into it, then create links so
that the original pathnames remain functional.  Then, list
/usr/home/.bkp1 in the disklist.  You may create as many `.bkp'
directories as you need.

--

then, my doubt is the following: if I create a hidden directory /.furvbackup and into 
this a make some soft-links to the areas I want to backup, does it will work right? 
and another, I suppose there isn't problem to backup directories ( not partitions or 
disks) with amanda, is it right?, example, into disk list  ->mypc
/path/to/directory always-full

Best regards,

Raúl
[EMAIL PROTECTED]

Re: Tapeless Backup Documentation - call for volunteers

[Niall O Broin]

On Thu, Jan 02, 2003 at 12:15:26PM -0500, Jon LaBadie wrote:

> There are messages similar to the following,
> posted frequently to the amanda-users list:
> 
>   There is not much documentation in setting up AMANDA
>   to be backuped up to a Hard Drive.  I checked web sites,
>   the MAN pages, the mailing lists.
> 
>   And three weeks of trying to do this on my own, I need help.
> 
> I know some of you are using this feature.
> Anyone care to volunteer to write a HOW-TO
> that might be added to our documentation "library".
> 
> You would gain fame and fortune (well fame anyway,
> among a small elite group of appreciative readers).

There is a sort of howto out there, but it's not perfect. I'd be willing to
write it, perhaps in cooperation with somebody(ies) else. However, I know my
method is sub optimal. I use some shell script hacking in my daily amdump
script and I know the "right" way to do this is with a customised changer
script. If anyone out there who has done that, but doesn't have the time or
inclination to write the howto, would care to pass on details to me I'd be
happy to oblige.



Kindest regards,



Niall  O Broin

Tapeless Backup Documentation - call for volunteers

[Jon LaBadie]

There are messages similar to the following,
posted frequently to the amanda-users list:

  There is not much documentation in setting up AMANDA
  to be backuped up to a Hard Drive.  I checked web sites,
  the MAN pages, the mailing lists.

  And three weeks of trying to do this on my own, I need help.

I know some of you are using this feature.
Anyone care to volunteer to write a HOW-TO
that might be added to our documentation "library".

You would gain fame and fortune (well fame anyway,
among a small elite group of appreciative readers).

Before you ask "why doesn't he do it himself",
I'm still running 2.4.2 which doesn't support
the file driver feature.


Thanks to anyone who tackles the task.
-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Documentation

[Brad Tilley]

I'll send you a copy once it's complete. I wouldn't want to send it the
whole list. Apparently, only a handful are interested in it.

On Wed, 2002-03-13 at 21:09, Robert SHEN wrote:
> Will it be possible to post it here?
> 
> - Original Message - 
> From: "Brad Tilley" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 14, 2002 1:29 AM
> Subject: Documentation
> 
> 
> > Hello,
> > 
> > I am preparing amanda documentation for our office. The documents are
> > specific to us, but general enough to probably be of use to others who
> > have similar amanda implementations (50+ Windows end users and about six
> > departmental Linux servers and workstations).
> > 
> > Is there a place where I could publish the documentation (once it is
> > finished) so others could benefit?
> > 
> > Thanks,
> > -- 
> > Brad Tilley, OUB Sys. Admin.
> > http://bursar.vt.edu/rtilley/pgpkey
> > 
> > 
> 
-- 
Brad Tilley, OUB Sys. Admin.
http://bursar.vt.edu/rtilley/pgpkey

Re: Documentation

[Eric Trager]

On 19 Apr 2002, Marcos Teodoro Dias Junior wrote:

> Hello,
>
> Where I can find some documentation at how to use amanda with tape
> changers ?

In the source tree, look in docs/TAPE.CHANGERS .

- Eric

Re: Documentation

[Eric Trager]

On 19 Apr 2002, Marcos Teodoro Dias Junior wrote:

> Hello,
>
> Where I can find some documentation at how to use amanda with tape
> changers ?

In the source tree, look in docs/TAPE.CHANGERS .

- Eric

Documentation

[Marcos Teodoro Dias Junior]

Hello,

Where I can find some documentation at how to use amanda with tape
changers ?


-- 

"Se vc conhece o inimigo e conhece a si mesmo, 
não precisa temer o resultado de cem batalhas. 
Se você se conhece mais não conhece o inimigo, 
para cada vitória ganha sofrerá também uma derrota. 
Se você não conhece nem o inimigo nem a si mesmo,
perderá todas as batalhas."
(Sun Tzu)

--
Marcos Teodoro Dias Junior -  Consultor Técnico
Conectiva S/A - Filial Rio - Brasil
55-21-2515-4888 -- [EMAIL PROTECTED]

Re: Documentation

[John R. Jackson]

>I did wrote a short doc on how to install amanda on Linux approx.
>7 months ago , and I did post it on this listMaybe it got lost a
>long the way :-)

That depends on how you define "lost" :-) :-).

I "found" your post.  It's article 1562 out of 4911 in my "yet to be
processed" Amanda folder.

Sigh.

>Tien That Ton

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Documentation

[Tien That Ton]

Reply





Hi,

I did wrote a short doc on how to install amanda on Linux approx. 7 months ago,
and I did post
it on this listMaybe it got lost a long the way :-)


Tien That Ton

Here's the Documentation

[Brad Tilley]

Here is the rough draft of my amanda documentation. 

It deals mostly with using amanda in a predominantly Windows based
environment. 

This doc is far from complete. It lacks a lot, but here it is anyway
with all of its imperfections.









Amanda Backup Documentation
By Brad Tilley [EMAIL PROTECTED]


Advanced Maryland Automated Network Disk Archiver (AMANDA)
Introduction:
This document was written for people who have intermediate system administration
skills with Unix/Linux.
When editing files in Unix, knowledge of vi (pronounced VEE EYE; a simple
text editor present on most every Unix system on earth) is absolutely necessary.
The backup server has no GUI; all interaction is from the command prompt,
and vi is the only editor. Also, vi is installed on every Linux server
in the office. So the following vi tutorial can be applied to any of our
Linux servers.


A Quick vi tutorial:
1. view file_name will open a file for read-only viewing. You
may want to use view to safely look at the file before attempting to edit
it. To exit view, hold down the 'shift' key and press 'z'
twice.
2. Before editing a file, always copy it to another directory. If you
make a mistake or accidentally delete the file, you can use the copy you
made to make things right. For example, if you are going to edit /etc/amanda/daily0/amanda.conf,
copy it to /opt first with this command:
cp -v /etc/amanda/daily0/amanda.conf /opt
Now you are ready to edit the file.
3. vi file_name will open a file for editing.
4. Once vi has a file open, press 'i' to add or change text
in the file. You'll see the --INSERT-- message appear at the bottom
of the screen. To undo changes that you've made to the file, press'Esc'
until you hear a beep or until you no longer see the --INSERT--
message (note: pressing 'Esc' too many times won't hurt anything),
then press 'u' until you have undone the changes as farback as you
need to.
5. Once you are finished editing the file, press 'Esc' then
hold down 'Shift' and press 'z' twice to save your changes
and and exit.
6. To exit the file without saving your changes, type a ':quit!'
That's a colon followed by the word quit followed by an exclamation
point.
7. That's it! You now know how to use vi for basic text file editing,
consider yourself a true geek.


Office Environment Overview:
The office network consists of Microsoft Windows 98se, NT, and 2000
PCs. The office has three MS NT servers. Two for domain authentication
and one for cash receipts.
Note: The cash receipts server is going to be moved to the Computing
Center when the new system is implemented. We also have three Linux servers
that perform file, print, web, ftp, firewall, and backup services. Most
of these machines are standard implementations.


Backup Hardware Overview:
Tape Drives: 2 Quantum DLT 4000 stand-alone units. (In warranty until
Nov. 2002)
Note: We are budgeting for a DLT 8000 in the 2002-2003 fiscal year.
Backup Server: 1 Dell GX1 450 MHz 768 RAM with SCSI software RAID striping
RH Linux 7.2 standard server install with all patches as of 3-13-02.


Backup Media Overview:
Tape Cartridges: 15 DLT IV (5 daily) (4 weekly) (4 monthly) (2 extras)
and 2 Cleaning Tapes.
Note: The cleaning tapes should only be used when the drive calls for
them. Never insert a cleaning tape unless the 'Use Cleaning Tape'
light on the drive is on.


Backup Software Overview:
AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a
backup system that allows the administrator of a LAN to set up a single
master backup server to back up multiple hosts to a single large capacity
tape drive. AMANDA uses native dump and/or GNU tar facilities and can back
up a large number of workstations running multiple versions of Unix. AMANDA
can also use SAMBA to back up Microsoft Windows 9x/NT/2000 hosts.


Currently, there are three backup sets:
1. daily0
2. weekly0
3. monthly0 Note: monthly0 hasn't been implemented yet (3-13-02)
Note: All backups are full, there are no incrementals.
The following entries in the amanda.conf file will make amanda do full
backups every time:
dumpcycle 0
runspercycle 1
tapecycle THE_NUMBER_OF_TAPES_THAT_YOU_HAVE


Daily Backup Process Overview:
Amanda runs each night Monday through Friday as a cron
job. The daily tapes must be changed each day. Daily's do not run over
the weekend. Daily's run to /dev/nst0 the first tape drive. Amanda
does a self check at 4 PM each weekday, and alerts the administrator through
email if something is wrong. To manually run a self check, log in as root
and run this command su amanda -c "amcheck daily0" This will ensure
that all remote backup clients can be reached and that the proper tape
is loaded in the drive. Amanda emails in-depth reports at the end of each
backup to the administrator.
Sample crontab entry:
[root@reg root]# crontab -l -u amanda
0

Re: Documentation

[ahall]

I have written two docuements.  One on excluding data with amanda, and one
on how to setup amanda to use gpg.  The exclude doc is now available in
the DOCS subdir, but it was about six months between when I finished it
and a new version of amanda was released.  Is there another location that
docs are archived and viewable?  Do the members of the list really want
docs flying around the list.  If so I would like to post my new gpg doc.


Thanks.

Andrew

Re: Documentation (Yes, post it!)

[Ruth Anne]

On Thu, 14 Mar 2002, Eric Trager wrote:

> On Thu, 14 Mar 2002, Doug Silver wrote:
>
> > On 14 Mar 2002, Brad Tilley wrote:
> >
> > > I'll send you a copy once it's complete. I wouldn't want to send it the
> > > whole list. Apparently, only a handful are interested in it.
> >
> > I disagree -- one of the things that I (and others I've talked to) have
> > noticed is that while Amanda is feature rich, it's documentation is
> > lacking.  Why not post it somewhere so other's can read through it and
> > potentially add to it.  Even if it's just from the client/end-user
> > perspective, I think it's better than nothing.
>
> Well put. Anything documenting successes and failures along the way that
> ends up searchable in the archives is a Good Thing. I've searched for
> issues with all kinds of programs on deja.com for years and sometimes it's
> a lone reply in a single thread that gives me a solution.
>

If you don't have the web space for it, I'd be willing to put it up.
Or maybe amanda.org would like it.

I've been having massive problems with using amanda with kerberos, in
large part due to lack of documentation. You'd better believe that
when I finally get all done, I am going to put up a document telling
how to do it.

--Ruth Anne

Re: Documentation (Yes, post it!)

[Eric Trager]

On Thu, 14 Mar 2002, Doug Silver wrote:

> On 14 Mar 2002, Brad Tilley wrote:
>
> > I'll send you a copy once it's complete. I wouldn't want to send it the
> > whole list. Apparently, only a handful are interested in it.
>
> I disagree -- one of the things that I (and others I've talked to) have
> noticed is that while Amanda is feature rich, it's documentation is
> lacking.  Why not post it somewhere so other's can read through it and
> potentially add to it.  Even if it's just from the client/end-user
> perspective, I think it's better than nothing.

Well put. Anything documenting successes and failures along the way that
ends up searchable in the archives is a Good Thing. I've searched for
issues with all kinds of programs on deja.com for years and sometimes it's
a lone reply in a single thread that gives me a solution.

- -  -   --
Eric Trager

Re: Documentation

[Doug Silver]

On 14 Mar 2002, Brad Tilley wrote:

> I'll send you a copy once it's complete. I wouldn't want to send it the
> whole list. Apparently, only a handful are interested in it.
> 
> On Wed, 2002-03-13 at 21:09, Robert SHEN wrote:
> > Will it be possible to post it here?
> > 
> > - Original Message - 
> > From: "Brad Tilley" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, March 14, 2002 1:29 AM
> > Subject: Documentation
> > 
> > 
> > > Hello,
> > > 
> > > I am preparing amanda documentation for our office. The documents are
> > > specific to us, but general enough to probably be of use to others who
> > > have similar amanda implementations (50+ Windows end users and about six
> > > departmental Linux servers and workstations).
> > > 
> > > Is there a place where I could publish the documentation (once it is
> > > finished) so others could benefit?
> > > 
> > > Thanks,
> > > -- 
> > > Brad Tilley, OUB Sys. Admin.
> > > http://bursar.vt.edu/rtilley/pgpkey
> > > 
> > > 
> > 
> 

I disagree -- one of the things that I (and others I've talked to) have
noticed is that while Amanda is feature rich, it's documentation is
lacking.  Why not post it somewhere so other's can read through it and
potentially add to it.  Even if it's just from the client/end-user
perspective, I think it's better than nothing.  

just my $.02 ;)

-- 
~
Doug Silver
Network Manager
Quantified Systems, Inc
~

Re: Documentation

[Brad Tilley]

I'll send you a copy once it's complete. I wouldn't want to send it the
whole list. Apparently, only a handful are interested in it.

On Wed, 2002-03-13 at 21:09, Robert SHEN wrote:
> Will it be possible to post it here?
> 
> - Original Message - 
> From: "Brad Tilley" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 14, 2002 1:29 AM
> Subject: Documentation
> 
> 
> > Hello,
> > 
> > I am preparing amanda documentation for our office. The documents are
> > specific to us, but general enough to probably be of use to others who
> > have similar amanda implementations (50+ Windows end users and about six
> > departmental Linux servers and workstations).
> > 
> > Is there a place where I could publish the documentation (once it is
> > finished) so others could benefit?
> > 
> > Thanks,
> > -- 
> > Brad Tilley, OUB Sys. Admin.
> > http://bursar.vt.edu/rtilley/pgpkey
> > 
> > 
> 
-- 
Brad Tilley, OUB Sys. Admin.
http://bursar.vt.edu/rtilley/pgpkey

Re: Documentation

[Robert SHEN]

I'm not the one who produced the document, you should post on the mailing
list
- Original Message -
From: "Lewis Watson" <[EMAIL PROTECTED]>
To: "Robert SHEN" <[EMAIL PROTECTED]>
Sent: Thursday, March 14, 2002 10:45 AM
Subject: Re: Documentation


> I would like to see the docs  Could you email it to me? I could also
put
> it on my web site if you just want it somewhere for reference
> lewis Watson
>
>
>
> - Original Message -
> From: "Robert SHEN" <[EMAIL PROTECTED]>
> To: "Brad Tilley" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, March 13, 2002 8:09 PM
> Subject: Re: Documentation
>
>
> > Will it be possible to post it here?
> >
> > - Original Message -----
> > From: "Brad Tilley" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, March 14, 2002 1:29 AM
> > Subject: Documentation
> >
> >
> > > Hello,
> > >
> > > I am preparing amanda documentation for our office. The documents are
> > > specific to us, but general enough to probably be of use to others who
> > > have similar amanda implementations (50+ Windows end users and about
six
> > > departmental Linux servers and workstations).
> > >
> > > Is there a place where I could publish the documentation (once it is
> > > finished) so others could benefit?
> > >
> > > Thanks,
> > > --
> > > Brad Tilley, OUB Sys. Admin.
> > > http://bursar.vt.edu/rtilley/pgpkey
> > >
> > >
> >
> >
> >
>
>

Re: Documentation

[Robert SHEN]

Will it be possible to post it here?

- Original Message - 
From: "Brad Tilley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 14, 2002 1:29 AM
Subject: Documentation


> Hello,
> 
> I am preparing amanda documentation for our office. The documents are
> specific to us, but general enough to probably be of use to others who
> have similar amanda implementations (50+ Windows end users and about six
> departmental Linux servers and workstations).
> 
> Is there a place where I could publish the documentation (once it is
> finished) so others could benefit?
> 
> Thanks,
> -- 
> Brad Tilley, OUB Sys. Admin.
> http://bursar.vt.edu/rtilley/pgpkey
> 
> 

Documentation

[Brad Tilley]

Hello,

I am preparing amanda documentation for our office. The documents are
specific to us, but general enough to probably be of use to others who
have similar amanda implementations (50+ Windows end users and about six
departmental Linux servers and workstations).

Is there a place where I could publish the documentation (once it is
finished) so others could benefit?

Thanks,
-- 
Brad Tilley, OUB Sys. Admin.
http://bursar.vt.edu/rtilley/pgpkey

Documentation Discrepancies

[Paul Lussier]

Hi all,

I was just reading through the docs for 2.4.2p2 and noticed a few 
discrepancies and/or places for improvement:

amanda-2.4.2p2/README   - still refers in several places to 2.4.1
- does not mention "what's new" in 2.4.2 at all

amanda-2.4.2p2/docs/FAQ - refers to Oren Teich's FAQ at
  http://ugrad-www.cs.colorado.edu/~teich/amanda
  which no longer exists.

amanda-2.4.2p2/docs/WHATS.NEW
- states the document is for 2.3, this is misleading
  IMO, and should rather only include "what's new"
  in 2.4.2 since 2.4.1.  Maybe there should be
  a COMING.ATTRACTIONS doc?

amanda-2.4.2p2/docs/UPGRADE
- still refers to upgrading from a pre-2.4.0 config
- does not mention anything about upgrading within
  2.4.x 


www.amanda.org  - should probably have links to all these docs
  to make it easier to access.  

- might want to have a "Features" page
  listing what the current/stable release does.

- not a lot of useful info there for someone
  looking to see if Amanda could be useful
  to them.  Granted, they could grab the source
  and read docs/*, but most want a quick summary.
  


Since I'm not sure  who's "in charge" of documentation, I sent this to
both -users and -hackers.  Hope this helps some :)
-- 

Seeya,
Paul

...we don't need to be perfect to be the best around,
and we never stop trying to be better. 
   Tom Clancy, The Bear and The Dragon

 If you're not having fun, you're not doing it right!