This document provides an introduction to mirroring features in EPiServer. Mirroring makes it possible to maintain content in one location and pushing the content to other sites. Mirroring rules and associated batch jobs are conveniently managed from the EPiServer CMS administration interface. With content mirroring you can define a selection of pages and allow them to be published in another EPiServer CMS system. Mirroring keeps track of pages that have been moved and deleted, maintaining the exact page structure.
How it works
Mirroring is a scheduled export/import of selected data from one site to another. Mirroring uses the export/import function in EPiServer CMS, and only content that belongs to CMS will be mirrored.
The following objects will be included in mirroring:
- Content items such as pages in selected parts of the page tree structure, and files linked to from these pages.
- Content types such as page and block types (optional, see XCOPY deployment).
- Tabs used for grouping properties.
- Visitor groups.
Export of templates between sites can be managed through XCOPY deployment, see Deploying to Windows servers.
Even though two-way mirroring is possible the mirroring service is traditionally configured as one-way-mirroring, which means that the mirroring service sends the content to another service. In EPiServer CMS the mirroring service is able to detect if the content has been mirrored before. In other words, if you run a mirroring job many times without changing of the content, then the content on the target site will be ignored and unchanged.
EPiServer CMO and EPiServer Commerce do not support mirroring. Also, content mirroring is not supported in cloud deployment such as Windows Azure Web Sites.
Mirroring can only be installed for CMS 7.5 through Deployment Center. To have mirroring with the latest EPiServer version, install a CMS 7.5 site with mirroring, and then upgrade to the latest through NuGet. There is no NuGet package available for the content mirroring functionality (it is installed as a separate service in a virtual directory on the server).
Refer to the administration section in the EPiServer CMS user guide for more information about the Export/Import and Mirroring user interfaces.