Installation guide

Understanding persistent binding

187

Troubleshooting

Figure 126 Original configuration before the reboot

Figure 127 shows the same host after the cable attached to adapter0

has been removed and the host rebooted. Since Windows was unable

to do a discovery on adapter 0, it assigned \\.\PHYSICALDRIVE0

to the first device it discovered. In this case, that first device is

connected to adapter1. Due to the shift, any software application

accessing \\.\PHYSICALDRIVE0 will not find data previously

written on the original \\.\PHYSICALDRIVE0.

Figure 127 Host after the rebooted

The default driver behavior does not store target bindings between

host reboots. The bindings are dynamically generated by the adapter

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