There really is not any error messages, except some CPA>CPS jobs run very slowly, and replication never finishes. If I monitor the job, I see the job hang or really slow down on certain jobs. Here are some followup questions::
1. In the past in my environment, some CPA>CPS jobs ran simultaneously with BE10d(writing to tape) jobs. This caused some file corruption on the CPS volume locations, and tech support explained that CPA>CPS jobs MUST NOT run at the same time as BE10d tape backup operations on the same fileset.
If there are corrupt files present on the CPS volume (due to the above), will subsequent CPA>CPS jobs be able to overwrite the corrupt file with the "good" file from the CPA server, or will the CPA>CPS operation fail/stop/slow-down when it gets to the corrupt file on the CPS volume?
2. Why does the Journals directory on CPA servers contain files from several days ago, when the CPA>CPS job is schedule to run daily?
3. How does the Journals directory on CPA servers get populated?