SERVER TO SERVER MIGRATION QUESTIONNAIRE & PROCESS DETAIL

Transcription

1 SERVER TO SERVER MIGRATION QUESTIONNAIRE & PROCESS DETAIL

2 HIVELOCIT Y SERVER TO SERVER MIGRATION QUESTIONNAIRE & PROCESS DETAIL This document is meant to help us ensure your server s migration to Hivelocity goes smoothly and that each party (you & Hivelocity) has all the information required to accomplish this. We require specific information prior starting a migration process that will allow us to investigate your existing system and create a migration plan. We are able to migrate 90% servers without issue. However, there are variables that may result in us turning down a migration job or for a migration job to take longer than normal. Examples of factors that could cause a migration issue are and not limited to the following: Source server has corrupted data. Source server OS is different than target, old and unsupported. Data to be migrated exceeds 2000GB. Source server hardware problems interrupting or retarding transfer of data. Source server is infected and unable to be cleaned. Custom Configurations File sizes. Migrating many small files takes much longer than transferring fewer large files. INFORMATION REQUIRED FOR MIGRATION EVALUATION 1. Management IP: 2. Access methods: 3. Ports of source server: 4. Amount of data to be migrated in GB: 5. OS of source server: 6. List what type of databases to be migrated (i.e. MSSQL, MySQL, Mongo, other) 7. Number of databases: 8. Size of each database:

3 SOURCE SERVER HARDWARE SPECS 1. CPU model: 2. Amount of RAM: 3. SATA, SAS or SSD drives: 4. Number and sizes of drives: 5. RAID (Yes or No): 6. Hardware or Software: 7. RAID type/level: 8. If hardware, RAID card model: 9. Server port speed: (i.e. 10Mbps, 100Mbps, 1Gbps other) 10. Any virtualization layer on server? (ESXi, ProxMox, SolusVM, HyperV, VMware, other)

4 APPLICATION TESTING 1. Please provide some sites and/or procedures to test your server prior to, during and after the migration. 2. Do you have a specific preferred date to be off your old server? 3. Do you need an expedited migration? 4. Do you need to schedule a maintenance window with your customers for this migration? We will require root or admin access to your Linux or Windows server in order to perform the migration. We will request this information via an encrypted trouble ticket prior to our starting the process and giving you a final approval. DNS AND REGISTRAR IP ADDRESSES 1. Would you like assistance making changes at your registrar or updating DNS? 2. Are you hosting DNS Zone file records on the server being migrated? 3. If yes, are you hosting DNS for one or more domains on the server? (It s likely the IP addresses within the zone file records may need to be updated to reflect newly assigned IPs on your new server. Part of our migration would be to work with you to get these IP addresses updated.) 4. Please list any other details you feel is important regarding the migration.

5 OUR DATA MIGRATION PROCESS Note: All migrations require some manual processes. Since there are DNS and IP changes that generally happen during migrations there is a possibility of downtime. Our goal is to minimize this as much as possible. After we analyze your existing servers we will make recommendations to help eliminate or minimize any service outage. If downtime is unavoidable then we will create a scheduled plan with you to ensure you can appropriately notify your customers of any maintenance windows that we schedule. 1. Once we receive the answers to our questions above our migration team will inform you via a trouble ticket if your server is likely to qualify for our migration service (90% of servers do). 2. We will request login credentials to your server via a secure & encrypted trouble ticket for a final inspection and final approval. 3. Upon final approval we will inform you that we are ready to start the migration at your direction within the same trouble ticket opened in step We will begin migrating your server s data to your new Hivelocity server. Most migrations are completed within several hours but this can vary depending on the amount of data, location of source server and the connection speed available to us at your data source. We will provide you with an initial estimated migration time within the first 90 minutes of starting the data transfer. 5. We will need to perform one final data sync after we have completed the migration of data. This final data sync will update your new server with any read/writes performed after we started the initial data grab. 6. It will be important that you and Hivelocity coordinate closely during stages 4 and 5. Once we complete stage 5 you will be instructed to update your IPs and DNS information to complete the transition of serving your data off your new Hivelocity server. This can be accomplished seamlessly with little to no downtime but it must be a coordinated effort to achieve.

6 CONTACT US 8010 Woodland Center Blvd Suite 700 Tampa FL Toll Free: Fax: Hivelocity.com