A company is running nightly backups to satisfy their 24-hour RPO. There are two critical applications that cannot be offline more than 4 hours with no more than an hour of data loss.
How can this be accomplished?
To meet the stringent Recovery Time Objective (RTO) of 4 hours and Recovery Point Objective (RPO) of 1 hour for the two critical applications, the most suitable approach is to use a combination of backup copy jobs and hourly VM replication, which corresponds to answer C. Backup copy jobs can ensure that backups are available offsite for disaster recovery purposes, while VM replication provides the ability to quickly failover to a replica VM in case of a primary VM failure, thereby minimizing downtime. Veeam's replication capabilities are designed to create exact copies of VMs at regular intervals, which can then be rapidly activated in case of a failure. This strategy ensures that the applications can be brought back online within the 4-hour RTO, with data loss not exceeding the 1-hour RPO, thus meeting the company's stringent data protection requirements for these critical applications.
The administrator of a VMware environment backed up by Veeam Backup & Replication has a critical server with corruption on one of its three data drives. What is the fastest way to bring this drive back online with the least disruption to business?
The fastest way to bring a corrupted data drive back online with the least disruption in a VMware environment is through Instant Disk Recovery. This feature allows the administrator to quickly restore the specific affected disk from a backup, minimizing downtime and impact on business operations. Reference: Veeam Backup & Replication User Guide, Veeam Instant Disk Recovery Guide
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.
The compliance team is requesting a Veeam engineer complete the following tasks on the backup environment:
1. All image-level backups are to be tested and validated
2. Recovery verification with a well-known malware scan
3. Send an email to the Veeam engineer with test results
What is the recovery verification function to meet this requirement?
SureBackup is the Veeam technology that allows you to verify the recoverability of backups. It can automatically verify the integrity of the backup, test it for malware (with the aid of third-party antivirus software), and send email notifications upon the completion of the job. This is accomplished by running the backups in an isolated environment called a Virtual Lab, without making any changes to the actual production environment. By using SureBackup, Veeam engineers can ensure that image-level backups are recoverable, can be verified against malware, and can report the results via email, thus meeting the compliance team's requests.
A number of VMs are running as interdependent applications. They need to fail over, one by one, as a group. What method should be used to do this?
To ensure VMs running interdependent applications fail over one by one, as a group, the method to use is D: Failover plan. In Veeam Backup & Replication, a failover plan allows for the orchestration of a group of replicas to fail over in a predefined sequence. This includes the capability to set up delays between starting each VM, which is crucial for interdependent applications that must be started in a specific order to function correctly. The failover plan ensures that dependencies among the group are respected and that the startup sequence follows the correct order, enabling a smooth and organized transition to the failover state.
