After a mastership request is processed at the master replica, sync_export_list is
invoked to export an update packet to the replica at the requester's
site. You can customize the export by specifying one or more of the
options and arguments that are valid for sync_export_list,
except for –replicas, which is always the
replica at the requester's site.
Procedure
-
On the VOB server host of the exporting replica, edit the file /var/adm/devops/clearcase/config/rfm_shipping.conf (Linux® and the UNIX® system) or
ccase-home-dir\var\config\rfm_shipping.conf (Windows®).
On Linux and
the UNIX system,
MultiSite installation creates the file
ccase-home-dir/config/services/rfm_shipping.template. If /var/adm/devops/clearcase/config/rfm_shipping.conf does not exist,
the installation creates it by copying the template file. If /var/adm/devops/clearcase/config/rfm_shipping.conf exists, a
note is printed in the installation log advising you to compare the existing file to the template
and make any necessary changes.
On Windows, MultiSite installation creates
the file ccase-home-dir\config\services\rfm_shipping.template. If ccase-home-dir\var\config\rfm_shipping.conf does not exist, the installation creates it by
copying the template file. If ccase-home-dir\var\config\rfm_shipping.conf exists, you must compare the existing file to
the template and make any necessary changes.
- Add the options and arguments to the following line:
RFM_OPTIONAL_ARGUMENTS =
For example, to compress update packets:
RFM_OPTIONAL_ARGUMENTS = -compress
To suppress informational messages, use a specific
shipping class (in this example, reqmaster), and
compress update packets:
RFM_OPTIONAL_ARGUMENTS = -quiet 1 -compress -sclass reqmaster