In case of a disaster (lost DB, no backups) or after a hard crash, it would be nice to have a cli command to scan on-disc recordings and make sure the db state matches the on-disk state.
Most of the db state can be recovered from the original metadata.xml files in the storage directory. The tenant name is part of the storage path and also known. The current publish/unpublish state can be derived from the presence of symlinks in the playback directory. Changed metadata is not stored on disk, though. An additional json file in the storage directory would solve this issue and allow complete recovery from a lost database.
In case of a disaster (lost DB, no backups) or after a hard crash, it would be nice to have a cli command to scan on-disc recordings and make sure the db state matches the on-disk state.
Most of the db state can be recovered from the original
metadata.xmlfiles in the storage directory. The tenant name is part of the storage path and also known. The current publish/unpublish state can be derived from the presence of symlinks in the playback directory. Changed metadata is not stored on disk, though. An additional json file in the storage directory would solve this issue and allow complete recovery from a lost database.