Data center migration key business and server areas may be one of the most potentially disruptive changes to an organization's IT assets.Even if the migration itself goes well, the organization's chief information officer needs to quickly demonstrate measurable improvements to prove this difficult process.
Data center migration should not be intimidating.Of course, this is more difficult, and time is tight, heavy task, but if the organization is very care about the consequences of data center migration project, it is likely that this is not ready to, needs to continue to improve its planning.The old military adage also applies here: "plan and then move", and data center migration usually requires more time and resources than originally anticipated.
Using the smart migration approach for data center transformation ensures that the project succeeds in the first attempt.Here are four key points for the data center's successful migration:
Don't rely on your own guesswork.
One of the organization's worst mistakes is overestimating the knowledge of their IT infrastructure and its supporting technology applications and services.Worryingly, this is one of the most common mistakes.There is no doubt that the lack of new technology and employee turnover makes it difficult for organizations to retain data center expertise.
Although everyone has made the greatest effort in documentation and reporting, they need useful knowledge as staff retrain or leave.Even if the document does exist, it can be of poor quality and uneven quality.For example, the developer failed to record the policy changes and reindex after the new version of the application.This approach will lead to migration problems and lack of a single version of the truth data.
The answer here is careful planning.Take enough time to properly complete the initial mapping and discovery phase, as this will save time and long-term costs.
Don't exceed your abilities.
It is tempting to view the data center migration project as part of a larger upgrade process and to view and implement other major changes simultaneously.While it can theoretically save time and cost, in practice it increases the chance of project failure and crashes the rest.When you have multiple projects, consider implementing them in order and ensuring that you have enough time to migrate.
Also, a common mistake is to set unrealistic goals and complete schedules, and to proceed without knowing the impact of the time scale.This may start with a statement, such as "the data center lease expires in three months, so we must move to the new data center before it expires."This may not be a problem for a small company with only 10 to 50 servers, but for larger companies, it will take longer than three months.In addition, its complexity also affects the time scale.Balancing service delivery and migration deadlines can lead to significant conflicts when the same 10-50 servers are constrained by the flexible service level agreement (SLA) of the 24/7 income-generating data center.
Even with a sensible migration plan, it is important to provide enough manpower to ensure that deadlines are not missed and employees are not tired.Assuming that IT support and operators are both moving to the data center and continuing to perform their normal duties, this will inevitably lead to a decline in the quality of both jobs.
Make sure you buy it widely.
From the beginning, managing user expectations needs to be part of the data center migration strategy.By ensuring early migration of affected business and IT communities.This will help to align the capabilities of the new data center with business requirements, smooth transitions during this period, and support measurable ROI.
The sheer technical complexity of the data center migration is almost uncontroversial.Advocacy organizations adopt the method of whole rather than isolated, this will help the organization to reach an agreement in action, and eliminate the opposition, as early as possible in order to prevent its slow the migration of or damage to the data center.The migration of data centers to completion requires decisive force to maintain this momentum.
4. Don't assume anything as usual (BAU).
Effective governance of daily data center activities is critical to providing timely, reliable and secure services.However, it has been found that even the best client and service provider business as usual (BAU) processes cannot handle the amount of speed or change required to support a data center migration.
The change management process on the client side and the service provider side is designed to restrict access to the data center, to move and stop activities.Usually, this kind of level 1 or level 2 change operation under the most strict change management control, such as multiple change the examination and approval committee, which before the transfer date will provide a lot of the time of delivery.
Data center migration cannot be seen as a large number of minor changes: migration, escalation, or cancellation.Instead, it must use pre-agreed-upon quantities of equipment and only plan, approve, and operate at a set time.This process must be approved at the senior business owner level to avoid all business as usual (BAU) change management process overloading or delay client and service change approval.
Similarly, the request management process is designed as business as usual (BAU) for providing new devices or accessing the system and dealing with major project requirements.Nonetheless, people have seen that data center migrations overwhelm the request management process and even make it stagnate.
The way to minimize this is to group the requests and make sure the permissions are well in advance.Then, when update relevant configuration management database, can be affected by the configuration of the project details as updates to the contract schedule management approval, rather than as a labor intensive personal request.
No matter how perfect the organization's planning, even the best data center migration strategy will face unprecedented complexity.To reduce risk, a pragmatic approach called smart migration is advocated here.This ensures a thorough initial foundation work and discovery, allowing the organization to remain flexible in the face of disruption and making quick informed decisions to overcome the difficulties of implementation.The chief information officer can then be sure that they will be able to meet the needs of the evolving business.
沒有留言:
張貼留言