Veritas NetBackup™ AdvancedDisk Storage Solutions Guide
- Introducing AdvancedDisk
- Licensing AdvancedDisk
- Configuring AdvancedDisk
- Configuring the AdvancedDisk option
- About AdvancedDisk file system requirements
- Configuring credentials for CIFS storage and disk storage units
- About AdvancedDisk storage servers
- About AdvancedDisk data movers
- About AdvancedDisk preferred or required read servers
- About data encryption for AdvancedDisk storage
- About key management for encryption of NetBackup AdvancedDisk storage
- Configuring key management for NetBackup AdvancedDisk storage encryption
- Configuring an AdvancedDisk storage server
- About AdvancedDisk disk pools
- Configuring a CIFS disk volume for AdvancedDisk encryption
- Configuring an AdvancedDisk disk pool
- Configuring an AdvancedDisk storage unit
- About storage lifecycle policies
- Creating a storage lifecycle policy
- Creating a backup policy
- Resilient Network properties
- Specifying resilient connections
- Managing AdvancedDisk
- Managing AdvancedDisk storage servers
- Managing AdvancedDisk disk pools
- Viewing AdvancedDisk disk pools
- About changing the AdvancedDisk disk pool size
- Adding volumes to an AdvancedDisk disk pool
- Changing AdvancedDisk disk pool properties
- Determining AdvancedDisk disk pool state
- Changing AdvancedDisk disk pool state
- Determining AdvancedDisk disk volume state
- Changing AdvancedDisk disk volume state
- Merging AdvancedDisk disk pools
- Removing a volume from an AdvancedDisk disk pool
- Inventorying a NetBackup disk pool
- Deleting an AdvancedDisk disk pool
- About monitoring AdvancedDisk storage capacity and usage
- Monitoring NetBackup disk activity
- Viewing AdvancedDisk disk reports
- Displaying detailed AdvancedDisk storage usage information
- Displaying KMS key information for AdvancedDisk encryption
- Toubleshooting AdvancedDisk
Resilient Network properties
The Resilient Network properties appear for the master server, for media servers, and for clients. For media servers and clients, the Resilient Network properties are read only. When a job runs, the master 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 master 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 master servers when they function as media servers. Resilient connections do not apply to master 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 different subdomain than the server, 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 dialog box properties describes the Resilient Network properties.
Table: Resilient Network dialog box properties
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.
The resilient status of each client also appears as follows:
In the NetBackup Administration Console, select in the left pane and then select a policy. In the right pane, a Resiliency column shows the status for each client in the policy.
In the NetBackup Administration Console, select in the left pane. In the right pane, a Resiliency column shows the status for each client.
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. Veritas recommends 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, Veritas recommends 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.
See the NetBackup Logging Reference Guide.