corrupt file and restore

[Kenneth Brody]

On 2/8/2011 10:51 AM, Dennis DIller wrote:
> The file has 48k

By "the file", I assume you mean the blob file?

While a "fresh" blob file is 48K, the file is initialized to contain several 
blocks of usable data.  On a small file, or a file with only a few memos, 
the blob file might never grow larger than this original 48K

> It was backup using Ipswitch WS_FTP Pro

In binary mode, I hope.

> The key file on a qual. file I assumed was bad
> because during back up this file failed

What error was given?

If the backup failed, then restoring from that backup won't help.

> I could not go into define files

Why not?

> or see any data in dclerk

What, exactly, did you see in dclerk?

> But I could see the other qual. file in dclerk in the same file

By that, I assume you mean that the other qualifier had records with data in it?

> during back up the only file that would not move over was keyeusa & lockfeusa

What error was given?

> I tried doing a delete lock file no luck either

What sort of "luck" were you expecting by deleting the lockfile?

> so I did a restore on the
> whole filepro dir.
> that the corrupt file was in.

Was the backup that you restored from any good?

> since the only files did not move over was the keyeusa and lock file

What error was given?

And by "move over" do you mean the backup or the restore?

> and went to that newer back up and moved over the blobeusa

So you restored a mismatched key and blob file?

> when I look into the file there is no data
> memo 28 edit ("5","20","12","39")

Was the backup that you restored from any good, and did you restore a 
matching key and blob?

-- 
Kenneth Brody