RepliStor not mirroring new DiskXtender BIN files

If I got you correctly the bin files are on the extended drive and they are turned to stubs by disk extender evetually? What I found out is that Replistor and DiskXtender do not work well together - diskXtender uses the custom file attributes to create stubs and Replistor does not "understand" them. I suspect that's what's going on in your case as well.

There are some configuration settings that are required for RS & DX to work together. If you use the following the 2 product are supported and work completely fine together.
1. DX must be at at least 5.60.049 Patch 4.
2. DxDmService.exe must be listed as a Process Exclude in RepliStor
3. If using RepliStor 6.2 Sp1, The Sync Offline Files option must be enabled in the Spec Mirroring Options.

Since you are using AX to write to DX, there is an extra caveat in this solution. In a typical AX/DX solution, the applications AX uses RPC to talk to DX to pass its data to the Extended drive. Depending on how you have your Document Write Path setup in AX, the I/O may be getting written without RS 'seeing' it.

There are 2 ways to get around this:
1. Change the Document Write Path in AX so it uses a UNC path (\\DXServer\AXPath) to the extended drive instead of a direct path such as X:\Application\path.

2. Take the DxDmService out of the Process Excludes in RepliStor.
NOTE (VERY IMPORTANT): If you do this, it is critical that you are not using Purge Rules on the Source box. If you are using Purge Rules file truncations will be picked up by RS and replicated to the Target. We do not want this b/c the files are getting truncated outside of DX by RS and you basically end up with erroneous data on the Target.

By taking the service out of the Process Exclude, we are telling RS to see ALL I/O operations coming from AX and evetuanlly DX.

Normally, we would want the DxDmService.exe as a process Exlcude b/c we want RS to ingnore operations coming from DX, such as Purges.