I think you are asking if a Windows based TSM client with a SSD disk and an
i3 CPU is good for making backups of a NAS storage device.
The SSD storage in the client for nas backup doesn't really serve any
purpose, the i3 CPU might be a limiting factor if you have many
simultanious streams on a fast network such as a 10Gb LAN, if it is a
single 1Gb LAN I think you should be fine with a plain (none deduped or
compressed) stream from the NAS to the TSM server.
Memory is important, make sure you have a few GB available for the TSM
client.
Also try and split the data retrieval (to/from NAS) and data sending
(to/from TSM server) paths network wise if you use 1Gb networks especially.
Test restores and see if you get all the metadata back when implementing
NAS backups on new types of NAS devices.
.


On Wed, Apr 9, 2014 at 3:40 PM, Robert Talda <rpt4 AT cornell DOT edu> wrote:

> Folks:
>   I¹m not well versed in Windows platform specifics, so this question from
> one of my customers has me flummoxed - and curious.
>
>   The system (³solid state computer with an i3 CPU²) in question will be
> dedicated to the backup of a 3rd party NAS device (not NetApp, sadly) so
> the TSM client will be the primary (if not only) application running on
> the system.
>
>   Any thoughts appreciated!
> ----
> Robert Talda
> EZ-Backup Team, CIT/Infrastructure
> Cornell University
> rpt4 AT cornell DOT edu
> 607-255-8280
>