We currently have one master site and one remote site with limited bandwidth between them. A remote file server has been configured to reduced the load on on the WAN connection during business hours and improve CAD application performance for the remote users. Unfortunately, publishing seems to be defeating this functionality. Publishing is currently configured to happen on check in. I'm curious if there is a better way to configure things.
Desired Functionality:
1.) Remote user uploads data --> data is stored on remote file server only
2.) Later, when replication is scheduled to take place (off hours)
a.) Data on remote file server should be copied (replicated) back to master server.
b.) Data on remote file server should be moved to replica vault (instead of cache vault).
3.) Once data arrives at the master server, it should then be published.
- Of course for users at the master site, publishing should still take place immediately upon check in.
Actual Functionality:
1.) Remote user uploads data --> data is stored on remote file server only
2.) WVS publishes the data
a.) The file is copied file from remote file server to the publish server - ACROSS the WAN
b.) The publisher publishes the files and then stores them on the master server (local).
c.) The files used for publishing are then deleted from the publish server
3.) Later, when replication is scheduled to take place (off hours)
a.) Data on remote file server is copied (replicated) back to master server - ACROSS the WAN AGAIN
b.) Data on remote file server is moved to replica vault (instead of cache vault).
I'm not sure the impact, but WVS authentication is currently set to use the user's credentials during the publish job (auth=$user). I'm concerned that this may cause WVS to pull from whatever file server the user has configured for their default vault, regardless of where the publisher is physically located.
Is there a way to have all data checked into the master server published on check in but delay publishing data checked into the remote site until after the data has replicated?