Find Resources and Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

Subscribe to this discussion

Data Center Migration Audit

Hi - I am working on creating a work plan for Data Center Migration and was wondering if anyone had to do this before and could share some idea/thoughts?? Currently, the risks that I had identified are those that one would typically see in a Data Center audit. Any help would be appreciated. Thanks!
You must sign in to rate content.
(Unrated)

Comments

RE: Data Center Migration Audit

Hi! I have not participate in a data center migration yet, but I have some ideas for you to consider.
generate back ups from the core applications and make sure it works propperly
centralize the documentation from the resources
Make sure that you have a rollback plan in case something goes wrong
Check out the compability of the applications with the new version you are migrating to.

Hope this help you. :)
Samantha M. at 4/25/2016 12:13:00 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

I was in the same dilemma 2 years ago - when I was a Sys Admin. The one thing that made the whole process seamless with less than 15 minutes overall downtime was MIRRORING AND REPLICATION! My Advise therefore based on my experience: 1) Ensure the clients' main server (Server 1) is up to maximum performance, since they are going to lose their backup server (Server 2) for a while. (we had both main and backup in the same DC. If they are in different locations, modify to suit you) 2) Client should replicate/mirror to Server 2. Ensure Server 2 is also up to performance - able to handle at least a week's processing. Make sure OS, applications, language packages, Apache, logs, backup scripts/functions, Database are all replicated. Client should spend time studying various aspects of their Server 1 - the process flow (and all the applications and dependencies that support this process flow). Admins in-charge of the Systems, Applications and Data should document these to ensure no aspect of the system is missed. Server 2 is now a fully capable standby server 3) Move Server 2 to new DC Setup configurations etc; Data admin should ensure that the database continues to be replicated between the main server still in old DC and Server 2 at new DC. 4) On the night with least processing, re-route all processing to Server 2. If the preparation stage was well done - you'll have less than 10 minutes downtime during this re-routing. Server 2 now becomes your main server. Monitor - At least 1 week. Somethings could have been missed, repair. Document any changes outside data that have been made to the system. 5) If all is well move Server 1 to new DC. Set it up as the Backup for a while and replicate the data to Server 1. Remember, Server 2is the one with the most current data since it's acting as the main server. Ensure you have up-to-date data and applications. 6) Client should pick the night with the least work load/processing and convert Server 1 back to be main server (by changing network configs etc). Server 2 goes back to being the backup. If all was done correctly, downtime will be very minimal again. Monitor. Obviously the client wants the least downtime. Their implementation plan should support this.
Ombongi.Moraa at 5/3/2016 1:27:55 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

thanks for sharing
Eric934 at 6/14/2016 2:57:08 PM Quote
You must sign in to rate content.
(Unrated)

RE: Data Center Migration Audit

thanks for sharing
Eric934 at 6/14/2016 2:57:08 PM Quote
You must sign in to rate content.
(Unrated)

RE: Data Center Migration Audit

I was in the same dilemma 2 years ago - when I was a Sys Admin. The one thing that made the whole process seamless with less than 15 minutes overall downtime was MIRRORING AND REPLICATION! My Advise therefore based on my experience: 1) Ensure the clients' main server (Server 1) is up to maximum performance, since they are going to lose their backup server (Server 2) for a while. (we had both main and backup in the same DC. If they are in different locations, modify to suit you) 2) Client should replicate/mirror to Server 2. Ensure Server 2 is also up to performance - able to handle at least a week's processing. Make sure OS, applications, language packages, Apache, logs, backup scripts/functions, Database are all replicated. Client should spend time studying various aspects of their Server 1 - the process flow (and all the applications and dependencies that support this process flow). Admins in-charge of the Systems, Applications and Data should document these to ensure no aspect of the system is missed. Server 2 is now a fully capable standby server 3) Move Server 2 to new DC Setup configurations etc; Data admin should ensure that the database continues to be replicated between the main server still in old DC and Server 2 at new DC. 4) On the night with least processing, re-route all processing to Server 2. If the preparation stage was well done - you'll have less than 10 minutes downtime during this re-routing. Server 2 now becomes your main server. Monitor - At least 1 week. Somethings could have been missed, repair. Document any changes outside data that have been made to the system. 5) If all is well move Server 1 to new DC. Set it up as the Backup for a while and replicate the data to Server 1. Remember, Server 2is the one with the most current data since it's acting as the main server. Ensure you have up-to-date data and applications. 6) Client should pick the night with the least work load/processing and convert Server 1 back to be main server (by changing network configs etc). Server 2 goes back to being the backup. If all was done correctly, downtime will be very minimal again. Monitor. Obviously the client wants the least downtime. Their implementation plan should support this.
Ombongi.Moraa at 5/3/2016 1:27:55 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

Hi! I have not participate in a data center migration yet, but I have some ideas for you to consider.
generate back ups from the core applications and make sure it works propperly
centralize the documentation from the resources
Make sure that you have a rollback plan in case something goes wrong
Check out the compability of the applications with the new version you are migrating to.

Hope this help you. :)
Samantha M. at 4/25/2016 12:13:00 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

Hi! I have not participate in a data center migration yet, but I have some ideas for you to consider.
generate back ups from the core applications and make sure it works propperly
centralize the documentation from the resources
Make sure that you have a rollback plan in case something goes wrong
Check out the compability of the applications with the new version you are migrating to.

Hope this help you. :)
Samantha M. at 4/25/2016 12:13:00 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

I was in the same dilemma 2 years ago - when I was a Sys Admin. The one thing that made the whole process seamless with less than 15 minutes overall downtime was MIRRORING AND REPLICATION! My Advise therefore based on my experience: 1) Ensure the clients' main server (Server 1) is up to maximum performance, since they are going to lose their backup server (Server 2) for a while. (we had both main and backup in the same DC. If they are in different locations, modify to suit you) 2) Client should replicate/mirror to Server 2. Ensure Server 2 is also up to performance - able to handle at least a week's processing. Make sure OS, applications, language packages, Apache, logs, backup scripts/functions, Database are all replicated. Client should spend time studying various aspects of their Server 1 - the process flow (and all the applications and dependencies that support this process flow). Admins in-charge of the Systems, Applications and Data should document these to ensure no aspect of the system is missed. Server 2 is now a fully capable standby server 3) Move Server 2 to new DC Setup configurations etc; Data admin should ensure that the database continues to be replicated between the main server still in old DC and Server 2 at new DC. 4) On the night with least processing, re-route all processing to Server 2. If the preparation stage was well done - you'll have less than 10 minutes downtime during this re-routing. Server 2 now becomes your main server. Monitor - At least 1 week. Somethings could have been missed, repair. Document any changes outside data that have been made to the system. 5) If all is well move Server 1 to new DC. Set it up as the Backup for a while and replicate the data to Server 1. Remember, Server 2is the one with the most current data since it's acting as the main server. Ensure you have up-to-date data and applications. 6) Client should pick the night with the least work load/processing and convert Server 1 back to be main server (by changing network configs etc). Server 2 goes back to being the backup. If all was done correctly, downtime will be very minimal again. Monitor. Obviously the client wants the least downtime. Their implementation plan should support this.
Ombongi.Moraa at 5/3/2016 1:27:55 AM Quote
You must sign in to rate content.
(1 ratings)

RE: Data Center Migration Audit

thanks for sharing
Eric934 at 6/14/2016 2:57:08 PM Quote
You must sign in to rate content.
(Unrated)

Leave a Comment

* required

You must login to leave a comment.