Partager via


3.2.5.4 InfrequentMaintenanceTimer Expiration

When the InfrequentMaintenanceTimer expires, the client MUST synchronize its ClientVolumeTable with the server as follows:

The client MUST send a SYNC_VOLUMES message request to the server. This is sent by calling LnkSvrMessage with a MessageType in the TRKSVR_MESSAGE_UNION (see section 2.2.12) of SYNC_VOLUMES, and a Priority value of zero.

In this message, the TRKSVR_CALL_SYNC_VOLUMES array (described in section 2.2.12.3) MUST have a TRKSVR_SYNC_VOLUME entry for each volume in the client's ClientVolumeTable. In each TRKSVR_SYNC_VOLUME structure:

See section 3.1.4.4.3 for the server processing of that subrequest. See section 3.2.4.4.3 for the client's completion of that subrequest.

After the completion of this message, as defined in section 3.2.4.4.3, the client MUST also subsequently do the following:

  • Set the VolumeTableQuotaExceeded flag in the VolumeInformation for all entries of the ClientVolumeTable to False, and set the FileTableQuotaExceeded flag to False.

  • Carry out the same steps as the steps performed for the FrequentMaintenanceTimer.

If any of the client's MoveNotificationCursor values are set, the client MUST attempt to send one or more MOVE_NOTIFICATION requests, as specified in section 3.2.6.1.