SnapCenter performs an application-aware restore by interacting directly with the Microsoft SQL Server instance. The automated workflow requires taking the target database offline, restoring the underlying storage LUNs from the selected Snapshot copy, and then bringing the database back online to complete the recovery process. For SnapCenter to execute these application-level commands and manage the database state, the SQL Server service must be running on the host. If the service is stopped, SnapCenter cannot communicate with the database instance, and the restore operation will fail.

A. Multipathing is a high-availability best practice for iSCSI but is not a strict requirement for a SnapCenter restore operation to function.

C. The SQL Server service must be running for SnapCenter to perform the application-specific steps of the restore, such as taking the database offline and online.

D. The iSCSI service (initiator) must be enabled and running for the host to access the LUNs where the database files are stored.

1. NetApp SnapCenter 5.0 Data Protection Guide for Microsoft SQL Server, Page 53, "Restore and recover Microsoft SQL Server databases". The documented workflow describes steps that SnapCenter performs on the database, such as "takes the database offline" and "brings the database online." These actions can only be performed if the SQL Server service is running and accessible to the SnapCenter plug-in.

2. NetApp Technical Report TR-4590: SnapCenter Best Practices, Page 10, Section 3.2 "SnapCenter Plug-In for Microsoft SQL Server". The document states, "The SnapCenter Plug-in for Microsoft SQL Server automates the backup and restore of Microsoft SQL Server databases." This automation relies on the plug-in's ability to communicate with a running SQL Server instance to quiesce and manage the database state during operations.