Tuesday, May 4, 2010

Repairing corrupt BKF file from multiple tape set

Most of you must have faced the agony of data loss due to sundry reasons. In such situations, a lot of people crib over not having a tool to take timely backups of the valuable data. Well, the things are not so terrible actually. For those who don't know, Windows (2000, XP, and Server 2003) users can use the NTBackup utility that enables you to take the backups in different modes such as differential and incremental modes. The backups, using NTBackup, are created in the form of BKF files. However, sometimes these BKF files too can get corrupted. In such cases, you should take appropriate corrective measures to solve the issue. However, if you are unable to do so then you should use a third-party BKF repair tool to repair BKF file.

Consider a scenario wherein you have taken the backup of some data in a multiple-tape set. The backed up data is located on two different tapes. When you try to restore the BKF file, you are unable to do so. An error message is displayed, that is:
“Error: An inconsistency was encountered on the requested media”

This error message is displayed when you restore the BKF file from the first tape, and start restoring the data from the next tape.

Cause:
The cause of this error message is that NTBackup prompts you to mount the incorrect piece of media to restore the backup from. Stated problem occurs when backup is appended innumerable times to make it reside on different members of a media set, not for a single backup set spanning a number of media.

Resolution:
To address this issue, you should select and restore and BKF file from one backup set at a time. This should resolve the problem. However, if you are still not able to resolve it then chances are that the BKF file is corrupt and, therefore, inaccessible. In such cases, you should use a third-party BKF repair tool to repair BKF file. Such read-only tools use fast yet sophisticated scanning algorithms to perform BKF recovery without overwriting the original data.

No comments:

Post a Comment