If you were talking to someone whose organization is considering NetApp Cloud Volumes Service for Google Cloud, what would you say?
How would you rate it and why? Any other tips or advice?
You need to plan out your architecture before you jump into any of these cloud environments. The good thing about NetApp is that they run on all three platforms, Azure, AWS, and Google. You need to have some idea of the architecture that you're putting in place, so you don't have to re-tool the thing later. We're using NetApp's admin tools, but not all of them yet because we're new to Google. And their team has been very proactive in working with us and helping us configure our environment. The service helped us to quickly move large numbers of files to the cloud. We have 15,000 patients' data that is being converted into this new system and we are doing data migration of about 100 gigabytes of storage. It's complex because we have to use HL7 protocols for that. That is an EDI language used for healthcare. That language stands by itself and there are different protocols to use when doing the migration and the mapping, and then the conversion of the HL7 transactions.
It is a good service for high availability that is very easy to configure. It is also very easy to put into our system running with NetApp. Currently, it is being used approximately 10 times a month. We have plans to include this service in other systems. Keep in mind that the network feeds require a special configuration. I would rate this service as an eight (out of 10).
What do you like most about NetApp Cloud Volumes Service for Google Cloud?
Thanks for sharing your thoughts with the community!
What is the most important first step for a company to take when moving towards mainframe migration? Where should evaluation of potential solutions begin in a large financial organization? Which users' input is most valuable?