Nicholas Cassimatis wrote: > As an appliance, I call that Hardware, as in it's a device outside of the > host getting the service, performing the service.
You can call an apple a pear, but that will not make it so. Now, more to the point, of course an appliance doing exactly one task (dedup incoming data) can be implemented to be faster than an appliance doing a multitude of tasks on the same amount of hardware. Remember that most TSM servers are sized for their current task, adding dedup to that will increase workload. My bet is that when TSM includes dedup, you will find that if you add the same amount of resources to your TSM server as you will find in your dedup appliance, (CPU, memory, I/O bandwidth) TSM can perform those tasks plus it's own tasks just as well as a separeate TSM server and dedup appliance. -- Met vriendelijke groeten, Remco Post, PLCS
