An administrator needs to recover specific configuration files from a backup of a Linux virtual machine named `vm-prod-lnx`. The virtual machine's storage layout uses Logical Volume Manager (LVM) across multiple managed disks.
The administrator downloads the Item-Level Recovery (ILR) script from the Recovery Services vault and attempts to execute it directly on `vm-prod-lnx` to mount the recovery point. However, the script fails to mount the logical volumes because of a volume group name and UUID conflict with the active system.
What should the administrator do to retrieve the required configuration files?
- AInitiate a 'Replace existing' restore operation in the Recovery Services vault to automatically overwrite the conflicting volume groups on `vm-prod-lnx`.
- BRun the recovery script on a Windows virtual machine deployed in the same virtual network, mount the volumes, and copy the files to `vm-prod-lnx` over a network share.
- Run the recovery script on a separate Linux virtual machine deployed in the same virtual network, mount the volumes, and transfer the files to `vm-prod-lnx`.Cevap
- DModify the downloaded script parameters to force-rename the active volume groups on `vm-prod-lnx` before mounting the backup disks.
Cevap
Run the recovery script on a separate Linux virtual machine deployed in the same virtual network, mount the volumes, and transfer the files to the original virtual machine.
Running the recovery script on a separate Linux helper virtual machine is the recommended approach when LVM volume group conflicts prevent mounting on the original VM. Because the helper VM does not have the same volume group names or UUIDs active, the script can mount the disks without conflict, allowing the administrator to copy the desired files back to the original VM.
Adım Adım Çözüm
Anahtar Kavram
Azure Backup Item-Level Recovery (ILR) for Linux VMs with LVM requires a helper VM when volume group conflicts occur.
Tahmini Süre:2m 0s