Uncomment and adjust to following lines accordingly: /Applications/CrashPlan.app/Contents/Resources/Java/conf/ui.properties (Mac).C:\Program Files\CrashPlan\conf\ui.properties (Windows).You will need to edit the ui.properties files, located here: Next up is to tell your Crashplan client on you computer to NOT connect to the engine running on the local computer but to the engine on the Synology.
UNABLE TO CONNECT TO BACKUP ENGINE CRASHPLAN UPDATE
You may need to update this key if you update or upgrade the Crashplan client. /Library/Application Support/CrashPlan/.ui_info (Mac).C:\ProgramData\CrashPlan\.ui_info (Windows).Next you will need to update the ui_info key for the Crashplan client running on your computer with the key extracted from your Synology. First you will need to retrieve the key on your Synology using command: cat /var/lib/crashplan/.ui_info echo You can do so by updating the ui_info key on your Crashplan installation on your computer. The trick after this, is to let the Crashplan client on your computer to communicate with the backup engine running on your Synology. First of all, you will need Java installed on your Synology and the community Crashplan package from PCloadletter. It requires some additional configuration. Do however note that this is not a supported solution by Code42. Crashplan’s continuous data protection for endpoint is available for $5 per month. Normally used for computer backup , but perfectly capable to backup my data residing on my Synology. To make sure all data is back-upped to an off-site location, I use Code42’s Crashplan. The diagram below shows the setup I came up with: The RTO would not matter that much as long as I’m able to recover the data.Īlso, I would like to reduce the number of cloud storage solutions (Google Drive, Onedrive, Dropbox) and their associated clients. The off-site backup would have to be affordable while growing in GB’s. Those are invaluable to me! I wanted to make sure that all this data is centralized on my Synology NAS and I have the requirement for an off-site backup. More important however, are my personal documents and my photos/videos. However, if one can avoid the loss of data, one should. I would not be a happy man, but a complete homelab reinstall would be possible without any backup. I could live with my homelab data being lost. So when I speak of ‘my beloved data’, I am talking about: I gave some thought on how my data would be safe if disaster would struck, like my Synology NAS catching fire. A while ago I finally had some attention for my much beloved data.
0 kommentar(er)
