Sending DS-System IP configuration updates to DS-Clients
The DS-System can send an update of its IP address configuration to its DS-Clients, including new, updated, or changed IP addresses.
NOTE: At least one existing DS-System IP address must be functional so the DS-Client can connect to receive the update.
To send DS-System IP configuration updates to DS-Clients, you must copy an XML format file to the Update folder on the DS-System machine. The name of the file determines if the update applies to all DS-Clients, DS-Client belonging to a specific customer account, or a specific DS-Client. For example:
• update.xml – Applies to all DS-Clients.
• update_xxxx.xml – Applies to all DS-Clients belonging to a specific customer (where xxxx is the account number, for example: update_CUST000001.xml).
• update_xxxx.xml – Applies to a specific DS-Client (where xxxx is the DS-Client number, for example: update_DSCXXXX00001.xml).
If more than one update is applicable to a specific DS-Client, the highest priority update will take precedence. The update priority is in the following sequence:
• An update specific to a DS-Client.
• An update specific to a customer account.
• An update for all DS-Clients.
The update file is an XML file with the following schema:
<!ELEMENT asigra-config-update (system-connection,secondary-connection*)>
<!ELEMENT system-connection (dns*)>
<!ELEMENT secondary-connection (dns*)>
<!ELEMENT dns (#PCDATA)>
The DNS entries contain either the DNS name of the DS-System or the DS-System IP address. The following is a sample file:
<asigra-config-update>
<system-connection>
<dns> sys1.yourcompany.com </dns>
<dns> sys2.yourcompany.com </dns>
<dns> 192.168.1.203 </dns>
</system-connection>
<secondary-connection>
<dns> backup1.yourcompany.com </dns>
<dns> backup2.yourcompany.com </dns>
</secondary-connection>
<secondary-connection>
<dns> 10.11.12.13 </dns>
</secondary-connection>
<secondary-connection>
<dns> finalfallback.yourcompany.com </dns>
</secondary-connection>
</asigra-config-update>
The DS-Client will download the auto-update during the System Admin process when it connects to the DS-System. The DS-Client will save the update file as update.xml in the buffer path.
The DS-Client will replace existing IP addresses from the primary connection entries with the newly received IP addresses (if any). In case the update does not contain any IP addresses, the existing primary connection will be retained.
NOTE: When DS-Systems are part of a DS-System replication group, their DS-Clients can be configured with secondary DS-System connection information for failover purposes. For more information on how to configure the DS-System for replication, see
“DS-System Replication”.
In the XML update file, the primary DS-System connection is the first one and it is placed between the <system-connection> tags. This is the DS-System where backup data is normally sent. Later, the data is replicated to the other DS-Systems in the DS-System replication group (if the DS-Client has been shared for replication).
Secondary DS-System connection information is optional. You can update this information for DS-Clients to take advantage of the alternate replication DS-Systems, whenever they cannot reach the primary DS-System.
All other connections (to any other DS-System) are secondary connections, with each replication DS-System placed between its own set of <secondary-connection> and </secondary-connection> tags. Each secondary connection will be added as a separate line in the DS-System connection settings for the DS-Client.