Hi Michael,
it's difficult to tell without a more concrete error message. Running
the command in debug mode (-v 9) might help to understand where the
script hangs.
What happens if you call `ssh ${BACKUP_USER}@${TARGETHOST}
rdiff-backup.bat ${BACKUPTO}` like the cron job? Or even something like
The command in my first email works fine when run on the Windows
machine, either directly or from within a batch file, locally in a
command prompt or in an ssh terminal from another machine. It only fails
when a shell script on another machine connects by ssh and run the batch
file from the
On 01/11/2021 15:21, Michael Crider - HOEC wrote:
We have used rdiff-backup for well over 10 years for our Linux servers
and workstations, and until recently to back up Windows servers and
workstations we mounted their drives locally on the backup server and
ran rdiff-backup against the mount.
We have used rdiff-backup for well over 10 years for our Linux servers
and workstations, and until recently to back up Windows servers and
workstations we mounted their drives locally on the backup server and
ran rdiff-backup against the mount. When our first Windows 10
workstations arrived
