|
[Veritas-bu] Disaster recovery configuration
2005-12-09 17:33:44
This is a multipart message in MIME format.
--=_alternative 007BF01C862570D2_=
Content-Type: text/plain; charset="US-ASCII"
We have are a small company.
We only have 1 Master Server with 14 clients. Our master server runs on
Solaris.
This is what we do for our cold dr process(no available hardware) and our
warm dr process(availible hardware).
Protecting the server
==================
Solaris allows you to create an image (or flash archive) of your server.
We create the flash archive(down all the daemons) and burn it onto a Dual
Layer DVD.
The Solaris OS Installer is what allows you to apply the flash archive to
a server. After the system is booted we run tpconfig and fix up what
broke. Works great for Solaris 8 and 10.
Protecting the Clients
==================
We run BMR. It's a great product for moving servers around. The only issue
we have is the lack of support for Solaris 10 BMR clients. It's great for
moving servers onto different hardware.
We currently don't have a HOT DR solution. It sounds like that is what
your trying to do. I'd love to hear what you come up with.
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 12/09/2005 04:06:11 PM:
> We're starting the process of building out another data center as a
> disaster recovery facility. One of the things I don't yet know how to
> configure is NetBackup. We've got a single Solaris master server today
> and will obviously be putting a Solaris backup server at the DR site.
> We will also have a tape library there that will be doing regular
> backups as well as handle any disaster recovery restorations.
>
> Should I do a global cluster configuration for NetBackup? If not, and I
> configure the 2nd server as just a media server, how do I promote it to
> be a master? What support mechanisms are there to keep the catalog up
> to date at the DR site?
>
> I've had a quick look through the Veritas web site but haven't found
> anything that documents best practises for cases like this.
>
> Any suggestions would be greatly appreciated.
>
> Thanks,
> .../Ed
>
> --
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts AT ewilts DOT org
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
--=_alternative 007BF01C862570D2_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">We have are a small company.</font>
<br>
<br><font size=2 face="sans-serif">We only have 1 Master Server with 14
clients. Our master server runs on Solaris.</font>
<br>
<br><font size=2 face="sans-serif">This is what we do for our cold dr process(no
available hardware) and our warm dr process(availible hardware).</font>
<br>
<br><font size=2 face="sans-serif">Protecting the server</font>
<br><font size=2 face="sans-serif">==================</font>
<br><font size=2 face="sans-serif">Solaris allows you to create an image
(or flash archive) of your server. We create the flash archive(down all
the daemons) and burn it onto a Dual Layer DVD.</font>
<br>
<br><font size=2 face="sans-serif">The Solaris OS Installer is what allows
you to apply the flash archive to a server. After the system is booted
we run tpconfig and fix up what broke. Works great for Solaris 8 and 10.</font>
<br>
<br><font size=2 face="sans-serif">Protecting the Clients</font>
<br><font size=2 face="sans-serif">==================<br>
We run BMR. It's a great product for moving servers around. The only issue
we have is the lack of support for Solaris 10 BMR clients. It's great for
moving servers onto different hardware.</font>
<br>
<br><font size=2 face="sans-serif">We currently don't have a HOT DR solution.
It sounds like that is what your trying to do. I'd love to hear what you
come up with.</font>
<br>
<br><font size=2><tt>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on
12/09/2005
04:06:11 PM:<br>
<br>
> We're starting the process of building out another data center as
a<br>
> disaster recovery facility. One of the things I don't yet know
how to<br>
> configure is NetBackup. We've got a single Solaris master server
today<br>
> and will obviously be putting a Solaris backup server at the DR site.<br>
> We will also have a tape library there that will be doing regular<br>
> backups as well as handle any disaster recovery restorations.<br>
> <br>
> Should I do a global cluster configuration for NetBackup? If
not, and I<br>
> configure the 2nd server as just a media server, how do I promote
it to<br>
> be a master? What support mechanisms are there to keep the catalog
up<br>
> to date at the DR site?<br>
> <br>
> I've had a quick look through the Veritas web site but haven't found<br>
> anything that documents best practises for cases like this.<br>
> <br>
> Any suggestions would be greatly appreciated.<br>
> <br>
> Thanks,<br>
> .../Ed<br>
> <br>
> -- <br>
> Ed Wilts, Mounds View, MN, USA<br>
> mailto:ewilts AT ewilts DOT org<br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
> <br>
> <br>
> <br>
</tt></font>
--=_alternative 007BF01C862570D2_=--
|
|
|
