The Lessons Learned
Migration Lessons Learned
Evaluate the worth of the content before migrating to the cloud.
In SharePoint, some site collections and sites become unused overtime. Before migrating, consider the content that is unused and archive it to reduce maintenance costs and increase site collection/site performance. This evaluation can include interviewing users and teams to identify and migrate the valuable and highly accessed content ONLY. The identified content should be kept in an isolated location still
This in-depth market intelligence program from VDC will help hardware, software and service suppliers and other stakeholders sharpen their value propositions and solution development efforts in the embedded cloud market. Migrating to the Embedded Cloud: The Impact of Cloud- Based Deployment Methodologies on the Embedded Ecosystem will study the migration to cloud-based development and deployment methodologies for mission-critical, high availability and embedded applications. VDC delivers the most comprehensive and accurate market research and analysis of the embedded cloud market available from any source.
In this paper, we tackle challenges in migrating enterprise services into hybrid cloud-based deployments, where enterprise operations are partly hosted on-premise and partly in the cloud. Such hy- brid architectures enable enterprises to benefit from cloud-based ar- chitectures, while honoring application performance requirements, and privacy restrictions on what services may be migrated to the cloud. We make several contributions. First, we highlight the com- plexity inherent in enterprise applications today in terms of their multi-tiered nature, large number of application components, and interdependencies. Second, we have developed a model to explore the benefits of a hybrid migration approach. Our model takes into account enterprise-specific constraints, cost savings, and increased transaction delays and wide-area communication costs that may re- sult from the migration. Evaluations based on real enterprise appli- cations and Azure-based cloud deployments show the benefits of a hybrid migration approach, and the importance of planning which components to migrate. Third, we shed insight on security policies associated with enterprise applications in data centers. We articu- late the importance of ensuring assurable reconfiguration of secu- rity policies as enterprise applications are migrated to the cloud. We present algorithms to achieve this goal, and demonstrate their efficacy on realistic migration scenarios.
Department of Computer Science and engineering, Sri Manakula Vinayagar Engineering College,
Abstract - Today, most of the cloud vendors provides Database as a service to store our application data in their server. Now Cloud computing meets the problem in data backup. The data backup is necessity when there is network or cloud service vendor failure. The important problem in the cloud computing is migrating our data from one cloud vendor to another. To changing the cloud vendor user needs data backup. Most of the cloud vendors providing these backup services at high cost, but it is more expensive for the users and IT organizations. The need of data backup services is growing rapidly and it requires a powerful data backup technique. In this paper, we explore a technique for “Data Backup and Recovery”. This technique reduces the cost of the solution and not only data protection from service failure but also makes the process of migration, much simpler. This approach eliminate the cloud vendor dependency and also avoid data backup cost. Internal drives of a legacy machine do all these at very low cost.
Healthcare Data to the Cloud
There’s a Big Data dilemma in healthcare. Data generated by the U.S. healthcare system reached 150 exabytes in 2011, according to the Institute for Health Technology Transformation, and at its current rate of growth, data in U.S. healthcare will soon reach the zettabyte scale. Not long after, the Institute predicts it will reach the yottabyte level. To offer some perspective on the latter, the popular IT blog Gizmodo estimated that storing a yottabyte on terabyte-sized hard drives would require one million city block sized data-centers, big enough to consume the states of Delaware and Rhode Island combined.
Customer Requirements and Impacts
It is important to fully understand the customer requirements for a given application before migrating the server into the cloud. Some customers have strict SLA’s or usage requirements to retrieving information and providing data. By understanding the needs and requirements of the customer, an assessment can be made on whether a server can be migrated to the cloud and still meet the requirements and expectations of the user base.
VI. C ONCLUSION
In this work, we discussed the motivation, requirements, feasibility of migrating CiteSeerX digital library to provide an IaaS model in a private cloud. We report the challenges we encountered prior to and during the migration. We also report the post-migration issues and possible solutions. CiteSeerX represents a typical small or medium size digital library and similar projects in terms of its size, architecture, availability, maintenance team size, and data throughput. These digital libraries are likely to have the same or similar challenges when upgrading their systems. Our experience indicates that moving to a private cloud is a cost-effective solution in the long term compared to a public cloud model such as Amazon EC2. The major cost of the latter is due to huge disk storage and high outbound traffic. In addition, the private cloud solution provides us more flexibility to extend the system and create/delete new VM servers. The vSphere hypervisor automatically moves failed servers to healthy ones. The major challenges include lack of documentation, resource allocation, system compatibility, a complete and seamless migration plan, redundancy/data backup, configuration, security and backward availability. The major lessons we learned through the migra- tion are summarized below: (1) An up-to-date and complete documentation can significantly reduce the length of learning and investigation time; (2) For a digital library, the critical factor which drives the system expansion is the size of the data and its growth rate; (3) Testing machines should be used before putting changes to the production, to save a lot of time;
You’ve learned about ProfitBricks’ advantages. You know that you can get ser- ver, network, and storage based on your needs – not based on pre-packaged configurations. You’ve done the analysis on how much money you will save with ProfitBricks. Now, you’re ready to get started with your ProfitBricks account. Whether you’re an expert, or you’re new to the cloud, having a good plan for migrating your existing infrastructure to the ProfitBricks cloud will ensure a suc- cessful, low-risk, and cost-effective migration. This guide covers best practices for migrating to the ProfitBricks cloud from your legacy physical or virtual infra- structure.
Migrating to or within the cloud may heighten some of the challenges you would normally encounter, but these are not insurmountable problems. Many times, when new technologies arrive, there is a perception that the technology will solve everything. Cloud technology provides many advantages to businesses, but as with all innovation, it will never negate the need for proper design and planning.
Make a cloud plan
Before all else, compile a cloud computing plan that is tailored to your business. Assess how your IT staff spend their time and their budget and choose a cloud service that will benefit your business across all areas whilst taking the pressure off your IT department! Migrating to cloud computing can allow a shift of focus within your IT department, meaning you no longer have to worry about server updates and
Users of the tool can create migration projects, define their requirements for the migrated database layer, describe their current database layer and receive recommendations, hints, and guidelines on where and how to migrate their data. The tool supports conflict resolution based on previously identified cloud data patterns, and provides data adapters that allow for the automatic migration of data to recommended data stores and services. We evaluated the applicability of our approach by migrating the NovaERM Enterprise Resource Management application to an internal Private Cloud of NovaTec and to Amazon Web Services solutions. Apart from the usefulness of the methodology and tool support, we were able to identify missing functionality that we plan to address in our future work. In particular, our evaluation shows that explicit support for the testing phase of the migration has to be supported by the cloud data migration tool. Moreover, the tool should provide sandboxing capabilities, functional testing for bug fixing, and performance benchmarking tools for different application workloads. These capabilities can also be used to support the optimisation of the database layer after its migration. Additional functionalities that are currently being developed include addressing the impact of the migration to compliance, supporting more than one source and/or target data stores or services and multiple migrations per project, increasing the number of adapters available in the tool, as well as improving the usability and functional suitability of the tool for domain experts. Another important direction for our future research is completing the methodology to enable support for the migration of the other two logical layers of the application architecture.
Integral to MCEITS’s success is overcoming the initial challenges of migrating Marine Corps’ legacy systems to the MCEITS hosting environment. The first challenge of migration is ensuring that the customers will have the same IT capabilities that they had with their local data centers. Secondly, MCEITS must help their customers adapt their internal business processes in order to ensure necessary coordination takes place between the customers and the data center. Finally, MCEITS’s must reassure the customer commands as they surrender the direct control they previously enjoyed over their systems. This reassurance will come as the customers embrace cloud computing technology and realize the advantages it offers.
The number two is encryption. : Cloud migration is generally processed via WAN. It means sensitive company’s data is moving through internet and it can be hacked by malicious behavior. Customer data should be replicated to cloud with encrypted status.
The number three is direct migration: Sensitive company’s migrating data must not be delivered to cloud via any internet storage or repository. Migrating data should be replicated directly to cloud instance because it may be hacked or lost at the Internet Storage or Repository during migration.
However, a successful migration effort needs well-defined process support. It does not only help to identify and address challenges associated with migration but also provides a strategy to evaluate different platforms in relation to application and domain specific requirements. This paper present a process framework for supporting migration to cloud computing based on our experiences from migrating an Open Source System (OSS), Hackystat, to two different cloud computing platforms. We explained the process by performing a comparative analysis of our efforts to migrate Hackystate to Amazon Web Services and Google App Engine. We also report the potential challenges, suitable solutions, and lesson learned to support the presented process framework. We expect that the reported experiences can serve guidelines for those who intend to migrate software applications to cloud computing.
Migrating eScience Applications to the Cloud: Methodology and Evaluation 25 data store or service, and refactoring support during the actual migration of the data. Users of the tool can currently create migration projects, define their requirements in terms of the migrated database layer to the Cloud, describe their current database layer and receive recommendations, hints and guidelines on where and how to migrate their data. Conflict resolution is based on previously identified Cloud Data Patterns, and data adapters are provided, allowing for the automatic migration of data to recommended data stores and services. We evaluated our proposal by migrating the SimTech Scientific Workflow Management System (SWfMS) to Amazon Web Services solutions, and showed that while useful, our methodology and tool need further improvements.
Even when a public cloud is in use, some organizations aren’t necessarily committed to building an infrastructure on it, analysts noted.
“We have talked to a lot of customers who have deployed four or five sizes of machines at Amazon or Rackspace. They will use the public cloud provider to find out how many resources they actually need, and then they’ll come back in-house and make a [virtual machine] in- ternally to match that,” said Kyle Hilgendorf, principal research analyst for Stamford, Conn.- based Gartner Inc. —Beth Pariseau
requirements, hardware dependency, software EOS, and mission criticality (BCDR).
• Target & Migrate – Determine those apps that have potential SaaS alternatives, that need to be
encapsulated to run on IaaS, or can be moved to a more long-term PaaS environment. For PaaS-
bound apps, determine the specific PaaS services (Compute, Storage, Network) required, validate at the code level what remediation is required, remediate and test against PaaS standards. Use this same process to validate app readiness for PaaS on new apps developed in the Cloud.
Cloud-based solutions offer many benefits, including mitigation of risk and reduction in resources required. Figure
1 illustrates additional benefits:
Current and Emerging Cloud Technologies
Technologies are now available for both desktop virtualization and application virtualization. Many applications are already available in the cloud, including Salesforce, Google Docs and Microsoft’s Office 365. These cloud- based applications employ a web front end, with all the processing completed on databases hosted on public or private cloud storage. The true dawn of cloud applications, however, will arrive when business and everyday