Yet - the crashplan container is up and running, and I can access the GUI, as well as see the container running within the Docker app on the Synology. In fact, I can find a few different Docker folders, but none with crashplan. I have SSH’d into the Synology, and looked around for the folder that contain the config files for Crashplan… have not been able to find any. This can be a little daunting as Crashplan still hasn’t issued an official package for Synology NAS devices. Go back to the Synology interface and go to: Docker > Container > Crashplan > Details > Terminal > Create > Bash and type the following: cat /var/lib/crashplan/. Enter in your ‘admin’ account password and you are given root. The thing is that Crashplan seem to have been developed with much lower connections in mind than the ones we have today. So after loggin in as admin, you have to ‘sudo -I’ which will then ask for creds. I SSH in as admin, and apparently Synology DSM 6.0+ software have removed the ability to directly login as root. Remote backup service Cloud computing Backup software Data center, host computer, computer Network, information Technology, data png 1000x991px 197.17KB. Iv read many of the issue discussions reported on Jlesages Github for crashplan. Iv read many of the support articles at. What Ive Done:Ive read many many discussions on where to find the my.service.xml file. The Problem:The folders/directories for the Crashplan container do not seem to exist, and therefore, I cannot reach the my.service.xml file to alter dedupe values. "Find your my.service.xml file and find these lines:" 1 Trying to change the Dedupe settings either to minimal or set my own value. docker run -it -rm /mssql/server /bin/bash and then look at the active user within the container: mssqled73727870bb:/ whoami mssql we see that the active user is mssql. Dedupelication is very slow, and uploads are very slow. However, I am having horribly slow upload speeds even though we have a fat connection. Should be plenty of memory and computer power. Then I did: ACL: And gave the user dockeruser Read/Write permission. Support for CrashPlan PRO (aka CrashPlan for Small Business) docker container Application Name: CrashPlan PRO (aka CrashPlan for Small Business) Application Site. When the dockercrashplan folder was created, I gave these permissions: Everyone:read/write. Ive worked with Crashplan, and theyve been no help in resolving the issue. So iv got a DS1515+ synology with 6gb of ram. Just curious if Im the only one who cant get Crashplan to restore a file larger than about 900 MB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |