HP3000-L Archives

November 2003, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Thomas M. Root" <[log in to unmask]>
Reply To:
Thomas M. Root
Date:
Tue, 25 Nov 2003 09:11:44 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Our 3000 is connected to an EMC Symmetrix which has the ability to replace
all our drives to another EMC box located at our disaster recovery site.
The notion of having a DR site with the previous night's backup data
preloaded on disk is very appealing, but the configuration of the DR system
is slightly different from our production system.

I know that I can use SYSGEN to create and maintain an alternate
configuration group, and that the GROUP= parameter of the START command
will allow me to boot a system using the alternate configuration.  It also
appears that NMMGR will let me maintain a file with an alternate network
configuration that could be renamed NMCONFIG when the DR system was
activated.  My questions are these:

1) Is there a way to have SYSGEN use my alternate network configuration
when it retrieves the NMMGR configuration data?

2) Is there a way to have NMMGR validate my network configuration using the
alternate system configuration group?

and 3) Is it realistic to think that if I pay proper attention to the
differences in system configurations, I could walk into my DR site, boot my
DR system from disk, mount my replicated user volumes and proceed to
recover my application system; or have I overlooked some gaping issue that
makes this all a pipe dream?

Thanks for your thoughts,

Tom

Thomas M. Root
Desert Schools FCU
Phoenix, AZ
602.433.7152
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2