Peer Software Forums: PeerLock and Replication Latency - Peer Software Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

PeerLock and Replication Latency How is the Release handled

#1 Guest_Christoph Kuderna_*

  • Group: Guests

Post icon  Posted 22 January 2008 - 07:06 AM

Hi,

I'm evaluating ways to use MS DFS-R and add remote file-locking through PeerLock.
I have a few technical questions and hope they can be answered here.

We have two servers that replicate using MS DFS-R as included in Server 2003 R2 and those servers have finished initial replication. When a file is now opened on Server A, the lock is put on the same file on Server B. When the modified file is closed on Server A and DFS-R starts to replicate the changes to the file this may take quite a while depending on the network bandwidth.
Doesn't the fact the PeerLock removes the lock on the file on Server B cause this server to initiate a replication back to Server A which might interfere with the already pending replication from Server A to Server?
In my testlab I added a large amount of data to Server A and replication started (some empty folders started to appear on Server cool.gif. Now when a file was opened on Server A before it had replicated to Server B (the parent folder was already on Server cool.gif, the NTFS permissions of the file were "lost" on Server A. They were actually reset to Windows default permissions.
I'm wondering if that may have been caused by PeerLock.

Is there a recommendation to disable it for large structures that have not completely replicated yet? Or should I stop users from accessing folder structures where replication has not been completed yet?

It would be great if you could provide some insight into this, as I really believe PeerLock could be great tool for a lot of our customers.

Thank you
Chris
0

#2 User is offline   PS_Support Icon

  • Advanced Member
  • PipPipPip
  • Group: Admin
  • Posts: 818
  • Joined: 05-December 03

Posted 22 January 2008 - 09:20 AM

Chris,

When using PeerLock in conjunction with DFS-R we recommend disabling the "Detect Files when Target Does Not Exist (Create Target Stub File)" setting. With this setting PeerLock will create a 0 size stub file on the Target if the file does not exits. When the source file is released the stub file will be removed. The only time PeerLock will create a stub file is if a Source file is open and the same file does not exist on the Target. This might explain why you have a directory structure created on the Target. Furthermore, DFS-R has no understanding of PeerLocks’ usage of stub files, therefore it might replicate the Target stub file and overwrite the Source file.

Let us know if you have any other questions.

Sincerely,
Peer Software, Inc.
Technical Support Team
0
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users