This document contains important information about Retrospect version 7.0 for Windows. Please read it carefully. The Retrospect family of backup software includes Retrospect Professional, Retrospect Disk-to-Disk, Retrospect Small Business Server, Retrospect Single Server, and Retrospect Multi Server. Unless otherwise noted, all items in this document refer to all members of the Retrospect backup family.
The EMC Dantz web site is constantly updated with the most recent support information for Retrospect and related products, including the following:
This document is divided into the following sections:
Support for Windows 64-bit operating systems: This release of Retrospect supports Windows XP Professional x64 Edition and Windows Server 2003 x64 Edition.
New versions of Linux supported: Retrospect supports Retrospect Client software running on more versions of Linux software than ever before. See the EMC Dantz Knowledgebase for a current list of supported versions of Linux.
Improved Backup Set encryption: Retrospect Backup Sets can now be encrypted using AES-256 (in addition to AES-128, DES, and SimpleCrypt), which uses a 256-bit key for improved security. To use AES-256 encryption, create a new Backup Set in Retrospect and select AES-256 from the Backup Set Security list box. NOTE: You cannot change the security settings for existing Backup Sets.
Scheduled grooming: This version of Retrospect includes a new type of script; a Groom script. Groom scripts provide users with the ability to schedule a time to reclaim disk space by deleting older files and folders from disk Backup Sets.
To create a Groom script, choose Automate>Manage Scripts from Retrospect's navigation bar. Click New, choose Groom from the list, and click OK. Groom scripts include a source, which can be one or more disk Backup Sets, and a schedule. Setting up the schedule for a Groom script is exactly the same as for any other script. See the Retrospect User's Guide or online help for more information.
When a Groom script runs, Retrospect deletes older files and folders from the source disk Backup Set(s) based on its specified grooming policy. Without a Groom script, Retrospect won't delete older files and folders until it requires more disk space.
If the disk backup set does not have grooming enabled, the script will add an error to the Operations Log and continue to the next Backup Set.
Grooming performance enhancements: This build of Retrospect includes a number of changes designed to speed up the process of grooming disk Backup Sets. Users should see noticeable improvements.
Flashing system tray icon: When you stop all Retrospect executions (from either the toolbar or the countdown dialog), the Retrospect icon in the system tray of your Windows taskbar will flash until you click the Stop all execution activity button in the Retrospect toolbar. As long as the icon is flashing, Retrospect will not execute any immediate or scripted operations.
Excluded folders on UNIX clients: Retrospect's "All Files" selector no longer excludes the following directories on Linux/Solaris clients--
/var/log
/var/cache
/tmp
NOTE: The "All Files Except Cache Files" selector does exclude these directories.
Disaster Recovery CD and Windows XP Service Packs: When you are creating a disaster recovery CD (DR CD) using the Prepare for Disaster Recovery wizard, Retrospect asks you to insert your Windows XP installation CD. In order to create a usable DR CD, you must insert a Windows XP installation CD that includes the same service pack as the system you want to restore.
For example, if you need to perform a disaster recovery of a computer running Windows XP with Service Pack 2, you must insert a Windows XP install CD with Service Pack 2 slipstreamed. For information on creating a Windows XP with SP2 installation CD, visit the following Web site: http://www.winsupersite.com/showcase/windowsxp_sp2_slipstream.asp.
Any time you update the service packs of the computers you are protecting, you must also update your disaster recovery CDs to use a Windows installation CD that integrates the new service pack.
Grooming database backups: This build of Retrospect fixes a problem with the grooming of SQL and Exchange database backups to disk Backup Sets. If you always perform Full database backups, you will did not experience this issue. If you perform Differential, Incremental, or Log database backups, Retrospect may have incorrectly groomed a Full backup from those disk Backup Sets.
When you install build 265 of Retrospect, it automatically locks all database backups performed with earlier versions of Retrospect to prevent them from being groomed. This prevents future grooming problems, but cannot undo the effects of grooming that may have already occurred. To protect against the possibility that Retrospect groomed a critical database backup before you installed this version, you should perform a new Full database backup of all affected databases immediately.
A side effect of locking older database backups is that they may require space on your hard disk that can never be reclaimed by grooming. If this is the case, you should create a new disk Backup Set with grooming enabled and perform a Full database backup of all affected databases to the new set. When you no longer need any of the data in the old disk Backup Set, you can recycle it.
License Codes: Retrospect requires a license code to function. The first time you start Retrospect, enter the license code.
If you purchased your Retrospect software via electronic download, your license code should be e-mailed to you by your vendor; if you did not receive the code, contact your vendor. Write down or print your license code for future reference and keep the code in a safe place. Without this license code, you will not be able to use your Retrospect software.
NOTE: An Upgrade Authentication Code (UAC) is not the same as a license code. If you received a copy of a Retrospect upgrade that came with an Upgrade Authentication Code you must obtain a permanent license code. To do so, go to www.emcdantz.com/en/uac and follow the instructions on this page, or contact EMC Dantz Customer Service.
Older Backup Sets: If you are an upgrade customer, you can use your older Backup Sets with Retrospect 7.0. However, once you use a Backup Set with Retrospect 7.0, you can no longer access it from earlier versions of Retrospect.
Microsoft Outlook: Retrospect’s "Force backup of Microsoft Outlook data" option no longer relaunches Outlook after a backup. You must relaunch Outlook manually.
Automatically skip to blank media: In Retrospect 7.0, this option is turned off by default. If the last member of the Backup Set is not available, Retrospect will display a media request asking for it and will not continue the operation until the media request is satisfied. To change this behavior, turn the option on. Click Configure>Preferences, then browse to the Media Request options. When this option is on, Retrospect will skip to any available blank media in the backup device when the current member is not available. NOTE: You will not be able to add data to the unavailable member later, even if it is not yet full.
Disaster Recovery: Retrospect now saves Backup Set Catalog Files on the Disaster Recovery CD for Windows XP, Windows 2000, and Windows Server 2003 operating systems (if there is enough space available). That means that for these operating systems you will no longer have to recreate the Catalog File from the storage media during disaster recovery.
Ignore ID: When you upgrade from an earlier version of Retrospect, backup devices with IDs that you previously ignored will display in the Storage Devices window. To ignore them again, choose Configure>Devices from Retrospect's navigation bar. In the Storage Devices window, click the Environment tab, then select the ID to ignore and click the Ignore ID button from the window's toolbar. You must exit and relaunch Retrospect for the changes to take effect.
Upgrading from versions of Retrospect prior to 5.6: If you are upgrading to Retrospect 7.0 from 5.5, take the following steps to preserve your Retrospect configuration information:
Upgrades from versions prior to Retrospect 5.5 are not supported. Uninstall the previous version of Retrospect, then install Retrospect 7.0. Your configuration information will be lost.
Scripted recycle backup: When performing a scripted recycle backup to a tape member with the correct name, Retrospect will generate a media request unless the "Automatically reuse named media" preference is selected. Click Configure>Preferences and then browse to the Media Erasure preferences to specify this option.
Recognized CD/DVD devices: Retrospect no longer recognizes certain unsupported CD/DVD drives. Instead, it launches a configuration tool which lets you create a custom driver for the device.
Disaster Recovery Catalog on network: If, during a Disaster Recovery, Retrospect asks you to locate a Catalog File that you know is on a network volume, cancel out of the dialog and accept the warning about halting the recovery. When the computer restarts, it continues with the recovery and Retrospect again asks you to locate the Catalog File. This time, you can navigate to the network volume and select the Catalog.
ReportsWatcher on NT 4.0: In order to use ReportsWatcher with Internet Explorer on Windows NT 4.0, you must have Internet Explorer v4.0 or better.
Terminal Services client on Windows NT 4.0: Running Retrospect in a Terminal Services client connected to a Windows NT 4.0 server is not supported.
Can’t save files to Desktop: Depending on the account that Retrospect is running under, you may not be able to save files (e.g., exported selectors) to the Desktop. If this is the case, manually browse to the desired user’s Desktop folder instead of using the top level Desktop option.
Problems backing up outcmd.dat: In some situations, Retrospect may have problems backing up the file outcmd.dat- which contains custom panes, toolbars, and menus- while Outlook is running. If you get error -1020 (sharing violation) when trying to back up this file, close Outlook and try backing up again, or use Retrospect’s Open File Backup functionality on Windows NT, 2000, XP, or Server 2003 systems.
Retrospect Launcher service fails to start: If this happens go to Configure>Preferences and browse to the Execution Startup preferences. Uncheck the "Enable Retrospect Launcher service" checkbox and click OK. Go back to the Execution Startup preferences, check the "Enable Retrospect Launcher service" checkbox, and click OK.
Creating a Disaster Recovery CD: Retrospect’s Disaster Recovery preparation wizard can save a custom CD image file, which you can later use with CD-R authoring and recording software to create a disaster recovery CD. The file is an image of a CD in the ISO 9660 format, which all popular authoring software (e.g. Easy CD Creator, Nero, B's Recorder Gold, RecordNow!, etc.) can use to record, or "burn," a CD. You cannot burn the CD using Retrospect. Though most authoring software has the capability to burn a disc from an ISO image, some programs do not have an intuitive user interface for this feature. If you have difficulty creating the CD, please refer to the documentation that came with your CD authoring software.
Proactive Backup/Backup Server: Proactive Backup and Backup Server are different terms that refer to the same thing. Retrospect for Windows and Windows and Linux clients use the term Proactive Backup. Retrospect for Macintosh and Macintosh clients use the term Backup Server.
Grooming: Older backups are not groomed from disk Backup Sets that are protected with AES, DES, or SimpleCrypt encryption.
Disaster recovery on computers with Promise RAID cards: This build of Retrospect fixes a problem that caused disaster recovery to fail on computers with certain Promise Technology RAID cards. Retrospect can now correctly load the required drivers and complete disaster recovery.
Disaster recovery on computers with Silicon Image Si 3112 SATAlink Controllers: This build of Retrospect fixes a problem that caused disaster recovery to fail on computers with Silicon Image Si 3112 SATAlink Controllers. Retrospect can now correctly load the required drivers and complete disaster recovery.
Backup Wizard resource in use errors: Under certain circumstances, Retrospect was generating an error -843 (resource is in use by another operation) message when executing backups from the Backup Wizard.
Error or assert backing up an Exchange server: Retrospect should no longer incorrectly generate an assertion failure at "tstring.cpp-1355" or error -557 (transaction already complete) message.
Grooming database backups: This build of Retrospect fixes a problem with the grooming of SQL and Exchange database backups to disk Backup Sets. See Tips and Late-Breaking Information for more details.
Assertion failures: When Retrospect encounters a serious error, it crashes and display an assert dialog. EMC Dantz has addressed the following asserts based on reports from Retrospect users:
Catalog out of sync: In some situations, Retrospect was reporting "Catalog out of sync" errors for disk Backup Sets with grooming enabled. This has been fixed.
Grooming and password protection: Retrospect is now able to groom password-protected disk Backup Sets (but not encrypted Backup Sets).
Validating scripts: Under certain circumstances Retrospect was erroneously reporting "Media for script scriptname unavailable" when checking media using the Automate>Manage Scripts command. This has been fixed.
Hanging on launch: Certain backup computer configurations were causing Retrospect to hang when it was launched. This problem has been fixed.
Backup Wizard script destination selection: When creating a backup script using the Backup Wizard, you can choose "Backup now" from the summary screen to run the script immediately. If there are multiple destination Backup Sets available, a drop-down menu allows you to choose which Backup Set to use. Previously, Retrospect always used the first Backup Set in the list, no matter which one you selected. Now Retrospect correctly uses the Backup Set you choose from the list.
Retrospect Single Server and Exchange mailboxes: Retrospect Single Server with the Exchange Database/Mailbox Add-on is now able to add Exchange mailboxes to an Exchange Server that is logged in as a Retrospect Client.
Can't grant necessary user privileges: Previously, Retrospect reported this error when trying to run as a specified user on a Windows NT 4.0 Secondary Domain Controller. This is no longer the case.
Exporting the Operations Log: When the "Export the backup report and operations log" preference is selected, Retrospect exports the entire Operations Log to the file "operations_log.utx". Previously, Retrospect only exported the Operations Log for the most recent operation.
Resource in use errors: This version of Retrospect addresses some situations that were incorrectly generating error -843 (resource is in use by another operation).
Best practices: EMC Dantz recommends that you perform a full backup of your line of business servers while all applications are closed before using Open File Backup for the first time. Although Open File Backup is designed to back up line of business servers while they are up and running, closing the servers down prior to performing the first backup adds an extra degree of safety. For the best results, schedule subsequent backups of up and running line of business servers for off-peak times.
Delays before copying: When using Open File Backup, you may notice a delay between when the backup is initiated and when copying begins. During this time, Retrospect is looking for a "disk inactivity threshold" on the disk it is backing up. Retrospect tries to meet the disk inactivity threshold from the time Open File Backup is initiated, until the "Retry timeout" period elapses. Thus, the delay before copying could be as long as the Retry timeout (the default is ten minutes). See the Retrospect User’s Guide for more information on specifying the Disk inactivity threshold and Retry timeout.
Multiple Volumes: For best performance, if an Open File Backup operation includes multiple volumes, but none of the open file data spans multiple volumes, make sure Retrospect's Protect Multi-Volume Datasets execution option is off.
Administrator privileges: If you are logged on to the backup computer and manually launch Retrospect, or if you are using the Retrospect Launcher service to automatically launch Retrospect for unattended operation, you must be logged on with administrator privileges in order to use Open File Backup to back up the local computer.
Windows error messages: Open File Backup requires a certain amount of free disk space on the disk that is being backed up. If you run Open File Backup in a low disk space environment, Windows may generate error messages, such as "The file system structure on the disk is corrupt and unusable" or "Delayed Write Errors." If the error message includes the word "Snapshot," this indicates that Open File Backup was unable to back up the requested volume.
In these cases, no data is lost and the disk is not corrupt, rather the Open File Backup could not be completed. Freeing up disk space on the disk being backed up and rebooting the computer solves this problem. If you do not reboot, subsequent Open File Backups may also fail.
Virus scanning software: EMC Dantz recommends not running active virus scans during Open File Backup. Anti-virus software can be installed and enabled, as long as there are no active scans during the backup.
Norton CleanSweep: There are known issues when using Open File backup with Norton CleanSweep. EMC Dantz recommends uninstalling CleanSweep, or disabling its installation monitors, csinsmnt.exe and monwow.exe.
Windows NT 4.0 to Windows 2000 Upgrades: If you are using Open File Backup and want to upgrade the backup computer or a client computer from Windows NT 4.0 to Windows 2000, follow these steps:
Conflicts with St. Bernard Open File Manager: If the backup computer has St. Bernard Open File Manager installed, you may experience problems using Retrospect’s Open File Backup. Uninstall St. Bernard Open File Manager to avoid problems.
Errors backing up open encrypted files: If you try to back up encrypted files that are open using Open File Backup on a Windows 2000 computer, you may get error -1102. To ensure the files get backed up, close them and back up again.
Some third-party drivers not installed: During disaster recovery of a local or client Windows computer, Retrospect automatically installs most third-party drivers required to communicate with the backup device, hard disk, and over the network. However, some drivers cannot be installed automatically. In this case, you will have to install the drivers during the temporary operating system setup (as in the case of some RAID drivers) or exit the Disaster Recovery Wizard to use the Windows Hardware Wizard or Hardware Manager (as in the case of some Network Interface Card drivers).
Recycle bin is empty after disaster recovery: Retrospect may automatically delete the contents of the Recycle Bin during disaster recovery. If you previously backed up the Recycle Bin, you can manually restore its contents to a folder after disaster recovery.
SQL container does not appear: If you install SQL server on a system that is already running Retrospect, you will need to reboot the server before Retrospect recognizes the SQL container.
Custom path for restoring data and log files: During a database restore operation with the default options, Retrospect restores database data and log files to their original locations, even if they are stored in different places (e.g., data files on C:\ and log files on E:\). If you choose to restore to a custom path, both data and log files are restored to a single location that you specify (e.g., D:\).
"Suspect" SQL 7 databases: After restoring a master SQL database on SQL 7, some database may appear grayed out and labeled "suspect" in the SQL Enterprise Manager. EMC Dantz recommends deleting all "suspect" databases and restoring them from the most recent backup.
Log backups of a SQL 7 database: In order to perform a log backup of a SQL 7 database, you must modify the database options. Open the SQL Enterprise Manager, right-click the icon for the database and select Properties. Click the Options tab and uncheck the "Truncate log on checkpoint" option. Click OK. You can now perform log backups of the database.
Recovery Storage Groups: Exchange 2003 includes a new Recovery Storage Group feature that allows you to mount a second copy of an Exchange mailbox store on the same server as the original database. Retrospect does not support backing up or restoring to recovery storage groups. In addition, to restore data to an Exchange 2003 server that includes a recovery storage group, you must either delete the recovery storage group before restoring, or create a Recovery SG Override registry key on the Exchange server as described on Microsoft's web site.
No Exchange mailboxes displayed: If you click the Mailboxes button and no Exchange mailboxes are displayed, make sure you are running Retrospect as a user with mailbox privileges. In most cases you should be running as with domain administrator privileges, not just local administrator privileges. See the Retrospect User’s Guide and Retrospect Online Help for more information.
If you get Retrospect error -3401 and Windows error 0x81002746, as well as no mailboxes, you cannot run Retrospect as "administrator". Create an account with the necessary privileges and name it something other than "administrator".
If you get Retrospect error -3401 or -3402 and Windows error 0x80040115, as well as no mailboxes, select the Exchange container in the Volumes Database, then click the Login as button. If there is no login information, enter it now and try again. If there is login information, there may be problems with the account. In that case you should make sure the account has not been deactivated or had its permissions revoked. You can also create a new account and use it to login instead.
Microsoft Exchange Server 2000: As part of its default installation, Exchange 2000 creates a virtual drive and assigns it the drive letter M. Retrospect does not back up this virtual drive, since it does not contain any information required for a complete and accurate restore.
Disaster Recovery: The EMC Dantz Knowledgebase includes detailed articles on Exchange disaster recovery.
Open File Backup: Retrospect’s Open File Backup capability does not work with Windows client software versions prior to 6.0. To use Open File Backup, update Windows clients to the latest version with the Retrospect client update file, then restart the client computers.
Windows XP Internet Connection Firewall: By default, Windows XP’s built-in Internet Connection Firewall restricts network access to many networking services.
When you install the Retrospect client on systems with the Windows XP Internet Connection Firewall enabled, the installer automatically makes the required changes to allow Retrospect client communication.
However, if you enable Windows XP’s built-in Internet Connection Firewall on a computer already running the Retrospect client, you will need to run a Retrospect utility to enable client communication through the firewall. Run the "retfwset.exe" utility, found in the Retrospect client directory (by default C:\Program Files\Dantz\Client), to allow Retrospect client communication.
Windows Socket 2 Update for Windows 95: Windows 95 clients require the Windows Socket 2 Update, available at no charge from Microsoft. Known as Winsock2, it is required only for Windows 95 and is available free from Microsoft’s web site.
Suspend: If a client user uses the "Suspend" function of Windows 95, which powers off a mobile computer without shutting it down, you must restart the client computer before Retrospect can access it. Microsoft has an update to address this problem, but Microsoft does not recommend updating unless you are severely impacted by it. For more information about this problem and the update, visit Microsoft’s web page.
Mac OS X clients: For clients older than version 5.0.540 use the following procedure to add existing Mac OS X clients to Retrospect 7.0. Uninstall the old client software, then update the clients to the current version by running the client installer on each Mac OS X client computer. Retrospect for Macintosh users will have to "forget" the old OS X clients and add the new OS X clients to the clients database, as well as to any scripts that included the clients. Retrospect for Windows users must update the client database. Choose Configure>Clients. Select the old client from the list and click Properties. Click the Access tab, click Change, then select the new client from the list and click OK. You do not have to update your scripts, since they will now automatically use the new client information.
Mac OS X client privileges: Before restoring or duplicating to a volume on a Mac OS X client, you must prepare the volume if you wish to retain its privileges. From the Mac OS X Finder, use the Show Info command on the volume. Choose Privileges from the info window’s menu then turn off the "Ignore privileges on this volume" option.
FileVault: If you are backing up Mac OS X clients that have the operating system's FileVault feature enabled, make sure to read "Working with Mac OS Clients" in the Retrospect User's Guide or Retrospect online help for important information.
Energy Saver: Apple’s Energy Saver control panel can put a non-PCI client Macintosh into "sleep" mode, which may produce error -530 with network backups. Avoid this problem by using the Retrospect Client control panel’s "Wait at Shutdown" preference and shutting down the client to put it in the "waiting for backup" mode (Mac OS 7/8/9 only), or by setting the CPU sleep option to never sleep.
Mac OS Extended Format (HFS+) Time Zone: When the local time zone is changed in the Date & Time control panel, the Mac OS shifts the local creation and modification times of files on HFS+ (extended format) volumes. This affects Retrospect’s normal backups when it scans the volumes for files which need to be backed up. Because file date/time stamps are different, Retrospect marks every file for backup. Retrospect is simply performing an incremental backup as it usually would; the only abnormality is that every file appears to have been modified.
Mac OS Extended Format (HFS+) Daylight Savings Time: Under Mac OS 8.1, changing the Daylight Savings Time setting shifts the local dates and times of files on HFS+ volumes. This affects Retrospect as described in the previous topic. Mac OS 8.5 solves this problem because it does not alter file date/time stamps when you change Daylight Savings in the Date & Time control panel.
Mac OS 7/8/9 clients don’t renew DHCP leases while waiting for shutdown: When a Mac OS 7/8/9 client has a DHCP-supplied IP address and its lease expires while the client is waiting for shutdown, the Macintosh does not renew its IP lease and continues using its old IP address. This can lead to a conflict when the DHCP server, thinking the IP address is now available, leases the IP address to a different computer.
There are two possible workarounds: leave DHCP-served Mac OS computers idle in the Finder instead of in the Retrospect client "Wait at Shutdown" mode and uncheck "Load Only When Needed" in the TCP/IP control panel; or, lengthen your DHCP server’s lease period. The likelihood of encountering this problem decreases as the length of DHCP leases increases.
Mounted recordable discs: Retrospect does not support recordable discs (CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVR+R DL, or DVD+RW discs) formatted for use with software that allows you to mount the discs in Windows Explorer and use them like floppy disks. In addition, when the disc mounting software and Retrospect are both running on the backup computer, conflicts may occur.
To use disc mounting software when Retrospect is running:
To use Retrospect when disc mounting software is running:
DVD-RAM devices: With some DVD-RAM drives, a drive may not appear in Retrospect’s Volumes Database unless a writable DVD-RAM cartridge is in the drive.
Windows NT 4.0 and ATAPI devices: Windows NT 4.0 Service Pack 3 and later greatly improve compatibility with ATAPI storage devices. If you are encountering problems with an ATAPI storage device, contact the computer vendor for a new IDE controller driver.
DirectCD: Retrospect is not able to access a CD/DVD device if an Adaptec DirectCD-formatted disc is in the drive. Eject all DirectCD volumes from the CD/DVD drive before opening Retrospect.
Imation LS-120 SuperDisk: Retrospect will not recognize a SuperDisk drive if a 1.4 M floppy disk was in the drive before Retrospect scanned for available backup devices. If the SuperDisk drive is not visible in Retrospect’s media request window, check whether Windows Explorer shows a drive letter for a removable disk in My Computer. If the SuperDisk drive has a letter in Windows Explorer but it is not in the media request window, click Environment, then click Refresh.
Auto-Ejecting removable disks: Retrospect automatically ejects removable disks by default. In Windows NT/2000/XP this could cause delayed write failures. Windows 98 may give you a blue screen error message when Retrospect automatically ejects a removable disk. To prevent this, go to Configure>Preferences, then browse to the Media Handling options and turn on the Don’t eject removable disks preference.
Conflicts with Promise ATA 100 controller: Evian.sys is a caching driver that shipped with older versions of the ATA 100 controller. This driver may conflict with components installed as part of Retrospect’s default installation on Windows NT 4.0 and Windows 2000 computers. If your system includes evian.sys, remove it before installing Retrospect. See the Support section of Promise Technology’s web site (www.promise.com) for more information about evian.sys.
The EMC Dantz web site has a searchable database of backup devices qualified for use with Retrospect. Check the database for specific information about your device.
EMC Dantz adds support for devices by releasing Retrospect Updates, which are "plug-in" files you place in the folder with Retrospect. When circumstances permit, EMC Dantz includes the latest update with Retrospect and it is automatically installed when you install Retrospect. (To reinstall the update, reinstall Retrospect.)
To see which version of the Retrospect Update you have, choose About Retrospect from Retrospect's Help menu. It lists the version of Retrospect, as well as the Retrospect Update version.
If you don't have a Retrospect Update, or your update version is too old for your device, you can get the latest Retrospect Update from the EMC Dantz web site.
Certain drives require specific versions of firmware, the drive’s built-in controlling software. To determine your drive’s firmware version, click Configure>Devices, and click the Environment tab. If your firmware is an earlier version than is required, contact your drive vendor.
Retrospect supports all drives which are accessible from Windows Explorer. This includes removable cartridge drives from Iomega, Imation’s SuperDisk, DVD-RAM drives from Hitachi, Panasonic, and Toshiba, and magneto-optical drives from Epson, Fujitsu, Mitsubishi Chemical, Olympus, Philips, Pinnacle, Ricoh, Sony, and others.
Copyright © 2005 EMC Corporation