![]() The only way I have been successful is to create the container without volume specification and then add manually through the GUI. Take advantage of the ease-of-use of CrashPlan’s self-service file backup and recovery workflow while protecting all of your organization’s vital data from ransomware or other calamity. Regardless of the error, if I open the GUI I see all volumes I originally specified on the command line when the container was created however, when I start the container, I get a docker API error. Enterprise-grade data protection billed monthly at 9.99 per-device. After removing the container and re-issuing the command without any changes, I might receive an error about the fifth volume specified. I found some upgrade.msi files in programdat\crashplan, but none of them worked. ![]() For example, if I have 7 different volumes specified, the first time I run it might complain about the third volume specified. Search within r/Crashplan r/Crashplan Log In Sign Up User account menu Found the internet 2 Issues with Upgrade.msi Close 2 Posted by u/NCHeavyHunter 4 years ago Issues with Upgrade.msi I am unable to update or uninstall crashplan because upgrade.msi is missing. I really wanted to incorporate all of the volumes on the command line using the -v switch (one for each), but when I do this I get a daemon error about a particular volume specified. When I originally create the container using "sudo docker run -d -name=crashplan-pro -p 5800:5800 -p 5900:5900 jlesage/crashplan-pro" everything works fine and I can go through the GUI to map the various volumes. I wanted to run it by you all and see what you think. I was able to get everything updated and back to syncing, but there was one hiccup that will prove to be an annoyance for future updates. Thanks all for the information - especially for the detailed instructions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |