Remote Storage Manager report a mismatch in the order of attached tape devices after reboot of a Windows system
There are instances where the mapping of attached tape device become out of order after a Windows server reboot. This may occur if one or more of the tape drives is either inaccessible or does not respond to the server correctly as the server is enumerating tape devices on boot.
Check HBA Card Settings:
HBAs usually have a configuration option within the firmware called “persistent binding”, which allows the SCSI target ID configuration for a device to be retained across reboots and/or fabric resets. This setting may help with retaining consistent device mappings for RSM and third-party backup applications.
Check if the HBA setting called “FC-TAPE” (FCP-2) is in use. This protocol allows for error recovery. Using this setting for HBAs that have access to tape libraries may help with tape device issues on a SAN.
See Also:
Troubleshoot Windows Disk Problems
Troubleshooting Windows SAN ProblemsDisks tape library mismatchDisks tape library mismatch
Filed under: Disks
Quite frankly, it seems to me that Storage Manager report a mismatch in the order of attached tape devices after reboot of a Windows system | windowswideopen.com has more to do with Apply card credit target Wednesday than yesterday. The Apply card credit target is just not as relevant to Storage Manager report a mismatch in the order of attached tape devices after reboot of a Windows system | windowswideopen.com as I had originally thought….