I have a NAS from Synology with which I synchronise and back up my data. Now, however,the desktop sync app is no longer available as an rpm package, so that I now have a compatibility issue between NAS and my Linux clients.
I am wondering if one solution could be to install the Synology Windows .exe application on the clients running on Wine. Would this .exe client have a) access to all my Linux files and b) network access to the NAS (via my Linux-configured network) for data synchronisation?
Does anyone know how this might work?
Does anyone have any other suggestions how I might solve this issue?
I don’t know for sure what the Synology application for file synchronisation with the NAS uses. On the NAS both SMB and NFS protocols are enabled. I usually access the NAS manually with Nautilus using SMB. My clients are Linux or Mac based.
Dos you mean that I can use the .exe (Windows) without needing to installl Wine? Otherwise, I’m not sure I understand what you mean. My problem is that Synology no longer provides a .rpm application for synchronisation of the OpenSUSE client data with itts NAS. There are now only exe, dmg, or deb packages, whereas previously an rpm package was availlable that had been compatible with Leap 15.2.
You should not need to rely on the desktop client software. It should be possible to ‘automate’ backups from the NAS itself. This article may be of value to you…
Yes, you are right. I already backup my (NAS) files automatically from the NAS itself. But that is NOT my problem. The function I am talking about is the automatic synchronisation of my client (desktop, laptop, cell phone) files with the NAS. This feature gives me access to all files I choose to synchronise practically instantaneously from any of my client. In other words, it is a local cloud, that requires an app on each client and the NAS,
(Those synchronised files are automatically backed up to a USB volume on the NAS at regular intervals.)
However, on looking at the article (many thanks for the tip!), I am wondering if the configuration reported there will give me a similar solution.
Lots of backup options over the network.Can use any supported network protocol ie SMB or NFS. SMB and NFS are network protocols and have nothing to do with backups persay.
Backups can be scheduled in many ways such as backintime or other backup programs there are a bunch or even scripts set to run under some conditions or times.
Great! This sounds like the solution I’m looking for. :)What would I have to do to ensure that the synchronisation is started automatically at (client) boot?
I assume that you’re just backing up a user’s files? In that case perhaps you could have it autostart upon login to the desktop environment and synchronize. Let’s see what others suggest here.
BTW, here’s a Unixmen guide where they show how to automate synchronization by creating a session for it and then implementing with a cron job…
I started testing with a one-shot file sync. It worked well. Unfortunately, there were about fifty files and/or folders that were not transferred. I confirmed that many (if not all) were rejected because their names contained special characters such as “:” or “?”. (The Synology sync had handled these well. Such file names had obviously not been rejected originally by my client file system . For example, an email reply ‘mbox’ file name (from Evolution) includes “Re:” or the email name subject may include a “?”).
Is there any way to configure ‘rsync’ to accept such file names?
Are you sure it is rsync that rejects those file names? Isn’t it the accepeting file system that can not cope with them? You did not mention what file system type is on the NAS, but I get the strong idea that the whole NAS is MS based.
In fact w e have only your saying "Unfortunately, there were about fifty files and/or folders that were not transferred. I confirmed that many (if not all) were rejected because their names contained special characters such as “:” or “?”. But you posted nothing of those “rejected” messages or whatever told you that some files were not copied. So I guess not many people here can try to analyse what happened.
I seem to have no problems with files with names having Unicode characters outside the ASCII range. This is from my backup system, where all files have been created using rsync from my working system:
backup:/backups/backup.0/boven.henm.xs4all.nl/home/henk/test/unicode # l
total 12
drwxr-xr-x 3 1000 1000 4096 May 24 12:35 ./
drwxr-xr-x 4 1000 1000 4096 May 24 14:16 ../
-rw-r--r-- 10 1000 1000 0 May 5 2020 alles goed?
-rw-r--r-- 10 1000 1000 0 Jan 11 2016 hello
drwxr-xr-x 2 1000 1000 4096 Mar 31 2014 öäüßÖÄÜ/
-rw-r--r-- 10 1000 1000 0 Feb 22 2016 Œé⁶
-rw-r--r-- 10 1000 1000 0 Jan 11 2016 Χαίρετε
-rw-r--r-- 10 1000 1000 0 Jan 11 2016 Здравствуйте
-rw-r--r-- 10 1000 1000 0 Jun 20 2016 Лшадсщ
-rw-r--r-- 10 1000 1000 0 Jan 11 2016 أهلا
-rw-r--r-- 10 1000 1000 0 Jan 11 2016 नमस्ते
backup:/backups/backup.0/boven.henm.xs4all.nl/home/henk/test/unicode #