Resilient network properties
To access this setting, in the web UI select . Select the server or client. If necessary click , then click , , or . Click .
For media servers and clients, the Resilient network properties are read only. When a job runs, the primary server updates the media server and the client with the current properties.
The Resilient network properties let you configure NetBackup to use resilient network connections for backups and restores. A resilient connection allows backup and restore traffic between a client and a NetBackup media server to function effectively in high-latency, low-bandwidth networks such as WANs. The data travels across a wide area network (WAN) to media servers in a central datacenter.
NetBackup monitors the socket connections between the remote client and the NetBackup media server. If possible, NetBackup re-establishes dropped connections and resynchronizes the data stream. NetBackup also overcomes latency issues to maintain an unbroken data stream. A resilient connection can survive network interruptions of up to 80 seconds. A resilient connection may survive interruptions longer than 80 seconds.
The NetBackup Remote Network Transport Service manages the connection between the computers. The Remote Network Transport Service runs on the primary server, the client, and the media server that processes the backup or restore job. If the connection is interrupted or fails, the services attempt to re-establish a connection and synchronize the data.
NetBackup protects only the network socket connections that the NetBackup Remote Network Transport Service (nbrntd) creates. Examples of the connections that are not supported are:
Clients that back up their own data (deduplication clients and SAN clients)
Granular Recovery Technology (GRT) for Exchange Server or SharePoint Server
NetBackup nbfsd process.
NetBackup protects connections only after they are established. If NetBackup cannot create a connection because of network problems, there is nothing to protect.
Resilient connections apply between clients and NetBackup media servers, which includes primary servers when they function as media servers. Resilient connections do not apply to primary servers or media servers if they function as clients and back up data to a media server.
Resilient connections can apply to all of the clients or to a subset of clients.
Note:
If a client is in a subdomain that is different from the server subdomain, add the fully qualified domain name of the server to the client's hosts file. For example, india.veritas.org is a different subdomain than china.veritas.org.
When a backup or restore job for a client starts, NetBackup searches the list from top to bottom looking for the client. If NetBackup finds the client, NetBackup updates the resilient network setting of the client and the media server that runs the job. NetBackup then uses a resilient connection.
Table: Resilient network properties
Property | Description |
|---|---|
FQDN or IP address | The full qualified domain name or IP address of the host. The address can also be a range of IP addresses so you can configure more than one client at once. You can mix IPv4 addresses and ranges with IPv6 addresses and subnets. If you specify the host by name, it is recommended that you use the fully qualified domain name. Use the arrow buttons on the right side of the pane to move up or move down an item in the list of resilient networks. |
Resiliency | Resiliency is either On or Off. |
Note:
The order is significant for the items in the list of resilient networks. If a client is in the list more than once, the first match determines its resilient connection status. For example, suppose you add a client and specify the client IP address and specify for Resiliency. Suppose also that you add a range of IP addresses as , and the client IP address is within that range. If the client IP address appears before the address range, the client connection is resilient. Conversely, if the IP range appears first, the client connection is not resilient.
Other NetBackup properties control the order in which NetBackup uses network addresses.
The NetBackup resilient connections use the SOCKS protocol version 5.
Resilient connection traffic is not encrypted. It is recommended that you encrypt your backups. For deduplication backups, use the deduplication-based encryption. For other backups, use policy-based encryption.
Resilient connections apply to backup connections. Therefore, no additional network ports or firewall ports must be opened.
Note:
If multiple backup streams run concurrently, the Remote Network Transport Service writes a large amount of information to the log files. In such a scenario, it is recommended that you set the logging level for the Remote Network Transport Service to 2 or less. Instructions to configure unified logs are in a different guide.