recoverpacket

Resetting epoch numbers automatically

When you send an update packet to another replica, success of the transport and import phases is assumed. Therefore, the sending replica's epoch number matrix is updated to reflect that the changes are made at the receiving replica. However, if the packet is lost before reaching the receiving replica, the sending replica's assumption that the receiving replica is up to date is incorrect.

The epoch numbers at the sending replica must be returned to the values they had before the packet was sent. Making these corrections to the sending replica's epoch number matrix causes it to include the same changes in the next update packet it sends to the receiving replica.

The administrator at the receiving replica must run an lshistory command to determine the time of the last successful import. The administrator at the sending replica uses this time in the recoverpacket command.

Resetting epoch numbers manually

If there are no saved epoch rows that are as old as the specified time, the recoverpacket command fails. In this case, the administrator at the receiving replica must use the lsepoch command to determine the correct epoch number, and the administrator at the sending replica must run chepoch on the sending replica to reset the epoch row. See the chepoch reference page, as well as information about recovering from lost packets in the "Troubleshooting MultiSite operations" chapter of ClearCase MultiSite Administrator's Guidethis guide.

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.

Specifying the time

Default

If the time is not specified, recoverpacket uses the current time (and, therefore, resets the epoch row so that the changes in the most recent update packet are resent).

–sin/ce date-time

Specifies the time of the last successful processing of a packet at the receiving replica. 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

Specifying the row to be modified

Default

You must specify a replica. If you do not specify a vob-selector, the command uses the current VOB.

replica-selector

Updates the current replica's estimate of the state of replica-selector. Specify replica-selector in the form [replica:]replica-name[@vob-selector]

replica-name

Name of the replica (displayed with lsreplica)

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)