Home
Command Home

logo_header

Soft - is your software and documentation
Asset - is something that must be protected
Management - is what we do
Enterprise - is the capability
Computing - is the power
Services - are what we provide


 Scalable Graphic (-export)

 

Scalable Graphic (-import)

Scalable Graphic (manage)

Synopsis

sync/replica

–exp/ort [ –max/size max-packet-size [ –lim/it num-packets ] ] [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment ] [ –compress ] { { –shi/p | –fsh/ip } [ –scl/ass storage-class ] [ –pex/pire date ] [ –not/ify e-mail-addr ] | –out packet-file-pname } replica-selector ...

sync/replica

–exp/ort [ –max/size max-packet-size [ –lim/it num-packets ] ] [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment ] [ –view view-tag ] [ –nblocking | –blocking_duration minutes | –wait_forever ] [ –compress ] [ –lockwait minutes ] [ –workdir temp-dir-pname ] [ –jfile job_ids_file ] { { –shi/p | –fsh/ip } [ –scl/ass storage-class ] [ –pex/pire date ] [ –not/ify e-mail-addr ] | –out packet-file-pname } [ –from replica-selector [ –host hostname] ] replica-selector ...

sync/replica

–imp/ort [ –invob VOB-selector ] [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment ] { –rec/eive [ –scl/ass storage-class ] | { packet-file-pname | staging-area-pname } ... }

sync/replica

–imp/ort [ –invob VOB-selector ] [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment ] [ –view view-tag] [–nblocking | –blocking_duration minutes | –wait_forever] [–lockwait minutes] [–workdir temp-dir-pname] [ –jfile job_ids_file ] [ –retry_interval minutes ] [ –max_attempts num-attempts ] { –rec/eive [ –scl/ass storage-class ] | { packet-file-pname | staging-area-pname } ... }

sync/replica

–imp/ort –to replica-selector [ –host hostname] [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment] [ –view view-tag ] [ –nblocking | –blocking_duration minutes | –wait_forever] [ –lockwait minutes] [ –workdir temp-dir-pname] [–jfile job_ids_file] [ –retry_interval minutes] [ –max_attempts num-attempts] { –receive [ –scl/ass storage-class] | packet-file-pname ... }

sync/replica

–imp/ort –host hostname [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment] [ –view view-tag ] [ –nblocking | –blocking_duration minutes | –wait_forever] [ –lockwait minutes] [ –workdir temp-dir-pname] [–jfile job_ids_file] [ –retry_interval minutes] [ –max_attempts num-attempts] { –rec/eive [ –scl/ass storage-class] | packet-file-pname ... }

sync/replica

–cancel [ –f/orce] [ –active] [ –host hostname] –job {job-id | job-uuid}

sync/replica

–wait_for_jobs [ –nblocking | –blocking_duration minutes | –wait_forever] [ –host hostname] { –jfile job_ids_file | –job {job-id | job-uuid} [,...] }

Table of Contents

Synopsis. 7

Table of Contents. 8

A.       Description.. 9

B.       Notes on the export phase. 10

C.       Notes on the import phase. 10

D.       Retrying synchronization when the VOB is locked.. 13

Restrictions. 13

E.       Blocking the multitool command line. 13

Options and arguments -- Export phase. 14

F.       Specifying the update packet size. 14

G.       Event records and comments. 15

H.      Packet compression.. 15

I.        Disposition of the update packet. 15

J.        Handling packet-delivery failures. 16

K.      Specifying the destination replicas. 18

L.       Remote source replica.. 18

M.      Resolving object path names. 19

N.       Creating a synchronization job list. 19

O.       Options and arguments -- Import phase. 19

P.       Restricting the update to a particular VOB.. 19

Q.       Event records and comments. 19

R.       Specifying the location of the update packets. 20

S.       Resolving object path names. 20

T.       Creating a synchronization job list. 20

U.       Reattempting the import. 21

V.       Initiating import operations at a remote host. 21

Additional syncreplica options for managed replicas. 21

W.      Canceling a synchronization job. 21

X.       Waiting for synchronization jobs. 22

How do I use the multitool syncreplica command to.. 23

Exports. 23

1.       Generate (Export) an update packet to be sent to boston replica and store the packet in a non-default location.. 23

2.       Generate (Export) an update packet to be sent to boston replica, place the packet file in a storage bay, for shipping at some later time by the store-and-forward facility. 23

3.       Generate (Export) an update packet and send it immediately to the boston replica.. 23

4.       Send a sync (Export) update to all siblings of boston@/vobs/samecs_dev, which lives on host samecs. 24

5.       Send a sync (Export) update to replica boston and compress the packet. 24

6.       Send a sync (Export) update in a view context. 24

Imports. 25

7.       Process (Import) an incoming update packet in directory /usr/tmp. 25

8.       Process (Import) all incoming update packets in the current host's storage bays. 25

9.       Import a packet in a view context. 25

10.     Import packets intended only for boston replica which lives on host samecs. 25

11.     Import all packets, but return the command line to the User after waiting 5 minutes. 26

12.     Import packets and make 4 attempts, at intervals of 1 minute. Return the command line immediately to the user. 26

Other.. 26

13.     Cancel sync job 15 on host samecs. 26

14.     Wait for job 6 to complete. 26

 

A.           Description

Synchronization of an existing replica with one or more sibling replicas is a three-phase process:

1.     At one site, a syncreplica –export command creates a logical update packet that contains changes that have occurred in the replica at that site (and perhaps other replicas, also).

2.     The logical packet is sent to one or more other sites.

3.     At another site, a syncreplica –import command applies the changes in the logical update packet to its replica of the same VOB.

Step 3 occurs at all sites that receive the logical packet.

Contents of a logical update packet:

In all cases, syncreplica –export creates a single logical update packet for use at all the specified destinations; the packet can be used to update those particular replicas only.

B.           Notes on the export phase

MultiSite is designed for efficient updating of replicas. syncreplica –export attempts to exclude operations that have been sent previously. (However, there is no harm in sending an operation multiple times to the same replica; the first operation is imported and subsequent identical operations are ignored.)

The replica is not locked during the export phase; in fact, the syncreplica –export command fails if the VOB is locked. Therefore, you must not schedule synchronizations during VOB backups (when the VOB must be locked). See also Retrying synchronization when the VOB is locked.

Specifying a directory for temporary files

syncreplica –export stores temporary files in the directory specified by the TMPDIR environment variable on Linux® and the UNIX system and the TMP environment variable on Windows. If you use the sync_export_list script to export update packets, you can use the –workdir option to specify the directory.

If the replica you are synchronizing is managed, you can specify the –workdir temp-dir-pname option to syncreplica –export. If temp-dir-pname does not exist, a new directory is created. Running syncreplica –workdir on a non-managed replica will cause the request to fail.

C.           Notes on the import phase

A logical update packet is applied to the appropriate replica on the host on which you import it, unless you restrict processing with the –invob argument. syncreplica consults the VOB registry in the current region to determine the locations of these replicas' storage directories. Thus, you do not have to specify particular replicas or storage locations.

The import process applies logical update packets in the correct order. Therefore, you can specify packets in any order on the command line.

The VOB replica is not locked during the import phase. Synchronization fails if the VOB is locked. See also Retrying synchronization when the VOB is locked.

Specifying a directory for temporary files

syncreplica –import stores temporary files in the directory specified by the TMPDIR environment variable on Linux and the UNIX system and the TMP environment variable on Windows. If you use the sync_receive script to import update packets, you can use the –workdir option to specify the directory.

If the replica you are synchronizing is managed, you can specify the –workdir temp-dir-pname option to syncreplica –import. If temp-dir-pname does not exist, a new directory is created. Running syncreplica –workdir on a non-managed replica will cause the request to fail.

Skipping packets

syncreplica –import refuses to process an update packet in the following situations:

In these cases, syncreplica –import displays an explanatory message.

With the Sync Manager managing the import, packets arriving out of order will be queued. When the missing dependencies arrive and are imported, queued packets are imported automatically, and in the correct order.

Update failures / replaying packets

In some cases, syncreplica –import begins to apply operations to a replica, but fails with an error message. For example, another process may have locked the VOB, causing the import to fail. After the VOB is unlocked, you can run syncreplica –import to process the entire update packet again.

There is no harm in importing update packets that have already been processed successfully; the same change will not be made twice.

For more information about update failures, see "Troubleshooting MultiSite operations" in IBM Rational ClearCase MultiSite Administrator's Guide.

Deletion of update packets

If a single invocation of syncreplica –import applies a packet successfully to all target replicas on the host, the update packet is deleted when the command completes its work. If the packet is processed with multiple syncreplica –import –invob commands, it is not deleted.

Preservation of identities and permissions

If a VOB replica preserves identities and permissions, syncreplica –import maintains the consistency of identities and permissions information for elements mastered by the VOB family's identities- and permissions-preserving replicas. For each such element, an error occurs if the element's group is not on the group list of the importing replica (on Linux and the UNIX system) or is not the same as the group of the importing replica (on Windows).

If a VOB replica preserves permissions only, syncreplica –import maintains the consistency of permissions information for elements mastered by the VOB family's identities- and permissions-preserving replicas and permissions-preserving replicas. Changes to identities for existing elements are ignored during import. New elements are assigned to the owner of the VOB at the current site, and the group of all new elements is the primary group of the VOB. (This is true even if the root user or a member of the ClearCase® administrators group imports the packet.)

If a VOB replica is nonpreserving, changes to identities and permissions of existing elements are ignored during import. New elements are assigned to the owner of the VOB at the current site, and the group of all new elements is the primary group of the VOB. (This is true even if the root user or a member of the ClearCase administrators group imports the packet.) Permissions set when the element is created are preserved, but subsequent permissions changes are ignored. Identities and permissions changes made at nonpreserving replicas are not propagated to other replicas.

Storage pools

Data containers from the update packets are placed in storage pools according to the standard element assignments. If the pool assignment for a new element cannot be determined, the element is assigned to the VOB's default source pool.

Trigger firing

ClearCase triggers do not fire in response to changes made during packet import.

Handling naming conflicts

syncreplica resolves naming conflicts among objects created at different replicas. For more information, read about conflict resolution in the "MultiSite operation" chapter of IBM Rational ClearCase MultiSite Administrator's Guide.

Delayed view updates

syncreplica does not inform any views (not even the view from which you enter the command) of the updates to replicas. All active views see updates within a few seconds, through their normal VOB-polling routines. You can force a view to recognize VOB updates by entering a cleartool setcs –current command.

D.           Retrying synchronization when the VOB is locked

By default, synchronization exports and imports fail if the VOB is locked. To allow syncreplica to retry a synchronization when it encounters a lock, set the CLEARCASE_VOBLOCKWAIT environment variable to the amount of time (in minutes) for syncreplica to keep trying to write to the VOB. For managed replicas, synchronization imports automatically retry a synchronization when a lock is encountered. You can specify the number of minutes to keep trying to write to the VOB using the –lockwait option to syncreplica.

During that time, syncreplica retries the write operation every minute. If the time elapses or CLEARCASE_VOBLOCKWAIT is set to zero, and the VOB is still locked, syncreplica exits with an error.

Note: syncreplica waits only if it detects the lock before it starts processing operations. If an administrator locks the VOB during processing, syncreplica exits with an error.

Restrictions

Identities: You must have one of the following identities:

To “wait for synchronization,” only Read permission on the MultiSite Administration ACL is required.

Locks: An error occurs if one or more of these objects are locked: VOB.

Mastership: No mastership restrictions.

Other: You must run syncreplica on the host where the VOB storage directory resides or use the –to and –host options to run syncreplica remotely. See Initiating import operations at a remote host.

E.           Blocking the multitool command line

When you issue a synchronization request with syncreplica on a managed replica, you can choose to specify a blocking duration for all jobs related to that request. Blocking duration refers to the amount of time that passes after you issue a synchronization request before you regain control of the multitool command line. You can also choose to run a job in “non-blocking” mode, which means that you regain control of the command line immediately after issuing a synchronization request. You can then monitor the progress of associated synchronization jobs by running multitool commands.

By default, if you do not specify a blocking duration, the command line does not return until the synchronization request completes (–wait_forever)...

–nblocking | –blocking_duration minutes | –wait_forever

Specifies the amount of time that passes after you issue a synchronization request before you regain control of the multitool command line. With –nblocking, you regain control of the command line immediately; with –blocking_duration, you regain control of the command line after a specified number of minutes, or when the synchronization request completes, whichever comes first; with –wait_forever, the command line does not return until the synchronization request completes.

Options and arguments -- Export phase

F.            Specifying the update packet size

Default

Each oplog together with its version data is treated as one physical packet.

If you do not specify –maxsize, the default packet size depends on the shipping option:

·                                    Packets created with –ship or –fship are no larger than the maximum packet size specified in the shipping.conf file (Linux and the UNIX system) or the MultiSite Control Panel (Windows).

·                                    Packets created with –out are no larger than 2097151 KB (2GB-1 KB).

–max/size max-packet-size [ –lim/it num-packets ]

The maximum size for a physical packet, expressed as a number followed by a single letter. For example:

500k

500 kilobytes

20m

20 megabytes

1.5g

1.5 gigabytes

The –limit option limits the number of files syncreplica generates; each file is no larger than max-packet-size. Use this option when the disk space for your storage bay or staging area is limited.

G.           Event records and comments

Default

Creates one or more event records, with commenting controlled by the standard ClearCase user profile (default: –nc). See Event records and comments in the multitool reference page. To edit a comment, use cleartool chevent.

–c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment

Overrides the default with the specified comment option.

H.           Packet compression

Default

Packets are not compressed.

–compress

Compresses all export packets.

Compression has no effect on packet naming. Use lspacket –long to display packet compression information.

I.              Disposition of the update packet

Default

None. You must specify how the update packets created by syncreplica –export are to be stored or transmitted to other sites.

If you use –ship or –fship and omit the –sclass option, syncreplica places the packet in the storage bay location specified for the –default class in the shipping.conf file or the MultiSite Control Panel. By default, this location is /var/adm/rational/clearcase/shipping/ms_ship on Linux and the UNIX system and ccase-home-dir\var\shipping\ms_ship on Windows.

–shi/p

–fsh/ip

Stores the update packet in one or more files in a store-and-forward storage bay; syncreplica creates a separate shipping order for each physical packet, indicating how and where it is to be delivered. The destinations are the host names associated in the VOB database with the replica-name arguments. (Replica-name/host-name associations are created with mkreplica –export and can be changed with chreplica.)

Using –f/ship (force ship) invokes the shipping server to send the update packet immediately. Using –shi/p does not invoke this server. To run shipping_server to send packets in storage bays, schedule sync_export_list –poll with the schedule command. (See the schedule reference page in the IBM Rational ClearCase Command Reference.)

–scl/ass class-name

Specifies the storage class of the packet and shipping order. syncreplica looks up the storage class in the shipping.conf (Linux and the UNIX system) or the MultiSite Control Panel (Windows) to determine the location of the storage bay to use.

Attention: Be sure to deliver a packet created with –out to its specified destinations promptly. If a replica has not yet received and applied this packet, it may not accept any subsequently generated packets from your replica until the first packet is received and processed.

–out packet-file-pname

The name of the first update packet. Additional physical packets, if any, are placed in files named packet-file-pname_2, packet-file-pname_3, and so on.

The update packets are not delivered automatically; use an appropriate method to deliver them.

You can create a packet using –out, and deliver it using the store-and-forward facility. See the mkorder reference page.

J.            Handling packet-delivery failures

Default

If a packet cannot be delivered, it is sent through the store-and-forward facility back to the administrator at the site of the originating replica. A mail message is sent to the store-and-forward administrator. This occurs after repeated attempts to deliver the packet have failed, and the allotted time has expired; it can also occur when the destination host is unknown or a data file does not exist. The store-and-forward configuration settings specify the expiration period, the e-mail address of the administrator, and the notification program.

–pex/pire date-time

Specifies the time at which the store-and-forward facility stops attempting to deliver the packet and generates a failure mail message instead. This option overrides the expiration period specified for the storage class in the shipping.conf file (Linux and the UNIX system) or MultiSite Control Panel (Windows).

The date-time argument can have any of the following formats:

date.time | date | time | now

where:

date:

= day-of-week | long-date

time:

= h[h]:m[m][:s[s]] [UTC [ [ + | - ]h[h][:m[m] ] ] ]

day-of-week:

= today |yesterday |Sunday | ... |Saturday |Sun | ... |Sat

long-date:

= d[d]month[[yy]yy]

month:

= January |... |December |Jan |... |Dec

Specify the time in 24-hour format, relative to the local time zone. If you omit the time, the default value is 00:00:00. If you omit the date, the default value is today. If you omit the century, year, or a specific date, the most recent one is used. Specify UTC if you want the time to be resolved to the same moment in time regardless of time zone. Use the plus (+) or minus (-) operator to specify a positive or negative offset to the UTC time. If you specify UTC without hour or minute offsets, the default setting is Greenwich Mean Time (GMT). (Dates before January 1, 1970 Universal Coordinated Time (UTC) are not valid.)

Examples:

·                     22-November-2002

·                     sunday

·                     yesterday.16:00

·                     0

·                     8-jun

·                     13:00

·                     today

·                     9-Aug.10:00UTC

–not/ify e-mail-address

The delivery-failure message is sent to the specified e-mail address.

If a failure occurs on a Windows host that does not have e-mail notification enabled, a message appears in the Windows Event Viewer. The message includes the e-mail-address value specified with this option and a note requesting that this user be informed of the status of the operation. For information about enabling e-mail notification, see the MultiSite Control Panel reference page.

K.           Specifying the destination replicas

Default

None.

replica-selector ...

Specifies the replicas to which you want to send update packets. These replicas must be in the same VOB family. Specify replica-selector in the form [replica:]target-replica-name[@source-vob-selector]

target-replica-name

Name of the replica to which you want to send the packet (you can display replica names with lsreplica)

source-vob-selector

VOB family of the replica; can be omitted if the current working directory is within the VOB.

Specify vob-selector in the form [vob:]pname-in-vob

pname-in-vob

Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)

Additional export options for managed replicas

All of these options are only valid for replicas whose synchronization method is “managed.”

Note: If you run a syncreplica command on a non-managed replica and include one or more of the following options, the options will cause the synchronization request to fail: –active, –cancel, –force, –from, –host, –job, –to, –workdir. Other options will be ignored.

L.            Remote source replica

Default

None.

–from replica-selector [ –host hostname ]

Specifies a remote source replica, replica-selector, for this export operation. With –host, specifies the hostname of the remote source replica. When –host is not specified, the host is looked up within the local VOB.

M.           Resolving object path names

Default

If you do not specify –view, the no resolution takes place.

–view view-tag

The view specified by view-tag is used to resolve the path names of objects displayed in the command output.

N.           Creating a synchronization job list

Default

None.

–jfile job-ids-file

Adds the IDs of all jobs created by the synchronization request to a job IDs file. If the job-ids-file already exists, the new job IDs are appended to the existing file.

O.           Options and arguments -- Import phase

P.           Restricting the update to a particular VOB

Default

Updates all replicas that are on the current host and are specified in the update packets.

–invob vob-selector

Updates the replica in the VOB family specified by vob-selector; all other replicas specified in the update packets are ignored. Specify vob-selector in the form [vob:]pname-in-vob

pname-in-vob

Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)

Q.           Event records and comments

Default

Creates one or more event records, with commenting controlled by the standard ClearCase user profile (default: –nc). See Event records and comments in the multitool reference page. To edit a comment, use cleartool chevent.

–c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment

Overrides the default with the specified comment option.

R.           Specifying the location of the update packets

Default

None.

–rec/eive [ –scl/ass storage-class ]

Scans either the current host's storage bays, or the storage bays for the replica's host as specified with the –to option. Any unprocessed update packets intended for this host are applied to the appropriate replicas on the host. With –sclass, syncreplica scans only the storage bays of the specified storage class.

If syncreplica finds any replica-creation packets, it sends mail to the store-and-forward administrator. (If the current host is a Windows host and there is no valid host specified in the SMTP Host box in the ClearCase Control Panel, a message appears in the Windows Event Viewer.) Use mkreplica to import these replica-creation packets.

packet-file-pname | staging-area-pname ...

Processes each packet-file-pname as an update packet. For each staging-area-pname specified, locates all previously unprocessed update packets in the directory and applies them to the appropriate replicas.

Additional import options for managed replicas

All of these options are only valid for replicas whose synchronization method is “managed.”

Note: If you run a syncreplica command on a non-managed replica and include one or more of the following options, the options will cause the synchronization request to fail: –active, –cancel, –force, –from, –host, –job, –to, –workdir. Other options will be ignored.

S.           Resolving object path names

Default

If you do not specify –view, the no resolution takes place.

–view view-tag

The view specified by view-tag is used to resolve the path names of objects displayed in the command output.

T.            Creating a synchronization job list

Default

None.

–jfile job-ids-file

Adds the IDs of all jobs created by the synchronization request to a job IDs file. If the job-ids-file already exists, the new job IDs are appended to the existing file.

U.           Reattempting the import

Default

No retries are attempted.

–retry_interval minutes

Specifies the number of minutes to wait between retries to import a packet.

–max_attempts num-attempts

Specifies the maximum number of attempts that the Sync Manager can make to import a packet.

V.           Initiating import operations at a remote host

Default

Imports all specified packets, in either all storage bays or the specified storage classes on the specified remote host.

By using the –host option together with –receive packet-file-pname, you can initiate an import operation for replicas on the host specified by hostname.

–to replica-selector

Specify the replica for which you will initiate an import operation.

Note: If you specify a packet name, with packet-file-pname, the packet must be located in a storage bay that is specified in one or more storage classes, that is, in the shipping.conf file (Linux and the UNIX system) or in the MultiSite Control Panel (Windows).

Additional syncreplica options for managed replicas

Note: If you run a syncreplica command on a non-managed replica and include one or more of the following options, the options will cause the synchronization request to fail: –active, –cancel, –force, –from, –host, –job, –to, –workdir. Other options will be ignored.

W.          Canceling a synchronization job

You can cancel a synchronization job for a replica with a synchronization method of “managed.”

Default

Cancels the specified job on the local host, only if it is not active.

–force

Suppresses any confirmation steps.

–active

Cancel the specified job, even if it is in the Active state. Without –active, syncreplica will not cancel the specified job if it is making active progress.

–host hostname

The name of the host that runs the specified job. When -host is not specified, the host is looked up within the local VOB. You do not need to specify a host name if the specified job runs on the local host.

–job job-id | job-uuid

The job-id or job-uuid of the scheduled job you want to cancel. You can find job identifiers using the syncinfo command.

X.           Waiting for synchronization jobs

You can monitor the progress of synchronization jobs by running multitool commands, if you run the jobs in “non-blocking” mode. See Blocking the multitool command line. After a synchronization request has been submitted, use the syncreplica –wait_for_jobs command to monitor the associated jobs and wait on them for a period of time that you specify.

Default

Wait until all the specified jobs on the local host are finished making active progress.

–host hostname

The name of the host that runs the specified job. When –host is not specified, the host is looked up within the local VOB. You do not need to specify a host name if the specified job runs on the local host.

–jfile job-ids-file | –job { job-id | job-uuid } [,...]

With –jfile, wait for all jobs listed in the specified job-ids-file to complete before returning control of the command line. A job-ids-file contains the IDs of all jobs associated with a synchronization request and is created by the syncreplica command if the –jfile option is specified. With –job, wait for all jobs specified by job-id or job-uuid. You can find job identifiers using the syncinfo command.

 

How do I use the multitool syncreplica command to

Exports

1.   Generate (Export) an update packet to be sent to boston replica and store the packet in a non-default location

multitool syncreplica –export –out /net/samecs/multisite/outgoing/boston_packet1 boston@/vobs/samecs

2.   Generate (Export) an update packet to be sent to boston replica, place the packet file in a storage bay, for shipping at some later time by the store-and-forward facility.

multitool syncreplica –export –ship boston@/vobs/samecs


Generating synchronization packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.02_3447_1
- shipping order file is /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_sync_boston_19-May-07.09.33.02_3447_1

3.   Generate (Export) an update packet and send it immediately to the boston replica

multitool syncreplica –export –fship boston@/vobs/samecs

Generating synchronization packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.
02_3447_1 - shipping order file is /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_sync_boston_19-May-
087.09.33.02_3447_1
Attempting to forward/deliver generated packets...
-- Forwarded/delivered packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.02_3447_1

4.   Send a sync (Export) update to all siblings of boston@/vobs/samecs_dev, which lives on host samecs

multitool syncreplica –export –fship –from boston@/vobs/samecs_dev –host samecs

job_uuid: nnnnnnnn.nnnnnnnn.nnnn.nn:nn:nn:nn:nn:nn    job_id: nn Generating synchronization packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_delhi_19-May-07.09.33.02_3447_1
Shipping order c:\Program Files\Rational\ClearCase\var\shipping\ms_ship\outgoing\sh_o_sync_delhi_19-May-02.09.33.02_3447_1
Attempting to forward/deliver generated packets ...
-- Forwarded/delivered packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_dehli_19-May-07.09.33.02_3447_1

5.   Send a sync (Export) update to replica boston and compress the packet

multitool syncreplica –export –fship –compress boston@/vobs/samecs

Generating synchronization /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.02_3447_1 ...
Shipping order /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_sync_boston_19-May-07.09.33.02_3447_1
Attempting to forward/deliver generated packets ...
-- Forwarded/delivered packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.02_3447_1

6.   Send a sync (Export) update in a view context

Multitool syncreplica –export –fship –view samecs_dev_view boston@/vobs/samecs

Generating synchronization packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_boston_19-May-07.09.33.02_3447_1...
Shipping order shipping /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_sync_boston_19-May-02.09.33.02_3447_1
Attempting to forward/deliver generated packets ...
-- Forwarded/delivered packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sync_bostn_19-May-07.09.33.02_3447_1

Imports

7.   Process (Import) an incoming update packet in directory /usr/tmp.

multitool syncreplica –import /usr/tmp/boston_packet1


Applied sync. packet /usr/tmp/boston_packet1 to VOB /net/samecs/ccvobstore/samecs_dev.vbs

8.   Process (Import) all incoming update packets in the current host's storage bays.

multitool syncreplica –import –receive

Applied sync. packet /var/adm/rational/clearcase/shipping/ms_ship/incoming/sync_london_19-May-
02.09.45.01_7634_1 to VOB /net/samecs/ccvobstore/samecs_dev.vbs

9.   Import a packet in a view context

multitool syncreplica –import –view samecs_dev_view /usr/tmp/boston_packet1

Applied sync. packet /usr/tmp/boston_hub_packet1 to VOB /net/samecs/ccvobstore/samecs_dev.vbs

10.       Import packets intended only for boston replica which lives on host samecs

multitool syncreplica –import –to boston@/vobs/samecs_dev –host samecs –receive

job_uuid: nnnnnnnn.nnnnnnnn.nnnn.nn:nn:nn:nn:nn:nn    job_id: 20
job_uuid: nnnnnnnn.nnnnnnnn.nnnn.nn:nn:nn:nn:nn:nn    job_id: 21
Applied sync. packet /usr/tmp/boston_hub_packet1 to VOB /net/samecs/ccvobstore/samecs_dev.vbs
Applied sync. packet /usr/tmp/boston_hub_packet2 to VOB /net/samecs/ccvobstore/samecs_dev.vbs

11.       Import all packets, but return the command line to the User after waiting 5 minutes

multitool syncreplica –import –blocking_duration 5 –receive

(no output and cursor does not return for 5 minutes)
Applied sync. packet /var/adm/rational/clearcase/shipping/ms_ship/incoming/sync_boston_hub_19-May-
07.09.45.01_7634_1 to VOB /net/samecs/ccvobstore/samecs_dev.vbs

12.       Import packets and make 4 attempts, at intervals of 1 minute. Return the command line immediately to the user.

multitool syncreplica –import –nblocking –max_attempts 4 –retry_interval 1 mypacket

job_uuid: nnnnnnnn.nnnnnnnn.nnnn.nn:nn:nn:nn:nn:nn    job_id: nn
(Use the syncinfo command to find out how the job is progressing.)

Other

13.       Cancel sync job 15 on host samecs

multitool syncreplica –cancel –host samecs –job 15
Should I cancel this synchronization job? [no]  y
The job has been cancelled.

14.       Wait for job 6 to complete

multitool syncreplica –wait_for_jobs –job 6
(No output and cursor is not returned to user until job has
finished. Then the expected messages are displayed.)