For a client’s operating system to be recovered using the integrated BMR feature, eligible file-level backups for the client must reside on a Unitrends Recovery-Series or UEB backup system or replication target running release 7.4 or higher. A file-level backup is eligible for an integrated BMR if it meets all of the following criteria:
• It is successful.
• It is a full, differential, or incremental file-level backup that contains disk metadata. Disk metadata is captured in all file-level backups run with agent version 7.4 or higher unless you exclude critical volumes using selection lists. If you are using selection lists, and you want to determine whether a backup is eligible, see To verify that a file-level backup is eligible for integrated bare metal recovery.
• It was run with agent version 7.4 or higher.
Note: Bare metal backups cannot be used for integrated bare metal recovery. You can recover an operating system from a bare metal backup using the procedure described in Windows image-based bare metal recovery . However, if you have eligible file-level backups for a failed client, it is recommended that you use one of these backups to perform an integrated bare metal recovery to take advantage of significant performance enhancements.
1 View backup details, as described in To view backup details.
2 Verify that for the Category DiskMetadata, the Entry is Yes.
If the Entry is Yes, then the backup contains disk metadata, and it is eligible for integrated BMR. If the Entry is No, then the backup does not contain disk metadata, and it is not eligible.
3 Repeat Step 2 as needed to determine whether other backups are eligible. If no eligible backups reside on your backup system, then you must run new file-level backups that capture disk metadata if you want to use integrated BMR in the event that the client fails. For details, see About executing file-level backups.