Home
AdministeringLearn how to administer the product.
Administering HCL VersionVault MultiSite
Packet transportation methods and configurationThe method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
Store-and-forwardThe MultiSite store-and-forward facility (the shipping server) is a file-transfer service that automates the transport phase of replica creation and synchronization. It can handle packets of any size (up to the maximum packet size specified in the shipping.conf file on Linux™ and the UNIX™ system or the MultiSite Control Panel on Windows™), can route files through a series of MultiSite hosts (one hop at a time), and includes support for handling data-communications failures.
Retries, expirations, and returned dataThe shipping server makes one attempt to transmit a packet to another host. If the packet cannot be transmitted (for example, because the receiving host is unavailable), the shipping server generates an error message and log file entry and exits.
Timeout period for unreachable hostsYou can specify that the shipping server wait a specified period of time before trying to contact a host that was previously identified as unreachable.

Timeout period for unreachable hosts

You can specify that the shipping server wait a specified period of time before trying to contact a host that was previously identified as unreachable.

For more information, see the shipping.conf reference page on Linux® and the UNIX® system or the MultiSite Control Panel reference page on Windows®.