Hello,
Backing up large client via Storage Node may be best possible option, i am 
not understanding the various level of networker additions and it you seem 
to suggest some don't depend on the master server for proper functions.
My understanding is all SN need to have Master servers, and if you 
properly configure your pools, client attribute for the SN and place other 
SN as alternative backup servers, including master server, you can fail 
over to them in the event of SN failure ( I doubt that they can be so 
flaky as to break down every day).
Backups may flow over ethernet compared to direct tape but backups should 
not fail, there may be even better way to architect them also.
HTH



MIchael Leone <Michael.Leone AT PHA.PHILA DOT GOV> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
04/02/2008 08:33 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Michael.Leone AT PHA.PHILA DOT GOV


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] Backups of Large clients 1+ TBs






EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
04/01/2008 04:13:25 PM:

> I think you are asking the question many of us are dealing with 
> right now..........what direction do you go?
> 
> We have gig connections, but we have more and more data we need to 
> backup.  Do we spend money and resources on a VTL....that still 
> means managing tapes.  Do we spend money on a de-dupe solution?  You
> can eliminate tapes if you don't HAVE to send stuff offsite but way 
> more expensive than a VTL environment.  Storage nodes will help 
> offload some of the work and storage for the networker server, but 
> its a license cost.

Something to be aware of with storage nodes ... they require a connection 
back to the NetWorker server. If that connection gets broken, the storage 
node doesn't back up the clients it's supposed to, since it's being 
controlled by the NetWorker server. (so my boss tells me)

We had that problem - we had a flaky connection to a couple of our sites, 
which had storage nodes with their own tape drives on them. They were 
supposed to backup the clients at those sites. Well, when the connection 
back here to the NetWorker server dropped, that storage node stopped 
backing up it's clients. (we eventually got those links fixed). So we 
bought NetWorker Business Edition Server licenses for those sites, so they 

don't depend on communicating with the NetWorker server here.

So I have NetWorker Network Edition server here in the data center, with 
70+ clients, and 2 tape libraries. We also have 4 NetWorker Business 
Edition Servers at 4 remote sites, which backup the servers in those 
respective sites, to their own tape drives. I have storage nodes here in 
the data center (dedicated storage nodes, with aftd devices, so some 
servers back themselves up to disk, and I clone from there).

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