These Task Manager tasks are used to support a multi-site configuration where a master server clones data loads to one or more binary servers. Refer to Configuring for Multiple Sites for more information.

This task is similar to the P2RTInitialLoad task used to load data from Publication Manager to the Viewer server with the Publish2RT task. The only difference is it loads data only to the master site. Its input parameter is same as P2RTInitialLoad, the Site Groups name.

For example:

This task creates a full clone packet from the master site and triggers CloneToSite tasks for all other sites in the site group. This task is equivalent to a re-host procedure. You can use this task as a recovery process as well, if any site goes out of sync due to an unrecoverable failure. Its input parameter is the Site Groups name.

For example:

This task is automatically triggered by the FullCloneFromMaster with the needed input parameters. This task downloads the given full clone packet and deploys it. This task can also be run manually on a newly added site or on an out of sync site.

If no incremental loads are run after the latest full clone packet was generated, the name of the latest full clone packet and the size of the packet in bytes is located in the Publisher server’s INSERVICE_CONFIG\System\Config\FullCloneBackupPackets.xml file. This task first cleans up all previous data and loads new data from the full clone packet.

Its input parameters are FullClonePacketName, siteId, and Size of clone packet (in bytes).

For example:

This task creates a full clone packet from a given Site Id and upload it to the shared locaction. This full clone packet can be used later as a recovery option or to clone a newly added site using the CloneToSite task. This task writes the full clone packet name and the site ID from where it was generated to the Publisher server’s INSERVICE_CONFIG\System\Config\FullCloneBackupPackets.xml file.

For example: