Why does ByteReplicator use .BRTMP temporary files?
When updating a file on the target, the PSListener will rebuild the file on the target with the bytes that are already there, plus the new bytes PeerSync is sending it. You will see this as a .BRTMP file extension. Once the build of the temporary file completes successfully, the temporary file will be renamed to the original file name, and the original file will be deleted. This method is used so that we do not interfere/manipulate the original target file. We want to be sure that all the work is completed successfully before we update the target file all at once.
Related articles
- Can I use DFS Namespaces when specifying folder paths in PeerSync?
- Configure PeerSync Listener's advanced settings
- Configure the PeerSync Listener installer to run unattended
- Does PeerSync Listener have to be installed on both servers when using the ByteReplicator?
- How does the ByteReplicator work?
- Set up synchronization/replication over TCP
- Upgrade PeerSync and PeerSync Listener
- What is the disk space requirement for PeerSync?
- Why does ByteReplicator use .BRTMP temporary files?