SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
BackupPC Windows Client
Author Message
Post BackupPC Windows Client 
Based on some of the work here http://www.goodjobsucking.com/?p=62 and
elsewhere, I finally put together a package that allows more-or-less
instant installation of a scripted client for Windows machines for
BackupPC that handles:

- Open files (VSS)
- Wake on LAN

For the past 3 years or so, this has gone through a number of tweaks, but
now I'm comfortable that it's a one-click, seamless installation, once the
server side is set up. It includes all the necessary binaries

I'm making it available here:

http://www.michaelstowe.com/backuppc/

(If there are banner ads, feel free to ignore them, they help pay for
bandwidth.)

Questions/comments welcome, of course.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
On 12/05/12 07:42, Michael Stowe wrote:
Based on some of the work here http://www.goodjobsucking.com/?p=62 and
elsewhere, I finally put together a package that allows more-or-less
instant installation of a scripted client for Windows machines for
BackupPC that handles:

- Open files (VSS)
- Wake on LAN

For the past 3 years or so, this has gone through a number of tweaks, but
now I'm comfortable that it's a one-click, seamless installation, once the
server side is set up. It includes all the necessary binaries

I'm making it available here:

http://www.michaelstowe.com/backuppc/

(If there are banner ads, feel free to ignore them, they help pay for
bandwidth.)

Questions/comments welcome, of course.

Firstly, I'd like to say "THANK YOU!", you have done truly an amazing
amount of work to get this far, and thank you very much, it will make my
life much easier I'm sure.

Secondly, a couple of things I needed to adjust in the scripts:

1) Rather than adding the windows administrator username and password
into the preuser and postuser scripts, I created a single auth.sh file,
and sourced that from each of the other two scripts. Obviously paying
particular attention to the permissions on this one file.
2) Since I have a space in my Administrator password I needed to add
some quotes to the command lines for winexe

--- tmp/preusercmd.sh 2012-05-12 06:53:21.000000000 +1000
+++ preusercmd.sh 2012-05-18 14:42:34.000000000 +1000
< at > < at > -1,9 +1,7 < at > < at >
#!/bin/bash
+. /etc/backuppc/scripts/auth.sh
WINEXE=/usr/bin/winexe
-UNAME="Administrator"
-PWD="password"
-WRKGRP="WORKGROUP"
BOX=$1
-$WINEXE --interactive=0 -U $UNAME -W $WRKGRP --password=$PWD //$BOX
'cmd /c c:\backuppc\pre-exec.cmd' <&-
+$WINEXE --interactive=0 -U $UNAME -W $WRKGRP "--password=${PWD}" //$BOX
'cmd /c c:\backuppc\pre-exec.cmd' <&-
sleep 5
echo "Rsync and shadow copy loaded"

--- tmp/postusercmd.sh 2012-05-12 07:13:56.000000000 +1000
+++ postusercmd.sh 2012-05-18 14:41:44.000000000 +1000
< at > < at > -1,11 +1,9 < at > < at >
#!/bin/bash
+. /etc/backuppc/scripts/auth.sh
WINEXE=/usr/bin/winexe
-UNAME="Administrator"
-PWD="password"
-WRKGRP="WORKGROUP"
WOLDIR=/usr/tools/wol
BOX=$1
-$WINEXE -U $UNAME -W $WRKGRP --password=$PWD //$BOX 'cmd /c echo '1' >
c:\backuppc\wake.up' <&-
+$WINEXE -U $UNAME -W $WRKGRP "--password=${PWD}" //$BOX 'cmd /c echo
'1' > c:\backuppc\wake.up' <&-
echo "Rsync and shadow copy unloaded"
if [ $xferOK -eq 1 ]; then
if [ -f $WOLDIR/$BOX.state ]; then
< at > < at > -13,7 +11,7 < at > < at >
echo -n "State before backup: "
echo $wasoff
if [ "$wasoff" = "OFF" ]; then
- $WINEXE -U $UNAME --password=$PWD //$BOX 'shutdown -f -s -c
"Backup Completed"' <&-
+ $WINEXE -U $UNAME "--password=${PWD}" //$BOX 'shutdown -f -s
-c "Backup Completed"' <&-
echo "System shut down"
fi
rm $WOLDIR/$BOX.state

Content of auth.sh (chmod 700 or 500)
#!/bin/bash
UNAME="Administrator"
PWD="some pass"
WRKGRP="WORKGROUP"

Finally, one thing that took me by surprise, I was asked by the windows
install utility for the rsync username and password, but the username
wasn't added to the rsyncd.conf file (so I added it manually) and the
username and password was not added to the rsyncd.secrets file (in fact,
the secrets file did not exist at all).

Not terribly important, but perhaps this could be added to the Client
Installer instructions, or else added to the program to be done during
installation.

PS, this was on a windows XP Pro machine (if it makes a difference)....

Thank you again for a great utility and solution.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
On 12/05/12 07:42, Michael Stowe wrote:
Based on some of the work here http://www.goodjobsucking.com/?p=62 and
elsewhere, I finally put together a package that allows more-or-less
instant installation of a scripted client for Windows machines for
BackupPC that handles:

- Open files (VSS)
- Wake on LAN

For the past 3 years or so, this has gone through a number of tweaks,
but
now I'm comfortable that it's a one-click, seamless installation, once
the
server side is set up. It includes all the necessary binaries

I'm making it available here:

http://www.michaelstowe.com/backuppc/

(If there are banner ads, feel free to ignore them, they help pay for
bandwidth.)

Questions/comments welcome, of course.

Firstly, I'd like to say "THANK YOU!", you have done truly an amazing
amount of work to get this far, and thank you very much, it will make my
life much easier I'm sure.

Secondly, a couple of things I needed to adjust in the scripts:

1) Rather than adding the windows administrator username and password
into the preuser and postuser scripts, I created a single auth.sh file,
and sourced that from each of the other two scripts. Obviously paying
particular attention to the permissions on this one file.
2) Since I have a space in my Administrator password I needed to add
some quotes to the command lines for winexe

--- tmp/preusercmd.sh 2012-05-12 06:53:21.000000000 +1000
+++ preusercmd.sh 2012-05-18 14:42:34.000000000 +1000
< at > < at > -1,9 +1,7 < at > < at >
#!/bin/bash
+. /etc/backuppc/scripts/auth.sh
WINEXE=/usr/bin/winexe
-UNAME="Administrator"
-PWD="password"
-WRKGRP="WORKGROUP"
BOX=$1
-$WINEXE --interactive=0 -U $UNAME -W $WRKGRP --password=$PWD //$BOX
'cmd /c c:\backuppc\pre-exec.cmd' <&-
+$WINEXE --interactive=0 -U $UNAME -W $WRKGRP "--password=${PWD}" //$BOX
'cmd /c c:\backuppc\pre-exec.cmd' <&-
sleep 5
echo "Rsync and shadow copy loaded"

--- tmp/postusercmd.sh 2012-05-12 07:13:56.000000000 +1000
+++ postusercmd.sh 2012-05-18 14:41:44.000000000 +1000
< at > < at > -1,11 +1,9 < at > < at >
#!/bin/bash
+. /etc/backuppc/scripts/auth.sh
WINEXE=/usr/bin/winexe
-UNAME="Administrator"
-PWD="password"
-WRKGRP="WORKGROUP"
WOLDIR=/usr/tools/wol
BOX=$1
-$WINEXE -U $UNAME -W $WRKGRP --password=$PWD //$BOX 'cmd /c echo '1' >
c:\backuppc\wake.up' <&-
+$WINEXE -U $UNAME -W $WRKGRP "--password=${PWD}" //$BOX 'cmd /c echo
'1' > c:\backuppc\wake.up' <&-
echo "Rsync and shadow copy unloaded"
if [ $xferOK -eq 1 ]; then
if [ -f $WOLDIR/$BOX.state ]; then
< at > < at > -13,7 +11,7 < at > < at >
echo -n "State before backup: "
echo $wasoff
if [ "$wasoff" = "OFF" ]; then
- $WINEXE -U $UNAME --password=$PWD //$BOX 'shutdown -f -s -c
"Backup Completed"' <&-
+ $WINEXE -U $UNAME "--password=${PWD}" //$BOX 'shutdown -f -s
-c "Backup Completed"' <&-
echo "System shut down"
fi
rm $WOLDIR/$BOX.state

Content of auth.sh (chmod 700 or 500)
#!/bin/bash
UNAME="Administrator"
PWD="some pass"
WRKGRP="WORKGROUP"

Finally, one thing that took me by surprise, I was asked by the windows
install utility for the rsync username and password, but the username
wasn't added to the rsyncd.conf file (so I added it manually) and the
username and password was not added to the rsyncd.secrets file (in fact,
the secrets file did not exist at all).

Not terribly important, but perhaps this could be added to the Client
Installer instructions, or else added to the program to be done during
installation.

PS, this was on a windows XP Pro machine (if it makes a difference)....

Thank you again for a great utility and solution.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Hmmm, I'm not sure why it wouldn't have created the rsyncd.secrets file,
but I'll see what's wrong with it. I'll also add some more explanation to
the installer, since it's possible to just skip and create the secrets
file manually.

I'll also bundle your suggested changes for an update, thank you!

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
On 21/05/12 07:25, Michael Stowe wrote:

Hmmm, I'm not sure why it wouldn't have created the rsyncd.secrets file,
but I'll see what's wrong with it. I'll also add some more explanation to
the installer, since it's possible to just skip and create the secrets
file manually.

I'll also bundle your suggested changes for an update, thank you!

No problem, I hope it helps.

One question, after my successful install and first backup last week, backuppc hasn't been able to do a second successful backup (it just eventually gets an ALARM and fails).

It seems to be hanging at the preusercmd script:
7417 ? S 9:45 /usr/bin/perl /usr/share/backuppc/bin/BackupPC -d
7423 ? S 66:17 _ /usr/bin/perl /usr/share/backuppc/bin/BackupPC_trashClean
17281 ? S 0:00 _ /usr/bin/perl /usr/share/backuppc/bin/BackupPC_dump hostname
17290 ? S 0:00 _ /bin/bash /etc/backuppc/scripts/preusercmd.sh hostname
17291 ? S 0:56 _ /usr/bin/winexe --interactive=0 -U Administrator -W DOMAIN --password=mypass //hostname cmd /c c:backuppcpre-exec.cmd

From the backuppc badxferlog:

Executing DumpPreUserCmd: /etc/backuppc/scripts/preusercmd.sh hostname
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

exiting after signal ALRM

Possibly during my testing and starting/stopping I've messed something up, is there a way to "reset" the state on the windows client? ie, to delete any shadow volumes, kill any rsyncd process, etc?

Thanks,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Post BackupPC Windows Client 
On 21/05/12 07:25, Michael Stowe wrote:

Hmmm, I'm not sure why it wouldn't have created the rsyncd.secrets file,
but I'll see what's wrong with it. I'll also add some more explanation
to
the installer, since it's possible to just skip and create the secrets
file manually.

I'll also bundle your suggested changes for an update, thank you!

No problem, I hope it helps.

One question, after my successful install and first backup last week,
backuppc hasn't been able to do a second successful backup (it just
eventually gets an ALARM and fails).

It seems to be hanging at the preusercmd script:
7417 ? S 9:45 /usr/bin/perl /usr/share/backuppc/bin/BackupPC
-d
7423 ? S 66:17 \_ /usr/bin/perl
/usr/share/backuppc/bin/BackupPC_trashClean
17281 ? S 0:00 \_ /usr/bin/perl
/usr/share/backuppc/bin/BackupPC_dump hostname
17290 ? S 0:00 \_ /bin/bash
/etc/backuppc/scripts/preusercmd.sh hostname
17291 ? S 0:56 \_ /usr/bin/winexe --interactive=0
-U Administrator -W DOMAIN --password=mypass //hostname cmd /c
c:\backuppc\pre-exec.cmd

From the backuppc badxferlog:

Executing DumpPreUserCmd: /etc/backuppc/scripts/preusercmd.sh hostname
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

exiting after signal ALRM

Possibly during my testing and starting/stopping I've messed something
up, is there a way to "reset" the state on the windows client? ie, to
delete any shadow volumes, kill any rsyncd process, etc?

Thanks,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Yes -- a reboot will do it (of course) but so will placing a file called
"wake.up" in the backuppc client directory.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
On 21/05/12 22:58, Michael Stowe wrote:
On 21/05/12 07:25, Michael Stowe wrote:
One question, after my successful install and first backup last week,
backuppc hasn't been able to do a second successful backup (it just
eventually gets an ALARM and fails).

It seems to be hanging at the preusercmd script:
7417 ? S 9:45 /usr/bin/perl /usr/share/backuppc/bin/BackupPC
-d
7423 ? S 66:17 _ /usr/bin/perl
/usr/share/backuppc/bin/BackupPC_trashClean
17281 ? S 0:00 _ /usr/bin/perl
/usr/share/backuppc/bin/BackupPC_dump hostname
17290 ? S 0:00 _ /bin/bash
/etc/backuppc/scripts/preusercmd.sh hostname
17291 ? S 0:56 _ /usr/bin/winexe --interactive=0
-U Administrator -W DOMAIN --password=mypass //hostname cmd /c
c:backuppcpre-exec.cmd

From the backuppc badxferlog:

Executing DumpPreUserCmd: /etc/backuppc/scripts/preusercmd.sh hostname
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

exiting after signal ALRM

Possibly during my testing and starting/stopping I've messed something
up, is there a way to "reset" the state on the windows client? ie, to
delete any shadow volumes, kill any rsyncd process, etc?

Yes -- a reboot will do it (of course) but so will placing a file called
"wake.up" in the backuppc client directory.

Tried "echo > wake.up" in a dos prompt window, which created the file into c:backuppc but it didn't seem to have any effect. Will get the machine rebooted and see how that goes.

Thanks,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Post BackupPC Windows Client 
On 21/05/12 22:58, Michael Stowe wrote:
Yes -- a reboot will do it (of course) but so will placing a file called
"wake.up" in the backuppc client directory.
Thanks, the wake.up file didn't help, but a reboot solved the problem.

I've now rolled this out across another three servers, and it has worked quite well. Thank you again.

I've also spent a lot of time today making it work on a remote windows XP Pro machine with the following notes (some you may like to think about, others are for my own and/or someone else's benefit).

1) In order for winexe to be able to talk to the machine, you will need to make file and printer sharing available. Since we are talking about the public internet, that isn't very sensible.
a) I installed openvpn on the backuppc server, and configured the router to port forward the port to backuppc (backuppc actually has a private IP on the LAN)
b) I installed openvpn on the windows XP client, configured and tested, and then set the service to automatic start, and to restart on failure
2) I configured the firewall to allow File/Printer Sharing (I set the scope to the subnet used by openvpn), or could disable the firewall on the openvpn interface, but I think windows nags you about the firewall being disabled.
3) I then tested, and winexe kept getting NT_STATUS_LOGON_FAILURE, I needed to disable simple file sharing to resolve this
4) I added the client hostname to my /etc/hosts with the IP allocated by openvpn
5) I got a passing error message from the postusercmd.sh at one stage, and would suggest the following change:

if [ ! -z $xferOK ] && [ $xferOK-eq 1 ]; then
Basically, if xferOK is not set, then [ $xferOK-eq 1 ] generates an error (and does not match), with my change it will not generate an error, and will still not match.

I've now modified my auth.sh as follows:
#!/bin/bash
UNAME="Administrator"
PWD=""
WRKGRP=""

if [ -f "/etc/backuppc/scripts/hostauth/${1}.sh" ]
then
. "/etc/backuppc/scripts/hostauth/${1}.sh"
fi

This allows me to set different username/password/workgroup for each client machine I'm going to backup. It also allows a default value.

I plan on rolling this out across a number of systems in the coming weeks. Will keep you updated on how things work out.

I originally though about using SSH to tunnel the rsync data and winexe, but selected openvpn for the following reasons:
a) openvpn has a simple installation program for every windows/mac and linux system I've come across (ie, doesn't need cygwin)
b) openvpn will tunnel all the misc ports required, so I don't need to mess with port forwarding in ssh
c) openvpn allows me to get access to the remote machine if I need to diagnose some issue with the backup/etc
d) openvpn will connect from each client to me, so I only need to setup the port forward on my router, instead of each individual remote systems router.
e) openvpn will provide a "static IP' without needing to deal with dynamic dns etc, since the client connects to me, and openvpn assigns a static IP

I hope that this will assist someone else, comments or suggestions are more than welcome... or if you do things differently and think it works better, please feel free to share.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Post BackupPC Windows Client 
First, thanks for doing this.  

I've had the original post bookmarked for quite some time (years, it seems) with plans to implement, and this simplifies the process quite a bit.  Performance is much better than rsync-over-autofs-smb (for any number of reasons).
5) I got a passing error message from the postusercmd.sh at one stage, and would suggest the following change:

if [ ! -z $xferOK ] && [ $xferOK-eq 1 ]; then
Basically, if xferOK is not set, then [ $xferOK-eq 1 ] generates an error (and does not match), with my change it will not generate an error, and will still not match.




I ran into that error "postusercmd.sh: line 10: [: -eq: unary operator expected" as well - even on successful runs.  It looks like $xferOK is never declared, but is just passed in.


 postusercmd.sh
BOX=$1XFEROK=$2
$WINEXE -U $UNAME -W $WRKGRP --password=$PWD //$BOX 'cmd /c echo '1' > c:backuppcwake.up' <&-
echo "Rsync and shadow copy unloaded"
if [ $XFEROK -eq 1 ]; then
   if [ -f $WOLDIR/$BOX.state ]; then
      read wasoff < $WOLDIR/$BOX.state
      echo -n "State before backup: "






Thanks for all your work on this!


-Kris Lou

Post BackupPC Windows Client 
First, thanks for doing this.

I've had the original post bookmarked for quite some time (years, it
seems)
with plans to implement, and this simplifies the process quite a bit.
Performance is much better than rsync-over-autofs-smb (for any number of
reasons).

5) I got a passing error message from the postusercmd.sh at one stage, and
would suggest the following change:

if [ ! -z $xferOK ] && [ $xferOK-eq 1 ]; then
Basically, if xferOK is not set, then [ $xferOK-eq 1 ] generates an
error
(and does not match), with my change it will not generate an error, and
will still not match.


I ran into that error "postusercmd.sh: line 10: [: -eq: unary operator
expected" as well - even on successful runs. It looks like $xferOK is
never declared, but is just passed in.

postusercmd.sh

BOX=$1

*XFEROK=$2*
$WINEXE -U $UNAME -W $WRKGRP --password=$PWD //$BOX 'cmd /c echo '1' >
c:\backuppc\wake.up' <&-
echo "Rsync and shadow copy unloaded"
if [ *$XFEROK* -eq 1 ]; then
if [ -f $WOLDIR/$BOX.state ]; then
read wasoff < $WOLDIR/$BOX.state
echo -n "State before backup: "



Thanks for all your work on this!

-Kris Lou

Not only are you exactly correct, but your fix is exactly what I left out
when I posted it the first time (I apparently deleted that line and hadn't
noticed.) The client side hasn't changed, but I'm updating the scripts
with the fixes this week, and will have it posted as soon as I do.

Thanks!

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
On 31/05/12 00:59, Michael Stowe wrote:
Not only are you exactly correct, but your fix is exactly what I left out
when I posted it the first time (I apparently deleted that line and hadn't
noticed.) The client side hasn't changed, but I'm updating the scripts
with the fixes this week, and will have it posted as soon as I do.

Just a little reminder that on each machine I've tried to install the client on, the rsyncd.secrets file wasn't created.
Also, when using a username other than Administrator (for rsync) the install also fails to use the correct username in the rsyncd.conf file.

Haven't had a chance to install on a 2008 server yet, but hope to have more of a play in the coming weeks.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Post BackupPC Windows Client 
On 31/05/12 00:59, Michael Stowe wrote:
Not only are you exactly correct, but your fix is exactly what I left
out
when I posted it the first time (I apparently deleted that line and
hadn't
noticed.) The client side hasn't changed, but I'm updating the scripts
with the fixes this week, and will have it posted as soon as I do.

Just a little reminder that on each machine I've tried to install the
client on, the rsyncd.secrets file wasn't created.
Also, when using a username other than Administrator (for rsync) the
install also fails to use the correct username in the rsyncd.conf file.

Haven't had a chance to install on a 2008 server yet, but hope to have
more of a play in the coming weeks.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au

Turns out it wouldn't create rsyncd.secrets unless the installation
directory already existed when the installer was started (whoops!)

I've fixed this, and a few other things, available here:
http://www.michaelstowe.com/backuppc


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post BackupPC Windows Client 
I'm trying to work with this to get it to restore files to their original paths via rsyncd as well.  Basically, I'm having the restore pre-cmd follow the same path as the dump pre-cmd ($type is helpful here), but bypassing vshadow and calling rsync with a different conf.  Single file restores work (with updated 1.7.15 cygwin1.dll), but restoring directories sort of mangles ownership and permissions beyond the first level.  


Do you guys have any suggestions for generic permissions-fixing when restoring to a cygwin-rsync system?


Thanks,

Kris Lou
klou < at > themusiclink.net ([email]klou < at > themusiclink.net[/email])


On Mon, Jun 4, 2012 at 12:27 PM, Michael Stowe <mstowe < at > chicago.us.mensa.org ([email]mstowe < at > chicago.us.mensa.org[/email])> wrote:
> On 31/05/12 00:59, Michael Stowe wrote:
Not only are you exactly correct, but your fix is exactly what I left
out
when I posted it the first time (I apparently deleted that line and
hadn't
noticed.) The client side hasn't changed, but I'm updating the scripts
with the fixes this week, and will have it posted as soon as I do.

Just a little reminder that on each machine I've tried to install the
client on, the rsyncd.secrets file wasn't created.
Also, when using a username other than Administrator (for rsync) the
install also fails to use the correct username in the rsyncd.conf file.

Haven't had a chance to install on a 2008 server yet, but hope to have
more of a play in the coming weeks.

Regards,
Adam

--
Adam Goryachev
Website Managers
www.websitemanagers.com.au



Turns out it wouldn't create rsyncd.secrets unless the installation
directory already existed when the installer was started (whoops!)

I've fixed this, and a few other things, available here:
http://www.michaelstowe.com/backuppc


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net ([email]BackupPC-users < at > lists.sourceforge.net[/email])
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/




Post BackupPC Windows Client 
I'm trying to work with this to get it to restore files to their original
paths via rsyncd as well. Basically, I'm having the restore pre-cmd
follow
the same path as the dump pre-cmd ($type is helpful here), but bypassing
vshadow and calling rsync with a different conf. Single file restores
work
(with updated 1.7.15 cygwin1.dll), but restoring directories sort of
mangles ownership and permissions beyond the first level.

Do you guys have any suggestions for generic permissions-fixing when
restoring to a cygwin-rsync system?

Thanks,

Kris Lou
klou < at > themusiclink.net

cygwin-rsync may not be able to handle this natively; I haven't had much
success.

It may be worthwhile to backup/restore ACL's separately:

http://www.microsoft.com/en-us/download/details.aspx?id=23510


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/

Post  
I'm just now discovering BackupPC and doing some initial development work, and I came across this post. I'm encouraged to see that this may simplify the deployment of an rSync client to Windows for scheduled backups of machines.

However, what about user-initiated backups? How would a user start a backup of their machine manually, and perhaps even configure files/directories to be backed up?

I started down the road of incorporating Unison as a means of doing this, and not sure if that is duplicating the effort of what you have provided.

View user's profile Send private message
Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB