This is not a caching technology, but instead is true replication of the content to another SharePoint® site. No client software is required to be installed.
Keep information current across geographic barriers, collaborate in virtual teams across the country and the world. Syntergy's Replicator for SharePoint™ supports the ability to define other SharePoint™ servers and create a partnership between them. At the list and site level you can then select specific areas that you wish to replicate and the target location for the replication. By setting up two servers talking to each other you have bi-directional replication which includes conflict resolution.
Key Benefits
- Integrated into SharePoint™ - no additional training of external applications
- Remote Differential Compression - Only transfer the blocks that change, not the whole file.
- Keep User and Group information synchronized between sites.
- Replicate permissions assigned on the list.
- Rules Engine to selectively replicate based on meta-data
- Supports replication of check-in/check-out state and all meta-data, including content types and site columns
- Conflict resolution support.
- Map library to an alternate named site.
- HTTP/HTTPS protocol only, no infrastructure changes.
- No crawlers that put a load on the server, all event based replication.
Technical Features
| Component | Feature |
|---|---|
| Scheduling |
|
| Partners |
|
| Replication Engines |
|
| Workflow |
|
| Alerts |
|
| API |
|
Content |
|
| Offline Support |
|
Remapping |
|
Technical Requirements
| Component | Requirement |
|---|---|
| Computer architecture |
|
| Processor speed | Under normal circumstances, the Replicator processor requirements are the same as SharePoint. When replicating large amounts of SharePoint content, Replicator uses a greater amount of CPU capacity. The expected load is comparable to up to 10 full time users accessing the web front end. |
| Memory |
Replicator Basic and Standard editions require at least 1.25 GB of available memory.
Replicator Enterprise Edition requires at least 1.5 GB of available memory. Additionally, ensure there is approximately 10 times the size of the largest file you expect to replicate in available memory. For example, if you are using Replicator Standard Edition and expect to replicate files that are 25 MB and smaller, then you should have 1.5 GB (1.25 + 10 x 0.025) of available memory for Replicator. |
| HDD storage |
Note: HDD storage requirements vary, depending on the expected replication schedule and size of replication packages. |
| Display |
|
| Operating system |
To use the Remote Differential Compression (RDC) compression method:
|
| Browser (recommended) |
|
| SharePoint |
|
| SQL Server |
Note: Replicator does not support versions of SQL Server included with the SharePoint installations, as Replicator requires its own database. Windows SharePoint Services' version of the SQL Server 2000 Desktop Engine (WMSDE) is not supported. Upgrade to the desktop engine or SQL Server (either 2000, 2005, or 2008 versions). |
| Server access |
|










