DOCUMENTATION: A configuration example for VERITAS NetBackup (tm) user-directed and database extension backups and restores when the master server is isolated from the backup network.

  • Article ID:100017356
  • Modified Date:
  • Product(s):

Problem

DOCUMENTATION: A configuration example for VERITAS NetBackup (tm) user-directed and database extension backups and restores when the master server is isolated from the backup network.

Solution

This document describes a configuration example for NetBackup user-directed and database extension backups and restores when the master server is isolated from the backup network.
 
This configuration example is designed to assist the NetBackup administrator when backup and restore data must transfer on a secure backup network, to which the NetBackup master server has no route.  A normal and fully supported NetBackup configuration always uses the backup network name of the client as its NetBackup configured name, and that backup network has a route to the master server for user-directed operations.  The configuration outlined in this document is considered a work-around when there is no route from the master server to the backup network and this work-around may be mutually exclusive to the configuration for certain other NetBackup features.  This configuration should be evaluated and tested for suitability with other NetBackup requirements before implementation in a production environment.
 
During a user-directed or database extension backup or restore operation, the NetBackup client must be able to connect to the master server and the master server must be able to connect to the NetBackup client.  If the NetBackup client name for the client is configured to be specific to the backup network it is on, and the master server has no route to that client, then client initiated (user-directed and database extension) backup and restore operations are not possible.  The following configuration allows the NetBackup client to initiate backup and restore operations, with data transfer on the secure backup network, as long as the client has an interface to an alternate network that can connect to the master server.

Pictorial representation of how to send backup through backup network rather than public network available in the attachment.

This article was initially written for Netbackup 6.0. But the troubleshooting procedure remains same in later netbackup versions as well.

Downloads

Was this content helpful?

Get Support