NAS from a TSM perspective - looking for good/bad/ugly

Oh how the projects just keep coming out of the cracks in the walls . . .

We are a Netware shop that will be converting to Windows for file and
print serving.  Part of this project is consolidation many, many
Netware servers into a handfull of centralized Windows systems.  Some
remote sites will be served via WAFS technology while others will
have onsite local servers that replicate back to the centralized
servers.  The plan is for all backups to take place from the
centralized servers.  Right now the NAS team is talking about 4-6 big
windows servers, each with about 4-8TB of storage comprising 3-6m files.
It is possible that HSM would be used on these servers. These
servers would replicate part or all of their filesystem to a
DR site.

We are interested in advice that can help us in designing this system
so that we can effectively backup and recover.

Some of the questions we are thinking about . . . .

1)  Would this be better on a NAS system (yea, I know this is a TSM
list)?
2)  What's a good NAS system (Netapp, Celerra, other)?
4)  If NAS, use NDMP or not?

3)  Any good suggestions on setting up big Windows servers for effective
backup and recovery?
      - limiting individual filesystem size
      - memory/cpu requirements for TSM client to back this up
      - raw volume backups and incrementals
4)  If you backup BIG windows or NAS systems, could you describe
how they are setup and how TSM is setup to effectively backup
and recover them.

We have a "chance" to do this right . . . .

Thanks!!!!!

Rick


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.