Database went into suspect mode database corruption One of our servers got migrated from one data center to other data center using third party tool called Zerto. After migration two databases went into suspect mode. Errors in the log: The log scan number (40359:103:2) passed to log scan in database <db name> is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup During undoing of a logged operation in database <db name> , an error occurred…