Sending DS-System IP configuration updates to DS-Clients

Working with DS-Client accounts : Sending DS-System IP configuration updates to DS-Clients

The DS-System can send an update of its IP address configuration to DS-Clients. This upgrade can contain new, updated, or changed DS-System IP addresses.

NOTE: At least one existing DS-System IP address must be functional because the DS-Client must connect to receive the update.

To send DS-System IP configuration updates to DS-Clients, you must place an XML format file in the Upgrade folder on the DS-System machine. The name of the file determines if the update applies to all DS-Clients, a specific customer account, or a specific DS-Client. For example:

• update.xml - Applies for all DS-Clients.

• update_????.xml - Applies to all DS-Clients of a specific customer (where ???? is the account number, for example: update_CUST000001.xml).

• update_????.xml - Applies only to a specific DS-Client (where ???? is the DS-Client number, for example: update_DSCXXXX00001.xml).

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):

• An update specific to a DS-Client.

• An update specific to a customer account.

• An update for all DS-Clients.

Update file format

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 a 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>

</system-connection>

<secondary-connection>

<dns> backup1.yourcompany.com </dns>

<dns> backup2.yourcompany.com </dns>

</secondary-connection>

<secondary-connection>

</secondary-connection>

<secondary-connection>

<dns> finalfallback.yourcompany.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

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 in the event the primary DS-System is unresponsive or unreachable for any reason. For more information on how to configure the DS-System for replication, see “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. 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 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.