![]() I installed your docker and added another path variable to bring in my unassigned device for local backups, I realize now I could have just changed how I mapped storage as you will see in my screenshot. Made sure my backups were up to date and stopped the gfjardim docker. I followed the instructions you provided to migrate my account to Pro. Thank you for providing this docker so quickly. Warning! Make sure to read the Taking Over Existing Backup section from the documentation if you are installing this container to replace another CrashPlan installation (from Windows, Linux, Mac or even another Docker container). Post any questions or issues relating to this docker in this thread. Make sure to look at the complete documentation, available on Github ! It also has a very nice, mobile-friendly web UI to access CrashPlan PRO's graphical interface and is actively supported! ![]() This container is based on Alpine Linux, meaning that its size is very small. See the dedicated section in the documentation for details. NOTE: If you are using another container, you can still migrate using this container. ![]() Once you are happy with the transition, you can remove the old CrashPlan container and its appdata folder. Login to your unRAID server and copy the app data (the goal being that the new docker re-use the same data):Ĭp -a /mnt/user/appdata/CrashPlan /mnt/user/appdata/CrashPlanPROįinally, install this container using the Community Applications plugin.Īfter these steps, everything should work like before. Stop the CrashPlan (Home version) container. Make sure you have migrated your CrashPlan account. If you want to migrate from CrashPlan for Home and are using my CrashPlan container, follow these steps for a smooth transition: Support for CrashPlan PRO (aka CrashPlan for Small Business) docker containerĪpplication Name: CrashPlan PRO (aka CrashPlan for Small Business) ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |