How to ensure Catalog data consistency in DR replication to start up NB on DR site?

[nbmagic]

We are planning on setting up NB on DR site. As PoC, at this time, we only want to be able to start NB on DR, and replicate all Database and needed files in order to start up NB server. Backups and archive data are not needed. However, the storage supports snapshot based volumes/lun replications, but doesn't have a tool to freeze up I/Os, to ensure the data consistency, only replicate whatever on the disk. Without this function,  can NB be started on DR?

Does NB has the ability to freeze I/O's before taking the snapshot, or any way to  ensure  the data consistency.

We are using NFS based backup media.

Thanks!

[RiaanBadenhorst]

There is no such snapshot integration for the catalog backup. How busy is your environment? Why don't you stop the services?

[Marianne]

You may want to read through NetBackup in Highly Available Environments Administrator's Guide  

There is a section that deals with Catalog Replication and requirements to ensure consistency. 

See Chapter 5: Deploying NetBackup master servers with full catalog replication -> About conditions for support of replicated NetBackup catalogs

[nbmagic]

This is not for backup, but DR recovery. Will this approach work? I meant, if I use storage replication to replicate catalog DB over to DR, and could the standby server in DR site be started?

[Marianne]

The section in the manual is about replication of NetBackup catalogs. Not Backups.
And recovery of NetBackup in a DR situation.

Please go through the section in the manual to ensure that ALL components that make up NBU catalogs reside on a single volume that is replicated in write-order fidelity manner.

When you have confirmed that ALL requirements in the manual have been met, go ahead and implement the replication.
Next step is to schedule regular tests.
This is how you will know if this is going to work for you...