cancel
Showing results for 
Search instead for 
Did you mean: 

Standby Master Server

JulianEli
Level 3

Hello there,

I would like to know if it is possible to have a netbackup master server and standby master server under the same NetBackup domain.

 

Is there any document that explains how to implement a standby master server, again, under the same netbackup domain.

 

Thank you in advance.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

A clustered master is the best to satisfy your requirement, but that needs to be done upfront. 
An existing standalone master server can only be converted to a cluster as consulting engagement.

A standby Linux server with same hostname and different IP address that is not on DNS can probably work.

The issue is not the hostname - that is easy to update/change.
The issue is keeping the catalog in sync with the production server.

Catalog replication is one way, but you need to ensure that ALL catalogs and db's reside on the same lun and that write-order fidelity is guaranteed by the replication technology.

This document explains the options in detail: NetBackup in Highly Available Environments Administrator's Guide 

 Have a look at the section under the topic: "About non-clustered NetBackup master server with catalog replication".

PS:
Your current environment is at risk as NBU 7.6 is no longer supported.
Please plan and schedule upgrade as a matter of urgency.

View solution in original post

4 REPLIES 4

Michael_G_Ander
Level 6
Certified

Have not seen anything about a standby master, but you could do a clustered master with a preferred active node.

Have assumed you want a master that can take over if the primary master fails.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Level 6
Partner    VIP    Accredited Certified

A clustered master is the best to satisfy your requirement, but that needs to be done upfront. 
An existing standalone master server can only be converted to a cluster as consulting engagement.

A standby Linux server with same hostname and different IP address that is not on DNS can probably work.

The issue is not the hostname - that is easy to update/change.
The issue is keeping the catalog in sync with the production server.

Catalog replication is one way, but you need to ensure that ALL catalogs and db's reside on the same lun and that write-order fidelity is guaranteed by the replication technology.

This document explains the options in detail: NetBackup in Highly Available Environments Administrator's Guide 

 Have a look at the section under the topic: "About non-clustered NetBackup master server with catalog replication".

PS:
Your current environment is at risk as NBU 7.6 is no longer supported.
Please plan and schedule upgrade as a matter of urgency.

Jim-90
Level 6

The simplest method to have a DR master server is to put it into VMware, realtime replicate the underlying storage to an offsite location.  If the primary one dies simple to resurrect at the DR site.   This assumes you have the ability to replicate storage.

Marianne
Level 6
Partner    VIP    Accredited Certified

@JulianEli

Have you seen attempts to help you?