To protect a physical Windows server running Microsoft SQL 2020, the Veeam Agent should be used. Veeam Agent is designed to provide comprehensive backup and recovery for physical servers, including those running critical applications like Microsoft SQL Server.

By adding a capacity tier to the Scale-out Backup Repository and enabling the "Copy" option, the administrator can create a backup that automatically copies data to a different media type (object storage) and also ensures that the data is offsite. This is accomplished without creating additional backup or backup copy jobs. The "Copy" option allows for immediate copying of backups to the capacity tier, meeting the criteria specified.

In a situation where VMs are orphaned after a power outage but their disk files remain intact on the datastores, the most efficient way to restore these VMs with minimal data loss is C: Perform Restore VM Files and only restore the VM configuration files. This approach involves using Veeam Backup & Replication to restore only the necessary VMX files (for VMware) or equivalent configuration files for other hypervisors, which contain the settings and configuration of the VMs.
Since the disk files are still present and intact on the datastores, restoring the configuration files allows the VMs to be re- registered with the hypervisor and brought back online quickly, without the need to transfer or restore the entire VM disk files, thus minimizing downtime and data loss.

In Veeam Backup & Replication, to utilize AWS S3 Glacier for long-term storage, the AWS S3 must first be added as a Capacity Tier within the Scale-Out Backup Repository (SOBR). This step is necessary before backups can be moved to Glacier. Once S3 is established as the Capacity Tier, the policies for moving backups to Glacier can be configured based on the retention requirements (in this case, after 90 days). This approach ensures that the monthly full backups are initially stored in S3 and thenoffloaded to Glacier for cost-effective long-term retention.References:
* Veeam Documentation: Scale-Out Backup Repository
* Veeam Help Center: AWS S3 as Capacity Tier and Archive Tier Configuration

Explanation
"Failover Now: Failover now refers to an immediate response to an unexpected system or service failure. In this case, the primary system or service experiencesan unplanned outage or becomes unavailable, and the failover process is triggered immediately to shift the workload to a secondary system or service."