I am trying to test an evaluational version of SFW. Have a problem with its VVR component between 2 Hyper-V VMs with Windows Server 2008.
Setup went fine, I setup replication without any problems. Status is Active and Green, I can see "Blocks Send" increasing, log filling and emptiing, everything seems to be ok.
Nevertheless secondary server's replicated disk do not update it's content/files until I stop replication and restart it again. No error anywhere.
it could be a silly question, I still want to ask, while you are replicating data from the primary to the secondary, do you keep the volume at secondary mounted all the time?
Your wordings gave me above feeling, sorry if not.
For volume on secondary, the volume is not meant to be accessed while replication happening. You can create a snapshot agains the volume at secondary, mount snapshot to access data and also you can refresh this snapshot periodically.
Very good question. It shows me that I was misunderstanding the concepts. Indeed, I am trying keep secondary volume mounted and access it. Is it possible, or it should be offline all the time by VVR design?
actually the other day, I forcibly mount the secondary volume, while it doesn't reflect the content that is being continuously updated. Just the mount take a snapshot when the file system is mounted.
For secondary volume access, I believe with a snapshot, plus a period refresh, is all you can. That is the basic principle to keep secondary volume unble to be accessed. the same thing like sun AVS, or emc SRDF.
But why they don't permit a read-only mount and reflect the real-time date update?