Retrospect Notes 
top

error -1103 write protected

I started to see “Scanning incomplete, error -1103 (write protected)” when backing up a disk which used to be able to backup successfully.

Why it happens?

It looks like Retrospect Express believes that the disk you are backing up is locked. Actually, Windows believes that way.

How to fix this?

Run CHKDSK /R drivename. When you run CHKDSK /R from the command prompt, you’ll see the following message:

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N)

My disk was formatted as NTFS. I cannot guarantee that answering ‘Y’ here won’t break anything, but I did. Once the check is done, I could backup the disk without the error by Retrospect Express.

(2/14/2007)

Directory structure

When a backup was made with Retrospect Express following directory structure are created:

\Retrospect \Dantz … empty file, but always created. \Backup Set A … backup set name \1-Backup Set A … 1-backup set name \AAxxxxx.rdb … a bunch of .rdb files.

imported