All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! This new drive is recognized in the bios scsi selector with all defaults , it is also seen when running tapeinst. It can also be seen in device manager as a normal functioning device after installing symantec drivers.
The problem is that neither ntbackup, or symantec backup exec can use this device. Ntbackup still wants to use my 4mm trevan, and symantec just sees nothing altogether. Does the tape drive have any dip switches to set the ID. Is it a external tape drive or internal. Sounds external by the way you "plug it in" so it is more then likely on a different bus then the raid that it boots from. Looking for a boot order in the bios of computer or the bios of the card it's on sounds like your on the right track.
Watch the boot process of the server without the tape drive attached and note the drive ID's. The external tape drive should have DIP switches, if it is internal it will have jumpers. Set the tape device ID to a number that is not conflicting with any of those at boot up.
SCSI cards that have a external connector, are usually a second bus. He's talking about a server so I would imagine it is not a cheapo card that just has a external connector. It wouldn't get that far. Does the tape drive match the SCSI card type i. If the drive is not Ultra, it will cause a conflict on the built-in array controller and could cause your boot issue.
Brand Representative for StarWind. SCSI is hot-plug. Backup Exec media server may require a reboot. Use the Discover tool to troubleshoot hardware errors or reservation conflicts The Discover tool outputs detailed attributes of backup devices that are attached to the server. Stop the Backup Exec services. Navigate to the Backup Exec installation directory.
To run the tool and create a text output, at a command prompt, run the following command: Discover. Troubleshooting SCSI issues using tracer. Click Start , and in the search box, type msinfo32 , and then press Enter. Use tracer. After the services restart, review the tracer log for any hardware errors or reservation conflicts.
Detect and uninstall any orphaned devices Orphaned devices may be present in Device Manager after you replace hardware, or perform firmware and driver updates. This selection shows all device drivers, including those that are not currently installed and running on the computer. Warning: Removing devices and drivers that are still required by the system may result in the system becoming unstable and unable to boot.
Right-click the device, and then select Disable. For Backup Exec and earlier, select Enable to remove the check mark; when the check box is clear, the device is disabled. Right-click the device, and then select Delete. A prompt to move the backup jobs to other devices or device pools may appear For Backup Exec , this appears as Retarget Jobs.
Note the jobs that are affected and move the jobs back to the original device after resolving the issue with the device. X: is the drive where Backup Exec is installed In the Veritas Device Driver Installed dialog, select the following options: - Use Veritas tape drivers for all supported tape devices - Delete entries for tape devices that are unavailable, removed, or turned off - Use Plug-and-Play drivers for Windows and later Restart Backup Exec services.
Final troubleshooting steps before contacting Veritas technical support Review the device manufacturer documentation to confirm if the device is working properly. Contact technical support for the device manufacturer. If technical support of the device manufacturer confirms that the device is working properly but you are still having issues, contact Veritas Technical Support.
How to resolve SCSI bus timeouts. I have also managed to detect the library on the server. Apparently, each type of drive has to have at least a control path set. On the server, one of the three SCSI tape drives was set as the control path. This allowed the server to detect the library via SCSI. I just had to do the same to one of the 3 SAS drives and it was seen by the server afterwards. View solution in original post. I know you have a simple question but I am not sure how to answer it.
Sorry, because I also think that is the root of my problem. Still, the Library is not detected on the It is detected by the machine. Both hosts can access the GUI console of the library. But I would assume the SCSI connections are just for detecting the drives and not the library itself. What did we miss?
0コメント