DS-System IP configuration update to DS-Client
The DS-System can be configured to send an update to the DS-Client. This upgrade can contain new, updated, or changed DS-System IP Addresses.
- Note: In order for this to work, at least one existing DS-System IP Address must be functional for the DS-Client to make a connection.
You must place an XML format file in the "Upgrade" directory of the DS-System. The name of the file determines if the update applies to all DS-Clients, individual Accounts, or a specific DS-Client:
- "update.xml" - applies for all DS-Clients
- "update_????.xml", where ???? is the account number (like "update_ASIG0001.xml") applies to all DS-Clients in an account
- "update_????.xml", where ???? is the DS-Client number (like "update_DSCXXXX00001.xml") applies to a particular DS-Client
In case more than one update applies for a particular DS-Client, the highest priority update will be used. Update priority is in the following order (highest to lowest):
The update file is a 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 a DS-System or the DS-System IP address. A sample XML configuration file would be:
- <asigra-config-update>
- <system-connection>
- <dns> sys1.asigra.com </dns>
- <dns> sys2.asigra.com </dns>
- <dns> 192.168.1.203 </dns>
- </system-connection>
- <secondary-connection>
- <dns> backup1.asigra.com </dns>
- <dns> backup2.asigra.com </dns>
- </secondary-connection>
- <secondary-connection>
- <dns> 10.11.12.13 </dns>
- </secondary-connection>
- <secondary-connection>
- <dns> finalfallback.asigra.com </dns>
- </secondary-connection>
- </asigra-config-update>
DS-Client auto-update functionality
The DS-Client will download the auto-update during its admin processes (daily or weekly), when it connects to the DS-System. The DS-Client will save the update file as "update.xml" in its DS-Client 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 kept.
Updating Primary and Secondary DS-System IP connection information to DS-Clients
When DS-Systems are part of a DS-System Replication Group (See "Replication".), their DS-Clients can be configured with secondary DS-System connection information for fail-over purposes, in the event the primary DS-System is down or unreachable for any reason.
In the XML update file, the primary DS-System connection is the first one and it placed between the <system-connection> tags. This is the DS-System where backup data is normally sent; afterwards 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 in order 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 a separate line in the DS-Client's "DS-System connection setup" (DS-User: Setup Menu > Configuration > Connections Tab).
If the secondary connection is an N+1 DS-System, then all addresses (of all nodes) must be included between the same <secondary-connection> and </secondary-connection> tags.
![]() ![]() |