Syncovery Support Forum

I figured it out. When you install the service it installs syncoveryrs.service under systemd. I forget if I launched the service manually or it started as part of the installation. Nevertheless, when I then followed the instructions and launched the background process ( SyncoveryRS start & Syncovery...

SELinux is not being used here.

Also, I was mistaken about the distro. It is Debian Stretch, not Buster.

I am trying to perform a pull backup and the job, for some reason, is not triggering the remote listing service on the machine with the files to be backed up. I have a MacOS backup server running Syncovery 9.32a. I am trying to perform a pull backup from a machine running Debian Buster and the Synco...

That is what the forums are for. I have worked one-on-one with you on certain issues over the years. Great products! Great service! No complaints!

The version of OS I am using is Armbian based on Debian Stretch. Hoping that another version of Debian might provide clearer codes I installed everything on Debian Jessie and it paid off. The message led me to the possibility that the SMB URI was malformed. Based on info at the link https://en.wikip...

So actually the syntax is DOMAIN/username . libsmbclient follows the same as smbclient. I should have known. FWIW, protocol settings need to be correct in smb.conf. For me it is... client min protocol = SMB2 client max protocol = SMB3 On to the next problem. I am now getting an error on the call to ...

I am trying to use Syncovery Linux to perform a pull backup from a few Windows machines. I cannot get the profile to login to the remote Windows machine using SMB. Eventually we will use SSH but for now SMB is the only way. Names below have been sanitized, but the construct is accurate. The domain i...

It does not exist in /lib though it does exist in /lib/arm-linux-gnueabihf, which is in /etc/ld.so.conf.d/arm-linux-gnueabihf.conf, so I thought nothing of it.

Adding a symlink fixes the issue.

Here you go... root:# ldd /usr/lib/Syncovery/SyncoveryCL not a dynamic executable root:# file /usr/lib/Syncovery/SyncoveryCL /usr/lib/Syncovery/SyncoveryCL: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.0.0, stripped

I am having an issue running SyncoveryCL on Linux on an ODROID-HC2, which uses the ODROID-XU4 platform. The unit uses an 8-core ARMv7. Below is a dump of one core for brevity. Also there is a dump of uname & dpkg. root:# cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 3 (v7l) BogoMI...