Theoretically you could run your NetWorker environment in a cluster config
with server on one node and storage on another node... if the NetWorker
server should fail move it to the 2nd node and bring down the storage
node...  You may want to find out from EMC if something like that could
work.

I've never run NetWorker in a cluster though... I'm happy with a single
monolithic bandwidth behemoth...  (Go T5240, you were made for backups :-P)

Alec

On Thu, Feb 25, 2010 at 8:48 AM, STANLEY R. HORWITZ <stan AT temple DOT edu> 
wrote:

> On 02 25, 2010, at 9:41 AM, Matthew Powell wrote:
>
> > We have an environment set up that has just one physical backup server
> right now. We are in the planning stages of setting up a storage node to
> help with the load. I have a question about the storage node. If for some
> reason the primary server went down could the storage node take the primary
> servers place and if so is this something that would be an easy switch or
> alot of work? Any advice on this would be greatly appreciated. Thanks for
> your time.
>
> Your storage node will stop working if the NetWorker server that controls
> it fails. Since a storage node lacks the NetWorker server binaries and the
> contents of /nsr/indexes as well as the configuration for all your backup
> devices, your only option for using your storage node to do backups in the
> absence of your NetWorker server would be to promote your storage node to a
> server, then treat it as a DR situation where you would use mmrecov on the
> storage node in order to bring back the most recent media index, then take
> the usual steps to restore the client file index. To do this, it is best of
> the storage node and the NetWorker server run the same Operating System and
> of course, have access to the same type of backup media hardware as does
> your server.
>
> By the time you do all of this, it might be easier to simply fix the
> problem with your server and bring it back online. If you do end up using
> your NetWorker storage node as a server, you will need to reverse the DR
> process on the original server once it is fixed in order to keep the media
> and client file indexes current.
>
> 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
>

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