Now got a corruption on MSDB ... so might well be associated with something else.
I wonder if the DR Copy that their IT people are using is mucking about with SQL itself. Or is that sort of "suspend I/O whilst a low level copy is made" 100% robust?
Server: Msg 8977, Level 16, State 1, Line 3
Table error: Object ID 149575571, index ID 1, partition ID 72057594039828480, alloc unit ID 72057594040811520 (type In-row data). Parent node for page (1:6547) was not encountered.
Server: Msg 8937, Level 16, State 1, Line 3
Table error: Object ID 149575571, index ID 1, partition ID 72057594039828480, alloc unit ID 72057594040811520 (type In-row data). B-tree page (1:12525) has two parent nodes (1:5086), slot 0 and (1:6589), slot 407.
Server: Msg 8934, Level 16, State 1, Line 3
Table error: Object ID 149575571, index ID 1, partition ID 72057594039828480, alloc unit ID 72057594040811520 (type In-row data). The high key value on page (1:27385) (level 0) is not less than the low key value in the parent (1:5086), slot 0 of the next page (1:12525).
Server: Msg 8934, Level 16, State 1, Line 3
Table error: Object ID 149575571, index ID 1, partition ID 72057594039828480, alloc unit ID 72057594040811520 (type In-row data). The high key value on page (1:27385) (level 0) is not less than the low key value in the parent (1:5086), slot 0 of the next page (1:12525).
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sysjobhistory' (object ID 149575571).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'msdb'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb).