Backup Central

Hello.

I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:

1) One gives “inet connect: Connection refused” though “telnet <IP>
873” from the very same FreeBSD server works just time. BackupPC
managed to make a successful backup of one share (of two) on this
computer once. Not sure what was different.

2) One gives “no ping”, then, after making $PingCmd for it empty,
“inet connect: Operation timed out”. telnet is successful as well
here; “nmblookup <name>” or “ping -c 1 <IP>” don't show any problems
when run from shell either.

3) The only Windows 7 box (the others are XP). Just plain “inet
connect: Operation timed out”, can't connect from any other computer
as well.

To sum up, I have two problems: BackupPC not connecting while
everybody else can, and rsyncd not working properly on Windows 7.

Any help will be strongly appreciated. The bizarre BackupPC failures
are making me question my sanity.

Sincerely,
Maxim

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Have you checked the firewalls on the affected machines? Especially Win7 can
be tricky. You might need to both allow whatever program you use to show the
rsync share name to your BPC-server as well as open the port.

I ran into something similar a little while ago.

--
/Sorin


-----Original Message-----
From: haruspex [mailto:princeps.candidus < at > gmail.com]
Sent: den 31 januari 2012 16:29
To: backuppc-users < at > lists.sourceforge.net
Subject: [BackupPC-users] Bizarre connection failures

Hello.

I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:

1) One gives "inet connect: Connection refused" though "telnet <IP>
873" from the very same FreeBSD server works just time. BackupPC
managed to make a successful backup of one share (of two) on this
computer once. Not sure what was different.

2) One gives "no ping", then, after making $PingCmd for it empty,
"inet connect: Operation timed out". telnet is successful as well
here; "nmblookup <name>" or "ping -c 1 <IP>" don't show any problems
when run from shell either.

3) The only Windows 7 box (the others are XP). Just plain "inet
connect: Operation timed out", can't connect from any other computer
as well.

To sum up, I have two problems: BackupPC not connecting while
everybody else can, and rsyncd not working properly on Windows 7.

Any help will be strongly appreciated. The bizarre BackupPC failures
are making me question my sanity.



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

On Tue, Jan 31, 2012 at 9:29 AM, haruspex <princeps.candidus < at > gmail.com> wrote:

I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:

1) One gives “inet connect: Connection refused” though “telnet <IP>
873” from the very same FreeBSD server works just time. BackupPC
managed to make a successful backup of one share (of two) on this
computer once. Not sure what was different.

2) One gives “no ping”, then, after making $PingCmd for it empty,
“inet connect: Operation timed out”. telnet is successful as well
here; “nmblookup <name>” or “ping -c 1 <IP>” don't show any problems
when run from shell either.

3) The only Windows 7 box (the others are XP). Just plain “inet
connect: Operation timed out”, can't connect from any other computer
as well.

To sum up, I have two problems: BackupPC not connecting while
everybody else can, and rsyncd not working properly on Windows 7.

Any help will be strongly appreciated. The bizarre BackupPC failures
are making me question my sanity.

Recent windows versions have a firewall on by default that needs to be
configured to allow inbound connections. One way to test basic
connectivity with rsynd is to run 'rsync target::' or 'rsync
target::module' from the backuppc server. Note the double colons that
distinguish a connection to rsyncd as opposed to running over ssh, and
that if you don't specify a destination in the command you should get
a directory listing. Not sure what to check on the one that works on
some of the shares - see if the logs show anything specific and look
for any possible network issues.

--
Les Mikesell
lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Hello.

I tried disabling the security suite altogether. No effect. Also, a
“manual” connection goes just fine, even from the computer where
BackupPC is installed, it is only BackupPC that can't connect. I'll
try showing rsync share names, but the failures seem to be earlier in
the process...

Sincerely,
Maxim

2012/1/31 Sorin Srbu <sorin.srbu < at > orgfarm.uu.se>:
Have you checked the firewalls on the affected machines? Especially Win7 can
be tricky. You might need to both allow whatever program you use to show the
rsync share name to your BPC-server as well as open the port.

I ran into something similar a little while ago.

--
/Sorin


-----Original Message-----
From: haruspex [mailto:princeps.candidus < at > gmail.com]
Sent: den 31 januari 2012 16:29
To: backuppc-users < at > lists.sourceforge.net
Subject: [BackupPC-users] Bizarre connection failures

Hello.

I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:

1) One gives "inet connect: Connection refused" though "telnet <IP>
873" from the very same FreeBSD server works just time. BackupPC
managed to make a successful backup of one share (of two) on this
computer once. Not sure what was different.

2) One gives "no ping", then, after making $PingCmd for it empty,
"inet connect: Operation timed out". telnet is successful as well
here; "nmblookup <name>" or "ping -c 1 <IP>" don't show any problems
when run from shell either.

3) The only Windows 7 box (the others are XP). Just plain "inet
connect: Operation timed out", can't connect from any other computer
as well.

To sum up, I have two problems: BackupPC not connecting while
everybody else can, and rsyncd not working properly on Windows 7.

Any help will be strongly appreciated. The bizarre BackupPC failures
are making me question my sanity.



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Hello.

“rsync target::” works just fine:
vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
docs Documents and Settings
dDrive Entire D Drive

The logs don't provide anything more specific than “Backup failed on
<HostName> (inet connect: Operation timed out)”. I guess the problem
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *”...

Sincerely,
Maxim

2012/1/31 Les Mikesell <lesmikesell < at > gmail.com>:
On Tue, Jan 31, 2012 at 9:29 AM, haruspex <princeps.candidus < at > gmail.com> wrote:

I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:

1) One gives “inet connect: Connection refused” though “telnet <IP>
873” from the very same FreeBSD server works just time. BackupPC
managed to make a successful backup of one share (of two) on this
computer once. Not sure what was different.

2) One gives “no ping”, then, after making $PingCmd for it empty,
“inet connect: Operation timed out”. telnet is successful as well
here; “nmblookup <name>” or “ping -c 1 <IP>” don't show any problems
when run from shell either.

3) The only Windows 7 box (the others are XP). Just plain “inet
connect: Operation timed out”, can't connect from any other computer
as well.

To sum up, I have two problems: BackupPC not connecting while
everybody else can, and rsyncd not working properly on Windows 7.

Any help will be strongly appreciated. The bizarre BackupPC failures
are making me question my sanity.

Recent windows versions have a firewall on by default that needs to be
configured to allow inbound connections.   One way to test basic
connectivity with rsynd is to run 'rsync target::'  or 'rsync
target::module' from the backuppc server.  Note the double colons that
distinguish a connection to rsyncd as opposed to running over ssh, and
that if you don't specify a destination in the command you should get
a directory listing.   Not sure what to check on the one that works on
some of the shares - see if the logs show anything specific and look
for any possible network issues.

--
  Les Mikesell
    lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

On Tue, Jan 31, 2012 at 9:59 AM, haruspex <princeps.candidus < at > gmail.com> wrote:

“rsync target::” works just fine:
vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
docs            Documents and Settings
dDrive          Entire D Drive

The logs don't provide anything more specific than “Backup failed on
<HostName> (inet connect: Operation timed out)”. I guess the problem
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *”...

Are you using the IP address in the backuppc config, or does it have
to do name resolution?

--
Les Mikesell
lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Hello.

Name resolution, via nmblookup. IP addresses are assigned via DHCP, so
subject to change. So you are saying that connection would have
established fine, but it tries to establish it with a wrong place?..
An interesting idea. Now, how can the result of the BackupPC name
resolution can be checked?..

Sincerely,
Maxim

2012/1/31 Les Mikesell <lesmikesell < at > gmail.com>:
On Tue, Jan 31, 2012 at 9:59 AM, haruspex <princeps.candidus < at > gmail.com> wrote:

“rsync target::” works just fine:
vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
docs            Documents and Settings
dDrive          Entire D Drive

The logs don't provide anything more specific than “Backup failed on
<HostName> (inet connect: Operation timed out)”. I guess the problem
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *”...

Are you using the IP address in the backuppc config, or does it have
to do name resolution?

--
 Les Mikesell
   lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

haruspex <princeps.candidus < at > gmail.com> wrote on 01/31/2012 10:59:12 AM:

Hello.

“rsync target::� works just fine:
vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
docs Documents and Settings
dDrive Entire D Drive

The logs don't provide anything more specific than “Backup failed on
<HostName> (inet connect: Operation timed out)�. I guess the problem
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *�...

Ah, but what you're testing and what BackupPC does are different.

In your test, you used the IP address. BackupPC uses the name of the host and tries to resolve it. Can you do:

rsync HostToTest::

(or whatever) and get a list of shares? If, so, great: it's something with BackupPC. If *not*, then it's a problem with name resolution.

From personal experience, I've found that it's infinitely easier and more reliable to simply fix the IP address of computers that will be backed up by BackupPC (either by assigning them a fixed IP or (preferred) having the DHCP server give them the same IP every time), and using /etc/hosts on the BackupPC machine (or even better: internal DNS) to resolve the name to the fixed IP.

There have been too many problems with dynamic IP's, especially with NetBIOS name resolution, for my taste. If you're going to invest time and effort into solving this problem, I would suggest putting that time into a Dynamic IP/DNS solution. (That's one of the few things I like about Active Directory...)

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

On Tue, 2012-01-31 at 20:25 +0300, haruspex wrote:
Hello.

Name resolution, via nmblookup. IP addresses are assigned via DHCP, so
subject to change. So you are saying that connection would have
established fine, but it tries to establish it with a wrong place?..
An interesting idea. Now, how can the result of the BackupPC name
resolution can be checked?..

nmblookup on the server

--
Tim Fletcher <tim < at > night-shade.org.uk>


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

On Tue, Jan 31, 2012 at 11:25 AM, haruspex <princeps.candidus < at > gmail.com> wrote:
Hello.

Name resolution, via nmblookup. IP addresses are assigned via DHCP, so
subject to change. So you are saying that connection would have
established fine, but it tries to establish it with a wrong place?..
An interesting idea. Now, how can the result of the BackupPC name
resolution can be checked?..

You just need to test things the same way to figure out what is wrong.
If dchp is set in the backuppc host file entry, backuppc should be
using nmblookup to find the name. For a quick check if things work
otherwise, you can put the current IP address in ClientNameAlias - and
if that makes backups work your problem is with name resolution.
There may be some things you can configure in the samba setup (like a
WINS server if you have one) to improve name resolution, or if the
hosts don't roam much you might be able to assign reserved IPs in
DHCP.

--
Les Mikesell
lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

could be a good idea to have dhcp set but have the adress fixed on the dhcp server
--

website: te paard naar sint Petersburg

mail: majacobs < at > xs4all.nl ([email]//majacobs < at > xs4all.nl[/email])

skype: michel.jacobs1

phone: +31204090046

cell: +31626030879

facsimile: +31878704476

Hello.

Thank you, you saved me from going insane. There was a wildcard DNS
entry, and my hostname (say, “ivanov”) was first resolved as
“ivanov.spb.ru MX <some-global-ip>”, instead of “nmblookup ->
<some-local-IP>”.

So the only remaining problem is with the truly unresponsive rsyncd,
on the Windows 7 box. Can't connect even from localhost. Either I
missed a firewall/antivirus setting somewhere, or the rsyncd doesn't
like Windows 7 (and it is even 32-bit).

Sincerely,
Maxim

2012/1/31 Les Mikesell <lesmikesell < at > gmail.com>:
On Tue, Jan 31, 2012 at 11:25 AM, haruspex <princeps.candidus < at > gmail.com> wrote:
Hello.

Name resolution, via nmblookup. IP addresses are assigned via DHCP, so
subject to change. So you are saying that connection would have
established fine, but it tries to establish it with a wrong place?..
An interesting idea. Now, how can the result of the BackupPC name
resolution can be checked?..

You just need to test things the same way to figure out what is wrong.
 If dchp is set in the backuppc host file entry, backuppc should be
using nmblookup to find the name.   For a quick check if things work
otherwise, you can put the current IP address in ClientNameAlias - and
if that makes backups work your problem is with name resolution.
There may be some things you can configure in the samba setup (like a
WINS server if you have one) to improve name resolution, or if the
hosts don't roam much you might be able to assign reserved IPs in
DHCP.

--
  Les Mikesell
    lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Hello.

For any possible future reference: the part about the wildcard may be
correct or may be nonsense, but what actually solved the problem was
adding the “domain” entry in /etc/resolv.conf.

Sincerely,
Maxim

2012/2/1 haruspex <princeps.candidus < at > gmail.com>:
Hello.

Thank you, you saved me from going insane. There was a wildcard DNS
entry, and my hostname (say, “ivanov”) was first resolved as
“ivanov.spb.ru MX <some-global-ip>”, instead of “nmblookup ->
<some-local-IP>”.

So the only remaining problem is with the truly unresponsive rsyncd,
on the Windows 7 box. Can't connect even from localhost. Either I
missed a firewall/antivirus setting somewhere, or the rsyncd doesn't
like Windows 7 (and it is even 32-bit).

Sincerely,
Maxim

2012/1/31 Les Mikesell <lesmikesell < at > gmail.com>:
On Tue, Jan 31, 2012 at 11:25 AM, haruspex <princeps.candidus < at > gmail.com> wrote:
Hello.

Name resolution, via nmblookup. IP addresses are assigned via DHCP, so
subject to change. So you are saying that connection would have
established fine, but it tries to establish it with a wrong place?..
An interesting idea. Now, how can the result of the BackupPC name
resolution can be checked?..

You just need to test things the same way to figure out what is wrong.
 If dchp is set in the backuppc host file entry, backuppc should be
using nmblookup to find the name.   For a quick check if things work
otherwise, you can put the current IP address in ClientNameAlias - and
if that makes backups work your problem is with name resolution.
There may be some things you can configure in the samba setup (like a
WINS server if you have one) to improve name resolution, or if the
hosts don't roam much you might be able to assign reserved IPs in
DHCP.

--
  Les Mikesell
    lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/