Module Admin Fatal Error on Secondary server

After installing some updates via Module Admin last week I have been receiving Fatal Errors on our Secondary server when re-visiting the Module Admin page (error attached)

We have a primary/secondary setup with the secondary taking a backup of the primary once a day and restoring to itself. Since the last batch of updates the primary is working fine however when you goto Module Admin for the first time on the secondary after the restore has taken place you get the fatal error. The error is also raised with the nightly cron checking for updates resulting in an email being sent containing the fatal text.

What I have found is that visiting the page once, getting the error then refreshing fixes it until the next backup/restore takes place

On looking at the SQL DB the installid in module_xml is identical on both servers, when you hit the page with the fatal error the DB is written with the correct installid and the error goes away only to return once again after the next nightly backup/restore

The primary is unaffected by this