It appears to be related to backup and block corruption. However, I have reviewed the situation and can confirm that there is no block corruption in the database. I have attached an excerpt from the validation for your reference. Based on this, you can safely ignore the block corruption alert.
Additionally, the initial alert regarding the backup process can also be disregarded, as it pertains to routine backup operations.
One point of concern is that the backup is currently running from the BCP site, whereas it should ideally be performed from the primary site. According to our policy, backups should not be configured at the BCP site unless there are exceptional approvals. It seems the backup has been running from the BCP site since August 4th, which might be due to recent BCM activities.
Please let me know if you need any further information or if there are additional actions required on this matter.
0 comments:
Post a Comment