Partager via


Onglet Réplication complète (Office SharePoint Server)

Mise à jour : 2008-08-28

The Full Replication tab initiates full replication operations. The two primary instances when an administrator would want to initiate a full replication operation are during an initial farm setup or data recovery wherein all or the majority of the profiles must be replicated again.

You must have the Manage user profiles permission on the Shared Services Provider (SSP) of the source and destination servers to run the full replication operation.

The full replication operation updates the properties being replicated. However, if a profile does not exist on the destination server, a new profile is created. .

The elements of this tab are described as follows.

  • Source Server
    Auto-populated by the value of the Source URL field on the Configuration tab.
  • Destination Server
    Auto-populated from the Destination URL(s) list on the Configuration tab; the first entry in the Destination URL(s) list is the default. Data can only be replicated to one destination at a time when performing full replication; therefore, you must manually change the destination URL if replicating to multiple destinations.
  • Total number of profiles
    Displays the total number of profiles in the source farm. This field shows the total number of profiles in the profile store, not just the domains listed on the Configuration tab.
  • Starting Profile Index
    Sets the profile index from which the full replication will start. This is used in error scenarios where users want to start the replication from the last processed profile that was captured by the error logs. Typically, you would start from 0.

    NoteRemarque :

    Profile index numbers are not reused, so it is possible to have a starting profile index number greater than the total number of profiles. This can cause the statistics to be incorrect.

  • Maximum Number of Threads
    Sets the number of threads to be used by full replication. The default value is 25. The more this value is increased, the faster the computer you will need.
  • Instrument Full Replication
    Indicates that instrumentation files will record the accounts that are successfully replicated. Log files will record the failed accounts and some error messages. A unique error log file will always be created for each instance; log files can be found in the folder containing the application. For an instrumentation log file to be created, the Instrument Full Replication check box must be selected.
  • Status
    Displays a scrollable list of successfully replicated user profiles, identified by account names. The Status list shows only the accounts which are replicated successfully. The failed accounts will be logged into an .rcv file. For more information, see Remarks.
  • Start Time
    Displays the start time for the current running instance of full replication.
  • End Time
    Displays the estimated end time, derived from the average speed of the profiles processed thus far and total number of profiles in the currently running instance of full replication. If you are not replicating the entire store, the estimated end time may be inaccurate.
  • Time Elapsed
    Displays the total time elapsed since starting the current running instance of full replication.
  • Time Remaining
    Displays the time remaining derived from the total number of profiles and the average speed of the profiles processed, thus far, in the currently running instance of full replication.
  • Total Time
    Displays the total time for the current running instance of full replication.
  • Accounts Processed Per Second
    Displays the average number of profiles processed per second.
  • Number of Threads in use
    Displays the current number of threads in use by the current instance of full replication.
  • Start/Stop
    Starts or stops full replication.

Remarks

If any user information fails to replicate during a full replication, a recovery (.rcv) file is created, listing the failed accounts. This file can then be used in Recovery tab to replicate user data for just the failed user accounts.