AUTO-RESPONSE: No automated response will occur.IMPACT: Fault tolerance of the pool may be compromised.REC-ACTION: Run 'zpool status -x' and replace the bad device.For each disk in the computer you may see the error message. However, whenyou log on and run thezpool status -xcommand, you see the following message:all pools are healthyThat is because of the ZFS import operation that is done during the first bootsequence. Bare Metal Restore (BMR) restores storage pools and contents in theBMR restoration environment and later imports to the client environment duringfirst boot. That can cause an error message or a warning message during the firstboot operation.These messages only occur during the first boot operation and you can safely ignorethem.BMR may not format or clear the ZFS metadataIf you opt for the creation of a ZFS storage pool on small number of disks during adissimilar disk restore (DDR), Bare Metal Restore (BMR) does not format or clearthe ZFS metadata on the disks that remain. Because of that, if you attempt to usethose disks to create other storage pools, you may see an error message that statesa disk is in use under the ZFS storage pool.37Operational notesNetBackup Bare Metal Restore operational notes
To work around this issue, use the-foption to create a new storage pool on thosedisks.Coexistence of two BMR-supported multi-path solutions can causeissuesCoexistence of two Bare Metal Restore (BMR)-supported multi-path solutions (EMCPowerPath and Linux native multi-path) with both actively configured on a clientcan cause issues and is not supported by BMR.A BMR issue can result if a multi-device that is configured over a SAN disk usingthe EMC PowerPath name, and the SAN disk is under both EMC PowerPath andthe Linux Native multi-path. In addition, this configuration is unsupported. However,if the same multi-device is configured over a SAN disk using the Linux nativemulti-path name then it works with BMR.A BMR restore may fail during a Linux DDR scenario between internaldisk and SAN diskA Bare Metal Restore (BMR) restore may fail during a Linux dissimilar disk restore(DDR) scenario from internal disk to SAN disk and vice versa.BMR does not consider the disk ordering in the BIOS. For SAN disk to an internalsystem disk, the restore may not work as expected because of the disk orderingchanges in the BIOS. This issue may be more common in GRUB installations.If you remove SAN disks before restoration, then the restore may work properlywith the existing BIOS ordering.BMR backups may fail on Citrix XenCenter virtualization due to disknamingBare Metal Restore (BMR) can only support disk naming conventions such ashdX,sdX,cXDn, and so forth.BMR backups can fail on Citrix XenCenter virtualization for the following reasons:■BMR does not recognize disk names such asxvdX, which are newly introducedon Citrix XenCenter virtualization. This issue is due to the Xen para-virtual driversthat are introduced in this type of virtual environment.
You've reached the end of your free preview.
Want to read all 105 pages?
........., Client-server, Windows PowerShell, NetBackup