Assuming you saw this recently, this is due to a recent bit of high-priority maintenance work to enable continuous backups on shared databases — involving a server restart. You shouldn’t worry about this error, provided it does not reproduce. I don’t think that’s very likely, so happy hacking!