Consolidating R-1 jobs may improve application performance, server and network resources, and streamline monitoring and management requirements.

Site Server CRS required Users to establish multiple "Projects" to mirroring or publish different websites from staging environments to production web servers. Often when implementing R-1 for the first time, Users maintain their legacy operating procedures and create multiple R-1 jobs.

The practice of running multiple R-1 jobs to publish content from the same root directory to production servers is unnecessary. By consolidating multiple R-1 jobs, organizations may realize performance enhancements in applications, servers and network resources. In addition there are fewer jobs to monitor and manage.

Case in point is when multiple Scheduled or Continuous Update jobs are running.

By utilizing the RepliWeb Include/Exclude filter capabilities, the amount of concurrent jobs from a common root folder, such as c:\inetpub\wwwroot can be significantly reduced. To deploy content to different web sites (i.e. target folders SiteA, SiteB, SiteC and SiteD) - it is recommended to consolidate those jobs into one job that defines the sub folders (SiteA, SiteB, SiteC and SiteD) as a "Include" specification. The defined Source is the common root folder c:\inetpub\wwwroot. All files would then be replicated from/to those defined folders.

This consolidation strategy can be applied to all scheduled jobs where applicable and will also reduce the amount of jobs that may be running to one or several Edge servers at the same time, as all processes are being run by one job instead of multiple separate jobs.

For detailed information on Including and Excluding files, please refer to the RepliWeb Reference Library

Sample Server Performance running multiple jobs:

Grouping Multiple R-1 Continuous Update Jobs:

Sample File Include/Exclude:

TOP