Hi,
I have problem with Win2k Server SP2 also.
My environment is:
Amanda 2.4.2p2 server running on Solaris 8
Samba 2.2.2 running on same Solaris 8 box
Win2k Server version SP2 (Japanese)
GNU tar 1.3.23(?)
I can see the amdump pulling file names from the Win2k machine
by monitor the network packet. I think after it got all
file list from the PC, it stops there. The CPU and network
becomes idle. Using Ctrl-C can stop it.
There is no any error message in the dump or log file.
I can use the amanda to backup the Solaris local disk partition
without any problem. And I can use smbclient to connect to the
Win2K server and retrieve file. (I don't know how to combine
smbclient with gnutar manually, so I didn't try it.)
Does anyone have an idea that I can try ?
Thank you very much in advance,
Shu Liu
On Mon, 3 Dec 2001, Amanda Admin wrote:
> Christophe,
>
> I use the samba package extensively (2.2.1a), though not for backup with
> amanda (yet) as you are trying.
>
> I tried a simple tar test using smbclient and had no problems. I connected
> to the client (my laptop, Win2k SP2, NTFS) from my amanda server (RH 7.1) as
> both myself and as my amanda user (member of the local Backup Operators
> group). Tarred up about 800K worth of files no problem. Then tested a bigger
> set of files (116 files, 46 directories, 550MB) also with no problems.
>
> Suspecting it might be disk space issue, I even tried this last test in a
> directory with not enough disk space to hold the resulting tar file. It
> failed as expected, but never froze.
>
> Try running your smbclient tests with a debug level of 3 and a log file
> (smbclient -l log -d 3) and see what the log says if/when the freeze occurs.
> Increasing the log level (up to 10) will give you incredible amounts of
> information (every function entry I believe).
>
> Also, check the Event Log on the client. Does the freezing only occur with
> one client or do other 2000 clients behave similarly? If not every client
> behaves the same, check permissions and/or service packs.
>
> I suspect the freeze occurs because the file may be in use. Or, if the tar
> is running for some time, perhaps a network problem.
>
> I searched the samba lists I'm a member of ([EMAIL PROTECTED],
> [EMAIL PROTECTED]) and didn't see any posts from yourself.
> You may try posting there also, check samba.org for the appropriate list
> (samba-users?).
>
> HTH,
> Doug
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Christophe Condomines
> > Sent: Thursday, November 29, 2001 7:09 AM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Problem with windows 2000 Professional
> >
> >
> > Hi,
> >
> > I am testing Amanda for my backup solution.
> > I use Amanda 2.2.4p2 on a Linux Red Hat 7.1 and
> > without any tape for the test.
> > The backup works fine on linux.
> >
> > I use samba 2.2.2 for the windows clients :
> > that works with NT and 98, but on windows 2000, the
> > amdump starts and
> > finally freeze.
> > I have checked the use of smbclient and a command
> > like tar c test.tar
> > produces the same freeze : smbclient starts to
> > retrieve some files and
> > finally stop. It's not always on the same file, it's
> > not always the same size, ...
> > Any suggestion ?
> >
> > I also try the amanda win32 client, failed on win95,
> > works on win2k
> > but very slowly.
> > Any comments ?
> >
> >
> > =====
> > Christophe Condomines
> > [EMAIL PROTECTED]
> >
> > ___________________________________________________________
> > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> > Yahoo! Courrier : http://courrier.yahoo.fr
> >
>
>
