Open topic with navigation

Simulating a connection

Double-Take Availability offers a simple way for you to simulate a connection in order to generate statistics that can be used to approximate the time and amount of bandwidth that the connection will use when actively established. This connection uses the TDU (Throughput Diagnostics Utility), which is a built-in null (non-existent) target to simulate a real connection. No data is actually transmitted across the network. Since there is no true connection, this connection type helps you plan for a disaster recovery solution.

1. Before and after simulating your connection, you should gather network and system information specific to Double-Take Availability operations. Use DTSetup to run DTInfo to automatically collect this data.
2. Select the DTSetup option for troubleshooting, then select the option for basic diagnostics.
3. When you run the diagnostics, it may take several minutes for it to finish processing. When it is complete, a .tar.gz file will be created in /var/run/etc/DT/. The file name will have DTInfo with the date and time. You must have root (or uid 0 equivalent) to execute the diagnostics or to copy or read the resulting file.
4. Opening the Connection Manager to establish the connection.
• Highlight the replication set and select Tools, Connection Manager.
• Right-click on the replication set and select Connection Manager.
5. The Connection Manager opens to the Servers tab. Depending on how you opened the Connection Manager, some entries on the Servers tab will be completed already. For example, if you accessed the Connection Manager by right-clicking on a replication set, the name of the replication set will be displayed in the Connection Manager. Verify or complete the fields on the Servers tab.
• Source Server—Specify the source server that contains the replication set that is going to be simulated to the TDU.
• Replication Set—At least one replication set must exist on the source before establishing a connection. Specify the replication set that will be connected to the TDU.
• Target Server—Select the Diagnostics target.
• Route—After selecting the Diagnostics target, the Route will automatically be populated with Throughput Diagnostics Utility (TDU).
• Mappings—Mappings are not required when simulating a connection because no data is actually transmitted to the target.
• Start Mirror on Connection—Make sure this option is selected so that your simulation will be realistic.
• Start Replication on Connection—Make sure this option is selected so that your simulation will be realistic.
6. Click Connect to establish the connection. The simulation data will be logged to the Double-Take Availability statistics file.
7. Repeat steps 1-3 to run the diagnostics utility after the simulation is complete.

Related Topics