The most ideal way to trigger the synchronization is when there is change in each share folder, and queuing the sync processes when there are multiple changes detected. It is beyond the scope of this post. >robocopy /E /PURGE /COPY:DAT \\SERVER\share_images C:\images
Then I could execute robocopy with something like the following:
>net use \\SERVER\share_images /USER:user1 password1 In order to do that, before I run robocopy, I use net use command for authenticating. Since I need to access the shared folder, I need to make sure that the connection could be established using correct user for authentication. I choose robocopy for its simplicity and it does the job well. Within the share folder I put the large image files to be distributed to the clients. My strategy is creating a chain distribution, from the Server to PC-01, PC-01 to PC-02, and so on, until PC-10. I have samba configured as shared storage. Let me give a little bit info about the infrastructure. įinally I implemented my distribution strategy as I explained in my previous post.
This post is related to my previous post about distributing large files.