Business continuity practices

1. Count and collect the Server distribution and usage capacity of the netapp storage fas3240/2240.

2. Determine the migration sequence and prepare p2v Based on the operating system type windows2003/2008.

3. Deploy the vmwarevsphere esxi server 5.5 environment on 6 new blades, and migrate the original system collected in step 2 to p2v. The migration environment requires better ip links and ip Address resources. Link requirements: the blade service supplier is required to prepare a two-way copy with a network speed of MB. In this way, all the images such as the Local disk, operating system, and database installation and configuration environment of the server can be uploaded to the virtual machine, form a complete and reliable Virtual Machine link.

4. After completing the above steps, all the resources and server resources at the operating system level will be migrated. As the existing production environment of the server is not damaged, rollback measures are available so that no data is lost.

5. The ing disks are all stored. There are two drawbacks in the backup restoration and import/export modes of the database: (1) it takes a long time for logical backup/physical copy of data, this operation does not meet the requirements of the existing network environment (2) because of the long time, and the failure to verify the correct data in a timely manner, it also has an impact on the existing environment.

6. We recommend that you use the oraclecdc Technology for continuous data capture. You can use the cdc and ogg technologies to complete the process. In this way, table-level data replication is formed. A complete table-level database is formed. Such a database is located in the lease storage of the six blades. This database features strong storage performance and carries all the data stored by netapp.

7. After the ing disk data is mapped to a table one by one using the ogg deployment method, we can obtain the oracle10g created by reconfiguration and installing the asm method on the new blade.

8. Although the table-level synchronization method of the ing disk migration is slow, production data and scheduled downtime are not affected.

9. After synchronization is complete, we select to change the IP address of the new blade virtual machine to the IP address of the original production server. Each physical machine corresponds to a new blade virtual machine. Then, select a nighttime business environment to complete system cutover. When the cutover method is used, unplug the production server network and access it to the new blade virtual machine.

10. The storage supplier accesses the new expansion cabinet.

11. The storage vendor re-deploys the netapp head and storage, configures blockcache size, and deploys the flexshare performance optimization package.

12. Re-implement the physical machine of the original production machine, format the disk, redeploy and configure windows, install the new oracle10g, and create the database with asm.

13. Use asm to migrate netapp and rental storage on different machines and process them based on asm command.

14. After the migration is completed, re-Synchronize the ogg data to the new physical machine.

15. cutover ip link.

16. Complete migration and test.

17. Finally, two data sets were formed. A set of netapp disk groups and expansion cabinets + physical machines, and a set of rental storage + new blade virtual machines. The latter is the disaster recovery of the former.