Update to this problem. The replication schema was pointing to the root directories on both archive servers and for some unknown reason it would not start replicating on one or both of the servers. When the root directory was removed from the schema and replaced with the next level of folders down everything worked fine. There were no files in the root directory to replicate, the files were all in lower level folders.
This is not solved as I want the root directories to work so when a new folder is created it will be replicated without having to go modify the replication schema every time.
It is as if the path was corrupted when it went to replicate, but the test function in replication settings passed.
I will post eventual solution when known.
I can see that your reseller worked with SolidWorks technical support on this issue when you reported it last year but I do not know what the outcome was.
In any case, the behavior that you describe where a scheduled replication fails to start if you have selected the file vault root and not individual subfolders is a known issue that is logged under this SPR:
435449 "Unable to 'schedule' replication of entire PDMWorks Enterprise vault when files are all contained in sub folders and not in root of vault"
The problem is that it is not fully reproduced in all environments - som vaults work just fine and others won't.
In the cases where it fails, we have seen that if you add at least one file to the vault root folder, the schedule will start working again. So if you still see the issue, try adding for example a txt file to the vault root and see if things improve.
-Tor Iveroth, EPDM support.
What is your replication schema?.Servers get laggy when replication schema time set to high frequency le.g.: * * *(everyday ,every hour,every minute).try to put replication time with say 5hr gap. and also stop it after 3 1/2 hrs.It all depends on how much data you are generating.
Thanks for the suggestion.
We currently are replicating every hour on the hour. 0 * *.
I see it stopped working over the 4 day holiday as our UK office had 2 days of work during that time that has not been replicated, even though the archive server log says it has been starting a replication every hour but the file count never decreases and stays the same.
We'll do some more investigation today and maybe get this issue sorted.
For initial testing let the replication happen every 2hrs and make sure it stops after 1hr45min.If there are file that are not being replicated you need to get that exact number.
after this you can generate the list of unreplicated files and try to perform a "get" operation,on servers where the file is not replicate.if on-demand replication goes well then id say problem is with the time.but if you get an error such "file could not be found on archive........" etc.the problem can be with your Data (EPDM storage).