Bitbucket Data Center shared home and database synchronization limits

Database and Shared Home Consistency

Bitbucket Data Center relies on the synchronization between the database and the shared home directory for system integrity. During a recovery process following a failed upgrade, the database must be restored to a state that matches the specific snapshot of the shared home directory.

When an upgrade modifies the database schema, the application may encounter inconsistencies if the shared home directory contains configuration or plugin data generated by the newer version while the database has been rolled back to a previous version.

What are the specific behavioral risks when the shared home directory is not restored to the exact timestamp of the database snapshot? Does Bitbucket provide a mechanism to detect version mismatches between the shared home and the database schema during startup?