Macrium Reflect images incorrectly reported as "other" files?

[jp7]

Hey all,

This is really more out of curiosity than an actual concern - I use Drivepool on a Windows 10 machine with an 11.8 TB pool. I use Macrium Reflect Workstation Edition to back up my Win 7 desktop to the pool on the Win 10 machine over the network. The current full image backup is about 1.1TB. Incrementals vary in size. What I have noticed is that although the backup image is duplicated within the pool (as it should be), DrivePool seems to think the 1.1tb backup image is an "other" file. In the screen shot, you can see what I'm talking about - the Macrium images are on drive G and duplicated to drive D respectively. I've tried rebalancing/remeasuring the pool and it made no difference. VSS is off as well on the Win 10 box, and so is Macrium Image Guardian. (MIG is installed but deactivated.)

It's not really a problem, since everything seems to be working, but it is disconcerting having the app not show what's actually happening. Does anyone have any idea what might be going on here?

 

[Shane]

Yeah, it shouldn't be doing that. Are D: and G: drives used for any non-pool files?

Maybe take a look at D: and G: drives with a program like WinDirStat (running as administrator, with Show Free Space and Show Unknown checked in Options)?

[jp7]

That is interesting. It does look like there's something there in the unknown category:

 

But even with Windows set to show hidden files, I can't see where that unknown file would be if not in the PoolPart folder:

No non-pooled files are on either D or G drives (as you can see above for G:). Very strange. Any ideas on what might be going on? I'm stumped.

Thanks!

[Shane]

Hmm. Might be a file/NTFS permissions issue. Try a utility called TreeSize Free as administrator? It lacks the shiny pincushion map, but it handles permissions a bit better and might help you track down the file(s) so you can check that.

Edit: might also want to run a chkdsk on the drive.

[jp7]

I looked at the permissions and System and Administrator users have full R/W permissions. Also ran CHKDSK and no errors were reported.

Here's the TreeSize analysis:

Very odd.

The Drivepool app still claims that there are no duplicated files on drive G:, even though the Macrium image is correctly duplicated from G: to other drives in the pool.

[Shane]

I'm stumped. There's just been a new stable release (2.2.4.1162) of DrivePool; if that doesn't fix it, might be worth opening a Support ticket as something's going on that literally doesn't add up.

[jp7]

Thanks. I did have the latest version installed in my previous post already, so no difference. I'll put in a ticket.