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.
Error notification in a mixed environment If a packet is delivered through a Windows® host on which electronic mail notification is not enabled, a failure on that Windows® host means that no notification message is sent by electronic mail.

Error notification in a mixed environment

If a packet is delivered through a Windows® host on which electronic mail notification is not enabled, a failure on that Windows host means that no notification message is sent by electronic mail.

Instead, a message is written to the event log; this message contains a request that the appropriate users be informed of the failure. For information about enabling electronic mail notification, see the MultiSite Control Panel reference page.