Haven’t read it, but we manage this by
rsyncing the /usr/openv folder across to our DR server – this includes using
nbdb_backup to do a hot backups of the SQL databases. We stop NB on the DR
system while we do it of course, so we don’t corrupt anything at the
remote end. J
To test our DR we:
1) Stop the daily rsync – so it doesn’t trash what we’re
doing
2) Start NB at the DR.
3) Delete and recreate the tape storage units to match what the DR
server has.
4) Delete all references to images on disk storage units –
because they don’t exist at the DR either
5) Start Restoring Data.
This has been tested 3 times recently, and
it worked perfectly every time. It’s been a while since I’ve done a
full catalog restore from tape, and certainly not with our current size
catalog, but it’s basically knocked 2-3 hours off our recovery times.
We still do catalog backups to tape, just
in case.
Cheers,
T.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of judy_hinchcliffe AT administaff DOT com
Sent: Friday, 5 December 2008 9:11
AM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Dr restores
without importing tapes.
I was wondering if anybody had read/implemented the doc:
Disaster recovery using partial catalog recovery in NetBackup…..?
This looks like the perfect solution for me.
I have a fully functional NetBackup environment in my DR site.
All I need to be able to do is restore from my production tapes without
having to import them.
If I do the “standard” for DR then I have a server sitting
up there doing nothing waiting for me to do a catalog recovery to it. As
I don’t need the policies, storage units, devices, but only need access
to the images, this white paper looks like a good fit for me.
I am looking at doing the replication of my images from the prod master
to the dr master into a new file system.
So has anybody else read this or implemented it?
If so, you see any issues that you think you would run into?
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
