3.0.0.368 upgrade - ALL DEVICES GONE!

[phuz]

My devices, events, EVERYTHING....GONE!

WTF.

11/1/2017 12:19:39 PM ~!~Database~!~Opening (Mode=Read Only) up HomeSeer database C:\Program Files\HomeSeer HS3\Data\HomeSeerData.hsd
11/1/2017 12:19:39 PM ~!~Error~!~Failed to get version information from configuration database (invalid database), data NOT loaded.
11/1/2017 12:19:39 PM ~!~Startup~!~HomeSeer version is: 3.0.0.368
11/1/2017 12:19:39 PM ~!~Startup~!~Creating Speaker Client Interface Object...
11/1/2017 12:19:39 PM ~!~Startup~!~This version of HomeSeer is registered as a HS3PRO version.
11/1/2017 12:19:39 PM ~!~Warning~!~Plug-in developer mode is enabled and connection time out is set to 900000 milliseconds.
11/1/2017 12:19:39 PM ~!~Info~!~Remote plug-in API interface started on port 10400
11/1/2017 12:19:39 PM ~!~Startup~!~Checking for available plug-ins
11/1/2017 12:19:39 PM ~!~Plug-In~!~Found plug-in: weatherXML, version: 3.0.0.73
11/1/2017 12:19:39 PM ~!~Plug-In~!~Found plug-in: Z-Wave, version: 3.0.1.137
11/1/2017 12:19:39 PM ~!~Startup~!~Initializing Plug-Ins
11/1/2017 12:19:39 PM ~!~Info~!~Plugin weatherXML has connected. IP:127.0.0.1:49567
11/1/2017 12:19:40 PM ~!~Plug-In~!~Finished initializing plug-in weatherXML
11/1/2017 12:19:40 PM ~!~Info~!~Plugin Z-Wave has connected. IP:127.0.0.1:49569
11/1/2017 12:19:40 PM ~!~Z-Wave~!~InitIO called, plug-in version 3.0.1.137 is being initialized...
11/1/2017 12:19:40 PM ~!~Z-Wave Warning~!~Z-Wave database file does not exist, so a new database is being created in C:\Program Files\HomeSeer HS3\Data\Z-Wave\Z-Wave2.db
11/1/2017 12:19:40 PM ~!~Z-Wave~!~Created new database C:\Program Files\HomeSeer HS3\Data\Z-Wave\Z-Wave2.db
11/1/2017 12:19:40 PM ~!~Z-Wave~!~465 Simple AV Control Command Class Control Commands have been loaded successfully.

[Rupp]

Did you try loading one of the backups? Did you back up your installation prior to upgrading?

[phuz]

Did you try loading one of the backups? Did you back up your installation prior to upgrading?

I don't back them up. Everything of mine is virtualized and I run Veeam backups daily, so I'm in the process of restoring it now. I just noticed that my HomeSeerData.hsd file is a whopping 1Kb in size. My confidence in HS continues to decline.

But honestly, it wouldn't be hard for HS3 developers to backup the database prior to upgrades. I'm shocked this isn't be done.

[Rupp]

Yea, VM can be hokey from time to time. Check out the automatic backups in this path.
C:\Program Files (x86)\HomeSeer HS3\Data\Backup

[phuz]

Yea, VM can be hokey from time to time. Check out the automatic backups in this path.
C:\Program Files (x86)\HomeSeer HS3\Data\Backup

VM has never been hokey for me. My ESXi environment has been rock solid. There's a reason industries run on VMWare. And I'll leave my HS3 server running for months at a time without issue. Funny how an "upgrade" is what breaks it. Has nothing to do with being virtualized.

All the backups in my backup folder are dated 4/23/2015, which is just beyond comical. I guess I'll just add a task to copy the HSD daily.

[randy]

I don't back them up. Everything of mine is virtualized and I run Veeam backups daily, so I'm in the process of restoring it now. I just noticed that my HomeSeerData.hsd file is a whopping 1Kb in size. My confidence in HS continues to decline.

But honestly, it wouldn't be hard for HS3 developers to backup the database prior to upgrades. I'm shocked this isn't be done.

HomeSeer does create automatic backups. There are 10 backups in the /data directory. One is created each time HomeSeer is restarted. They will be named HomeSeerData_X.hsd, where X is a number from 1-10. The numbers are not necessarily in the order the backups are created, but you can tell by the timestamp on the file. Below 1045Home_10.hsd (I used my own naming on the file) is the most recent.




Shutdown HomeSeer. Backup the entire /data subdirectory. Find the database that is timestamped just before you upgraded, delete HomeSeer.hsd, then rename the correct backup to HomeSeer.hsd.

Alternately you can select a different database (I.E. HomeSeer_3.hsd) from the setup screen and run it. The downside of this is that your backups will be created using the new name such as HomeSeer_3_X.hsd.