Developers Guide

Volume management
24 Dell EMC SC Series with Red Hat Enterprise Linux 7x | CML1071
2.9.2 Recovering from a boot from SAN snapshot view volume
Snapshot view volumes of a boot from SAN volume, when presented back to the same host, are
automatically bootable. This is because the volumes are now tracked using their unique and identifying UUID
values inside of /etc/fstab and /boot/grub2/grub.cfg instead of using their system device file names.
Additionally, the entries and aliases within /etc/multipath/bindings and /etc/multipath/wwids are also
automatically updated to reflect any boot device changes.
Note: Ensure that the original boot from SAN volume is no longer mapped to the server object to prevent any
boot time conflict when attempting to boot from the alternately mapped snapshot view volume. The snapshot
view volume should also be mapped to the host as LUN ID 0.
2.9.3 Configuring the HBA BIOS
The HBA BIOS configuration on each Linux host should be configured to identify all SC Series storage
controller World Wide Port Names (WWPNs) of all the active and alternate controllers. The configuration of
the HBA BIOS in this manner ensures that any boot from SAN volumes will remain visible and accessible on
all fabric-zoned controller paths in the event of any SC Series storage controller failover or other path failure
events.