- #Crashplan cannot connect to backup engine how to
- #Crashplan cannot connect to backup engine pro
- #Crashplan cannot connect to backup engine windows
This can be added to the BEGINNING of the line, right after the quotes, so using the theoretical directory listed in step 1, it might look something like this SRV_JAVA_OPTS="-Djava.io.tmpdir=/home/myname/crashplan-temp -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx512m =300 =300 .ttl=0 =0"ĥ. Where is a pointer to the directory you created in step 1. We need to add an additional paramater specifying the new temp directory. Open up this file, and look for this line: SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx512m =300 =300 .ttl=0 =0"Ĥ. Once you have your temp folder created, you need to edit the run.conf file which is located here: /usr/local/crashplan/bin/run.confģ. – So, for example, your directory might be: /home/myname/crashplan-tempĢ. – IMPORTANT: The directory must be without the noexec restriction. – The user CrashPlan was installed under must have write permissions on the directory you create – They recommend putting the directory in a user’s home directory (not root’s) Here are the specifications for that folder You will need to create a new tmp folder for CrashPlan on your Linux server. Here are the instructions to get it to work again.ġ. Thank you to Renee S from CrashPlan for posting a viable solution that works on that forum!īasically, the short of it is, CrashPlan doesn’t have the right parameter on the /tmp/ folder it needs to perform the backups. I finally came across this post on CrashPlan’s own site that has a viable answer! Unfortunately the title of the post doesn’t say anything about “Waiting for Backup” so it is hard to connect it as the solution for this particular issue. I actually didn’t even want to do this, so I disabled that, but it still didn’t find my problem. Now, as far as I understand it, inotify is only needed if you want to do scanning for real-time file changes. I eventually started looking at the logs, and found this Java error in one of the log files: Exception in thread "W30145090_ScanWrkr" : Could not initialize class .InotifyManagerĪt .JNAInotifyFileWatcherDriver.(JNAInotifyFileWatcherDriver.java:21)Īt .BackupSetsManager.initFileWatcherDriver(BackupSetsManager.java:393)Īt .BackupSetsManager.startScheduledFileQueue(BackupSetsManager.java:331)Īt .BackupSetsManager.access$1600(BackupSetsManager.java:66)Īt .BackupSetsManager$lay(BackupSetsManager.java:1073)Īt .run(AWorker.java:158) I didn’t think this was the problem for me…so I would suggest you skip those steps if you see them. There were various posts online about versions of Java and changing things with the Java install. I even uninstalled and re-installed CrashPlan completelyĤ. I tried restarting the CrashPlan Engine multiple timesģ. I verified that ports 443, 42 were allowed for outbound connectionsĢ. These are the troubleshooting steps I performed:ġ. No matter what I tried, it would just sit there saying “Waiting for Backup” or “Connecting to Backup Desitnation” and would say 0 files completed.
#Crashplan cannot connect to backup engine pro
CrashPlan PRO Online (CrashPlan Central) was selected as the destinationģ. The folders were successfully selected I could see them on CrashPlan’s web interface as selectedĢ. So, what happened to me was, I got everything configured correctly, but still could not get the backup going.
#Crashplan cannot connect to backup engine windows
Using the Windows CrashPlan Client to manage a headless Linux serverĪlso there is more on CrashPlan’s own site about this here.Īnyways, so the rest of this article assumes that you have successfully gotten CrashPlan installed on your Linux server, and that you are able to manage it via a remote client and select folders for backup.
Installing CrashPlan on a Headless Linux Server
#Crashplan cannot connect to backup engine how to
Thank you to Bryan for posting these tremendously helpful posts on how to get CrashPlan up-and-running on headless Linux server (aka: pretty much any Linux Web Server). First off, I want to give a shout-out to a very helpful post.
0 kommentar(er)
