Can't restore K2000 Database
So here is what I have resetup on my new K2000. I have to recreate all of my Labels, setup all of the users, setup Ldap authentication, reset the time server, all links for my dozen RSAs and K1000, reset the general settings section which include action buttons, share passwords, boot manager settings, and default boot environments. Thank goodness my old K2000 is still up and running (even though it had a power supply failure recently) so I can manually copy my settings. Now granted most of these settings can be recreated easily except for the labels. What if I have 100 labels setup? How do you expect me to remember all of these labels? Why is it exceptable for me to spend a day or 2 to resetup my K2000 so that it is useable, when I could just restore the database and have everything up and running in an hour or 2? Why do I even have an option to backup the database?
Sorry about the long rant here. I have made a feature request for the K2000 to add this to the product on Kace's user voice site. If you would like to support this feature request, you can visit my request at http://kace.uservoice.com/forums/82717-k2000/suggestions/2015931-be-able-to-restore-the-k2000-database
Answers (2)
Just wrapping up a migration from a vk2000 with a 250GB datastore to a NEWLY deployed vk2000 with a 500GB datastore. I found this KACE KB article http://www.kace.com/support/resources/kb/article/What-is-the-best-practice-for-backing-up-the-K2000 which seems to indicate that the database file is not necessary for restore as long as you have all of the other packages.
Fortunately I'm not in a disaster recovery situation and have both VK2000's running side-by-side (with different IPs) in case I need to manually enter some non-packaged configuration data.
Anyone else have experience with this 'restore to another box' scenario?
I realize this question is almost a year old, but I came across it while looking for other backup/restore posts. I can confirm that in the current version it is still an issue, however I believe there is a work-around. You should be able retrieve the database backup from the restore share, or if you are using the off board package transfer, from whatever server you are sending it to, and then "upload package for import" from the drop down menu on the import screen.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.