![]() To me it seems like when I choose adopt a backup, it makes crash plan upgrade the NAS software which is causing it to crash. I go to the crash plan website to see if the NAS is connected and backing up to crash plan, and it says it not connected. After stopping and restarting the crash plan app on the NAS the configuration page or site comes back online but my client computer (headless) contacting the NAS says it can't connect to the crash plan engine. Looking at the NAS the crash plan info page gives a 404 error. After I choose adopt, Crashplan on my computer client (headless) contacting the NAS says ''updating" then crashes. In this case I am taking the previous NAS crashplan backup installation and trying to use the same NAS to continue on. Choosing adopt allows you to take your backup from another computer and let the current computer take it over. At 9.99 per month per device, plus taxes, it’s more expensive than many other services. I sign in and choose adopt so I can take up where I left off. CrashPlan has a decent selection of features, especially if you need user management tools. Contents 1 Installation 2 Basic Usage 3 Running Crashplan on a headless server 3.1 X11 forwarding over SSH 3.2 Local client 4 Troubleshooting 4. Backing up to the cloud servers requires a monthly subscription. I am able to connect to it just fine with my client (via headless). CrashPlan is a backup program that backs up data to remote servers, other computers, or hard drives. The old device does not need to be online. Available devices from within the user's account are displayed. From the action menu, choose Replace a Device. ![]() Navigate to the new device's device details. With Entware-ng installed, I installed crash plan (from scratch). Sign in to the Code42 console as an administrator. Now I see what you are referring to, I have installed it but it still doesn't work. You are correct, mine stopped in july without having Entware-ng. ![]() What can I do? Is there some way to prevent it from trying to update? Or trick it into thinking that it doesn't need to update? 2nd, there is 4 TB up there and that would take me months to throw back. I can't start all over, it would make me erase everything from crash plan, of which I don't have copies of somethings. Now it seems like it works but when I choose adopt my previous backup, it tries to update itself and then crashes never to be seen again. After playing with it and trying several times to get it back up I decided to reinstall the package. I check with crash plan and it says that my qnap has not been backing up for days. CrashPlan PROe is informing you that adopting a prior backup will erase the backup created immediately after signing into. However, I wake up one morning last week and I can't attach to crash plan interface via client (headless of course) no matter what I try. In the past I was able to adopt a backup using your package and actually have been plugging along just fine for almost a year. You are so awesome to take the time to create and maintain this! First, thank you for taking the time to create this package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |