A 3-node Microsoft SQL Always On cluster is running in a VMware environment. The RPOs are:
• 1 day for the cluster nodes
• 15 minutes for the log files
How should the cluster be backed up?
Correct Answer:A
For backing up a 3-node Microsoft SQL Always On cluster running in a VMware environment with the specified Recovery Point Objectives (RPOs), the most suitable option is A: Veeam Backup and Replication - Create a VMware backup job, include the 3 nodes of the cluster. Use Application-Aware Processing to back up the transaction logs every 15 minutes. This approach allows for the entire SQL cluster nodes to be backed up as part of a regular VM backup job, which satisfies the 1-day RPO for the cluster nodes. The Application-Aware Processing feature of Veeam Backup & Replication ensures that the SQL databases are in a consistent state during backup. Moreover, this feature allows for the transaction logs to be backed up separately at a more frequent interval, in this case, every 15 minutes, meeting the 15-minute RPO requirement for the log files. This dual approach ensures comprehensive protection for both the SQL cluster nodes and the critical transaction logs, aligning with the specified RPOs.
A company has an application on a VMware VM that stores customer photos. Customers may request their photos be removed at any time. The server needs to be restored from last week's backup. What Veeam restore process allows for custom scripting to be run to automatically remove any required photos before the server is returned to production?
Correct Answer:C
The Veeam restore process that allows for custom scripting to be run before returning a server to production is Staged Restore. This feature enables administrators to perform necessary operations, like running a script to remove customer photos, during the restore process before the VM is brought back online.References: Veeam Backup & Replication User Guide, Veeam Staged Restore Guide
Why is it recommended to have at least one backup proxy server in each site when defining a replica job?
Correct Answer:E
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.
Company security policy states that backups must be copied to a remote location within 8 hours.
What step can a backup administrator take to receive an alert automatically if the backup copy job violates the company's policy?
Correct Answer:D
To receive an automatic alert if the backup copy job violates the company's 8-hour policy for copying backups to a remote location, the backup administrator should enable the appropriate Recovery Point Objective (RPO) monitor. This feature tracks the age of the latest backup and alerts when it exceeds the defined RPO.References: Veeam Backup & Replication Documentation, Veeam RPO Monitoring and Reporting Guide
A customer wants to set up a Scale-Out Backup Repository. Due to malware concerns, immutability is recommended. An on-premises server can be used to hold primary backups, but it can only hold about 21 days of backups. A copy of the backups should be stored in AWS. The retention for all backups is 60 days.
Which configuration of a Scale-out Backup repository meets these requirements?
Correct Answer:D
To meet the requirements of setting up a Scale-Out Backup Repository (SOBR) with immutability for malware protection and specific retention policies, the most fitting configuration is D: Copy and move mode with a Performance Tier configured on a Linux Hardened Repository using the XFS file system and immutability set for 21 days, and a Capacity Tier on Amazon S3 with immutability set for 60 days. This setup utilizes the copy and move mode to ensure that backups are first stored on the on-premises Linux Hardened Repository with an immutability setting that prevents modifications to backups, providing protection against malware for the most recent 21 days of backups. As this on- premises server has limited capacity, older backups beyond 21 days are moved to the Capacity Tier in Amazon S3, where they are also protected with immutability for the entire 60-day retention period. This configuration leverages the strengths of both on-premises and cloud storage while ensuring that all backups are protected from modification or deletion by immutability, aligning with the customer's malware protection concerns and retention requirements.
What is a Recovery Point Objective (RPO) in regards to disaster recovery?
Correct Answer:B
In the context of disaster recovery, the Recovery Point Objective (RPO) is best defined by option B: The acceptable data loss measured in time that can be tolerated. RPO is a critical metric in disaster recovery and business continuity planning that specifies the maximum amount of data (measured in time) that an organization can afford to lose in the event of a disaster or system failure. It effectively sets the limit for how frequently data backups or replications should occur. For instance, an RPO of 4 hours means that the organization must be able to recover data from no more than 4 hours prior to the disaster, implying that backup or replication operations should occur at least every 4 hours. Establishing an RPO is essential for developing an effective data protection strategy, as it guides the choice of backup methodologies and technologies to meet the organization's tolerance for data loss.