Thanks for pitching in.
I assume it's a Windows method, as it appears on the LAN as a Windows network item, and the manual for the router seems to imply it's only set up for Windows 7. It's all in French though, and my French is a bit lacking in the technical department.
a) which file sharing method is being used by the remote disk?
I think I'd been imagining I could do both at the same time. Having read up on it a bit more, especially that helpful link you posted, I realise this is a more complex process than I'd first imagined.
b) are you "mount"ing the remote file system before trying to copy/rsync to it?
That's a useful bit of information I hadn't been aware of. I'd assumed they use the same basic shell commands but behind the scenes, as it were.
GUI programs often do not have anything to do with mounts and setup temporary connections.
I have looked at the rsync man page, but clearly need to spend more time on it. I'm clearly more out of my depth here than I thought I was. After reading the link you posted I tried mounting the remote drive, but without success:
To learn more details about rsync, read the man page - man rsync
. For example, I wasn't aware that rsync supported smb: protocol. Yep, checked the man page - no mention at all. rsync works over ether rsh or ssh connection. Of course, if you mount the remote file system locally, then rsync will be able to perform some magic, but it will treat the remote FS as a local FS and there are very different behaviors in rsync when that happens, some are undesirable.
dmesg | tail didn't produce anything that looked additionally helpful, so I shall return to the reading. Meanwhile I may just opt for the simpler solution of trying out cloud storage for the backup process.
~$ sudo mount -t cifs //neufbox/lacie1tb -o username=admin,password=******** /mnt/neufbox
mount: wrong fs type, bad option, bad superblock on //neufbox/lacie1tb,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
Thanks again for your help. (It's taken me a while to get back as I've been laid up with 'flu.)