I have a similar setup, except I'm using a GigE link over DWDM/leased
fiber, as well as a pair of 2Gb/s FC connections.
I have a master at two sites, each site has a tape library.
the /opt/openv filesystem is replicated using VVR, and the tapes are
replicated using ITC, so each backup writes simultaneously to a tape at
each location.
in the case of a DR event, the 2nd master would take over the replicated
filesystem, daemons started, and the device configuration wizard would
be run to reconfigure Netbackup to see whatever drives were available
(probably only the 2nd site drives, rather than both sites' drive as the
original master had seen.)
All second copy tapes would be promoted to pirmary and we're off to the
races.
as far as the hostname thing.....
each of my masters has 2 NICs.
the nic names have nothing to do with the "master" name.
both systems are named "master", in /etc/nodename, etc....netbackup is
installed with "master" as the name in all configs.
at head office, the NIC names in DNS, and in the /etc/hosts files are
master-ho1 and master-ho2
at the DR site, the NIC names in DNS, and in the /etc/hosts files are
master-dr1 and master-dr2
at head office, there is a dns alias that points "master" to
"master-ho1"
in our DR plan, there is a note to change the alias to point to
master-dr1, however that is only significant for launching the GUI from
a host other than the master, as both masters have an entry in their
hosts files that point "master" to the same IP as the primary NIC.
works fine for us.....alternating the catalog backups to 2 tapes, one at
HO and one at DR is a good idea, or if you don't have FC connectivity to
the second site, make sure a copy of your catalog tape is sent to the DR
site with your data tapes.
Paul
--
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Sponsler, Michael
Sent: July 31, 2006 10:03 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Disaster Recovery Site
I'm working to get a Disaster Recovery Site setup and
configured. I'm running my backups on my master server (netbackup 6.0)
from City A, and that master server backs up information from Cities X,
Y, and Z. The plan is to have another Master Server (netbackup 6.0),
for disaster recover, setup at City B (it's 100 miles away, with a 10
meg fiber link to city A). I was wondering about a "best practices"
approach. The catalog for the master server in City A sits on an
external RAID device (Sun StoreEdge 9980). The catalog is to be
replicated using Veritas Volume Replicator to a Sun StorEdge 9980 in
City B, so that the Disaster Recovery site as a mirror to the catalog in
City A. The idea is, is that if City A were for some reason to either
Fall off the map, or be disconnected from the internet, City B's master
server could pick up where City A left off. I know there are tape
issues involved here, and what I'm trying to setup is basically a
Netbackup Cluster. Now given the fact that City A and City B are at
least 100 miles apart, is there anything anyone can recommend for my
situation?
Also, given that I'll have two master Servers (an active /
passive thing), what would be the best way to approach hostnames? Does
netbackup allow you to change the hostname? Are there any issues with
changing a master server's hostname? Has anyone worked with the
Netbackup Cluster software? Would they recommend it for a Disaster
Recovery Site like I described?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060731/7d6a1bcb/attachment-0001.html
-------------- next part --------------
====================================================================================
La version fran?aise suit le texte anglais.
------------------------------------------------------------------------------------
This email may contain privileged and/or confidential information, and the Bank
of
Canada does not waive any related rights. Any distribution, use, or copying of
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately
from
your system and notify the sender promptly by email that you have done so.
------------------------------------------------------------------------------------
Le pr?sent courriel peut contenir de l'information privil?gi?e ou
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires d?sign?s est interdite Si vous
recevez
ce courriel par erreur, veuillez le supprimer imm?diatement et envoyer sans
d?lai ?
l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de
votre
ordinateur toute copie du courriel re?u.
|
