Technially - yes. But 1) BE has source-side deduplication so it does at least a) offload target CPU from dedupe job b) saves tons of RAM for target as there's no need to keep hash tables and c) offload network as data is not travelling raw. StarWind from the other side does none of this as it's a primary data deduplication. We **may** have better saving numbers because of the many backup jobs overlap but hey... It's 2013 and storage is dirt cheap. Makes sense to dedupe flash and RAM but not SAS or (hell) SATA. That's why I'd recommend to experiment of course but I think everybody should do his job: Symantec dedupe backups (as they are sitting @ source), Microsoft dedupe file dumps (as they do it off-line so don't steal tons of resoures) and StarWind dedupe primary data, running VMs. Something neither Symantec nor Microsoft cannot do.
kspare wrote:Backup Exec has a deduplication option. Would starwind be able to replace that with very large deduplicated disk?