Master to Replica file server and RFS to Master

Hi @SM_10773308 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Best regards,

Hi SM_10773308,

the normal way files travel is as follows:
- uploads with preference set to master will go to master and get replicated when they are requested with site set RFS1 or RFS2 or by predictive caching schedule if configured

- uploads with site set RFS1 will go to RFS1. When requested with setting to master or RFS2 they will be adhoc copied to master or RFS2, otherwise they will be collected by the background queue router3.1 or by forced sync of the file server. 

- uploads with site set RFS2: see above and replace RFS1 and RFS2.

the replica download works as follows:
- site set to RFS1, download file A.PRT 

- the system checks whether A.PRT is already replicated to RFS1

- if a copy of the file is already there the user gets the download link for the file on the RFS1 server

- if a copy of the file is not present the replica file server downloads (syncs) the file from the master or adhoc from another file server and afterwards the user gets the download link for the file on the RFS1 server.

Hi @SM_10773308,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.
Please note that industry experts also review the replies and may eventually accept one of them as solution on your behalf.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,