A planned failover of three VMs has just completed successfully, starting the VMs at the disaster recovery location. What next actions are available for the failover plan?
After completing a planned failover for VMs to the disaster recovery site, the typical actions available in Veeam Backup & Replication for a failover plan are:
Undo: This allows you to reverse the failover and return the VMs to the original location.
Start: This would be used to initiate the failover plan if it needs to be executed again.
Edit: This option permits modifications to the failover plan.
Delete: This allows the removal of the failover plan if it is no longer needed. There are no options for Copy in the context of a failover plan, and the Cancel option is typically available before and during the failover process, not after completion.
Why is it recommended to have at least one backup proxy server in each site when defining a replica job?
Having at least one backup proxy server in each site when defining a replica job is recommended because the backup proxy servers are responsible for data processing and transfer. Having proxies in both sites enables a stable connection for VM data transfer across sites, as they handle the data compression, deduplication, and transfer processes. This setup ensures that data is efficiently moved from one site to another, thereby making replication more resilient and reliable. Proxies do not automatically restart replication after failure (A), remove the need for VM snapshots during transit (B and F), or enable automatic WAN acceleration (D), although they can work in conjunction with WAN accelerators if configured to do so. They also don't directly deduplicate data during transit across the WAN (C), although they do compress and optimize it for transfer.
A physical Windows server protected by a centrally managed Veeam agent is physically damaged. A Hyper-V infrastructure is available, and the physical server is eligible for virtualization.
Which recovery step provides the lowest possible RTO?
Instant VM Recovery is a feature in Veeam that allows you to start a virtual machine directly from a backup file without waiting for the full restore. Using Instant VM Recovery to Hyper-V is the best option for achieving the lowest possible Recovery Time Objective (RTO) because it allows the damaged physical server's backup to be run as a VM in the Hyper-V environment almost immediately. The Veeam Agent for Microsoft Windows supports Instant Recovery to a Hyper-V VM, which will enable you to restore service quickly while you can plan for a more permanent recovery solution.
To be able to increase backup retention, the company has bought a Data Domain deduplication appliance.
After setting up the jobs to use it, the backup administrator observes an increase of resource consumption on the backup server. The proxy configuration has not been modified.
What is causing the issue?
When integrating a Data Domain deduplication appliance with Veeam Backup & Replication, it is typically used as a backup repository. The backup server may need to take on the gateway role, especially if the Data Domain is integrated over NFS or CIFS. This means that the backup server will be responsible for processing the data flow between the Veeam proxies and the deduplication appliance. If the gateway server (backup server) is not well-resourced, this additional workload can cause an increase in resource consumption on the backup server. The appliance's resources and the SSL certificate are not related to increased resource consumption on the backup server, and simply needing additional resources for deduplication (D) is not specific enough without indicating the gateway role.
A company wants to ensure that, during a replication failover, database servers boot before the application servers. How can this be accomplished?
Veeam Backup & Replication allows you to set up failover plans to control the order in which VMs are started during a failover. By creating a failover plan, you can specify that the database servers boot before the application servers. This is achieved by setting up VM dependencies within the failover plan, ensuring that the database servers (which are critical for the application servers to function) are operational before the application servers start. Creating a disaster recovery template (B), creating a replica mapping (C), or initiating a planned failover (D) does not directly address the boot order of the servers during failover.
