Default post-recovery health checks for cleanroom

After cleanroom recovery is complete, by default, Commvault runs scripts to validate database and directory health.

Windows

Oracle database monitoring and self-healing

• Automated discovery: Finds all Oracle services configured for automatic startup, removing the need for manual checks.

• Automated recovery: Attempts to fix databases that are not in the OPEN state (for example, MOUNTED, STARTED, or idle) and return them to a healthy state.

SQL Server health check and reporting

• Automatic instance detection: Detects and checks all SQL Server instances on the local machine.

• Connectivity validation: Connects to each instance and runs a query to confirm it is both running and accessible.

• System integration: Returns an exit code (0 for success, 1 for failure) to indicate SQL Server status.

Active Directory health diagnostics

• Centralized health check: Runs critical health tests across all domain controllers in the Active Directory forest.

• Multi-point diagnostics: Performs tests such as ping, service status, and dcdiag checks for replication, DNS, and FSMO roles.

• Flexible reporting: Generates reports in HTML, JSON, or console formats for different use cases.

Linux

Oracle database monitoring and auto-recovery

• Auto-discovery: Scans /etc/oratab for databases marked for autostart.

• Self-healing: Attempts to open or recover instances that are MOUNTED or not open.

• Clear reporting: Displays status for each database and an overall success/failure summary.

• Clean execution: Creates and deletes temporary helper scripts during execution.

• Integration ready: Returns exit codes (0 = healthy, 1 = issues) for monitoring tools.

SQL Server service monitoring

• Service check: Uses systemctl to verify if the mssql-server service is running.

• Simple reporting: Prints a clear running or not running message.

• Exit code: Returns 0 if running, 1 if not, for integration with monitoring tools.