On Thu, Jul 10, 2008 at 2:14 AM, Paul Bijnens
<Paul.Bijnens AT xplanation DOT com> wrote:
> On 2008-07-10 04:45, FL wrote:
>>
>> Hi.
>> I'm using the latest AMANDA 2.6.0p1 on a Debian Linux box (I compile
>> the source--Debian packages are behind). The Linux clients work (except
>> for
>> an occasional 80 hour dump, as bad as that sounds on many levels,
>> including
>> dump levels). However, the windows client estimates time out. Not being a
>> Windologian, I implore the group for guidance. I'm using bsdtcp, not ssh.
>> My amstatus follows.
>>
>> FL
>>
>> [amandabackup@opennms Daily]$ amstatus Daily
>> Using /var/log/amanda/Daily/amdump
>> From Wed Jul 9 18:05:02 EDT 2008
>>
> [...]
>>
>> curdata.gc.cuny.edu:c: 0 10405m wait for
>> dumping
>> curdata.gc.cuny.edu:e: 0 planner: [disk "e:",
>> all estimate timed out]
>> curdata.gc.cuny.edu:e:Applications 0 planner: [disk
>> "e:Applications", all estimate timed out]
>
> So you installed cygwin on those Windows clients, and run some port
> of Amanda-clients for Cygwin on Windows, right?
> And you're using gnutar for cygwin on those windows clients?
> Which version?
I'll be able to answer these questions specifically when I have access;
for now let me say that I installed the latest zmanda windows client
using the installation package available on the zmanda download
page. This is the version: AmandaBackupClient-2-5-2p1.msi
I did not go out of my way to install cygwin or gnutar---I
understand that the zmanda windows client does this and that the zmanda
wiki advises against installing your own versions; from the
zmanda wiki: http://wiki.zmanda.com/index.php/Windows_client
"The Amanda Windows client package uses the Microsoft Windows installer
and includes Amanda client dependencies (Gnu tar, GnuZip, OpenSSH) as
part of the package.
This Windows client uses Cygwin and will install Cygwin binaries. If
you have Cygwin installed,
this package may not work."
> For at least one windows client you did get an estimate for
> at least one DLE.
>
> Is there any difference in the definition of the DLE's of one that
> works or one that does not work?
Here are the DLEs
# windows client test
curdata.gc.cuny.edu c:\ comp-root-tar
curdata.gc.cuny.edu e:\ comp-root-tar
curdata.gc.cuny.edu z:\ comp-root-tar
curdata.gc.cuny.edu e:\Applications comp-root-tar
curdata.gc.cuny.edu e:\ArcIMS comp-root-tar
The first worked; the rest didn't
> On the client, in the client debug files, (wherever those may be
> located in cygwin) do you see an error message when gnutar does
> it's estimates on the different drives?
> Or do they just take too long, and the amanda server has given
> up waiting for those numbers?
>
> --
> Paul Bijnens, xplanation Technology Services Tel +32 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
> http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
> ***********************************************************************
> * 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, *
> * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
> * ... "Are you sure?" ... YES ... Phew ... I'm out *
> ***********************************************************************
>
|
