Lost configuration after server restart

[Arturo Alvarado]

After a server restart Jira hast lost it's configuration.  It started asking questions like it was a new server, which it wasn't.

If I go into the /var/atlassian/application-data/jira/database the database file looks large enough to have the actual data.
-rw-r----- 1 jira jira 1343488 Aug 18 03:24 h2db.mv.db 

but all users and projects where lost.

How can I get all my projects back?

Even the dbconfig file has an old date.

-rw-r----- 1 jira jira 884 Aug 3 2017 dbconfig.xml

And contents look normal.

<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>h2</database-type>
<schema-name>PUBLIC</schema-name>
<jdbc-datasource>
<url>jdbc:h2:file:/var/atlassian/application-data/jira/database/h2db</url>
<driver-class>org.h2.Driver</driver-class>
<username>sa</username>
<password></password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<min-evictable-idle-time-millis>4000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>5000</time-between-eviction-runs-millis>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
</jdbc-datasource>
</jira-database-config>

[Arturo Alvarado · Accepted solution]

Nevermind, I just pulled an backup and noticed that the h2db.mv.db file was way larger, so I guess the file got damaged or destroyed.

[Nic Brough -Adaptavist-]

Sounds  like it.  There's a good reason the docs all say you should not use h2 for anything other than dev and test.

[Arturo Alvarado]

Yeah, lesson learned.  Thank you.