Policy Pages Reference : Optimization Policy Settings : CIFS Prepopulation
  
CIFS Prepopulation
The prepopulation operation effectively performs the first SteelHead read of the data on the prepopulation share. Later, the SteelHead handles read and write requests as effectively as with a warm data store. With a warm data store, RiOS sends data references along with new or modified data, dramatically increasing the rate of data transfer over the WAN.
The first synchronization, or the initial copy, retrieves data from the origin file server and copies it to the RiOS data store on the SteelHead. Subsequent synchronizations are based on the synchronization interval.
The RiOS 8.5 and later Management Consoles include policies and rules to provide more control over which files the system transfers to warm the RiOS data store. A policy is a group of rules that select particular files to prepopulate. For example, you can create a policy that selects all PDF files larger than 300 MB created since January 1st, 2013.
CIFS Prepopulation is disabled by default.
Prepopulation
Complete the configuration as described in this table.
Control
Description
Enable CIFS Prepopulation
Prewarms the RiOS data store. In this setup, the primary interface of the SteelHead acts as a client and prerequests data from the share you want to use to warm the data store. This request goes through the LAN interface to the WAN interface out to the server-side SteelHead, causing the in-path interface to see the data as a normal client request.
When data is requested again by a client on the local LAN, RiOS sends only new or modified data over the WAN, dramatically increasing the rate of data transfers.
Enable Transparent Prepopulation Support using RCU
Opens port 8777 to allow manual warming of the RiOS data store using the Riverbed Copy Utility (RCU) to prepopulate your shares.
Most environments do not need to enable RCU.
Add a New Prepopulation Share
Displays the controls for adding a new prepopulation CIFS share.
Remote Path
Specify the path to the data on the origin server or the UNC path of a share to which you want to make available for prepopulation. Set up the prepopulation share on the remote box pointing to the actual share in the head-end data center server. For example:
\\<origin file server>\<local name>
Note: The share and the origin-server share names cannot contain any of these characters:
< > * ? | / + = ; : " , & []
Account
Specify the account number on the CIFS share.
Specify the account used to access the prepopulation share: for example: <Domain>\<username>
Password
Set the password for accessing the CIFS share.
Password Confirm
Confirm the password.
Synchronization Enable
Enable the following synchronization options:
•  Sync Schedule Date, Time - Sets date (YYYY/MM/DD) and time (HH:MM:SS) for synchronizing the appliance with the server.
•  Sync Interval - Set number and select Minutes, Hours, Days, or Disabled from the drop-down list.
Comment
Optionally, include a comment that describes the share configuration.
Add
Adds the new CIFS share configuration to the policy definition.
Remove Selected
Select the check box next to the name of the CIFS share configuration and click Remove Selected.