From: John H. <jj...@gm...> - 2010-01-29 16:10:38
|
I am trying to configure backuppc to back up a windows machine (XP) over a small LAN and am having quite a bit of difficulty. When I run the backup, Backuppc says it cant find the client. (My firewalls are removed, my Netgear router is functioning using DHCP, and has statically mapped the IP address of both the linux machine and XP machine) In the debian machine I can ping the XP machine, and visa versa. Backuppc is running under Debian 5, and the latest stable version of Samba. I am attempting to use "SMB" protocol to talk to the XP machine. I do not want to use rsync, (so please don't try and send me off in that direction.) I suspect that my problem relates to the config of Samba and that documentation in Backuppc makes an undocumented assumption of how Samba is configured. I would very much like: 1) some clarification of both backuppc settings and Samba setting from someone who has backuppc backing up xp clients over a small LAN. e.g. show me relevant sections of your config and .pl files. 2) a pointer to a Samba-xp how to....where Samba is NOT a domain controller 3) a clarification to: When using backuppc and SMB, is the assumption that Samba is acting/configured as a domain controller or not? For backuppc to work, what is the easiest way to configure Samba (not as a domain controller?) Thanks very much for your help John |
From: <koe...@ko...> - 2010-01-29 16:28:33
|
> 1) some clarification of both backuppc settings and Samba setting from > someone who has backuppc backing up xp clients over a small LAN. e.g. > show > me relevant sections of your config and .pl files. First: backuppc wiki :http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Tips_and_Tricks I don't use it anymore but this is what i remember: The user you fill in in the config.pl e.g. user: backupuser passw: password You add that user to every PC to the administrator group (and backup operators?) > 2) a pointer to a Samba-xp how to....where Samba is NOT a domain > controller When your clients are statically mapped, use that as client name. Then you don't need nmblookup to find the clients and don't need a WINS server for netbios name lookups > > 3) a clarification to: When using backuppc and SMB, is the assumption that > Samba is acting/configured as a domain controller or not? For backuppc to > work, what is the easiest way to configure Samba (not as a domain > controller?) backuppc and smb just have to do with how you access the clients. It has nothing to do with DC's etc. You only need the package installed to have the smbclient program +- I'm not at work so I can't check info from the backup servers. I hope this helps a bit. Koen Linders |
From: John H. <jj...@gm...> - 2010-01-29 19:48:42
|
thank you Koen! some clarification questions below: On Fri, Jan 29, 2010 at 11:28 AM, <koe...@ko...> wrote: > > 1) some clarification of both backuppc settings and Samba setting from > > someone who has backuppc backing up xp clients over a small LAN. e.g. > > show > > me relevant sections of your config and .pl files. > > First: backuppc wiki > : > http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Tips_and_Tricks > > I don't use it anymore but this is what i remember: > The user you fill in in the config.pl e.g. user: backupuser passw: > password > You add that user to every PC to the administrator group (and backup > operators?) > Assume I have 3 xp machines, each machine has one user, with admin privilidges, and a password. Are you saying that in my config.pl, I need to add, for every machine I want to back up, the user name and password? What do I do if the machine I want to back up, has only one user with no password but admin privlidges? > > > > 2) a pointer to a Samba-xp how to....where Samba is NOT a domain > > controller > > > When your clients are statically mapped, use that as client name. > .....use *that* as client name".....What is *that* referring to? the clients IP address (xx.xx.xx.xx)? The client PCs 'name'? > Then you don't need nmblookup to find the clients and don't need a WINS > server for netbios name lookups > > > > > 3) a clarification to: When using backuppc and SMB, is the assumption > that > > Samba is acting/configured as a domain controller or not? For backuppc to > > work, what is the easiest way to configure Samba (not as a domain > > controller?) > > backuppc and smb just have to do with how you access the clients. It has > nothing to do with DC's etc. You only need the package installed to have > the smbclient program +- > So you are saying that I do not need to configure SMB as a domain controller...? > > I'm not at work so I can't check info from the backup servers. > I hope this helps a bit. > > Koen Linders > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |
From: Les M. <les...@gm...> - 2010-01-29 20:36:54
|
On 1/29/2010 1:48 PM, John Hudak wrote: > > First: backuppc wiki > :http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Tips_and_Tricks > > I don't use it anymore but this is what i remember: > The user you fill in in the config.pl <http://config.pl> e.g. user: > backupuser passw: password > You add that user to every PC to the administrator group (and backup > operators?) > > Assume I have 3 xp machines, each machine has one user, with admin > privilidges, and a password. Are you saying that in my config.pl > <http://config.pl>, I need to add, for every machine I want to back up, > the user name and password? You can do that in the web interface in the 'edit config' link for each host. > What do I do if the machine I want to back up, has only one user with no > password but admin privlidges? Your other option - and probably what most people do - is to add a backup user on each machine (if they aren't in a domain who is in the administrator and backup user groups so the login/password stays the same. > When your clients are statically mapped, use that as client name. > > .....use *that* as client name".....What is *that* referring to? the > clients IP address (xx.xx.xx.xx)? The client PCs 'name'? The cleanest way to do this is to have local dns with entries for each name. That way normal (not just windows/netbios) network connections will work with the names. Next best for a small set is to put them in the hosts files. > backuppc and smb just have to do with how you access the clients. It has > nothing to do with DC's etc. You only need the package installed to have > the smbclient program +- > > So you are saying that I do not need to configure SMB as a domain > controller...? No, if you have local passwords on each machine you don't need any domain controller. -- Les Mikesell les...@gm... |
From: John H. <jj...@gm...> - 2010-01-29 20:46:08
|
thank you...where do I put" my local dns entries"? -John On Fri, Jan 29, 2010 at 3:36 PM, Les Mikesell <les...@gm...> wrote: > On 1/29/2010 1:48 PM, John Hudak wrote: > > > > First: backuppc wiki > > : > http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Tips_and_Tricks > > > > I don't use it anymore but this is what i remember: > > The user you fill in in the config.pl <http://config.pl> e.g. user: > > backupuser passw: password > > You add that user to every PC to the administrator group (and backup > > operators?) > > > > Assume I have 3 xp machines, each machine has one user, with admin > > privilidges, and a password. Are you saying that in my config.pl > > <http://config.pl>, I need to add, for every machine I want to back up, > > the user name and password? > > You can do that in the web interface in the 'edit config' link for each > host. > > > What do I do if the machine I want to back up, has only one user with no > > password but admin privlidges? > > Your other option - and probably what most people do - is to add a > backup user on each machine (if they aren't in a domain who is in the > administrator and backup user groups so the login/password stays the same. > > > When your clients are statically mapped, use that as client name. > > > > .....use *that* as client name".....What is *that* referring to? the > > clients IP address (xx.xx.xx.xx)? The client PCs 'name'? > > The cleanest way to do this is to have local dns with entries for each > name. That way normal (not just windows/netbios) network connections > will work with the names. Next best for a small set is to put them in > the hosts files. > > > backuppc and smb just have to do with how you access the clients. It > has > > nothing to do with DC's etc. You only need the package installed to > have > > the smbclient program +- > > > > So you are saying that I do not need to configure SMB as a domain > > controller...? > > No, if you have local passwords on each machine you don't need any > domain controller. > > -- > Les Mikesell > les...@gm... > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |
From: Les M. <les...@gm...> - 2010-01-29 21:15:23
|
On 1/29/2010 2:45 PM, John Hudak wrote: > thank you...where do I put" my local dns entries"? In your local DNS server. Some routers offer the facility, or you can run bind on the server running backuppc. You can make up a domain name that isn't registered and it will work for machines that use it as their DNS server (but not the general public). -- Les Mikesell les...@gm... |
From: Les M. <les...@gm...> - 2010-01-29 16:48:11
|
On 1/29/2010 10:10 AM, John Hudak wrote: > I am trying to configure backuppc to back up a windows machine (XP) over > a small LAN and am having quite a bit of difficulty. When I run the > backup, Backuppc says it cant find the client. (My firewalls are > removed, my Netgear router is functioning using DHCP, and has statically > mapped the IP address of both the linux machine and XP machine) In the > debian machine I can ping the XP machine, and visa versa. > > Backuppc is running under Debian 5, and the latest stable version of > Samba. I am attempting to use "SMB" protocol to talk to the XP > machine. I do not want to use rsync, (so please don't try and send me > off in that direction.) > I suspect that my problem relates to the config of Samba and that > documentation in Backuppc makes an undocumented assumption of how Samba > is configured. > I would very much like: > 1) some clarification of both backuppc settings and Samba setting from > someone who has backuppc backing up xp clients over a small LAN. e.g. > show me relevant sections of your config and .pl files. > > 2) a pointer to a Samba-xp how to....where Samba is NOT a domain controller > > 3) a clarification to: When using backuppc and SMB, is the assumption > that Samba is acting/configured as a domain controller or not? For > backuppc to work, what is the easiest way to configure Samba (not as a > domain controller?) I can't help very much with this, but you should be able to debug your samba setup by trying to connect manually with smbclient. One thing that might not be obvious is that your /etc/samba/smb.conf file is used for some settings. If you've changed things like workgroup or password server there for server side settings that shouldn't apply to client connections you might need to add a -s/path/to/different/smb.conf to the SmbClient*Cmd settings. -- Les Mikesell les...@gm... |
From: John H. <jj...@gm...> - 2010-01-29 19:38:27
|
Hi Les: thanks for the reply...like I said in the my post, the Samba install is 'right out of the box'..i did not change anything in the smb.config file, except what was documented in the backuppc doc (as best I understood it). I agree 100% with your conjecture that it is some setting in the smb config file, but what? My premise is this: something in the smb.config file is *different* than what the backuppc configuration discusses, which is causing the communicaition problem, but what is it? I guess that is why I am looking for something a bit more comprehensive on the samba server setup discussion. John On Fri, Jan 29, 2010 at 11:48 AM, Les Mikesell <les...@gm...>wrote: > On 1/29/2010 10:10 AM, John Hudak wrote: > > I am trying to configure backuppc to back up a windows machine (XP) over > > a small LAN and am having quite a bit of difficulty. When I run the > > backup, Backuppc says it cant find the client. (My firewalls are > > removed, my Netgear router is functioning using DHCP, and has statically > > mapped the IP address of both the linux machine and XP machine) In the > > debian machine I can ping the XP machine, and visa versa. > > > > Backuppc is running under Debian 5, and the latest stable version of > > Samba. I am attempting to use "SMB" protocol to talk to the XP > > machine. I do not want to use rsync, (so please don't try and send me > > off in that direction.) > > I suspect that my problem relates to the config of Samba and that > > documentation in Backuppc makes an undocumented assumption of how Samba > > is configured. > > I would very much like: > > 1) some clarification of both backuppc settings and Samba setting from > > someone who has backuppc backing up xp clients over a small LAN. e.g. > > show me relevant sections of your config and .pl files. > > > > 2) a pointer to a Samba-xp how to....where Samba is NOT a domain > controller > > > > 3) a clarification to: When using backuppc and SMB, is the assumption > > that Samba is acting/configured as a domain controller or not? For > > backuppc to work, what is the easiest way to configure Samba (not as a > > domain controller?) > > I can't help very much with this, but you should be able to debug your > samba setup by trying to connect manually with smbclient. One thing > that might not be obvious is that your /etc/samba/smb.conf file is used > for some settings. If you've changed things like workgroup or password > server there for server side settings that shouldn't apply to client > connections you might need to add a -s/path/to/different/smb.conf to the > SmbClient*Cmd settings. > > -- > Les Mikesell > les...@gm... > > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |
From: Les M. <les...@gm...> - 2010-01-29 19:56:26
|
On 1/29/2010 1:38 PM, John Hudak wrote: > Hi Les: > thanks for the reply...like I said in the my post, the Samba install is > 'right out of the box'..i did not change anything in the smb.config > file, except what was documented in the backuppc doc (as best I > understood it). > I agree 100% with your conjecture that it is some setting in the smb > config file, but what? > My premise is this: something in the smb.config file is *different* than > what the backuppc configuration discusses, which is causing the > communicaition problem, but what is it? > I guess that is why I am looking for something a bit more comprehensive > on the samba server setup discussion. Have you tried using smbclient manually to connect to the share? You may be able to get better error messages there. Most of smb.conf relates to server settings but a few, like workgroup and password server would affect client connections. -- Les Mikesell les...@gm... |
From: John H. <jj...@gm...> - 2010-01-29 20:26:42
|
As I reviewed the 200+ pages of the smb documentation, it occured to me to try that....If I figure out how to do it, i will Thanks for the suggestion John On Fri, Jan 29, 2010 at 2:56 PM, Les Mikesell <les...@gm...> wrote: > On 1/29/2010 1:38 PM, John Hudak wrote: > > Hi Les: > > thanks for the reply...like I said in the my post, the Samba install is > > 'right out of the box'..i did not change anything in the smb.config > > file, except what was documented in the backuppc doc (as best I > > understood it). > > I agree 100% with your conjecture that it is some setting in the smb > > config file, but what? > > My premise is this: something in the smb.config file is *different* than > > what the backuppc configuration discusses, which is causing the > > communicaition problem, but what is it? > > I guess that is why I am looking for something a bit more comprehensive > > on the samba server setup discussion. > > Have you tried using smbclient manually to connect to the share? You > may be able to get better error messages there. Most of smb.conf > relates to server settings but a few, like workgroup and password server > would affect client connections. > > -- > Les Mikesell > les...@gm... > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |
From: Les M. <les...@gm...> - 2010-01-29 20:50:05
|
On 1/29/2010 2:26 PM, John Hudak wrote: > As I reviewed the 200+ pages of the smb documentation, it occured to me > to try that....If I figure out how to do it, i will > > Thanks for the suggestion Most of the docs relate to server options that you don't need to know about. 'man smbclient' should be more than enough. Try: smbclient --user username //host/share and answering the password prompt. That should get you connected or tell you why not. You can then use ftp-like commands if you want, but the main point is to make the connection work. If your sharename has shell metacharacters like $, put single quotes around, like '//host/C$' -- Les Mikesell les...@gm... |