Specifications

Chapter 3 Installation and Setup
6. Click Save and then click Close. The Spoke Servers window will open.
To delete a spoke server:
1. On the hub server, click the System tab.
2. Click DTX Control in the top navigation bar. The side navigation bar will include the name of the server to which you
are logged in.
3. Click Properties in the side navigation bar, and then click Spoke Servers. The Spoke Servers window will open.
4. Click the checkbox to the left of the spoke servers you wish to delete. To delete all spoke servers, click the checkbox
to the left of Name at the top of the list.
5. Click Delete. A confirmation dialog box will appear.
6. Confirm or cancel the deletion.
NOTE: When a spoke server is deleted, it is no longer allowed to communicate with the hub server. Only spoke servers that are no longer active
should be deleted. If a spoke server is still active, it may be re-registered using the Register Spoke Server wizard.
Promoting spoke servers
Promoting a spoke server to be a hub server is usually done only if the current hub server is no longer operational and will
not be brought back into service. (For less severe problems with a hub server, the backup and restore operations can be
used.)
If a spoke server must be promoted, be sure to run the replication task, if possible on all other spoke servers, then on the
spoke server being promoted, immediately before the promotion. This will prevent loss of data from the other spoke
servers. See Replication on page 23 for more information.
(After the promotion of a spoke server to a hub, if the server that was originally the hub becomes operational again, it will
have to register as a spoke server, since a system can have only one hub server.)
To promote a spoke server to be a hub server:
1. On the spoke server, click the System tab.
2. Click Tools in the side navigation bar.
3. Click Promote to hub server. The Promote Hub Server Wizard will appear.
4. Follow the prompts and heed the cautionary warnings in the wizard. The spoke server on which the wizard is running
will become the hub server, and the other spoke servers will be advised of the changed configuration.
3.6 Replication
Replication is a task that synchronizes the hub and spoke server databases. By default, replication runs every 12 hours
on each spoke server. A spoke server’s first replication occurs automatically when the spoke server is added to the
DTX Control system. You may change the interval that the replication task runs on each spoke server, or you may initiate
an immediate replication.
During replication, the spoke server sends all of its database changes since the last replication to the hub server. The hub
server then incorporates those changes and sends all of its database changes since the last replication to the spoke
server (excluding the changes that spoke server just sent to the hub server).
If an item is added on a spoke server, and another item with the same name (but perhaps with different configuration
parameters) is added on the hub server, then after replication, both items will appear on both the hub and spoke servers,
with a tilde (~) and a number added to one of the names. The administrator should handle the issue appropriately - in some
cases, the duplicate item may need to be renamed; in others, the duplicate item should be deleted.
Page 23 724-746-5500 | blackbox.com