> My thought was that if we had issues with the first Jukebox, or server,
> we could troubleshoot it while the 2nd one just keeps on going...Again, 
> I just want to do the right thing, and the incompatibility is a big obstacle.

If that's what you're looking to do, a bog-standard cluster in active/passive 
should be fine.  Just connect the jukebox to both using the same connections 
and drive/robot names and ordering and fail over between them.  If you're 
thinking about using a second server just in case the first one falls over, 
you're talking about a *LOT* of hassle to amalgamate the two servers onto one.  
 
The other option would be to install the server software on it and use it as a 
storage node with a failover script available which will run lots of nsradmin 
to disable all of the original server's resources and continue to run NW there 
until it's back online.  Or just get a reasonable support contract on your 
primary server's hardware.... ;)
 
Cheers,
 
Stuart.

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