檔案複寫File-based replication

適用於: Configuration Manager (最新分支)Applies to: Configuration Manager (current branch)

Configuration Manager 會使用檔案複寫在階層中網站間傳送檔案資料。Configuration Manager uses file-based replication to transfer file-based data between sites in your hierarchy. 此資料包括您想要部署到子站台中發佈點的應用程式和封裝。This data includes applications and packages that you want to deploy to distribution points in child sites. 它也會處理未處理的探索資料記錄,站台會將這些資料記錄傳送至其父站台,然後加以處理。It also handles unprocessed discovery data records that the site transfers to its parent site and then processes.

站台之間的檔案型通訊會透過 TCP/IP 連接埠 445 來使用伺服器訊息區 (SMB) 通訊協定。File-based communication between sites uses the server message block (SMB) protocol on TCP/IP port 445. 若要控制站台透過網路傳輸的資料量,請指定頻寬節流設定和脈衝模式。To control the amount of data the site transfers across the network, specify bandwidth throttling and pulse mode. 使用排程來控制透過網路傳送資料的時機。Use schedules to control when to send data across the network.

路由Routes

下列資訊可協助您設定和使用檔案複寫路由。The following information can help you set up and use file replication routes.

檔案複寫路由File replication route

每個檔案複寫路由都會識別站台可傳送檔案資料的目的地站台。Each file replication route identifies a destination site to which a site transfers file-based data. 每個站台都支援連接至特定目的地站台的一個檔案複寫路由。Each site supports one file replication route to a specific destination site.

若要管理檔案複寫路由,請移至 [系統管理] 工作區。To manage a file replication route, go to the Administration workspace. 展開 [階層設定] 節點,然後選取 [檔案複寫] 。Expand the Hierarchy Configuration node, and then select File Replication.

您可以變更下列檔案複寫路由設定:You can change the following settings for file replication routes:

檔案複寫帳戶File replication account

此帳戶會連線至目的地站台,以及將資料寫入該站台的 SMS_Site 共用。This account connects to the destination site, and writes data to that site's SMS_Site share. 接收站台會處理寫入至此共用的資料。The receiving site processes the data written to this share. 根據預設,將站台新增至階層時,Configuration Manager 會將新站台伺服器的電腦帳戶指派為其檔案複本帳戶。By default, when you add a site to the hierarchy, Configuration Manager assigns the new site server's computer account as its file replication account. 然後,它會將此帳戶新增至目的地站台的 SMS_SiteToSiteConnection_<sitecode> 群組。It then adds this account to the destination site's SMS_SiteToSiteConnection_<sitecode> group. 此群組位於電腦本機,可授與對 SMS_Site 共用的存取權。This group is local to the computer that grants access to the SMS_Site share. 您可以將此帳戶變更為 Windows 使用者帳戶。You can change this account to be a Windows user account. 如果您變更帳戶,請務必將新帳戶新增至目的地站台的 SMS_SiteToSiteConnection_<sitecode> 群組。If you change the account, make sure you add the new account to the destination site's SMS_SiteToSiteConnection_<sitecode> group.

注意

次要網站一律使用次要網站伺服器的電腦帳戶做為 [檔案複寫帳戶] 。Secondary sites always use the computer account of the secondary site server as the File Replication Account.

排程Schedule

設定每個檔案複寫路由的排程。Set the schedule for each file replication route. 此動作限制資料可以傳輸至目的地站台的資料類型和時間。This action restricts the type of data and time when data can transfer to the destination site.

速率限制Rate limits

指定每個檔案複寫路由的速率限制。Specify rate limits for each file replication route. 此動作控制站台在將資料傳輸到目的地站台時使用的網路頻寬:This action controls the network bandwidth the site uses when it transfers data to the destination site:

  • 脈衝模式:指定站台傳送至目的地站台的資料區塊大小。Pulse mode: Specify the size of the data blocks that the site sends to the destination site. 您也可以指定傳送每個資料區塊之間的時間延遲。You can also specify a time delay between sending each data block. 當您必須經由低頻寬的網路連線將資料傳送至目的地站台時,請使用此選項。Use this option when you must send data across a low-bandwidth network connection to the destination site.

    例如,您有每五秒傳送 1 KB 資料的限制,而非每三秒傳送 1 KB 的限制。For example, you have constraints to send 1 KB of data every five seconds, but not 1 KB every three seconds. 此限制與特定時間的連結速度或其使用狀況無關。This constraint is regardless of the speed of the link or its usage at a given time.

  • 限制為每小時的最大傳送速率:站台只會使用您指定的時間百分比,將資料傳送至目的地站台。Limited to maximum transfer rates by hour: The site sends data to a destination site by using only the percentage of time that you specify. Configuration Manager 不會識別網路的可用頻寬。Configuration Manager doesn't identify the network's available bandwidth. 它會將可傳送資料的時間細分成時間片段。It divides the time it can send data into slices of time. 接著,它會在一小段時間內傳送資料,下一段時間則不傳送資料。It then sends the data in a short block of time, which is followed by blocks of time when it doesn't send data.

    例如,您將最大速率設為 50%For example, you set the maximum rate to 50%. Configuration Manager 會在沒有傳送任何資料時的一段相等時間間隔之後,傳輸一定時間量的資料。Configuration Manager transmits data for an amount of time followed by an equal period of time when it doesn't send any data. 它不會管理所傳送之資料區塊的實際大小。It doesn't manage the actual size of the data block that it sends. 站台只會管理傳送資料的時間長度。The site only manages the amount of time during which it sends data.

    警告

    根據預設,網站最多可以使用三個 [並行傳送] 將資料傳送至目的地網站。By default, a site can use up to three concurrent sendings to transfer data to a destination site. 當您啟用檔案複寫路由的速率限制時,它會將並行傳送至該站台限制為一個。When you enable rate limits for a file replication route, it limits the concurrent sendings to that site to one. 此行為即使在 [限制可用的頻寬 (%)] 設為 [100%] 時也適用。This behavior applies even when the Limit available bandwidth (%) is set to 100%. 例如,如果您針對寄件者使用預設設定,這樣就會將傳送至目的地站台的傳輸速率減少為預設容量的三分之一。For example, if you use the default settings for the sender, this reduces the transfer rate to the destination site to be one-third of the default capacity.

次要站台之間的路由Routes between secondary sites

在兩個次要站台之間設定檔案型複寫路由,在站台之間路由傳送檔案型內容。Configure a file replication route between two secondary sites to route file-based content between those sites.

傳送者Sender

每個網站都有一位傳送者。Each site has one sender. 傳送者會管理從一個站台到目的地站台的網路連線。The sender manages the network connection from one site to a destination site. 它可以同時建立對多個站台的連線。It can establish connections to multiple sites at the same time. 為了連線至站台,傳送者會使用至該網站的檔案複寫路由,並識別用來建立網路連線的帳戶。To connect to a site, the sender uses the file replication route to the site and identifies the account it uses to establish the network connection. 傳送者也會使用這個帳戶將資料寫入目的地站台的 SMS_Site 共用。The sender also uses this account to write data to the destination site's SMS_Site share.

根據預設,傳送者會使用多個並行傳送 (或執行緒 ) 將資料寫入目的地站台。By default, the sender writes data to a destination site by using multiple concurrent sendings, or a thread. 每個執行緒都可以將不同的檔案型物件傳輸到目的地站台。Each thread can transfer a different file-based object to the destination site. 當傳送者開始傳送物件時,傳送者會繼續寫入該物件的資料區塊,直到整個物件傳送完畢為止。When the sender begins to send an object, it continues to write blocks of data for that object until it sends the entire object. 當它將物件的所有資料都傳送完畢後,新的物件就可以開始在該執行緒上傳送。After it sends all the data for the object, a new object can begin to send on that thread.

若要管理站台的傳送者,請移至 [系統管理] 工作區,然後展開 [站台設定] 節點。To manage the sender for a site, go to the Administration workspace, and expand the Site Configuration node. 選取 [站台] 節點,然後選取您想要管理之站台的 [內容] 。Select the Sites node, and then select Properties for the site you want to manage. 切換到 [傳送者] 索引標籤,以變更傳送者設定。Switch to the Sender tab to change the sender settings.

您可以為傳送者變更以下設定:You can change the following settings for a sender:

並行傳送上限Maximum concurrent sendings

根據預設,每個站台都會使用五個並行傳送 (執行緒)。By default, each site uses five concurrent sendings (threads). 有三個執行緒可在將資料傳送到任何一個目的地站台時使用。Three threads are available for use when it sends data to any one destination site. 增加此數目時,您可以增加站台間資料的輸送量。When you increase this number, you can increase the throughput of data between sites. 更多執行緒表示 Configuration Manager 可以同時傳輸更多檔案。More threads mean that Configuration Manager can transfer more files at the same time. 不過,增加數量也會增加對網站間網路頻寬的需求。Increasing this number also increases the demand for network bandwidth between sites.

重試設定Retry settings

根據預設,每個站台都會重試有問題的連線兩次,每次連線嘗試間會有一分鐘的延遲。By default, each site retries a problem connection two times, with a one-minute delay between connection attempts. 您可以修改站台進行連線嘗試的次數,以及嘗試之間等候的時間長度。You can modify the number of connection attempts the site makes, and how long to wait between attempts.

後續步驟Next steps

Database replicationDatabase replication