CC-RTC Synchronization - synchronizing a large number of files
Hi,
We're using cc-rtc-synchronizer to synchronize from ClearCase Streams to RTC (v4.0.6)
Our ClearCase stream is configured with 30~ components, in total 300K files. Total size of 130 GB.
The synchronization is one-way, and should synchronize from CC to RTC on a daily basis.
Also, we need to synchronize several of these CC Streams (same components each), due to parallel devolopment.
Is there a smart way to synchronize this large workspace ?
Should I divide the synchronization into a number of integration streams ?
Can I schedule the synchronization process to run for each component on a different time ?
Thank you,
Yael
We're using cc-rtc-synchronizer to synchronize from ClearCase Streams to RTC (v4.0.6)
Our ClearCase stream is configured with 30~ components, in total 300K files. Total size of 130 GB.
The synchronization is one-way, and should synchronize from CC to RTC on a daily basis.
Also, we need to synchronize several of these CC Streams (same components each), due to parallel devolopment.
Is there a smart way to synchronize this large workspace ?
Should I divide the synchronization into a number of integration streams ?
Can I schedule the synchronization process to run for each component on a different time ?
Thank you,
Yael
One answer
I think one of the challenge is the initial synchronization, which potentially takes long. The subsequent synchronization only replicates delta from the last successful synchronization, so I expect it finishes in reasonable time ( which depends on the volume of the changes, although). In either case, the ClearCase stream is locked during the synchronization, so this work-around article may help you to configure the synchronization.
Workaround: Create a lock-free Rational ClearCase synchronization for UCM streams by running custom scripts
I do not recommend to break it to multiple synchronization because every synchronization attempt to lock the stream.
Workaround: Create a lock-free Rational ClearCase synchronization for UCM streams by running custom scripts
I do not recommend to break it to multiple synchronization because every synchronization attempt to lock the stream.