RE: [BackupPC-users] RE: WIndows SMB problems

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Actually I had the same problem with this host using smbclient manually,
so I have isolated it to smbclient.  Near as I can tell, it is just some
locked files causing the smbclient to time out.  When I exclude those
files (for example \\winnt\repair) everything is fine. Some of the
windoze clients give errors on those same locked files, but the backup
does not fail. I don't no why it started to fail on this host, but it is
working now with the excludes, any ideas?

Next problem I encountered, was excluding multiple dirs and files was
not working properly with smb, it would just exclude the first one
listed, once I removed the -r for regular expression matching in the
smbclient command, it started working correctly.  Anyone care to comment
about that, am I doing something wrong?

Thanks,

David

On Wed, 2003-09-03 at 10:06, Brown, Wade (MED, ASL) wrote:
> Ok, you isolated backuppc by running samba manually.  Samba works fine
> with other winpc's so it's probably not at fault.  Does this happen
> during fulls, incrementals or both?

> 
> When you run the samba command manually, are you getting the same error
> output?  You can add the debug option to the command.  That creates a
> lot of data but it might give you a clue as to why samba dies.
> 
> How about manually executing the command again but only backup a
> restricted set of directories?  That is, start with "program files" then
> add "winnt", etc.
> 
> How about isolating the backup server and it's samba implementation?
> Can you use another Unix box to test the same version of samba?
> 
> Are the two winpc's in any way related?  Same service pack vs a
> different rev on the others?  Auto patch installs, etc.  Same/different
> subnets?  When running the samba command manually, setup a ping to the
> machine.  Does the ping fail when samba dies?  Anything in the PC event
> logs?
> 
> Check the obvious on the server, too.  Disk space ok?  Anything in the
> server logs that would indicate network or other OS problems?  You never
> know...
> 
> Good luck.
> 
> - Wade
> 
> 
> 
> 
> 
> -----Original Message-----
> From: David Cramblett [mailto:da...@ax...]
> Sent: Wednesday, September 03, 2003 11:05 AM
> To: bac...@li...
> Cc: Brown, Wade (MED, ASL)
> Subject: RE: [BackupPC-users] RE: WIndows SMB problems
> 
> 
> No it doesn't seem to be stopping in the same place. Last night it
> stopped at \WINNT\fonts\some_file and today at \WINNT\repair\some_file,
> getting buy the previous point just fine.  The other machine that I am
> having trouble with stopped at \Program Files\Common\some_file. Just now
> I ran the smb command manually from the command line and watched it, it
> got to a point and then just sat there for a minute and then stopped. 
> No error was given. I tried testing communication via ICMP and that
> seemed fine.
> 
> David
> 
> On Tue, 2003-09-02 at 12:22, Brown, Wade (MED, ASL) wrote:
> > Sounds like a timeout problem.  Do you see any evidence of a
> particular
> > file that is very large.  It may not be listed in the xfer log but the
> > file before it might be...  Do they always stop at the same point?
> > 
> > - Wade
> > 
> > 
> > 
> > -----Original Message-----
> > From: David Cramblett [mailto:da...@ax...]
> > Sent: Tuesday, September 02, 2003 1:28 PM
> > To: bac...@li...
> > Subject: [BackupPC-users] RE: WIndows SMB problems
> > 
> > 
> > I have a couple of windoze 2000 Machines that were working for about a
> > week and have since started reporting an error, "exiting after signal
> > ALRM" at the bottom of the transfer file.  There have been no changes
> > that I know of and I have two other windoze 2000 machines that have
> > continued to backup fine as well as 10 or so Unix machines that
> continue
> > to backup fine.
> > 
> > I have BackupPC version 2.0.0 and smbclient version 2.2.8a
> > 
> > I have tried excluding some of the directories that show up with
> locked
> > files in the transfer log, but this has not helped and doesn't seem to
> > cause trouble on the other windoze machines anyways. I just can't seem
> > to see anything in the logs about what is causing the failure.  
> > 
> > I will provide a host and server log to anyone interested in helping,
> > thanks,
> > 
> > David
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > BackupPC-users mailing list
> > Bac...@li...
> > https://lists.sourceforge.net/lists/listinfo/backuppc-users
> > http://backuppc.sourceforge.net/
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> BackupPC-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/