Hi,
I've just setup a new Win10 machine, and thought I'd try this solution
to do the backup...
So far, I have installed the MS SSH server, using the powershell command
line installation method, copied the backuppc ssh public key across,
used a powershell script to fix permissions on the file. Confirmed I
could login from the backuppc host as a new backuppc user
(administrative access).
I then downloaded cygwin, ran the setup, and installed rsync plus all
other defaults (did not install SSH).
I then changed the default SSH shell to bash instead of powershell
(registry key).
Fixed the PATH variable in the .bashrc to ensure cygwin's /bin was included
Copied the below script to my new hosts.pl config file, along with the
following host specific config:
$Conf{ClientNameAlias} = [
'10.1.1.119'
];
$Conf{XferMethod} = 'rsync';
$Conf{RsyncdUserName} = 'BackupPC';
$Conf{RsyncShareName} = [
'/cygdrive/C/'
];
$Conf{RsyncSshArgs} = [
'-e',
'$sshPath -l BackupPC'
];
$Conf{RsyncClientPath} = '/cygdrive/c/cygwin64/root/bin/rsync.exe';
$Conf{PingMaxMsec} = 100;
$Conf{BlackoutPeriods} = [];
However, when I try to run the backup, I get the following:
Executing DumpPreUserCmd: &{sub {
#Load variables
my $timestamp = "20210226-012400";
my $shadowdir = "/cygdrive/c/shadow/";
my $shadows = "";
my $bashscript = "DAYS=2\
etc (cut)
print map { " '$_' => $sharenameref->{$_}
" } sort(keys %{$sharenameref}) unless $?;
}}
Eval return value: 1
Running: /usr/local/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc
--bpc-host-name hostvm2 --bpc-share-name /cygdrive/C/ --bpc-bkup-num 0
--bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
--bpc-bkup-inode0 5 --bpc-log-level 1 --bpc-attrib-new -e /usr/bin/ssh\ -l\
BackupPC --rsync-path=/cygdrive/c/cygwin64/root/bin/rsync.exe --super
--recursive --protect-args --numeric-ids --perms --owner --group -D --times
--links --hard-links --delete --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\
%9l\ %f%L --stats --checksum --one-file-system --timeout=72000
10.1.1.119:/cygdrive/C/ /
full backup started for directory /cygdrive/C/
Xfer PIDs are now 31043
This is the rsync child about to exec /usr/local/bin/rsync_bpc
cmdExecOrEval: about to exec /usr/local/bin/rsync_bpc --bpc-top-dir
/var/lib/backuppc --bpc-host-name hostvm2 --bpc-share-name /cygdrive/C/
--bpc-bkup-num 0 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
--bpc-bkup-inode0 5 --bpc-log-level 1 --bpc-attrib-new -e /usr/bin/ssh\ -l\
BackupPC --rsync-path=/cygdrive/c/cygwin64/root/bin/rsync.exe --super
--recursive --protect-args --numeric-ids --perms --owner --group -D --times
--links --hard-links --delete --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\
%9l\ %f%L --stats --checksum --one-file-system --timeout=72000
10.1.1.119:/cygdrive/C/ /
Xfer PIDs are now 31043,31172
xferPids 31043,31172
rsync: [sender] send_files failed to open "/cygdrive/C/DumpStack.log.tmp":
Device or resource busy (16)
new recv cd+++++++++ ---r-x--- 328384, 328384 0 .
rsync: [sender] send_files failed to open "/cygdrive/C/hiberfil.sys": Device or
resource busy (16)
rsync: [sender] send_files failed to open "/cygdrive/C/pagefile.sys": Device or
resource busy (16)
rsync: [sender] send_files failed to open "/cygdrive/C/swapfile.sys": Device or
resource busy (16)
As far as I can tell, this would suggest that we are not actually doing
the backup from the shadow copy... so, good news, I got a full backup of
the machine (excluding open files), but bad news is I don't know why it
didn't work.
I can login from the backuppc host as the backuppc user on the windows
machine, and I can then create a shadow volume and delete it, but not
sure what else to test, or where to get additional logs from....
Any suggestions greatly appreciated
Regards,
Adam
On 26/2/21 07:31, Greg Harris wrote:
Okay, I was just making things way harder than they needed to be.
Sorry Jeff. Doug, from my understanding DeltaCopy is nearly just an
alternative version of cygwin-rsyncd. I think all you need to do is
dump these scripts into the bottom of the .pl file for the host.
Otherwise, all of the other setup you normally do should be the same.
Thanks,
Greg Harris
On Feb 23, 2021, at 10:58 AM, backu...@kosowsky.org
<mailto:backu...@kosowsky.org> wrote:
Yes. SSH needs to be minimally configured just as you do when using
the 'rsync' method (over ssh) for any other system.
And SSH is pretty basic for any type of communication, login, file
transfer between machines in the 20th century (with the exception
maybe of pure Windows environments)
Technically, SSH may not be a dependency for rsync in that you can
use 'rsyncd' without SSH but the vast majority of rsync usage between
local and remote machines (with or without backuppc) is over ssh.
Greg Harris wrote at about 15:51:26 +0000 on Tuesday, February 23, 2021:
I was hoping that I could reply with at least a basic outline.
However, I’m still trying to figure out what I’m missing.
Jeff, you seem to imply that there’s no client side config that
needs to be done? When I installed SSH via the base CygWin, it
seems like there is at least basic setup steps to getting sshd
running. Maybe you are considering those basic install pieces?
Sorry I’m such a newb on this, but I’m wading my way through and
feeling a bit tripped up as I try to do the minimum possible to
maximize the usage.
Additionally, it seems that openssh is not a dependency for rsycn in
Cygwin, so I had to specify both separately.
I get the feeling that what I was expecting to do is a hybrid of
using the BackupPC Cygwin install on the client and then this script
on the server side, rather than configuring anything on either side.
Maybe my expectations are wildly off.
Thanks,
Greg Harris
On Feb 18, 2021, at 9:30 AM, Doug Lytle <supp...@drdos.info
<mailto:supp...@drdos.info><mailto:supp...@drdos.info
<mailto:supp...@drdos.info>>> wrote:
'cygpath' is part of the basic 'cygwin' package.
Okay,
For someone that has always used DeltaCopy on the clients, is there
a step-by-step instruction page that explains on how to use this?
Thanks!
Doug
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
<mailto:BackupPC-users@lists.sourceforge.net><mailto:BackupPC-users@lists.sourceforge.net
<mailto:BackupPC-users@lists.sourceforge.net>>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
<https://lists.sourceforge.net/lists/listinfo/backuppc-users>
Wiki: https://github.com/backuppc/backuppc/wiki
<https://github.com/backuppc/backuppc/wiki>
Project: https://backuppc.github.io/backuppc/
<https://backuppc.github.io/backuppc/>
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
<mailto:BackupPC-users@lists.sourceforge.net>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
<mailto:BackupPC-users@lists.sourceforge.net>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
