Redundant Netbackup System -- Help..

[cscho]

Hi,

I have a set of systems that I know support the Netbackup client and I need to set up a geo-redundant backup system to collect the backups.

What I am hoping is someone can tell me if the following will work:

I have a couple of HP RX2800s (HPUX) each with 8x600GB disks that I want to set up in an geographically separate Active/Standby(DR)configuration.

From what I have read so far, I guess they would act both as Master/Media/Storage Servers. The standby would need to Replicate the backups from the Active Server so that it would be ready to take over if the Active one failed. 

Reading the various High Availability docs it seems that replication can be achieved with AIR and I see references to OpenStorage

or Media Server Deduplication Pool. Are these extra to the standard Netbackup installation/compatible with HPUX? - I really have no clue here... 

As you can probably tell I am a new to the whole Backup area let alone Symantec Netbackup so any assistance would be gratefully received.

Thanks..

[Nicolai]

Features and option are document in the NetBackup 7.x Operating System guide

 http://www.symantec.com/docs/TECH76648

If you take at look at page 55 you can see HP-UX 11.31 is supported on IA64.

Best Regards

Nicolai

[cscho]

Hi Nicolai,

Thanks for the response. I guess the point of my somewhat rambling earlier questions is.

1) Does that set up sound realistic, any obvious issues? and 2) to use the replication offered by AIR, would I need anything on top of the standard Netbackup License/installation?

Thanks

Chris

[Marianne · Accepted solution]

AIR is meant for 2 separate master servers (different hostnames) where backups to supported deduped storage is replicated to remote site, followed by import of replicated data into remote master's image catalog.This feature needs NetBackup Data Protection Optimization (dedupe) license.
See http://www.symantec.com/docs/TECH154323 .

AIR is not clustering - it will not automatically 'take over' when production master fails.
No policy config is replicated, neither is there any need for DR/remote master to have comms with Prod clients. The idea is to restore to alternate clients at remote site.

Maybe this WhitePaper will give you additional ideas to make master highly available:
http://eval.symantec.com/mktginfo/enterprise/white_papers/b-whitepaper_implementing_highly_available...

and NBU 7.5 Site Disaster Recovery: http://symantec.com/docs/TECH66060