Persistent binding

This will be helpful during the time of Server Reboot, device re-scan cases where the c#t#d# changes are probable.

persistent binding in short will pair your hba and storage array port.
if persistent binding is setup correctly, the hba assigns a unique target id to a specific array.
with this you can be very sure that device IDs (cXtYdZ names) do not change when more than one arrays are zoned to the same port.

PB helps OS always to see SAN devices with the same SCSI target IDs across system reboots. every HBA manufacturer does it a bit differently, specific details can be found from HBA installation guides

One thing not yet mentioned is that it probably won't be an issue if you are using Windows hosts, but it can be a real issue if you don't use PB on some (most? all?) Unix hosts.

The only time I've seen it required on Windows hosts is when connecting to FC tape drives for something like Legato Networker.

you don't have to do persistent binding on HPUX and AIX (ODM takes care of it), but man ...you reboot Solaris or Linux without persistent binding..like Forest Gump said .."it's like a box of chocolate ..you never know what you are going to get"