,Apatosaurus not Brontosaurus.
Apatosaurus, not Brontosaurus. "Brontosaurus" refers to the incorrectly assembled skeleton (wrong head on the body).
What is NetApp up to, partnering with a cloud IT provider, Amazon, that's positioned long-term to try and annihilate NetApp's business? Let's start from the position that you are a NetApp customer with your own FAS array and you want to use Amazon Web Services, the AWS cloud computing facility, on some data in that array. How …
Did you know that customers worried about latency between their NetApp DC and AWS can deploy Riverbed Steelhead WAN optimisation? All they need is an appliance or software version of Steelhead in the DC and a Cloud Steelhead (CSH) at the AWS side and the NetApp replication is deduped along with any other data directly between DC and AWS. No need at all for the Colo site that NetApp specify and the CSH is set up as easily as buying an instance from Amazon in the first place via an online portal.
Regards,
Jim Morris Group Business Development Manager
Zycko Benelux BV Smart Business centre, Daalwijkdreef 47, 1103 AD, Amsterdam The Netherlands
Yes to Jim's point, CSH is an amazing tool to get customer on-prem over to AWS, but it serves a specific use case where the NPSAWS serves different use cases. We have Riverbed customer using CSH for this exact purpose today (backup to AWS). Now for the customer data center connection to the Direct Connect facility, you don't have to have a the private/direct circuit, Riverbed is another alternative that works great. We see this fitting well for a lot of our data center consolidation use cases back to the NPSAWS system.
NetApp use cases: http://day1solutions.com/netapp
We have customers running in US-East today, but have many from EMEA that are interested, even multi-region with UK-Ireland <-> US-East. Feel free to reach out to me if you have any questions luisb@day1solutions.com