Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

EV10.0.1 FSA And Double-Take replication V6 problem

Created: 12 Feb 2013 • Updated: 01 Mar 2013 | 2 comments
This issue has been solved. See solution.

Hi,

We have setup FSA File server (Double-Take Source) and Double-Take target server as mentioned in the link below

http://www.symantec.com/business/support/index?pag...

However we can open any archived files fine from Source File server which is FSA Target server. But unable to open any archived files from Target File Server (Replicated File Server). FSA Agents installed and registry keys are set on source and target file server.

Just getting an inforamtion pop up message "Could not open file ...."

Is there anything else needs to be configured? What if the placeholders are created before setting up the registry key " AdditionalReparseTags a value of 10 (Hexadecimal)." in Source Server (FSA Target)?

Many Thanks

Comments 2 CommentsJump to latest comment

TonySterling's picture

It sounds like you followed the steps here for the Source, did you set the key on the Target server?

Support for File System Archiving from Windows file servers that run Double-Take replication software

Article:TECH183398  |  Created: 2012-03-09  |  Updated: 2013-01-18  |  Article URL http://www.symantec.com/docs/TECH183398

Also, is this only for files archived before you set the registry key?  Do ones archived afterwards work?

SOLUTION
ia01's picture

We have this one set as well

  1. On the Double-Take target server, create a DWORD registry value named ClearOfflineBit under the following registry subkey:

    HKEY_LOCAL_MACHINE
    \SYSTEM
     \CurrentControlSet
      \Services
       \EvFilter

Give ClearOfflineBit a value of 0. This registry value allows the replicated placeholders to show the placeholder icon and to display the correct size of 4 KB.

We can open some files however they are not showing correct Size on Disk. Any idea? Should show 4k for size on disk.

The files we can't open - Vault service account doesn't have explicit permissions on those shares.