Compatibility and system requirements / recommendations. Verify both HW and SW compatibility with the new environment.
Installation Routine. Task list for the installation of the software on the new system.
Data Migration. If needed, how is the applications corresponding data restored into the application.
Pre-Requisites or dependencies. What, if anything is a necessary component of this software.
Connectivity. What data connectivity components and configurations need to be in place to ensure user connectivity to the application
Security. If necessary plan to migrate the current security model to the new installation.
Logistics. A task list of the entire migration process that addresses the whos, whats and whens of the migration in total.
Administration. Assignment of administrative rights and integration into your current administrative model.
End Users. Identification of the effected user base and items to migrate on client workstations. Develop a plan for doing any needed updating of user devices and create any user procedures or instructions that are required.
Communications. Often overlooked, communication to administrators, management and end users is the best way to manage risk during a migration. Proactive communication also keeps the monkey off our back so you can do your job.
Phases. Migrations are often more complex than simply installing new software. A migration implies that you have software that already contains specific configurations and data. And that its an application that provides a service/tool to existing connected users. Additionally, a migration often implies that you are moving software that is of value... perhaps even mission-critical software used by your organization. For these reasons it may be best to plan for a phased migration that includes testing, pilot and stepped roll-outs.
Support. During a complex migration its often best to plan for the worst. Set up communications channels with manufactures or third party-support. As an example, this support can take the form of on-call phone support or on-site support by a systems consultant during the planning or physical migration. Know your resources and put the aces in their places as a rule during a complex migration.
System Tolerance/Redundancy and Exit Strategy. Can you back out of your migration if everything blows up…? Make sure you can.
Good luck!
2006-09-05 09:15:29
·
answer #1
·
answered by Chuck C 3
·
0⤊
0⤋
Establish, implement and Test the setup more than one time. Alpha, Beta, small scale release procedures defined and measured. Verify the backups. Verify that the failover works. Simulate hardware failures to verify that the correct failover mechanisms work. Deliberately try and break the server with network floods and DOS attacks. Verify the max number of requests. Verify backup of server and software. Verify recovery procedure and time required. Verify database corruption detection and recovery.
2006-09-05 09:24:29
·
answer #2
·
answered by bondoman01 5
·
0⤊
0⤋
make sure when moving software from one server to another you have full security when you move it
looking for a the best anti virus look no more having avg/nortoms/macfee /they cant stop
anything
try zoneAlarm internet security suite
it does what it say's take the test with
zoneAlarm internet security suite
all in one firewall/anti virys/anti spyware
set the anti virus/anti spyware to full system scan
zoneAlarm internet security suite
all in one firewall / anti virus/ anti spyware
no1 auto virus killer that will kill off a virus
as the virus try to download on to your system
when you open your explorer and search on the net
there are virus on websire that will auto download
this all in one firewall/anti virus/anti spyware
will kill the download link fast and auto kill the virus
http://www.zonelabs.com/store/content/home.jp
many big company are using this & microsoft is one of them that use zoneAlarm internet security suite
2006-09-05 09:13:43
·
answer #3
·
answered by Anonymous
·
0⤊
0⤋
1) Ensure that the machine configurations are compatible with the software
2) Ensure that the new machine has access to all related integration points, i.e. databases etc
3) Ensure that you have failover scheme in place so that if anything goes wrong you can switch back to the current machine
2006-09-05 09:13:32
·
answer #4
·
answered by bostoncity_guy 2
·
0⤊
0⤋
Where can I find a new job when the server switch-over goes wrong?
2006-09-05 09:11:34
·
answer #5
·
answered by elw 3
·
1⤊
0⤋
i've got been to countless different sections. i began out out as a universal at philosophy. I left because of the fact it regarded like lots of the human beings there have been spouting platitudes and claiming them as genuine philosophies.
2016-12-12 03:08:39
·
answer #6
·
answered by ? 4
·
0⤊
0⤋
Do you have a good backup?
Have you tested your backup to make sure you can restore from it?
Do you have plenty of high caffeine energy drinks in stock?
Oh yeah... Do you have a good backup?
2006-09-05 09:12:20
·
answer #7
·
answered by troythom 4
·
1⤊
0⤋