Skip to main content

A Roadmap to move from Cloud to In premise - The reverse migration -- Is Cloudflation at myth?

 Cloudflation as a term is being used and talks on the spiralling cost of cloud bills for an organization. The easily available and provisioning options leads to workloads that run for no reasons, orphaned accounts and a gamut of costs that are accrued by multiple departments without much of an oversight. There is a trend to reduce the workloads and have a semblance of order. It is imperative that we have plans that helps to reverse the migration to cloud and bring back some of the workloads that might work cheaper to run local.

Is there a roadmap to achieve this goal? A few pointers in this direction

A roadmap for moving from the cloud to in-premise computing should include the following steps:

  1. Assess current workloads: Assess the current workloads that are running on the cloud and determine which workloads would be most suitable for in-premise computing.

  2. Identify in-premise infrastructure: Identify the in-premise infrastructure that will be needed to run the identified workloads. This includes servers, storage, and networking equipment.

  3. Plan the migration: Create a plan for migrating the workloads from the cloud to in-premise computing. This plan should include details such as the timeline, resource allocation, and dependencies.

  4. Test and validate: Test and validate the new in-premise infrastructure and workloads to ensure they are functioning properly and meet the requirements.

  5. Migrate data: Migrate the data from the cloud to the in-premise infrastructure. This may include data backup, replication, and archiving.

  6. Monitor and maintain: Monitor and maintain the in-premise infrastructure and workloads to ensure they are running smoothly and to address any issues that may arise.

A checklist that can be used for this purpose would include the following items:

  • Assess current workloads and infrastructure
  • Identify workloads suitable for in-premise computing
  • Identify in-premise infrastructure requirements
  • Create a migration plan
  • Test and validate new infrastructure and workloads
  • Migrate data from the cloud to in-premise infrastructure
  • Monitor and maintain in-premise infrastructure and workloads
  • Review and evaluate the migration process
  • Continuously monitor and improve the in-premise infrastructure

It's important to note that this process can take time and may require a significant investment in terms of resources and expertise, so it's important to have a clear plan and budget in place. Additionally, it's important to ensure that the in-premise infrastructure meets the security, compliance, and regulatory requirements of your organization.

Comments

Post a Comment

Popular posts from this blog

Malware Damage - It is real and you need to be ready ...

  Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...
Post a Comment
Read more

CIO Questions answered - Your comments welcome - The reflections of the inner self

Briefly describe the typical size and organization of an IT team that you have managed. Include the division of responsibilities, how you track progress, etc. My experience ranges from me working independently, mainly to maintain my independence when I perform audits to managing a team of more than 25 - 100 consultants in various roles. I have handled multiple projects simultaneously where we have multiple consultants (typically from five to ten) working on multiple projects. We have used a set of tools to specifically monitor progress as well as the milestones. The projects involved were simple roll out of products (Microsoft Active Directory Domain Builds, Log Consolidation, Vulnerability Management) in line with product specifications to complex integration of systems that involves building multiple SoA interfaces for healthcare applications. For a successful project there needs to be proper delegation, personally I believe a person can deliver if he is not micromanaged, identifyi...
Post a Comment
Read more