Issue

Christopher
Technical Support
StableBit DrivePool
2.1.1.561
Windows 7 (64 bit)
Public
Alex

I don't see anything in the trace file that indicates any kind of problems. Unfortunately due to the amount of disk activity it only captured about 40 seconds worth of history (limited to 100MB log file -- 1.1 million lines of decoded text) and I don't see any write activity to any of the go_ape files.

The Service log looks fine and the Error Reports are not showing anything that would indicate drive corruption.

----

I just did a restore of 2.2 GBs of mostly jpegs (1,786 files) to the pool and compared the restored copies with the originals, byte by byte, and they are all identical. This was in a x3 duplicated folder on a 25+ TB pool.

I used CrashPlan 3.6.4 on Windows Storage Server 2008 R2 Essentials (same kernel as Windows 7) and StableBit DrivePool 2.1.1.561.

I did notice that CrashPlan uses over 300MB of RAM while restoring. It loves that memory.

I suspect that something else might be causing this, or at least affecting the restore process somehow. Perhaps some 3rd party software is involved in indexing the files as they're being restored? Or perhaps the disk that StableBit DrivePool selects to store the restored files on is itself having some kind of issue? It's hard to say, but I definitely can't reproduce any kind of restore corruption over here.