Unsolved

This post is more than 5 years old

78 Posts

561

September 11th, 2009 07:00

Blocked Files

My Replistor setup in an image collector mode. I am replicating the entire OS drive to a secondary drive on a different server. I am getting a blocked file that I can't seem to get rid of the blockage. The file is defined as the Master File Table ($MFT). The exact blockage is listed as:

Source: "C:\" "$MFT"
Destination File: \\?\L:\$MFT::$DATA

This is not a folder or file within the OS, it's the Master File Table.

I have deleted the specification and re-added. I don't get this blocked file immediately, but when the Sync is almost done. I have seen this before on other servers, but there was no fix, it just went away after I re-added my specs. This time it seems to be consistent.

262 Posts

September 17th, 2009 19:00

Hi,

What is image collector mode?

It doesn't know such a mode.

How do you set it up?

2 Intern

 • 

106 Posts

September 18th, 2009 07:00

You are correct that this is the Master File Table and we have seen some instances where this file can be blocked. It does not always happen as you noted.

I recommend you upgrade to version 6.4 of RepliStor as a first step. There has be some work on using RepliStor to replicate the entire boot volume and specifically as regards this issue.

However, you can also specifically exclude this by adding a manual entry in the RepliStor registry. I will not go into the specifics in this response but I would recommend you contact EMC Technical Support to investigate this specific workaround.

Also, I assume you have checked the Boot Load the driver box. This is documented in the White paper on Powerlink.

2 Posts

October 22nd, 2009 01:00

Replistor 6.3.1.3 has a fix for blocked files and replicating registery with VMWARE VM. i have implemented a rather large site with several image collectors, it occasionally has issues with VSS, however since the patch for Replistor 6.3 i don't see any more blocked files. please note the following:
1) you need to use the "load boot driver" and restart the source server.
2) create a seperate specification for each source drive
3) place the data directory on C drive, and verify the drive has sufficient free space (configure disk space monitor to avoid congesting C drive)
4) blocked file can also be caused by using VSS, so be carefull when using it.

2 Intern

 • 

106 Posts

October 27th, 2009 10:00

One additional comment: We have found that the image collector concept does not work with Windows 2008 R1, or R2. Replicating the boot drive results in a DR image that will not boot. Development is currently working on this issue but at this point, the Image Collector concept only works with Windows 2003.

RepliStor 6.4 also addresses the $MFT blocked file issue but as mentioned only for Windows 2003 at this time.
No Events found!

Top