
Understanding persistent binding
139
Troubleshooting
Figure 78 Original configuration before the reboot
Figure 79 shows the same host after the cable attached to HBA0 has
been removed and the host rebooted. Since Windows was unable to
do a discovery on HBA0, it assigned \\.\PHYSICALDRIVE0 to the
first device it discovered. In this case, that first device is connected to
HBA1. Due to the shift, any software application accessing
\\.\PHYSICALDRIVE0 will not find data previously written on the
original \\.\PHYSICALDRIVE0.
Figure 79 Host after the rebooted
The default driver behavior does not store target bindings between
host reboots. The bindings are dynamically generated by the HBA
when new target devices are detected.
Note: Tape devices are treated the same as disk devices in Windows with
respect to persistent binding. Refer to your tape device documentation for
more information.
HBA 0
HBA 1
HBA 2
PHYSICALDRIVE0
PHYSICALDRIVE4
PHYSICALDRIVE8
Windows
Host
HBA 0
HBA 1
HBA 2
Windows
Host
PHYSICALDRIVE0
PHYSICALDRIVE4
Comentarios a estos manuales