<< Click to Display Table of Contents >> Navigation: Peer Global File Service Help > File Synchronization Jobs > Creating a File Synchronization Job > Step 2: Participants |
On the Participants page, you select a file-sharing protocol for the job and start the process of adding participants to your job.
A File Synchronization job requires at least two participants. Each participant consists of a Management Agent and a storage object (volume, share, export, or folder). After you add participants, they appear in the Participants table. The table lists each participant's Management Agent, storage path, and other key information needed for the File Synchronization job.
Follow these steps:
1.Select the file-sharing protocol that matches the workload for this job: SMB, NFS, or Multi-Protocol. The file-sharing protocol you select applies to the entire job and cannot be changed after the job is created.
Available protocol options vary based on your environment and license.
Note: Multi-Protocol requires specific license support. Before creating a job that uses both SMB and NFS, verify that your license includes Multi-Protocol support. For more information about the Multi-Protocol feature, see Multi-Protocol in the Advanced Topics section.
Agent Type |
License Supports Multi-Protocol? |
Available Protocol(s) |
Default Selection |
---|---|---|---|
All Windows-based |
N/A |
SMB |
SMB is preselected and required |
All Linux-based |
No |
NFS |
NFS is preselected and required |
All Linux-based |
Yes |
NFS or Multi-Protocol |
No default—you must choose |
Mixture of Windows- and Linux-based |
Yes |
SMB, NFS, or Multi-Protocol |
No default—you must choose. |
2.Click Add to open the Add New Participant subwizard.
The subwizard walks you through the process of adding a participant:
•Select the Management Agent that will manage the storage device.
•Choose the type of storage platform that hosts the data you want to replicate.
•Enter the credentials needed to access the storage device and provide other storage information.
•Specify the path to the data (the watch set) and select whether the participant will be used as a seeding target.
•(Optional) Enable Edge Caching for the participant.