A Robotic Library set to Emulation Mode is either not detected by or cannot be properly managed by the Backup Exec Software

Article:TECH45853  |  Created: 2009-01-12  |  Updated: 2009-01-12  |  Article URL http://www.symantec.com/docs/TECH45853
Article Type
Technical Solution

Product(s)

Environment

Issue



A Robotic Library set to Emulation Mode is either not detected by or cannot be properly managed by the Backup Exec Software

Solution



After the proper device drivers have been loaded, a robotic library sends a Unique Product Identification String to Windows so that the device can be properly detected/managed by Windows and other Third Party Backup Applications.  By default, most robotic libraries are set to be detected in their native operating mode, which means that the device is identified by its true make/model.

Some models of robotic libraries can be set to operate in an Emulation Mode.  Emulation makes it possible for a robotic library, autoloader, or tape drive to emulate or appear to be a different device than it actually is.  The primary reason to enable emulation on most devices is so that Backup Software Applications that do not have an available device driver for a more updated model of the library are able to install a Legacy Device Driver for the device instead.  

Please note:  Device Drivers are available for most of the supported tape hardware that is listed on the Symantec Hardware Compatibility List (HCL) and Symantec has only tested tape hardware operating in a native mode to work with our backup software applications.  Robotic Libraries that operate in an emulated mode may not function or be detected properly by Backup Exec or any of the other Symantec Tape Backup Applications and will not be supported.  The risk of unrecoverable data loss may also occur.



Legacy ID



281310


Article URL http://www.symantec.com/docs/TECH45853


Terms of use for this information are found in Legal Notices