The main purpose of data center migration is to manage applications that provide services for the business. Whenever you consider migrating from one data center to another, you must first consider the availability of underlying services. These services include infrastructure applications such as active directories and client oriented applications such as SAP.
As for services that support most enterprise applications, such as active directory and DNS, a common practice is to extend these core services across data centers. The service is still on both sides of the data center until the migration is completed.
Risk two: data migration
The application data move from one place to another place may be one of the most complex part of the data center migration project, a simple solution is to perform tape or hard disk based backup and recovery, execution, but similar to translation migration, backup and restore the ability to provide timely service in the recovery area is limited. In addition, backup and recovery is not the best method for data migration - it is more suitable for data recovery scenarios limited disaster recovery scenarios.
The main way to select most data migration is to configure a leased line. If there is a special connection between two data centers, the migration team can make full use of the synchronization mechanism based on hardware or software to perform data migration. In addition to migrating data, this method can also be used to perform P2P migration, P2V migration, and virtual machine to virtual machine (V2V) migration.
Many companies decide to have multiple connections between two data centers. Connect at least two lines: one path is connected with the end user support and data center normal traffic to the data center, in order to support the active directory application and application to application traffic; Second Road, often faster connection to perform data synchronization. Dual connection can prevent two kinds of different traffic interference or influence each other.
Risk three: Hardware migration
There are usually two strategies for migrating physical servers: one is called lift and shift, and the other is called data replication. In the translation strategy, the hardware is placed on the moving truck, and then installed into the new data center. The system has been backed up before moving to the new site, but this strategy poses some risks.
One of the biggest risks is that the physical server may be damaged during handling, and the damage in the process of transport may cause backup to be useless. Another challenge is that the two data centers are too far apart, so this approach is impractical and cannot guarantee that the service can be available within an acceptable period of time.
The second strategy is to transfer data through a leased line. Leased lines bring two kinds of sub-swing hardware solutions. One scheme is to perform physical machine to physical machine (P2P) migration. P2P migration requires the acquisition of similar hardware, so that the application and hardware of the original data center can be migrated and the downtime is the shortest.
Another hardware migration scheme is the transformation from physical machine to virtual machine (P2V). P2V needs to convert a physical machine into a virtual machine by renting a line.
P2V aims to achieve two goals:
The first goal is to move the workload from one data center to another data center, while ensuring the lowest hardware cost.
The second goal is to achieve data center transition by transferring to the virtual platform. P2V migration is a popular option, because many engineers have become accustomed to implementing this transformation, which is part of the data center project before.
沒有留言:
張貼留言