Hello,
Well, you tougched upon a sticky subjet with Networker and redundency, it 
could be viewed in many fashons, i.e server redundency, recover redundency 
etc etc.

Over the years, i have recovered networker at dr many times, so i am 
always looking for a way to get it up and running quickly, one of the 
approach that comes to my mind is to replicate nsr directory to some DR 
facility so you can by pass mmrecov process. Having a Standby server at DR 
is not feasable financially as well as from hardware\licencing prespective.
I would like Networker to go to someting like SQL server so clustering etc 
would become viable.
In absence of such, i belive EMC may still offer some form of high 
avalibility product that makes that possible.
Having a secound master server may not be feasable, since you now have to 
recover two master servers during DR , let alone the licensing, 
host\hardware and personell issues to recover two servers, i belive two 
master server will not share indexes.
It may be best practice to continue using one type of media in your 
current enviroment, unless mixed media is used for archiving\cloning etc.
As far as Data and recovery prespective, investigate what an diduplication 
and VTL can do for you. Utilizing  snapshots with replication may also be 
suitable in some inviroment.
Using barebone\ghosting recovery is another posibility.
HTH

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER