Amanda with SMB

[Shulov Leonid]

Hi
1. What client program I must load on windows XP host that Amanda  do 
backup ?
2. If you know what RTFM - I be rewarding.
Leonid

AW: Problems with amflush

[Jörn Rübel]

Hi John,

> -Ursprüngliche Nachricht-
> Von: Jon LaBadie [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 23. Juli 2003 19:13
> An: Jörn Rübel
> Betreff: Re: Problems with amflush
> 
> 
> On Wed, Jul 23, 2003 at 07:51:51AM +0200, Jörn Rübel wrote:
> > Hello,
> > 
> > i've got a problem with amflush. I got my backup from 
> tuesday (yesterday) on the holdingdisk (/dump/amanda/) 
> but not on tape. when i run amflush, the following error occurred:
> > 
> > *** A TAPE ERROR OCCURRED: [cannot overwrite active tape 
> DailySet1-02].
> > Some dumps may have been left in the holding disk.
> > Run amflush again to flush them to tape.
> > The next tape Amanda expects to use is: DailySet1-01.
> > 
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   amflush: ERROR Cannot flush without tape.  Try again.
> > 
> > 
> > STATISTICS:
> >   Total   Full  Daily
> >       
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:00
> > Dump Time (hrs:min)0:00   0:00   0:00
> > Output Size (meg)   0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- -- 
> > Filesystems Dumped0  0  0
> > Avg Dump Rate (k/s) -- -- -- 
> > 
> > Tape Time (hrs:min)0:00   0:00   0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%)   0.00.00.0
> > Filesystems Taped 0  0  0
> > Avg Tp Write Rate (k/s) -- -- -- 
> > 
> > 
> > DUMP SUMMARY:
> >  DUMPER STATS   
>  TAPER STATS 
> > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  
> KB/s MMM:SS  KB/s
> > -- 
> - 
> > host1.dom -ta/host/etc   NO FILE TO FLUSH 
> -
> > host1.dom -s/home.nis   NO FILE TO FLUSH 
> -
> > host1.dom -ta/host/log   NO FILE TO FLUSH 
> -
> > host1.dom /etc  NO FILE TO FLUSH 
> -
> > host1.dom -b/tripwire   NO FILE TO FLUSH 
> -
> > host2.dom -ta/host/etc   NO FILE TO FLUSH 
> -
> > host2.dom -s/home.nis   NO FILE TO FLUSH 
> -
> > host2.dom -ta/host/log   NO FILE TO FLUSH 
> -
> > host2.dom /etc  NO FILE TO FLUSH 
> -
> > host2.dom -b/tripwire   NO FILE TO FLUSH 
> -
> > host3.dom -ta/host/etc   NO FILE TO FLUSH 
> -
> > host3.dom -s/home.nis   NO FILE TO FLUSH 
> -
> > host3.dom -ta/host/log   NO FILE TO FLUSH 
> -
> > host3.dom /etc  NO FILE TO FLUSH 
> -
> > host3.dom -b/tripwire   NO FILE TO FLUSH 
> -
> > 
> > (brought to you by Amanda version 2.4.2)
> > 
> > How can i tell amanda to use the tape DailySet1-02 to flush 
> the last backup on the tape from tuesday?
> > 
> 
> Two things:
> 
> 1) Are you sure there are files there to be flushed?
>From the report above "NO FILE TO FLUSH" I wonder.
> 

my holdingdisk contains the files i want to backup. 

>Maybe it is just an empty, dated directory, and even if you
>use a tape that amanda wants, it will "waste" that tape usage
>by thinking it used it but have nothing to write to the tape.
> 
> 2) Amanda wants to use tape 01, you want it to use 02.
>Do you only have 2 tapes in circulation?

No, there are 5 tapes for one week (monday-friday, no backup on saturday and sunday)

> 
>If you really want to destroy what is on tape 02 and its
>various index files and use it immediately, try doing a two
>step series, first "amrmtape" the tape which will remove it
>and what is on it from amanda's records, then "amlabel -f"
>the tape again.  Then amanda will accept it as a new tape.

This works fine. But today i got another problem: after amflush amanda expects the 
tape 01 for monday and not 04 for thursday. How can i fix this?

Thanks for your help.

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


Regards

Jörn

Bu fýrsatý kaçýrmayýn!!!

Title: AYLIK 4







  
  

  
  
  


  
  AYLIK 3$ 'DAN BAŞLAYAN ŞOK 
  FİYATLARLA HOSTİNG HİZMETİ! BU KAMPANYA KAÇMAZ!
 
  Şimdiye kadar web hosting üzerine 
  bildiklerinizi unutun! Artık yepyeni bir dünyaya geldiniz. Uygun fiyat 
  seçeneklerimizle, sağlam bir teknik ekip ile hizmet veren
  www.areshosting.com  'da her 
  yol çözüme gider. Size uygun olan Web Hosting paketlerimizi inceledikten 
  sonra 2 adımda sipariş verebilir hesabınızı hemen aktif hale 
  getirebilirsiniz. Ares Hosting müşterilerine aradıkları ve 
  bekledikleri hizmetleri dünya standartlarında sunmaktadır.Ücretsiz 
  kurulum, 7/24 saat teknik destek vererek müşterilerinin memnuniyetini 
  önplanda tutar.Birçok firmanın 1.derecede tercih nedeni olduğu AresHosting 
  websitelerini Windows 2003 .Net Server'larda barındırmaktadır.İnternet'te 
  yerim olsun diyorsanız AresHosting'in sınırsız paketlerinden sizde 
  yararlanın.
  
  
  NOT: BU MAİL ARACILIĞYLA 
  ARADIĞINIZI SÖYLERSENİZ HER ALACAĞINIZ PAKETTE 10 MB BEDAVA YER 
  KAZANACAKSINIZ!!!
  Ares Hosting, Ares Yayıncılık 
  Organizasyon ve Bilişim Hizmetleri tescilli markasıdır.
  Cenk Şefik: 0535 329 62 32
  [EMAIL PROTECTED] 
  

  
  
  
  Mini Bireysel  (20Mb) +10mb Bedava!
  4 $
  Aylık
  
  
  Detaylar


  Midi Bireysel (30 Mb) +10mb Bedava!
  5 $
  Aylık
  
  
  Detaylar


  Maxi Bireysel (50 Mb) +10mb Bedava!
  7 $
  Aylık
  
  
  Detaylar


  
  
  
  Mini Kurumsal (75 Mb) +10mb Bedava!
  9 $
  Aylık
  
  
  Detaylar


  Midi Kurumsal (125 Mb) +10mb Bedava!
  15 $
  Aylık
  
  
  Detaylar


  Maxi Kurumsal (175 Mb) +10mb Bedava!
  20 $
  Aylık
  
  
  Detaylar


  
  
  
  Mini Ekonomik (15 Mb) +10mb Bedava!
  3 $
  Aylık
  
  
  Detaylar


  Midi Ekonomik (25 Mb) +10mb Bedava!
  4 $
  Aylık
  
  
  Detaylar


  Maxi Ekonomik (40 Mb) +10mb Bedava!
  5 $
  Aylık
  
  
  Detaylar


  
  
  
  Mini Pro (Özel) (100 Mb) +10mb Bedava!
  12 $
  Aylık
  
  
  Detaylar


  Midi Pro (250 Mb) +10mb Bedava!
  20 $
  Aylık
  
  
  Detaylar


  Maxi pro (500 Mb) +10mb Bedava!
  29 $
  Aylık
  
  
  Detaylar


  
  
  
  
  

  
  

  
  


"

Re: newbie problems

[Jon LaBadie]

On Wed, Jul 23, 2003 at 11:12:02AM -0600, Yogish wrote:
> Hi 
> I am a newbie with amanda,  I have configured amanda according to a book, However 
> when I try to amdump it gives me following error.I have also attached the 
> amanada.conf and disklist files.Can anyone please help me

That is a very long single line.
Spliting it is appreciated by some mail readers.

> This was the error I ran into when I checked the log files
> START planner date 20030722
> INFO planner Adding new disk localhost:/home/.

Not a factor here, but it is strongly recommended that you NOT use
localhost, but use machine names instead.

> START driver date 20030722
> WARNING driver WARNING: ignoring holding disk /home/tmp: Permission denied

Obvious permission/ownership problem on what you plan to use as a holding disk.

> FINISH planner date 20030722
> STATS driver startup time 14.803
> ERROR taper no-tape [not an amanda tape]

Sounds like you did not "amlabel" the tape.
Each tape you use must first be labelled.

> FAIL driver localhost /home/ 0 [can't switch to incremental dump]

I'll guess your amanda.conf setting for reserve is the default 100%.
Unless you lower it, your holding disk will not be used.
Because of the ownership/permission problem this was not a factor.

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

Re: newbie problems

[Frank Smith]

--On Wednesday, July 23, 2003 11:12:02 -0600 Yogish <[EMAIL PROTECTED]> wrote:

> Hi 
> I am a newbie with amanda,  I have configured amanda according to a
> book, However when I try to amdump it gives me following error.I have
> also attached the amanada.conf and disklist files.Can anyone please help
> me
> This was the error I ran into when I checked the log files
> START planner date 20030722
> INFO planner Adding new disk localhost:/home/.
> START driver date 20030722
> WARNING driver WARNING: ignoring holding disk /home/tmp: Permission
> denied

You've said /home/tmp is your holdingdisk, but evidently your backup
user doesn't have permission to write there, so it isn't used.

> FINISH planner date 20030722
> STATS driver startup time 14.803
> ERROR taper no-tape [not an amanda tape]

Looks like you forgot to label your tape or some other tape was left
in the drive (man amlabel,  probably 'amlabel normal normal01')

> FAIL driver localhost /home/ 0 [can't switch to incremental dump]

Since it couldn't find the correct (labeled) tape to write to, it
would normally dump to your holding disk, but since that wasn't
available either, it quit.

Also, don't use 'localhost', use the fully-qualified name of the
server (i.e., host.domain.com) instead. The use of 'localhost'
will bite you sometime in the future during a restore.

> FINISH driver date 20030722 time 28.470

Other comments:

1. Usually it is best to try 'amcheck ' before trying an amdump,
as it gives meaningful errors for most config problems before wasting
time doing estimates and dumps that might not work.

2. Your config is not quite right:
   dumpcycle 7 weeks
   runspercycle 5 weeks
   tapecycle 25 tapes

dumpcycle is the max time between full (level 0) backups.  7 weeks seems
like a long time, but maybe thats what you want

runspercycle is how many times during the dumpcycle Amanda runs.  It is
just a number with no units of measure.  I'm sure you are planning on
running Amanda more than 5 times in 7 weeks.

tapecycle is the total number of tapes to rotate through before over-
writing the first one.  It must be at least equal to runspercycle times
runtapes, but you normally want twice that so you don't take a chance
on overwriting your last full dump  with a failed one, plus a couple
extra to allow for a bad tape or two to be removed.
   For example, with a dumpcycle of 1 week, and runspercycle of 5 (for
Monday-Friday backups), you need a bare minimum of 5 tapes but 12 would
be much safer.

3.  Mentioning your OS and Amanda version, as well as if it was installed
from a package or source, often help people find your problem.  It wasn't
necessary for your current problem, but will if you have more subtle
problems in the future.

Frank


>  
>  
> Regards
> Yogish
> --
> Yogish.G.K
> American Healthcare Solutions Inc
> 405, South Lincoln
> Steamboat Springs CO-80487
> Ph-970-870-6232 ( EXT 106) (office)
> Email: [EMAIL PROTECTED]  
> 



--
Frank Smith [EMAIL PROTECTED]
Systems Administrator  Voice: 512-374-4673
Hoover's Online  Fax: 512-374-4501

Re: newbie problems

[Paul Bijnens]

Yogish wrote:
I am a newbie with amanda,  I have configured amanda according to a 
book, However when I try to amdump it gives me following error.I have 
Did you see the excellent explanation in docs/INSTALL too?

also attached the amanada.conf and disklist files.Can anyone please help me
This was the error I ran into when I checked the log files
START planner date 20030722
INFO planner Adding new disk localhost:/home/.
START driver date 20030722
WARNING driver WARNING: ignoring holding disk /home/tmp: Permission denied
Error nr one.  the amanda holding disk must be writeable by the
amanda user.  It is best that you make this a dedicated directory,
and not /tmp or /var/tmp.  See below.

FINISH planner date 20030722
STATS driver startup time 14.803
ERROR taper no-tape [not an amanda tape]
Before using a tape with amanda, you must write a special header
to the tape, so that amanda can tell which tape is for her.
You do this with the command "amlabel".  See the man page.
Or did you label the tape and the label got erased by using
the rewind-tape device instead of the non-rewinding tapedevice?
Something like this should work (having a correct tapedev):

  amlabel YourConfig normal01

FAIL driver localhost /home/ 0 [can't switch to incremental dump]
You may ignore this error.  Amanda here states that she cannot
do an incremental dump, because she never did a full dump
of that filesystem yet.  She wanted do try an incremental dump
to holdingdisk because a full dump to tape did not work out.
That problem will go away when you have labeled a tape, or when
you don't reserve all of the holdingdisk for incremental backups
(the default "reserve 100" parameter in you amanda.conf file).
DISKLIST:

Fine. Not an error, but it is unwise to name your computer "localhost".
Use the real domainname.  A configuration usually starts out with
one hosts, then grows to many.  At restore time, which computer
is "localhost" when you have more than one?
Personally, I would use mountpoint instead of disknames.
AMANDA.CONF:

> tapedev "/dev/st0"

Wrong! You should use the NON-rewinding device. (Maybe this is why
the label of the tape got erased?).  Make that:
tapedev "/dev/nst0"

> dumpcycle 7 weeks
> runspercycle 5 weeks
> tapecycle 25 tapes
I see you are using a redhat rpm.  It is not an error, but it confuses
people a lot.  Runspercycle is normally without a unit (moreover, the 
unit "weeks" means "times 7": so you specified runspercycle 35).
Then, are you really really sure you want only 1 full backup every 7 
weeks?  Then you need more than 25 tapes too.
Using the "always-full" dumptype makes this little bit confusing,
because that dumptype overrides the dumpcycle.  Good enough
if you tape is large and you have enough time each night.

You probably mean:

dumpcycycle 1 week
runspercycle 5
tapecycle 25 tapes
meaning:  I want one full dump every week, and I insert a tape
5 times during that week (probably not in the weekend).
In your 25 tapecycle you have now 5 times a full backup of every 
filesystem.  (And dumptype "always-full" makes that a full backup
on each tape.)
Comfortable enough.

holdingdisk hd1 {
comment "main holding disk"
directory "/home/tmp"   # where the holding disk is
use 290 Mb  # how much space can we use on it
...   # chunksize 2 Gb
> }
I would create a dedicated directory as holdingdisk. Name the directory
after your config.
 directory "/home/amandahold/normal"

And don't forget "chown amanda /home/amandahold/normal"!

I would specify a chunksize, even if the filesystem on the
holdingdisk can hold large files:
 chunksize 1 Gb

If you add more holdingdisks, amanda can spread a single dump over
several holdingdisks this way too.
Paul

Re: newbie problems

[Jason P.Pickering]

Hi Yogish. It would seem that the permissions on you holding disk are not
correct. Did you try "chown amanda:amanda /home/tmp" to give amanda
permission to write to the disk?
Regards..JPP



On Wed, 23 Jul 2003, Yogish wrote:

> Hi
> I am a newbie with amanda,  I have configured amanda according to a book, However 
> when I try to amdump it gives me following error.I have also attached the 
> amanada.conf and disklist files.Can anyone please help me
> This was the error I ran into when I checked the log files
> START planner date 20030722
> INFO planner Adding new disk localhost:/home/.
> START driver date 20030722
> WARNING driver WARNING: ignoring holding disk /home/tmp: Permission denied
> FINISH planner date 20030722
> STATS driver startup time 14.803
> ERROR taper no-tape [not an amanda tape]
> FAIL driver localhost /home/ 0 [can't switch to incremental dump]
> FINISH driver date 20030722 time 28.470
>
>
> Regards
> Yogish
> --
> Yogish.G.K
> American Healthcare Solutions Inc
> 405, South Lincoln
> Steamboat Springs CO-80487
> Ph-970-870-6232 ( EXT 106) (office)
> Email: [EMAIL PROTECTED]
> 

The old GnuTar vs. Dump topic

[Stefan G. Weichinger]

Hi, amanda-users,

is there a brief comparison between using dump or tar with amanda
anywhere?

I´d like to have the dis/advantages in a compact form.

Thank you,
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

newbie problems

[Yogish]

Hi 
I am a newbie with amanda,  I have configured 
amanda according to a book, However when I try to amdump it gives me following 
error.I have also attached the amanada.conf and disklist files.Can anyone please 
help me
This was the error I ran into when I checked the 
log files
START planner date 20030722INFO planner Adding 
new disk localhost:/home/.START driver date 20030722WARNING driver 
WARNING: ignoring holding disk /home/tmp: Permission deniedFINISH planner 
date 20030722STATS driver startup time 14.803ERROR taper no-tape [not an 
amanda tape]FAIL driver localhost /home/ 0 [can't switch to incremental 
dump]FINISH driver date 20030722 time 28.470
 
 
Regards
Yogish
--Yogish.G.KAmerican 
Healthcare Solutions Inc405, South LincolnSteamboat Springs 
CO-80487Ph-970-870-6232 ( EXT 106) (office)Email: [EMAIL PROTECTED]


amanda.conf
Description: Binary data


disklist
Description: Binary data

Re: How could amflush NOT flush ? :o)

[Gene Heskett]

On Wednesday 23 July 2003 11:03, Kurt Yoder wrote:
>Nicolas Ecarnot said:
>> Hi,
>>
>> My Amanda setup keeps improving tests after tests and I still have
>> so many questions.
>> Today is : How could I do to make automatic flushes (autoflush)
>> but without deleting the holding disk directories ?
>>
>> What I'd like to have is this situation :
>> - cron launches amdump
>> - the autoflush option is set, so as to write datas on the holding
>> disk AND to tape
>> - but to keep the last holding disk directory
>> - Another cron would remove the (n-1) last hoslding disk directory
>>
>> That way, I could restore the previous-day files directly from the
>> holding disk files, without having to go search my tapes.
>
>Just an idea for you: use rsync to make on-line backups of all your
>amanda disks. This is what I do. That way, there's no tweaking of
>amanda necessary (though rsync must be set up). Restoring files from
>your on-line backups is then as simple as using "scp", "ftp", or
>whatever you want.

I'll second that, works great.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: How could amflush NOT flush ? :o)

[Jon LaBadie]

On Wed, Jul 23, 2003 at 05:34:59PM +0200, Nicolas Ecarnot wrote:
> On Wed, Jul 23, 2003 à 10:36:42AM -0400, Jon LaBadie wrote:
> [...]
> 
> > # make LinkDir if needed
> > [ -d ${LinkDir} ] || mkdir ${LinkDir}
> > # should do error processing, but I'm lazy
> > 
> > # link to dump file
> > ln ${Dfile} ${LinkFile}
> 
> No hard links to directory under FreeBSD... sorry
> (Even with the preliminary mkdir)

If I coded correctly, ${Dfile} should never be a directory.

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

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Jon LaBadie]

On Wed, Jul 23, 2003 at 05:53:22PM +0200, Nicolas Ecarnot wrote:

> I'm absolutely confuse to appear as asking too much,
> but I sure would prefer not to touch my amanda configuration,
> so the Kurt's solution seems nice (apart the ressources considerations).

That may not be as bad as you imagine.  It is not a doubling of
the space as the holding disk files are removed as they are taped.

Another approach, unmentioned til now, is a combination of RAIT,
the file:driver, and normal tape backup.  I believe it was recently
announced that a RAIT mirror setup could contain a tape device and
a hard disk "file:driver" device.  That might also solve the recovery
problem as the index would still apply.  You might have to determine
a way to remove daily the hard disk copy of the mirrored backup.

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

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Paul Bijnens]

Nicolas Ecarnot wrote:

But I really can't admit there is no way to tell to amflush not to
remove the holding disk files !
Should I ask the dev mailing list if the patch exist ?
No, there is no patch.  (But I still think there is some
way in the hard-link-files-method. The changes to the config
are not big at all.)
But, rephrasing the problem:  you want to be able to restore
files from disk, because it's much faster than tape.  But you want
the data on tape too, because they are safer there.
Two solutions:

1. Use LVM (if you are using Linux) and create a snapshot of the
filesystem, and keep it around for the next day.  (This had the
added benefits that making backup with gnutar won't change the
access times of the files, and no more warnings like "file changed
while reading...".)  I have a working setup with this. Works very nice.
Snapshots also work on Solaris 8+ and on BSD.
2. Use RAIT, with one output to tape, the other to disk, and
throwing the parity away:
  tapedev  "rait:tape:/dev/nst0,file:/bigdisk/onlinebup,null:"
or something like that.
I never tested such a setup, but others have.  Google around a bit.
--
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  *
***

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Nicolas Ecarnot]

On Wed, Jul 23, 2003 à 03:54:40PM +0100, Niall O Broin wrote:
> A little thinking here would help

I sure need advices :o)

>- in your script which runs amanda, all you 
> have to do is hardlink every file in the last holding directory to a 
> similarly named file in another directory and you're done. But I'm not sure 
> what that gets you TBH, apart from a set of files. Because amanda has now 
> flushed those files, she won't look in the holding disk when asked to 
> recover.

So true ! I did not think about that.
I didn't think about that because I was thinking about this system just for me, the 
console sysadmin in his cave, that dd and untar like breathing.
Indeed, for the other 'normal' sysadmins, this will be easier to use the amrecover 
mecanisms and the usual way.

Anyway, if I manage to do that, this daily copy will be very useful.

>Two options there :
> 
> 1) Recover from those backups manually

I already did some tests. This does work.

> 2) Also before the daily run, copy (not link) the index files (and possibly 
> some more stuff) elsewhere. After the daily run, rename this other directory 
> to the name of the just flushed holding directory.Then, if you need to 
> recover from the holding disk, you just put the (1 amanda run old) set of 
> files back in place, and amrecover, working from the old files, happily 
> retrieves from the holding disk.

Though this seems complex, it is not.
But this still implies a *copy*
(... Also before the daily run, copy (not link) the index files (and possibly... )
and then some more space on my holding disk...

Well, for every one, thank you for your advices. For this problem, I stop here on this 
list.
I may look at the code, and perhaps ask the coders.
This is not a vital feature, though useful, so let's not spend too many time on it.

If I have enough room, I'll do a dumb copy and this will be simple.
If not, I won't do anything else than walk to the tapes building... :o)

Thanks to everyone, have a nice day.

-- 
Nicolas Ecarnot

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Nicolas Ecarnot]

On Wed, Jul 23, 2003 à 04:41:12PM +0200, Paul Bijnens wrote:
> You have two configs; Config1 "reserve 100" and a bogus
> "tapedev /no/such/tape" and holdingdisk set to
> "/bigdisk/amandahold/Config1/".
> The other, Config2, "tapedev /dev/nst0" (or whatever is the
> real tapedev) and holdingdisk "/bigdisk/amandahold/Config2".
> The disklist is shared (use a hard link :-) ).
> 
> We make the dumps with Config1, and they stay in the holdingdisk
> because your tapedev is bogus.
> Then we populate the other holdingdisk with links to this one,
> using "cpio --link" as program to create the symlinks:

(damned, I'm looking the english translation of the french 
expression "faire la fine bouche" !)
I'm absolutely confuse to appear as asking too much,
but I sure would prefer not to touch my amanda configuration, so the Kurt's solution
seems nice (apart the ressources considerations).

But I really can't admit there is no way to tell to amflush not to remove the holding 
disk
files !

Should I ask the dev mailing list if the patch exist ?

-- 
Nicolas Ecarnot

Re: amrecover remotely: TCP/IP connection stalls

[Joshua Baker-LePain]

On Wed, 23 Jul 2003 at 2:07pm, Andreas Ntaflos wrote

> Hello list(s),
> 
>   First of all, sorry for crossposting but I think this is both a
>   question for -users as well as -hackers. I hope I get some response
>   since I've been through the archives so thoroughly I get a headache
>   only from thinking of them...

Responding to users only -- that's where this belongs.

>   Both hosts run the services needed for backup operations (amindex,
>   amidxtape, amandad, etc, etc). We have set the server up for tapeless 

Only the server needs amindexd and amidxtape.  Clients only need amandad.

>   And here it sits forever until it dies. tcpdump shows that backup
>   tries to reach mobilkom and awaits ACK but gets nothing and only
>   retransmits the request packets. mobilkom eventually ACKs something,
>   but definately nothing concerning the ongoing connection. I will attach
>   the log output of tcpdump, starting at the moment amrecover started on
>   mobilkom.
>
>   The point is that we need amrecover working, or else the system would
>   never be able to restore 300GB worth of user data in the event of any
>   kind of emergancy, since extracting the files on backup itself and
>   then transferring them to mobilkom is not an option.

In a pinch, you could always use NFS mounts and run amrecover on backup 
but sitting in a directory on mobilkom.

But it should work correctly.  Are there any firewalls in the way?  What 
does amidxtaped*debug on the server look like?

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

Re: strange "disk offline" error

[Joshua Baker-LePain]

On Wed, 23 Jul 2003 at 10:57am, Kurt Yoder wrote

> sendsize[7578]: time 0.020: calculating for amname '/', dirname '/',
> spindle -1
> sendsize[7578]: time 0.020: getting size via dump for / level 0
> sendsize[7578]: time 0.020: calculating for device '/' with ''
> sendsize[7578]: time 0.022: running "/bin/dump 0Esf 1048576 - /"
> sendsize[7578]: time 0.023: running /usr/local/libexec/killpgrp
> sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v]
> -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s)
> ..
*snip*

> Notice line 6 "Usage: " message. Perhaps dump is not acting the way
> amanda expects? Is this my problem? I had trouble getting gnu tar to
> compile, but maybe I should try again so I can use it instead of
> dump.

Yup, that's definitely the problem.  Is amanda picking the right dump for 
your filesystem?  You can tell by the output of ./configure (it might also 
be in the amandad*debug files -- I'm not sure).

tar is nice for being so cross platform.  If you can get that to go, it 
might be your better option.

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

Re: How could amflush NOT flush ? :o)

[Nicolas Ecarnot]

On Wed, Jul 23, 2003 à 10:36:42AM -0400, Jon LaBadie wrote:
[...]

>   # make LinkDir if needed
>   [ -d ${LinkDir} ] || mkdir ${LinkDir}
>   # should do error processing, but I'm lazy
> 
>   # link to dump file
>   ln ${Dfile} ${LinkFile}

No hard links to directory under FreeBSD... sorry
(Even with the preliminary mkdir)

-- 
Nicolas Ecarnot

Re: Estimate tieouts

[Jason Edgecombe]

Jon LaBadie wrote:
On Tue, Jul 22, 2003 at 09:15:39AM -0400, Jason Edgecombe wrote:

Hi everyone,

 I am having estimate timeouts from an amanda client.

The client's logs for amandad have the following error messages at the end:
amandad: time 81.782: dgram_recv: timeout after 10 seconds
amandad: time 81.782: waiting for ack: timeout, retrying
amandad: time 91.782: dgram_recv: timeout after 10 seconds
amandad: time 91.782: waiting for ack: timeout, retrying
amandad: time 101.782: dgram_recv: timeout after 10 seconds
amandad: time 101.782: waiting for ack: timeout, retrying
amandad: time 111.782: dgram_recv: timeout after 10 seconds
amandad: time 111.782: waiting for ack: timeout, retrying
amandad: time 121.782: dgram_recv: timeout after 10 seconds
amandad: time 121.782: waiting for ack: timeout, giving up!
amandad: time 121.782: pid 17514 finish time Tue Jul 22 00:17:03 2003
My etimeout value on the server is -1800.


Doesn't seem like estimate timeouts, starting after only 81 seconds.
Sounds like some network communication attempt failing.

I'm running amanda 2.4.3 on the client and 2.4.4 on the server.

My firewall is properly letting packets through.

Both client and server share a connection via the campus 100mbs network 
and a private gigabit network. I'm backing up over the gigabit network.

I can run the backup manually and the estimate phase runs fine, but it 
doesn't want to run at night.

Does anyone have any insight into this?



Two networks.  Sounds like the amanda connection works over one but
not the other.  And for some reason, during the day, with manual
attempts the working network is used, in evening, from cron, the
other, non-working network is used.  Maybe name resolution differences
on the two networks?
I checked this with ethereal, everthing is in fact running over the 
gigabit ethernet.

I noticed that the amanda server uses udp port 993 as the src. so the 
first part of the amanda network conversation goes like this:

server port 993 -> client port 10080 hi
server port 993 <- client port 10080 hi back
server port 993 -> client port 10080 sendsize
server port 993 -> client port 10080 ack sendsize
Is this correct? does amanda always use port 993 as the source port?

I hypothesize that my dumps are only finishing sometimes because port 
993 is blocked by default. port 993 works work only a few minutes until 
the "allow related" rule timesout.

Jason Edgecombe

Re: How could amflush NOT flush ? :o)

[Kurt Yoder]

Nicolas Ecarnot said:
> Hi,
>
> My Amanda setup keeps improving tests after tests and I still have
> so many questions.
> Today is : How could I do to make automatic flushes (autoflush) but
> without deleting the holding disk directories ?
>
> What I'd like to have is this situation :
> - cron launches amdump
> - the autoflush option is set, so as to write datas on the holding
> disk AND to tape
> - but to keep the last holding disk directory
> - Another cron would remove the (n-1) last hoslding disk directory
>
> That way, I could restore the previous-day files directly from the
> holding disk files, without having to go search my tapes.

Just an idea for you: use rsync to make on-line backups of all your
amanda disks. This is what I do. That way, there's no tweaking of
amanda necessary (though rsync must be set up). Restoring files from
your on-line backups is then as simple as using "scp", "ftp", or
whatever you want.

-- 
Kurt Yoder
Sport & Health network administrator

Re: strange "disk offline" error

[Marc Mengel]

Kurt Yoder wrote:

Weird errors here. The root user is definitely in the passwd file.
Could this be part of the problem?
Thanks for any ideas on fixing this...
Maybe a silly question, but, can your amanda backup user read the passwd file
on that system?
Marc

Re: strange "disk offline" error

[Kurt Yoder]

More information about this problem:

Looking more closely in /tmp/amanda/sendsize...debug, I see
something strange:

sendsize[7578]: time 0.020: calculating for amname '/', dirname '/',
spindle -1
sendsize[7578]: time 0.020: getting size via dump for / level 0
sendsize[7578]: time 0.020: calculating for device '/' with ''
sendsize[7578]: time 0.022: running "/bin/dump 0Esf 1048576 - /"
sendsize[7578]: time 0.023: running /usr/local/libexec/killpgrp
sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v]
-h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s)
...
sendsize[7578]: time 0.138: .
sendsize[7578]: estimate time for / level 0: 0.116
sendsize[7578]: no size line match in /bin/dump output for "/"
sendsize[7578]: .
sendsize[7578]: estimate size for / level 0: -1 KB
sendsize[7578]: time 0.138: asking killpgrp to terminate
sendsize[7578]: time 1.149: done with amname '/', dirname '/',
spindle -1

Notice line 6 "Usage: " message. Perhaps dump is not acting the way
amanda expects? Is this my problem? I had trouble getting gnu tar to
compile, but maybe I should try again so I can use it instead of
dump.

-- 
Kurt Yoder
Sport & Health network administrator

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Niall O Broin]

On Wednesday 23 July 2003 15:36, Nicolas Ecarnot wrote:

> The doc (under FreeBSD 5.1) also says that the hard links can't be used for
> directories, but only for files. I tested it, and indeed, I'm stuck.
>
> A little search on google explained me that the filesystem limits that
> because every file needs to now who is its father (directory), and has to
> have only one father. This seems related to some inability to detect the
> recursivity in some cases (... foggy, ain't it ? :o)
>
> Well, so I'm stuck here with my problem... too bad...

A little thinking here would help - in your script which runs amanda, all you 
have to do is hardlink every file in the last holding directory to a 
similarly named file in another directory and you're done. But I'm not sure 
what that gets you TBH, apart from a set of files. Because amanda has now 
flushed those files, she won't look in the holding disk when asked to 
recover. Two options there :

1) Recover from those backups manually

2) Also before the daily run, copy (not link) the index files (and possibly 
some more stuff) elsewhere. After the daily run, rename this other directory 
to the name of the just flushed holding directory.Then, if you need to 
recover from the holding disk, you just put the (1 amanda run old) set of 
files back in place, and amrecover, working from the old files, happily 
retrieves from the holding disk.

Option 2) sounds messy, but once it's scripted, it'd be smooth.

-- 
Niall

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Paul Bijnens]

Paul Bijnens wrote:

   #!/bin/sh
   cd /bigdisk/amandahold/Config1
   amdump Config1
   cd /bigdisk/amandahold/Config1
   find . | cpio -pl /bigdisk/amandahold/Config2
Better add a -d option to cpio like:
   ... cpio -pdl ...
so that is does automatically create the directory named after the
date.

   amflush Config2

(Untested program, just invented here.)
Still untested program :-)



--
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  *
***

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Paul Bijnens]

Nicolas Ecarnot wrote:

Selon Paul Bijnens <[EMAIL PROTECTED]>:

Nicolas Ecarnot wrote:

I first thought about a script that would launch amdump without the
option autoflush, then copy the last created directory, then launch
amflush. But that copy is way too large for my not-so-small 120Go
holding disk.
Instead of a copy, make hard links to the original files.
...
The doc (under FreeBSD 5.1) also says that the hard links can't be used for
directories, but only for files. I tested it, and indeed, I'm stuck.
 
Well, so I'm stuck here with my problem... too bad...
No, it still works.  Just create the directories (they don't take
megabytes, and hardlink the files in them).  But actually, in
the holdingdisk, all files are on the same level, so there are
no directories to link to.
Setup:

You have two configs; Config1 "reserve 100" and a bogus
"tapedev /no/such/tape" and holdingdisk set to
"/bigdisk/amandahold/Config1/".
The other, Config2, "tapedev /dev/nst0" (or whatever is the
real tapedev) and holdingdisk "/bigdisk/amandahold/Config2".
The disklist is shared (use a hard link :-) ).
We make the dumps with Config1, and they stay in the holdingdisk
because your tapedev is bogus.
Then we populate the other holdingdisk with links to this one,
using "cpio --link" as program to create the symlinks:
   #!/bin/sh
   cd /bigdisk/amandahold/Config1
   amdump Config1
   cd /bigdisk/amandahold/Config1
   find . | cpio -pl /bigdisk/amandahold/Config2
   amflush Config2
(Untested program, just invented here.)

--
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  *
***

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Jon LaBadie]

On Wed, Jul 23, 2003 at 04:36:31PM +0200, Nicolas Ecarnot wrote:
> Selon Paul Bijnens <[EMAIL PROTECTED]>:
> 
> > Nicolas Ecarnot wrote:
> > 
> > > I first thought about a script that would launch amdump without the
> > > option autoflush, then copy the last created directory, then launch
> > > amflush. But that copy is way too large for my not-so-small 120Go
> > > holding disk.
> > 
> > Instead of a copy, make hard links to the original files.
> 
> I'm confuse to see that I never took the time to read the hard link related
> part of the 'man ln'. So, though I often use symlinks, I've never used hard
> links.
> So I read the doc, and made some tests : This a just great and simple.
> According to what I understand, any file in a unix filesystem is accessed

# obviously excellent understanding of what you read deleted

> The doc (under FreeBSD 5.1) also says that the hard links can't be used for
> directories, but only for files. I tested it, and indeed, I'm stuck.

That is generally correct.  At least on Solaris, the SA has access to
a second linking command (/usr/sbin/link) which does allow creation of
hard links to directories.  This is safe to do IF the two links are
in the same directory (same parent dir).  For example, you might want
both a "tmp" and a "temp" directory name, but want them to be the same dir.
Or unix uses "tmp" and some windows application insists on upper case TMP.

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

Re: How could amflush NOT flush ? :o)

[Jon LaBadie]

On Wed, Jul 23, 2003 at 03:53:13PM +0200, Nicolas Ecarnot wrote:
> Hi,
> 
> My Amanda setup keeps improving tests after tests and I still have so many questions.
> Today is : How could I do to make automatic flushes (autoflush) but without deleting 
> the holding disk directories ?
> 
> What I'd like to have is this situation :
> - cron launches amdump
> - the autoflush option is set, so as to write datas on the holding disk AND to tape
> - but to keep the last holding disk directory
> - Another cron would remove the (n-1) last hoslding disk directory
> 
> That way, I could restore the previous-day files directly from the holding disk 
> files, without having to go search my tapes. 
> 
> I first thought about a script that would launch amdump without the option 
> autoflush, then copy the last created directory, then launch amflush.
> But that copy is way too large for my not-so-small 120Go holding disk.
> 
> Have you any idea ?


Use links instead of copies.  You would have to keep looking for new
files and directories and as they appear, make a link to them.  The
reason this would work is that when amdump removes its file, the
second link to the data would remain and thus the data not removed.

You also would not want to link to them until they are renamed without
the ".tmp" extension.

Here is a possible script, totally untested and using my paths.

HoldDir=/u/dumps
AmandaDir=${HoldDir}/amanda
AmandaDupDir=${HoldDir}/amanda-dup
IntervalTime=60

# if you want the new directories to have specific permissions
# you may have to put in a umask setting, something like:
# "umask 077" to make the dirs "drwx--"

# Get to top of Amanda Tree
cd ${AmandaDir} || { # error processing if can't cd to holding dir
# any notices, or mail, or ... you want
# but we can't go on
exit 1
}

while true  # endless loop
do
find . -type f |# locate all ordinary files
grep -v '.tmp$' |   # eliminate the tmp files
while read Dfile
do
# check if link already made
# I'd prefer the -e option of new shells, but ...
if [ -f ${AmandaDupDir}/${Dfile} ]
then
continue# nothing to do
fi

# split name into dir and file parts
Ddir=`dirname ${Dfile} | sed 's,^\./,,'`
Dname=`basename ${Dfile}`
LinkDir=${AmandaDupDir}/${Ddir}
LinkFile=${LinkDir}/${Dname}

# make LinkDir if needed
[ -d ${LinkDir} ] || mkdir ${LinkDir}
# should do error processing, but I'm lazy

# link to dump file
ln ${Dfile} ${LinkFile}
# ditto error processing
done

# sleep for a bit before doing all this again
sleep ${IntervalTime}
done



Hope you find this interesting/useful/???

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

Re: How could amflush NOT flush ? :o) [OFF TOPIC]

[Nicolas Ecarnot]

Selon Paul Bijnens <[EMAIL PROTECTED]>:

> Nicolas Ecarnot wrote:
> 
> > I first thought about a script that would launch amdump without the
> > option autoflush, then copy the last created directory, then launch
> > amflush. But that copy is way too large for my not-so-small 120Go
> > holding disk.
> 
> Instead of a copy, make hard links to the original files.

I'm confuse to see that I never took the time to read the hard link related
part of the 'man ln'. So, though I often use symlinks, I've never used hard
links.
So I read the doc, and made some tests : This a just great and simple.
According to what I understand, any file in a unix filesystem is accessed
via its inode number, and not its name. That's why one can use as many names
we want for the same inode.

The doc (under FreeBSD 5.1) also says that the hard links can't be used for
directories, but only for files. I tested it, and indeed, I'm stuck.

A little search on google explained me that the filesystem limits that
because every file needs to now who is its father (directory), and has to
have only one father. This seems related to some inability to detect the
recursivity in some cases (... foggy, ain't it ? :o)

Well, so I'm stuck here with my problem... too bad...

Too bad because your idea whas simple, so great !

-- 
Nicolas Ecarnot

Re: How could amflush NOT flush ? :o)

[Paul Bijnens]

Nicolas Ecarnot wrote:

I first thought about a script that would launch amdump without the
option autoflush, then copy the last created directory, then launch
amflush. But that copy is way too large for my not-so-small 120Go
holding disk.
Instead of a copy, make hard links to the original files.

--
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  *
***

How could amflush NOT flush ? :o)

[Nicolas Ecarnot]

Hi,

My Amanda setup keeps improving tests after tests and I still have so many questions.
Today is : How could I do to make automatic flushes (autoflush) but without deleting 
the holding disk directories ?

What I'd like to have is this situation :
- cron launches amdump
- the autoflush option is set, so as to write datas on the holding disk AND to tape
- but to keep the last holding disk directory
- Another cron would remove the (n-1) last hoslding disk directory

That way, I could restore the previous-day files directly from the holding disk files, 
without having to go search my tapes. 

I first thought about a script that would launch amdump without the option autoflush, 
then copy the last created directory, then launch amflush.
But that copy is way too large for my not-so-small 120Go holding disk.

Have you any idea ?

-- 
Nicolas Ecarnot

Re: Backup History question

[Jon LaBadie]

On Wed, Jul 23, 2003 at 08:08:25AM +0100, Niall O Broin wrote:
> On Wednesday 23 July 2003 04:18, Jon LaBadie wrote:
> 
> > > How can I easily and quickly get a list of the last n backup tapes which
> > > were used?  I need to be able to identify the tapes for rotation to an
> > > offsite storage facility.
> >
> > tail -'n' tapelist  ?
> 
> No - that gets you the OLDEST n tapes.  head -n tapelist  will get you the n 
> most recently used tapes.

Whoops, right you are.

Similar comments should be made about my other post on this subject.

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

amrecover remotely: TCP/IP connection stalls

[Andreas Ntaflos]

Hello list(s),

  First of all, sorry for crossposting but I think this is both a
  question for -users as well as -hackers. I hope I get some response
  since I've been through the archives so thoroughly I get a headache
  only from thinking of them...

  This is the setup of Amanda in our case:

  The amanda backup server is called `backup' and is connected to the
  backup client called `mobilkom' via a 100Mbit/s crossover cable.
  
  Both hosts run the services needed for backup operations (amindex,
  amidxtape, amandad, etc, etc). We have set the server up for tapeless 
  operation, using a `small' 600GB IDE disk array instead of tapes. Dumping 
  works really well, both with dump and with tar. The `tapes' get cycled
  through the chg-multi script and all is well.

  Both hosts run Amanda 2.4.4p1 and both on RedHat Linux 8.0 with kernel
  version 2.4.18. 

  But a backup is worth nothing without the ability to restore it, hm?

  Here begins the problem:

  Using amrecover from `mobilkom' to access the index/catalogue on the
  backup server (`backup') works fine, we can select and add files for
  extraction and recovery. But once the point is reached to actually
  extract the files from backup back to mobilkom the connection stalls
  and eventually dies out after hours.

  Here's what we do:

  mobilkom% amrecover -C normal -s backup -t backup

  AMRECOVER Version 2.4.4p1. Contacting server on backup ...
  220 backup AMANDA index server (2.4.4p1) ready.
  200 Access OK
  Setting restore date to today (2003-07-23)
  200 Working date set to 2003-07-23.
  200 Config set to normal.
  200 Dump host set to mobilkom.
  Trying disk /d ...
  Trying disk md0 ...
  $CWD '/d' is on disk 'md0' mounted at '/d'.
  200 Disk set to md0.
  /d
  amrecover> ls
  2003-07-3 testdir1/
  amrecover> add testdir1
  Added dir /testdir1 at date 2003-07-2
  amrecover> extract
  
  Extracting files using tape drive file:/dump/normal03 on host backup.
  The following tapes are needed: normal03

  Restoring files into directory /d
  Continue [?/Y/n]? y

  Extracting files using tape drive file:/dump/normal03 on host backup.
  Load tape normal03 now
  Continue [?/Y/n/s/t]? y

  [here we wait for hours]
---  
  
  And here it sits forever until it dies. tcpdump shows that backup
  tries to reach mobilkom and awaits ACK but gets nothing and only
  retransmits the request packets. mobilkom eventually ACKs something,
  but definately nothing concerning the ongoing connection. I will attach
  the log output of tcpdump, starting at the moment amrecover started on
  mobilkom.

  The point is that we need amrecover working, or else the system would
  never be able to restore 300GB worth of user data in the event of any
  kind of emergancy, since extracting the files on backup itself and
  then transferring them to mobilkom is not an option.

  Can somebody give us any input? This does not seem to be a frequently
  encountered problem, or my archive-searching abilities and google have
  died, which is not the case (hopefully).

  Any help is greatly appreciated. Really.

Thanks in advance!  

PS: I think this problem is related to the one discussed in this message
(from the NetBSD-current mailing list though):
http://mail-index.netbsd.org/current-users/2002/07/08/0002.html

He there has the problem that the TCP connection times out via the
lookback interface while it works when doing amrecover remotely. Our
problem here goes vice versa.

PPS: If any other logfiles are needed just tell me and I'll attach them,
we have lots of them here (amidxtaped.timestamp.debug, etc).
-- 
Andreas "ant" Ntaflos | "A cynic is a man who knows the price of
[EMAIL PROTECTED]   | everything, and the value of nothing."
Vienna, AUSTRIA   |  Oscar Wilde
12:47:17.218808 mobilkom.641 > 192.168.0.2.amandaidx: S 3610466566:3610466566(0) win 
5840  (DF)
12:47:17.219303 192.168.0.2.amandaidx > mobilkom.641: S 865495684:865495684(0) ack 
3610466567 win 5792  (DF)
12:47:17.219422 mobilkom.641 > 192.168.0.2.amandaidx: . ack 1 win 5840 
 (DF)
12:47:17.228024 192.168.0.2.amandaidx > mobilkom.641: P 1:50(49) ack 1 win 5792 
 (DF)
12:47:17.228149 mobilkom.641 > 192.168.0.2.amandaidx: . ack 50 win 5840 
 (DF)
12:47:17.228438 mobilkom.641 > 192.168.0.2.amandaidx: P 1:19(18) ack 50 win 5840 
 (DF)
12:47:17.228596 192.168.0.2.amandaidx > mobilkom.641: . ack 19 win 5792 
 (DF)
12:47:17.228685 mobilkom.641 > 192.168.0.2.amandaidx: P 19:21(2) ack 50 win 5840 
 (DF)
12:47:17.228717 192.168.0.2.amandaidx > mobilkom.641: . ack 21 win 5792 
 (DF)
12:47:17.229742 192.168.0.2.amandaidx > mobilkom.641: P 50:65(15) ack 21 win 5792 
 (DF)
12:47:17.230021 mobilkom.641 > 192.168.0.2.amandaidx: P 21:44(23) ack 65 win 5840 
 (DF)
12:47:17.268265 192.168.0.2.amandaidx > mobilkom.641: . ack 44 win 5792 
 (DF)
12:47:17.268406 mobilkom.641 > 192.168.0.2.amandaidx: P 44:46(2) ack 65 win 5840 
 (DF)
12:47:17.268461 1

Q: amanda, samba and winpc

[Raúl Wild-Spain]

Hi,

I've decided to add a winpc into my backup planning. I've followed the doc 
amanda-common/doc/SAMBA.gz from my Debian. 

Thus, into my disklists appears

xaloc//garbi/H$comp-user-tar  -> the amanda server xaloc must to connect 
through Samba to //garbi/H$

and into my /etc/amandapass

//garbi/H$login%passwordSTQ

I've tried to connect with smblient from xaloc to garbi (into another workgroup, STQ) 
and it worked ok. Amcheck said nothing strange...

but today, when I arrived, amanda had still not reported any information (by mail, as 
a result of latest backup), and forcing with amreport  this is the result:

*** THE DUMPS DID NOT FINISH PROPERLY!

The next tape Amanda expects to use is: FURV-POLICY04.

FAILURE AND STRANGE DUMP SUMMARY:
  xaloc  /dev/sdc2 RESULTS MISSING
  xaloc  /dev/sdc1 RESULTS MISSING
  xaloc  /etc RESULTS MISSING
  xaloc  /dev/sdd1 RESULTS MISSING
  kannagara  /etc RESULTS MISSING
  xaloc  //garbi/H$ RESULTS MISSING


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00   0:00   0:00
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- --

Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0
Avg Tp Write Rate (k/s) -- -- --

.
DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
kannagara/etc  MISSING --
xaloc//garbi/H$MISSING --
xaloc/dev/sdc1 MISSING --
xaloc/dev/sdc2 MISSING --
xaloc/dev/sdd1 MISSING --
xaloc/etc  MISSING --

(brought to you by Amanda version 2.4.2p2)


what's happening??, I don't understand why amanda have troubles and reply with 
"RESULTS MISSING". 

I need help!!!

Best Regards,

Raúl Cruz
[EMAIL PROTECTED]

Re: Backup History question

[Niall O Broin]

On Wednesday 23 July 2003 04:18, Jon LaBadie wrote:

> > How can I easily and quickly get a list of the last n backup tapes which
> > were used?  I need to be able to identify the tapes for rotation to an
> > offsite storage facility.
>
>   tail -'n' tapelist  ?

No - that gets you the OLDEST n tapes.  head -n tapelist  will get you the n 
most recently used tapes.


-- 
Niall