Highlighted

The Changed Data Volume Is Not Replicated / Synchronized in the Seconday Host

I created a replication set as follows

pic1.jpg

 

untitled1.JPG

 

Problem:

When a folder is created in the data volume in the primary host, the secondary host's data volume is not updated or replicated with the folder even after waiting it for a day. The folder does not exist in the secondary host.

Can you guys assist me on this. What is the cause of the problem?

 

Thanks

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Hi! Making the assumption

Hi!

Making the assumption that you're browsing the secondary rather than performing a migrate!

VVR operates at block level underneath the filesystem.  This means that replicated changes don't necessarily reflect when browsing the secondary as the blocks are written to the disk without the local NTFS instance knowing about it.  This makes browsing the secondary an unreliable way to validate the secondary data.

If you remove the drive letter and re-add it on the secondary side you should force NTFS to refresh and then see your folder.

Dan

View solution in original post

2 Replies
Highlighted
Accepted Solution!

Hi! Making the assumption

Hi!

Making the assumption that you're browsing the secondary rather than performing a migrate!

VVR operates at block level underneath the filesystem.  This means that replicated changes don't necessarily reflect when browsing the secondary as the blocks are written to the disk without the local NTFS instance knowing about it.  This makes browsing the secondary an unreliable way to validate the secondary data.

If you remove the drive letter and re-add it on the secondary side you should force NTFS to refresh and then see your folder.

Dan

View solution in original post

Highlighted

Hi,   Agree with Dan (Hi Dan,

Hi,

 

Agree with Dan (Hi Dan, long time)

 

Also, to show its working, make a file on the primary, echo 1 to the file, then migrate to secondary, open the file and verify 1 is there, then echo 2 to the file, then migrate back to the primary and check the file has 1 and 2 in it.

 

Make sure you're in sync at before any migrations.