One day after I updated Crashplan enterprise version I tried to log in to Crashplan PROe console only to find out that I am unable to.
I made a colossal mistake. I updated installation with several newer versions, one after the other. I didn’t check after each upgrade if I everything works. I should have waited for a while between each upgrade or at least restart the server. Thinking why I did that, I realized it was due to the fact that in the past I never had a problem and I was a bit limited with time.
Instead of regular login I was presented with a new user login. I couldn’t log in, even if I wanted to create a new user. Installation was really borked.
That got me worried, really worried and I kept thinking how to fix Crashplan Proe login without restoring backup dump. In a way I lost administration ability and ability to restore user data, by admin or by users. My next question was how to administer CrashPlan PROe and keep old data.
So I contacted support, I said hey guys, I cant login to PROe, how can I fix it. Their response was quick, solution: Sir that is easy, uninstall the PROe server, reinstall the PROe server and restore the backup dump before the upgrade. Well all good, but what happens If you don’t have the backup dump before doing upgrade?
Unfortunately Crashplan PROe only have one type of naming convention, that is proeserver backup. Why didn’t I checked the server after the upgrade you ask? Well I did, and it worked. Perhaps login was cached and I didn’t used it for a while, you know, its that kind of software that just works.
I was thinking for a while what to do, you see, you just cant delete all the history data and notify your users: There has been a change… you know what I mean.
Solution is very simple. Install Crashplan PROe on another server (version before the upgrade), create the same admin user you had before.
Copy backup dump to new server and restore it – BUT don’t close Crashplan page in the browser, that is the most important step.
Open CMD as admin, go to c:\program files\crash plan PROe server\bin
Type: restore_database.bat C:\temp\”name of your file.sql.gz” (be sure to enter your path to the db dump), make sure that services have started.
Now, go back to the browser and log in
You will be logged to good old CrashPlan PROe admin console and you will be able to go through the interface, create a db dump.
You can go back to the old server, uninstall problematic instance and install the proper version, import backup file and voila. Problem solved.