Multicator®

Q. What is the Multicator?

A. TurboGold’s Multicator allows database updates to be sent simultaneously (using IP multicasting) to all subscribers of the databases. With TurboGold's multicasting, all database subscribers receive synchronized broadcasts of database updates significantly reducing both the frequency and amount of network traffic while improving bandwidth utilization.

Q. Can email databases be multicast?

A. Yes, email databases can be multicasted. However, TurboGold’s Multicator does not update the "Inbox" folder until the next replication cycle so users still need to replicate. Email databases can also be multicast for cache stuffing (updates to subscribers' local TurboGold cache), in which case there is no need to replicate. The benefit for multicasting email to cache is that the user’s access documents will already be in the local cache.

Q. How does Multicator reduce bandwidth requirements?

A. Because there is a one-to-many broadcast of database updates, subscribers will have less information to retrieve during their next online replication cycle. For example, assume 1,000 users replicated the names.nsf database locally. Each time an update is made to the database would require the update be transmitted in a separate replication. With the Multicator, all 1,000 users would be updated simultaneously resulting in a 1,000-to-1 bandwidth reduction. Updates occur automatically as they are made meaning all subscribers have the same information at the same time.

Q. Are the Multicator updates encrypted?

A. Yes, an encryption key is securely exchanged; the multicast updates are then encrypted using this key.

Q. If a Multicator update is missed by a client what happens?

A. For local replicas the update will be picked up at the next replication cycle. When this occurs the cache verification logic of TurboGold will retrieve the latest document. This is retrieved directly from the Domino server since the updated document will not have been stored in cache.

Q. What if each user has different replication formulas, how can the Multicator deal with this?

A. The TurboGold verifier sends the same update to each client. The TurboGold client applies the replication formula to decide if the update should be applied to the local replica or not.

Q. Does Multicator require the User Datagram Protocol (UDP)?

A. Yes, TurboGold’s multicasting is accomplished with UDP.

Q. Will Multicator traffic work through a Virtual Private Network (VPN)?

A. Yes, the Multicator data stream would be encapsulated into a tunneling protocol of a VPN, Point-to-Point Tunneling Protocol (PPTP). Note: The multicast data is not typically propagated by routers of the Internet.

Q. If I use the Multicator, do I still need to replicate on schedule?

A. Yes, it is a good practice to periodically replicate databases. This will ensure that any “missed” database updates be captured. It is important to note that only “missed” database updates will be replicated.

Q. Is Multicator supported by TurboGold Server-to-Server software?

A. Yes, Multicator is supported by TurboGold Server-to-Server software.

Q. Does TurboGold Enterprise Edition require that I change a different configuration database on each server if I want to enable Multicator on all the verifiers in my enterprise?

A. Yes, Multicator must be enabled in each configuration document. However, the database policy of using Multicator must only be entered in a single database that is replicated throughout the enterprise. This enablement is facilitated by the ability to inherit configuration settings from a policy document.