Search the Community
Showing results for tags 'synology'.
Found 3 results
Greetings! Running Retrospect Server 16.6.0 (114) on a MacPro trashcan updated to Catalina 10.15.3. Currently there are no 'client' machines, I'm simply backing up 5 shared volumes on a Synology RS2414rp+ (also current DSM) to LTO-6. I've added the shares via Sources using 'afp://myFileServer.local/Share_Name', and set it to log in using a registered user with admin privileges. The shares all show up in Sources with the green status indicator. Backup scripts are set up to run after hours, and I've got a 5-member media set, two blanks, and a cleaning tape in my 8 slot robot. All Good, right? Nope. Shortly after a script starts, Retro begins scanning. Then it hangs and I get a macOS system alert saying the server is shutting down. After that, my Retro log fills with 'file not found' errors and nothing gets backed up. Checking the Sources pane after this, the target volume shows as disconnected. Status goes green again via either Browse button or Locate. Any ideas? Thanks in advance!
We would like to install a retroclient on a Synology RS815RP+ NAS running DSM 6.1.3-15152. We know that Retrospect Clients are not officially supported on Synology or Qnap, but we have a client already working well on another RS815RP+, installed by our previous linux specialist. Our current specialist wrote: "I haven't been able to find any documentation regarding installing RCL on a synology device. I'm hesitant to try on a production device as synology's "linux" is their own special distribution. Retrospect I think recommends installing the RCL on a windows or linux machine (as normal), and mounting the NAS device on your RCL target, and just backing up the mounted directory" Has anyone else done a client install and are there any special considerations that must be made?
I have been having problem backing up shares on Qnap and Synology workstations. Symptoms: Retrospect hang with beach-ball icon, force quit on activity monitor doesn't help, whole system has to be rebooted ( a pain when working remotely) In console log there will be continuous messages of "afpfs_DoReconnect" loops Have got a updated version of Retrospect from support, which worked for one backupset, but with worrying log files. Solution: In my case it was a assumption by retrospect that I run a Windows server with workgroups. If NAS device is 10.0.0.100, with user admin | adminpassword, connect to share as user= 10.0.0.100\admin (local user), and password = adminpassword Since doing this have run backups succesfully, and log not full of "Not done after 30s", or "error -1011, API request" Hope this helps someone, as it got really frustrating playing with retro.ini files. My config : Retrospect Server 15, running on Mac Pro Xeon, backing up to LTO6 via SAS