This article describes how dependencies in Microsoft Cluster Server (MSCS) resources are used.

The basic unit of failover in MSCS is the group. The group is the set of tasks or items that must all be on the same node of the cluster for a particular objective to be accomplished. Each group can be on only one node in the cluster at a time, but different groups can be owned by different nodes. Each group contains one or more resources. A resource is a process or data item that is managed and watched by the cluster service of the node on which the group resides. If a resource fails, the cluster service will first attempt to restart the resource, but, if that is unsuccessful, the cluster service will move the group to another node if one is available.

As stated above, the group should contain all resources that must be on the same node for processing to occur. In that sense, the resources of the group are interdependent. More pragmatically, often one resource must be online before another resource can configure itself and start correctly. The second resource is said to "depend" on the other. The Cluster Administrator allows you to designate one resource as depending on another. If this is done, the Cluster service will not start the resource until the one it depends upon is started. If a resource fails, the resources that depend on it will be taken offline, and, if it restarts, the resources will be returned to an online state.

Many of the resource types that ship with MSCS have requirements for dependencies. The only resource types that do not usually depend on another resource are the Physical Disk, and IP Address. The Network Name resource must depend upon an IP address so that it can register the name and address pair with WINS. The other resources have similar requirements.

The cluster service will start resources in the order of their dependencies. In the above example, a typical group going online would start the Disk and IP Address resources first, because they have no dependencies. The Network Name resource would be started next, and after that starts, the File Share resource would start, because both the Disk and Network Name resources are online.

Note that it is not possible to have resources in different groups depend on one another. Because different groups can reside on different nodes, there is no way to guarantee that the dependencies can be satisfied.

You can also define dependencies where none are required to satisfy logical dependencies that you create. For instance, you may not want your Internet Information Server (IIS) virtual web page describing the

To execute a simple backup using TAR in Linux, enter the following command at the prompt:

tar -cvf /dev/st0 /home<enter>

(home is used as an example of a directory.)

For more information on the different switches for TAR, enter the following command at the prompt:

man tar<enter>

Other useful tape related commands in Linux:

• mt -f /dev/st0 status -- information regarding the tape drive
• mt -f /dev/st0 rewind -- rewind the media
• mt -f /dev/st0 reten -- retension the media
• mt -f /dev/st0 erase -- erase data on the media
• tar -tvf /dev/st0 -- verify the contents of the tape using tar
• tar -xvf /dev/st0 -- restore the contents of the tape using tar

General keyboard shortcuts

• CTRL+C (Copy)
• CTRL+X (Cut)
• CTRL+V (Paste)
• CTRL+Z (Undo)
• DELETE (Delete)
• SHIFT+DELETE (Delete the selected item permanently without placing the item in the Recycle Bin)
• CTRL while dragging an item (Copy the selected item)
• CTRL+SHIFT while dragging an item (Create a shortcut to the selected item)
• F2 key (Rename the selected item)
• CTRL+RIGHT ARROW (Move the insertion point to the beginning of the next word)
• CTRL+LEFT ARROW (Move the insertion point to the beginning of the previous word)
• CTRL+DOWN ARROW (Move the insertion point to the beginning of the next paragraph)
• CTRL+UP ARROW (Move the insertion point to the beginning of the previous paragraph)
• CTRL+SHIFT with any of the arrow keys (Highlight a block of text)
• SHIFT with any of the arrow keys (Select more than one item in a window or on the desktop, or select text in a document)
• CTRL+A (Select all)
• F3 key (Search for a file or a folder)
• ALT+ENTER (View the properties for the selected item)
• ALT+F4 (Close the active item, or quit the active program)
• ALT+ENTER (Display the properties of the selected object)
• ALT+SPACEBAR (Open the shortcut menu for the active window)
• CTRL+F4 (Close the active document in programs that enable you to have multiple documents open simultaneously)
• ALT+TAB (Switch between the open items)
• ALT+ESC (Cycle through items in the order that they had been opened)
• F6 key (Cycle through the screen elements in a window or on the desktop)
• F4 key (Display the Address bar list in My Computer or Windows Explorer)
• SHIFT+F10 (Display the shortcut menu for the selected item)
• ALT+SPACEBAR (Display the System menu for the active window)
• CTRL+ESC (Display the Start menu)
• ALT+Underlined letter in a menu name (Display the corresponding menu)
• Underlined letter in a command name on an open menu (Perform the corresponding command)
• F10 key (Activate the menu bar in the active program)
• RIGHT ARROW (Open the next menu to the right, or open a submenu)
• LEFT ARROW (Open the next menu to the left, or close a submenu)
• F5 key (Update the active window)
• BACKSPACE (View the folder one level up in My Computer or Windows Explorer)
• ESC (Cancel the current task)
• SHIFT when you insert a CD-ROM into the CD-ROM drive (Prevent the CD-ROM from automatically playing)
• CTRL+SHIFT+ESC (Open Task Manager)

Dialog box keyboard shortcuts

If you press SHIFT+F8 in extended selection list boxes, you enable extended selection mode. In this mode, you can use an arrow key to move a cursor without changing the selection. You can press CTRL+SPACEBAR or SHIFT+SPACEBAR to adjust the selection. To cancel extended selection mode, press SHIFT+F8 again. Extended selection mode cancels itself when you move the focus to another control.

• CTRL+TAB (Move forward through the tabs)
• CTRL+SHIFT+TAB (Move backward through the tabs)
• TAB (Move forward through the options)
• SHIFT+TAB (Move backward through the options)
• ALT+Underlined letter (Perform the corresponding command or select the corresponding option)
• ENTER (Perform the command for the active option or button)
• SPACEBAR (Select or clear the check box if the active option is a check box)
• Arrow keys (Select a button if the active option is a group of option buttons)
• F1 key (Display Help)
• F4 key (Display the items in the active list)
• BACKSPACE (Open a folder one level up if a folder is selected in the Save As or Open dialog box)

Microsoft natural keyboard shortcuts

• Windows Logo (Display or hide the Start menu)
• Windows Logo+BREAK (Display the System Properties dialog box)
• Windows Logo+D (Display the desktop)
• Windows Logo+M (Minimize all of the windows)
• Windows Logo+SHIFT+M (Restore the minimized windows)
• Windows Logo+E (Open My Computer)
• Windows Logo+F (Search for a file or a folder)
• CTRL+Windows Logo+F (Search for computers)
• Windows Logo+F1 (Display Windows Help)
• Windows Logo+ L (Lock the keyboard)
• Windows Logo+R (Open the Run dialog box)
• Windows Logo+U (Open Utility Manager)

Accessibility keyboard shortcuts

• Right SHIFT for eight seconds (Switch FilterKeys either on or off)
• Left ALT+left SHIFT+PRINT SCREEN (Switch High Contrast either on or off)
• Left ALT+left SHIFT+NUM LOCK (Switch the MouseKeys either on or off)
• SHIFT five times (Switch the StickyKeys either on or off)
• NUM LOCK for five seconds (Switch the ToggleKeys either on or off)
• Windows Logo +U (Open Utility Manager)

Windows Explorer keyboard shortcuts

• END (Display the bottom of the active window)
• HOME (Display the top of the active window)
• NUM LOCK+Asterisk sign (*) (Display all of the subfolders that are under the selected folder)
• NUM LOCK+Plus sign (+) (Display the contents of the selected folder)
• NUM LOCK+Minus sign (-) (Collapse the selected folder)
• LEFT ARROW (Collapse the current selection if it is expanded, or select the parent folder)
• RIGHT ARROW (Display the current selection if it is collapsed, or select the first subfolder)

Shortcut keys for Character Map

After you double-click a character on the grid of characters, you can move through the grid by using the keyboard shortcuts:

• RIGHT ARROW (Move to the right or to the beginning of the next line)
• LEFT ARROW (Move to the left or to the end of the previous line)
• UP ARROW (Move up one row)
• DOWN ARROW (Move down one row)
• PAGE UP (Move up one screen at a time)
• PAGE DOWN (Move down one screen at a time)
• HOME (Move to the beginning of the line)
• END (Move to the end of the line)
• CTRL+HOME (Move to the first character)
• CTRL+END (Move to the last character)
• SPACEBAR (Switch between Enlarged and Normal mode when a character is selected)

Microsoft Management Console (MMC) main window keyboard shortcuts

• CTRL+O (Open a saved console)
• CTRL+N (Open a new console)
• CTRL+S (Save the open console)
• CTRL+M (Add or remove a console item)
• CTRL+W (Open a new window)
• F5 key (Update the content of all console windows)
• ALT+SPACEBAR (Display the MMC window menu)
• ALT+F4 (Close the console)
• ALT+A (Display the Action menu)
• ALT+V (Display the View menu)
• ALT+F (Display the File menu)
• ALT+O (Display the Favorites menu)

MMC console window keyboard shortcuts

• CTRL+P (Print the current page or active pane)
• ALT+Minus sign (-) (Display the window menu for the active console window)
• SHIFT+F10 (Display the Action shortcut menu for the selected item)
• F1 key (Open the Help topic, if any, for the selected item)
• F5 key (Update the content of all console windows)
• CTRL+F10 (Maximize the active console window)
• CTRL+F5 (Restore the active console window)
• ALT+ENTER (Display the Properties dialog box, if any, for the selected item)
• F2 key (Rename the selected item)
• CTRL+F4 (Close the active console window. When a console has only one console window, this shortcut closes the console)

Remote desktop connection navigation

• CTRL+ALT+END (Open the Microsoft Windows NT Security dialog box)
• ALT+PAGE UP (Switch between programs from left to right)
• ALT+PAGE DOWN (Switch between programs from right to left)
• ALT+INSERT (Cycle through the programs in most recently used order)
• ALT+HOME (Display the Start menu)
• CTRL+ALT+BREAK (Switch the client computer between a window and a full screen)
• ALT+DELETE (Display the Windows menu)
• CTRL+ALT+Minus sign (-) (Place a snapshot of the entire client window area on the Terminal server clipboard and provide the same functionality as pressing ALT+PRINT SCREEN on a local computer.)
• CTRL+ALT+Plus sign (+) (Place a snapshot of the active window in the client on the Terminal server clipboard and provide the same functionality as pressing PRINT SCREEN on a local computer.)

Microsoft Internet Explorer navigation

• CTRL+B (Open the Organize Favorites dialog box)
• CTRL+E (Open the Search bar)
• CTRL+F (Start the Find utility)
• CTRL+H (Open the History bar)
• CTRL+I (Open the Favorites bar)
• CTRL+L (Open the Open dialog box)
• CTRL+N (Start another instance of the browser with the same Web address)
• CTRL+O (Open the Open dialog box, the same as CTRL+L)
• CTRL+P (Open the Print dialog box)
• CTRL+R (Update the current Web page)
• CTRL+W (Close the current window)

·         e-learning again on subject Exchange Server 2010  be the first one to learn about it. Invest sometimes on the material to be the first mover in exchange server 2010. The following is useful link to help you and it is free.

Get ahead of the learning curve and explore the training and product information on Exchange Server 2010.

Collection 6899: Exploring Features of Exchange Server 2010

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=249671

Product Overview

http://www.microsoft.com/exchange/2010/en/us/overview.aspx

Beta information:

http://www.microsoft.com/exchange/2010/en/us/try-it.aspx

Kelvin Chow

Technical Account Manager | Microsoft Services

1. Verify the hardware is detected properly by the Operating System

Open Device Manager in Windows and verify that your hardware is present. Verify that your controller, tape drive(s), and robotic library (if applicable) are present in Windows Device Manager:

In Windows 2003, right click My Computer and choose Manage. From the Computer Management snap-in, click on Device Manager (Figure 1).

(Figure 1):

In Windows 2008, right-click Computer and choose Manage. From the Server Management snap-in, expand Diagnostics and click on Device Manager (Figure 2).

(Figure 2):

If the tape drive, medium changer, or controller is listed with an error or is not listed in Device Manager, then you should verify that the hardware is connected to your server properly and that the proper drivers are installed. Verify the controller can detect the device properly by booting into the controller BIOS.

2. Review the System Event Logs for hardware errors.  While in the Computer Management or the Server Management console, review the System Event Logs and see if there are any hardware errors being reported from the tape drive, robotic library, or controller cards.

The following are examples of hardware errors that might be present in the System Event Logs:

 Event ID 5: Signifies SCSI parity errors. This can be caused by a faulty SCSI card or faulty SCSI termination.

 Event ID 7: Signifies bad blocks. This could be the result of a driver issue, faulty media, or dirty read/write heads on the tape drive. Run a cleaning job and replace the media with new media if possible. If the issue continues with new media,

 Event ID 9: Signifies SCSI bus timeouts. These errors usually occur when the SCSI bus resets itself, or the SCSI hardware does not respond in a timely fashion. Sometimes slowing the SCSI bus down can resolve these issues, as well as installing the latest SCSI drivers and firmware.  In certain high end servers, moving the SCSI card to a different Peripheral Component Interconnect (PCI) slot, one that does not share the same bus as a RAID controller has been known to fix these errors.

 Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues.

 Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date.


3. Verify the device configuration is supported by Backup Exec

3a. Verify that the inquiry string matches the Hardware Compatibility List (HCL)
If the device is presenting itself properly to the operating system, then it should be supplying the operating system with an inquiry string.
In order for the device to work properly within Backup Exec, the inquiry string the device provides must match exactly with what is documented on the HCL: http://entsupport.symantec.com/carveout_PID_15047_view_CL.htm 

1. The ADAMM.LOG file:
The adamm.log file is located in x:\Program Files\Symantec\Backup Exec\. Open this log file using a text editor such as Notepad, and scroll to the end of the log file.  The adamm.log file is appended to each time the Backup Exec services are started, and the detailed information for each device is outputted to this log during a process called Device Discovery.

Below is example output from a Device Discovery (Figure 3):

Figure 3:



The above shows a single tape drive (Tape0) and a robotic library (MediumChanger0). The Inquiry String for the tape drive is QUANTUM SDLT320, and it is using firmware version 2E2E. The robotic library has an inquiry string of QUANTUM UHDL and is using firmware version 0016.  

2. The DEVICEMAP registry:

The Inquiry String, as well as most of the Device Discovery information, can also be found in the DEVICEMAP portion of the SCSI Registry:

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port #\Scsi Bus #\Target Id #\Logical Unit Id #\

The SCSI Port, SCSI Bus, SCSI ID (TAR), and LUN Number can be found under the SCSI Address in Device Discovery in the adamm.log file (highlighted in Figure3).
Below is the DEVICEMAP registry hive from the tape drive from the above example (Figure 4):

Figure 4:

NOTE: You should not, under any circumstances, edit the registry settings under DEVICEMAP. These keys should be automatically populated if the hardware is configured and functioning properly.

Comparing the Inquiry Strings with the HCL:

Locate your drive and/or library on the HCL. Compare the Inquiry String found in the Step 1 or Step 2 to that what is in the HCL. The inquiry string must match exactly between the HCL and what is being reported to the server by the device.

NOTE: The ^ character in the Inquiry Strings on the HCL represents the number of spaces that are expected in the actual Inquiry String.

The following is from the HCL for the above device (Figure 5):

Figure 5:

NOTE: The above (Figure 5) represents a single entry on the HCL, and would be found in a single line and not on two entries.

3b.Verify the connection method matches the HCL.

In addition to verifying the inquiry string, also verify that the method which the hardware is connected to the server matches what is on the HCL (SCSI, Fibre, SAS, IDE, SATA). In addition, tape drives should not be connected to RAID controllers.
Using the above example (Figure 5), this device is supported when connected via SCSI.

NOTE: There are many devices that support multiple connection methods. In such examples, the device would be listed twice on the HCL. If your device supports a connection method that is not listed on the HCL, then it is possible that your device has not been tested for such a connection and therefore support will be given a limited basis. It is also possible that Symantec is in the process of qualifying the particular device for that connection method. In these cases, please open a support case with Symantec.

3c. verify the hardware addressing scheme is correctly configured.

Verify that the device is configured to use the proper addressing scheme. The above Quantum device is a Multi-LUN device, so it must be configured at the controller level as Multi-LUN addressing.
For robotic libraries, verify that the addressing scheme is set properly between the drives and the robotic library:

• SCSI ID. If your library and/or drives support SCSI ID addressing, then verify that the library has a lower SCSI ID than the tape drives.
• Multi-LUN. If you library and/or drives support Multi-LUN addressing, then verify that the drives have a lower LUN number than the library.
• For more information on verifying the addressing scheme for your hardware, see the Related Documents or consult your hardware documentation.

4. Use tracer.exe to perform a SCSI trace while restarting the Backup Exec services.

Stop the Backup Exec services and launch tracer.exe from the x:\Program Files\Symantec\Backup Exec\ directory. With tracer capturing SCSI information, restart the Backup Exec services using x:\Program Files\Symantec\Backup Exec\Servicesmgr.exe. Once the services have been restarted, review the tracer log for any hardware errors or reservation conflicts.
Please see the following document for more information on capturing and reading tracer logs:

Troubleshooting hardware with the Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
http://support.veritas.com/docs/285630 

5. Troubleshooting Robotic Library Issues

5a. Verify Robotic Library Support is enabled.

If troubleshooting an issue with a robotic library, verify that the robotic library support option has been installed:

In the Backup Exec console click on Tools > Serial Numbers and Installation.

In the installation wizard go past the serial numbers screen and verify that the Enable Robotic Library Support option is selected and installed (Figure 6):

Figure 6:



If the option is not selected, select the option and proceed with the installation.

5b. Verify that the SCSIChanger service is started.

If the library is not detected, and robotic library support is enabled, verify that the SCSIChanger service has been started. Click on Start > Run and type msinfo32 and hit enter. Expand out Software Environment and the click on System Drivers. Scroll down and find the SCSIChanger service and verify that it is started (Figure 7):

Figure 7:



If the SCSIChanger service is not started, or listed, then uninstall the Enable Robotic Library support option and then reinstall it.

5c. verify that the autoloader's media management is set to Random.  

If the library is detected, but you are having issues moving or managing media, verify that the library is in Random and not Sequential mode. Consult your hardware documentation for configuring this setting.

6. Install latest drivers and firmware

Ensure that the latest drivers and firmware have been installed for the tape drive, robotic library, and for the SCSI controller. Symantec drivers should be loaded for the tape drive for best performance. Symantec does not test performance or compatibility with Original Equipment Manufacturer (OEM) drivers, unless noted on the Hardware Compatibility List.

Backup Exec tape drivers can be downloaded from the Symantec Support Web site at http://www.symantec.com/business/support/downloads.jsp?pid=15047 . Select the appropriate Backup Exec version number in the Product Version drop-down box, and select Driver as the File Type.


7. Check for Orphaned Devices in Device Manager  

Please see the following document for how to check for orphaned devices in Windows Device Manager:

How to remove old tape drivers from Windows that are no longer needed or in use.
http://support.veritas.com/docs/308914 

It is quite possible that orphaned devices may be present in Device Manager, especially after replacing hardware, or performing a firmware or driver update. Verify that there are no orphaned tape drives, medium changers, or controllers.

Remove any orphaned device(s) to eliminate any potential conflict.

8. Perform a power-cycle of the Autoloader, Tape Drive, and Server

Power down the robotic library, tape drive, and server. Power back on the robotic library and/or tape drive. Once the autoloader or tape drive has fully initialized, power the server back on.

9. Disable, delete and re-enable the device in Backup Exec

From the devices tab in Backup Exec, right-click the device and select Enable. This should remove the check mark next to the device and disable it. After disabling the device, right-click the device again, this time choosing delete.      
After deleting the device(s), stop the Backup Exec services. With the services stopped, run Tapeinst.exe from x:\Program Files\Symantec\Backup Exec\. Choose the following options (Figure 8):

Figure 8:

It would also be advised to have tracer.exe running at this time as indicated in step #4 to review for any SCSI errors. Restart the Backup Exec services, and see if the devices are detected properly.

10. Verify that the Device and Media Service is running under a Domain Admin account.

1. Verify the hardware is detected properly by the Operating System

Open Device Manager in Windows and verify that your hardware is present. Verify that your controller, tape drive(s), and robotic library (if applicable) are present in Windows Device Manager:

In Windows 2003, right click My Computer and choose Manage. From the Computer Management snap-in, click on Device Manager (Figure 1).

(Figure 1):

In Windows 2008, right-click Computer and choose Manage. From the Server Management snap-in, expand Diagnostics and click on Device Manager (Figure 2).

(Figure 2):

If the tape drive, medium changer, or controller is listed with an error or is not listed in Device Manager, then you should verify that the hardware is connected to your server properly and that the proper drivers are installed. Verify the controller can detect the device properly by booting into the controller BIOS.

2. Review the System Event Logs for hardware errors.  While in the Computer Management or the Server Management console, review the System Event Logs and see if there are any hardware errors being reported from the tape drive, robotic library, or controller cards.

The following are examples of hardware errors that might be present in the System Event Logs:

 Event ID 5: Signifies SCSI parity errors. This can be caused by a faulty SCSI card or faulty SCSI termination.

 Event ID 7: Signifies bad blocks. This could be the result of a driver issue, faulty media, or dirty read/write heads on the tape drive. Run a cleaning job and replace the media with new media if possible. If the issue continues with new media,

 Event ID 9: Signifies SCSI bus timeouts. These errors usually occur when the SCSI bus resets itself, or the SCSI hardware does not respond in a timely fashion. Sometimes slowing the SCSI bus down can resolve these issues, as well as installing the latest SCSI drivers and firmware.  In certain high end servers, moving the SCSI card to a different Peripheral Component Interconnect (PCI) slot, one that does not share the same bus as a RAID controller has been known to fix these errors.

 Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues.

 Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date.


3. Verify the device configuration is supported by Backup Exec

3a. Verify that the inquiry string matches the Hardware Compatibility List (HCL)
If the device is presenting itself properly to the operating system, then it should be supplying the operating system with an inquiry string.
In order for the device to work properly within Backup Exec, the inquiry string the device provides must match exactly with what is documented on the HCL: http://entsupport.symantec.com/carveout_PID_15047_view_CL.htm 

1. The ADAMM.LOG file:
The adamm.log file is located in x:\Program Files\Symantec\Backup Exec\. Open this log file using a text editor such as Notepad, and scroll to the end of the log file.  The adamm.log file is appended to each time the Backup Exec services are started, and the detailed information for each device is outputted to this log during a process called Device Discovery.

Below is example output from a Device Discovery (Figure 3):

Figure 3:



The above shows a single tape drive (Tape0) and a robotic library (MediumChanger0). The Inquiry String for the tape drive is QUANTUM SDLT320, and it is using firmware version 2E2E. The robotic library has an inquiry string of QUANTUM UHDL and is using firmware version 0016.  

2. The DEVICEMAP registry:

The Inquiry String, as well as most of the Device Discovery information, can also be found in the DEVICEMAP portion of the SCSI Registry:

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port #\Scsi Bus #\Target Id #\Logical Unit Id #\

The SCSI Port, SCSI Bus, SCSI ID (TAR), and LUN Number can be found under the SCSI Address in Device Discovery in the adamm.log file (highlighted in Figure3).
Below is the DEVICEMAP registry hive from the tape drive from the above example (Figure 4):

Figure 4:

NOTE: You should not, under any circumstances, edit the registry settings under DEVICEMAP. These keys should be automatically populated if the hardware is configured and functioning properly.

Comparing the Inquiry Strings with the HCL:

Locate your drive and/or library on the HCL. Compare the Inquiry String found in the Step 1 or Step 2 to that what is in the HCL. The inquiry string must match exactly between the HCL and what is being reported to the server by the device.

NOTE: The ^ character in the Inquiry Strings on the HCL represents the number of spaces that are expected in the actual Inquiry String.

The following is from the HCL for the above device (Figure 5):

Figure 5:

NOTE: The above (Figure 5) represents a single entry on the HCL, and would be found in a single line and not on two entries.

3b.Verify the connection method matches the HCL.

In addition to verifying the inquiry string, also verify that the method which the hardware is connected to the server matches what is on the HCL (SCSI, Fibre, SAS, IDE, SATA). In addition, tape drives should not be connected to RAID controllers.
Using the above example (Figure 5), this device is supported when connected via SCSI.

NOTE: There are many devices that support multiple connection methods. In such examples, the device would be listed twice on the HCL. If your device supports a connection method that is not listed on the HCL, then it is possible that your device has not been tested for such a connection and therefore support will be given a limited basis. It is also possible that Symantec is in the process of qualifying the particular device for that connection method. In these cases, please open a support case with Symantec.

3c. verify the hardware addressing scheme is correctly configured.

Verify that the device is configured to use the proper addressing scheme. The above Quantum device is a Multi-LUN device, so it must be configured at the controller level as Multi-LUN addressing.
For robotic libraries, verify that the addressing scheme is set properly between the drives and the robotic library:

• SCSI ID. If your library and/or drives support SCSI ID addressing, then verify that the library has a lower SCSI ID than the tape drives.
• Multi-LUN. If you library and/or drives support Multi-LUN addressing, then verify that the drives have a lower LUN number than the library.
• For more information on verifying the addressing scheme for your hardware, see the Related Documents or consult your hardware documentation.

4. Use tracer.exe to perform a SCSI trace while restarting the Backup Exec services.

Stop the Backup Exec services and launch tracer.exe from the x:\Program Files\Symantec\Backup Exec\ directory. With tracer capturing SCSI information, restart the Backup Exec services using x:\Program Files\Symantec\Backup Exec\Servicesmgr.exe. Once the services have been restarted, review the tracer log for any hardware errors or reservation conflicts.
Please see the following document for more information on capturing and reading tracer logs:

Troubleshooting hardware with the Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
http://support.veritas.com/docs/285630 

5. Troubleshooting Robotic Library Issues

5a. Verify Robotic Library Support is enabled.

If troubleshooting an issue with a robotic library, verify that the robotic library support option has been installed:

In the Backup Exec console click on Tools > Serial Numbers and Installation.

In the installation wizard go past the serial numbers screen and verify that the Enable Robotic Library Support option is selected and installed (Figure 6):

Figure 6:



If the option is not selected, select the option and proceed with the installation.

5b. Verify that the SCSIChanger service is started.

If the library is not detected, and robotic library support is enabled, verify that the SCSIChanger service has been started. Click on Start > Run and type msinfo32 and hit enter. Expand out Software Environment and the click on System Drivers. Scroll down and find the SCSIChanger service and verify that it is started (Figure 7):

Figure 7:



If the SCSIChanger service is not started, or listed, then uninstall the Enable Robotic Library support option and then reinstall it.

5c. verify that the autoloader's media management is set to Random.  

If the library is detected, but you are having issues moving or managing media, verify that the library is in Random and not Sequential mode. Consult your hardware documentation for configuring this setting.

6. Install latest drivers and firmware

Ensure that the latest drivers and firmware have been installed for the tape drive, robotic library, and for the SCSI controller. Symantec drivers should be loaded for the tape drive for best performance. Symantec does not test performance or compatibility with Original Equipment Manufacturer (OEM) drivers, unless noted on the Hardware Compatibility List.

Backup Exec tape drivers can be downloaded from the Symantec Support Web site at http://www.symantec.com/business/support/downloads.jsp?pid=15047 . Select the appropriate Backup Exec version number in the Product Version drop-down box, and select Driver as the File Type.


7. Check for Orphaned Devices in Device Manager  

Please see the following document for how to check for orphaned devices in Windows Device Manager:

How to remove old tape drivers from Windows that are no longer needed or in use.
http://support.veritas.com/docs/308914 

It is quite possible that orphaned devices may be present in Device Manager, especially after replacing hardware, or performing a firmware or driver update. Verify that there are no orphaned tape drives, medium changers, or controllers.

Remove any orphaned device(s) to eliminate any potential conflict.

8. Perform a power-cycle of the Autoloader, Tape Drive, and Server

Power down the robotic library, tape drive, and server. Power back on the robotic library and/or tape drive. Once the autoloader or tape drive has fully initialized, power the server back on.

9. Disable, delete and re-enable the device in Backup Exec

From the devices tab in Backup Exec, right-click the device and select Enable. This should remove the check mark next to the device and disable it. After disabling the device, right-click the device again, this time choosing delete.      
After deleting the device(s), stop the Backup Exec services. With the services stopped, run Tapeinst.exe from x:\Program Files\Symantec\Backup Exec\. Choose the following options (Figure 8):

Figure 8:

It would also be advised to have tracer.exe running at this time as indicated in step #4 to review for any SCSI errors. Restart the Backup Exec services, and see if the devices are detected properly.

10. Verify that the Device and Media Service is running under a Domain Admin account.