Troubleshooting Bad Backup Set header and other similar errors

Resources


The error "Bad Backup Set header found" (and similar errors) indicates that Retrospect encountered an issue when reading a section of the backup set. There are two possibilities:

  • Hardware issue: There could be a bad connection, a bad drive, or bad media. See below for troubleshooting hardware.

  • Data issue: A hardware issue led to bad data on media. To ensure the data is recoverable, please do a verify, a rebuild, and a restore of a recent backup. If these succeed, the data is intact. If any of these fail, the data is not intact. Please change to new media, create a new backup set, and perform a large backup. A large backup with new media should indicate whether the hardware issue is still occuring.

Troubleshooting hard drives:

  1. Run a disk check utility to verify the disk is functioning correctly.

Troubleshooting USB/Firewire devices:

  1. Make sure the connection between the backup device and the computer is secure. Connect devices directly to the computer. Do not daisychain devices or connect the device through USB/Firewire hubs.

  2. Try different ports and cables. Try the device on a second computer. If there are still errors, it is an indication that there is a problem with the device. If the device works properly on a second computer, it is an indication that there is a problem with the original computer.

  3. On Windows, make sure the computer has the latest USB/Firewire card drivers.

  4. Firewire users should try disconnecting all firewire devices except for the backup device and try again. As an example, Firewire Webcams have been known to cause communication problems with hard disks.

  5. In rare cases, the firmware for the USB Bridge (part of the external USB drive case) may need to be updated. Check with the external drive or USB bridge maker for updates.

  6. Make sure the USB 2 devices are being used with a USB 2 port for best performance.

Troubleshooting SCSI devices:

  1. Make sure the device is properly terminated. If there are other devices daisychained, disconnect the other devices and connect the device that you are having problems directly to the computer.

  2. Update the drivers and firmware for your SCSI card and update the firmware for your device if possible. Try different SCSI cards, cables and terminators.

  3. If you are using Retrospect for Macintosh, verify that the SCSI card you’re using is supported by the specific OS version. Note: Adaptec has dropped support for the Mac OS as of 10.3.x. Most devices are qualifed on the Macintosh using ATTO UL3 and UL4 SCSI cards.

  4. Try the device on a second computer. If there are still errors, it is an indication that there is a problem with the device. If the device works properly on a second computer, it is an indication that there is a problem with the original computer.

Troubleshooting Fibre Channel devices:

  1. Try different fibre channel cards and cables and make sure the cable is connected securely. Update the drivers and firmware for the fibre channel card. Update the firmware for the device.

  2. Try the device on a second computer. If there are still errors, it is an indication that there is a problem with the device. If the device works properly on a second computer, it is an indication that there is a problem with the original computer.


Última atualização: February 3, 2015