What must be manually addressed during a failover event with database-level protection?

During a failover event with database-level protection, SQL Server Agent jobs and linked servers must be manually addressed. This is because when a failover occurs, the system may not automatically redirect these jobs and references to linked servers to the new primary server where the database has failed over.

SQL Server Agent jobs, which typically schedule and execute tasks such as backups, maintenance plans, or batch jobs, will need to be reconfigured or validated after a failover to ensure they function correctly. The jobs might be set to execute against a specific server which is no longer the primary after the failover event.

Similarly, linked servers, which are used to execute queries against a remote SQL Server or other data sources, may also require reassessment and configuration after a failover to ensure that they can properly connect and function in the new environment.

Addressing these aspects ensures that the operational continuity of the database management tasks is maintained, contributing to the overall stability and performance of the databases after a failover scenario.