FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention: SYSTEM AND METHOD FOR ASSESSMENT OF RISK ASSOCIATED WITH
SERVER MIGRATION
2. Applicant(s)
NAME NATIONALITY ADDRESS
TATA CONSULTANCY Indian Nirmal Building, 9th Floor, Nariman Point,
SERVICES LIMITED Mumbai, Maharashtra 400021, India
3. Preamble to the description
COMPLETE SPECIFICATION The following specification particularly describes the invention and the manner in which it
is to be performed.

TECHNICAL FIELD
[0001] The subject matter described herein, in general relates to server migration
and, in particular, relates to assessment of risk associated with server migration.
BACKGROUND
[0002] Server migration is a well known process in various enterprises where data is
moved from one server to another. Data may be moved between servers for different reasons, such as security, up-gradation of servers, or consolidation of applications. This process can either be performed by a team of personnel specialized in dealing with servers or people with reasonable skills to migrate their own data between servers. It is pertinent to note that during said migrations, data may be temporarily inaccessible and the server may not be able to cater to the users during such durations.
[0003] Conventionally, during migration between one data centre and another data
centre, the first data center ensures that a specified level of performance of the application will be maintained following migration of the application. In the process of ensuring maintenance of post-migration performance, the first data centre can assess various high-level requirements regarding migration system and migration environment. For example, the first data centre can determine the network requirements, server requirements, and storage requirements for the application. Further, such high-level requirements can be used to determine whether a target data centre would be capable of hosting the application in light of the requirements.
SUMMARY
[0004] The subject matter described herein is directed towards a method and system
for assessment of risk associated with server migration. In an implementation, the method includes providing, over a communication network, a plurality of parameter queries corresponding to the server migration from a source server onto a target server. A weight is assigned to each of the plurality of parameters queries. Further, inputs on each of plurality of parameter queries are obtained from one or more stakeholders over the

communication network. The stakeholders are associated with components of a migration environment. The risk associated with server migration is determined based on the inputs from the one or more stakeholders and the weights assigned to each of the plurality of parameter queries.
[0005] These and other features, aspects, and advantages of the present subject
matter will be better understood with reference to the following description and appended claims. This summary is provided to introduce a selection of concepts. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used for to limiting the scope of the claimed subject matter.
BRIEF DESCRIPTION OF DRAWINGS
[0006] The above and other features, aspects, and advantages of the subject matter
will be better understood with regard to the following description, appended claims, and accompanying drawings where:
[0007] Fig.1 illustrates a network environment implementing a server migration
index system for assessment of risk associated with server migration, according to an embodiment of the present subject matter.
[0008] Fig.2 illustrates an embodiment of the server migration index system and
various components.
[0009] Fig.3 illustrates a method for assessment of risk associated with server
migration, according to an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0010] Conventionally, before server migration, planning is achieved in terms of
finding suitable target server for migration. Such planning phase planning involves the assessment of risk of any failure during the migration, in view of all the activities that are required to be performed during migration. However, the parameters selected for such assessment are usually high-level, such as migration system parameters and migration

environment parameters. Additionally, said conventional approaches do not consider quantitative assessment as to risks and difficulty level with regard to server migration. Moreover, the conventional approaches for planning server migration do not consider the inputs of stakeholders in the process of migration planning. In addition, the approach is on a case-to-case basis and not generic, i.e., applicable to plurality of situations and environments.
[0011] The subject matter disclosed herein relates to system and method for
quantitative assessment of risk associated with server migration. According to an implementation, the approach according to the present subject matter involves obtaining specific inputs over a network on certain parameter queries from various stakeholders in migration process. The said queries pertain to several parameters that affect or can affect the risk and/or cost associated with migration. In an implementation, the present subject matter further involves generic and quantitative measurement of risks by assigning a weight, for example, numerical weight, to all parameter queries as per their importance. The system processes the inputs received by stakeholders and derives a migration index that spells out the level of risk in migration and helps the administrators to make a decision.
[0012] The stakeholders with regard to the migration environment may include
personnel responsible for hardware inventory, automated testing, governance, version control, planning register, IT knowledge base, etc. According to one implementation of the subject matter, all the above or more stakeholders give specific inputs on the parameter queries. The parameter queries, based on the relative importance and relevance of the parameter are assigned numerical weight. The queries are published keeping in mind the various ground level difficulties in implementing a server migration. The system in the present subject matter may also send the parameter queries to the stakeholders via the network. In other words, the risk assessed, for example, quantitatively, is based on actual and real experience of the stakeholders and there is no scope for estimates, assumptions ,or approximation thereby, leading to increased precision and accuracy in assessment of risk associated with the migration process.
[0013] Additionally, according to the present subject matter, the active involvement
of stakeholders in the risk assessment provides a pragmatic perspective as to whether to

carry out the migration process or not, and provides a reliable and profound assessment of the risks associated with a migration process between two servers.
[0014] Fig. 1 illustrates a network environment 100 implementing a server migration
index system 102, according to an embodiment of the present subject matter. In said embodiment, the network environment 100 includes the server migration index system 102 configured for assessment of risk associated with the migration of a server in an enterprise. In an example, the server migration index system 102 can be configured to achieve a quantitative assessment of the risk associated with the server migration. In one implementation, the server migration index system 102 may be included within an existing information technology infrastructure or an existing server migration system of an enterprise.
[0015] According to an aspect, the server migration index system 102 can be
employed for risk assessment associated with server migration in various implementations. For example, the server migration index system 102 can provide risk assessment in server migration for Financial/Trading environments, On-line Transaction Processing systems, Supply Chain Management(SCM) systems, Financial Management (ERP) systems, Customer Relationship Management (CRM) systems, Web Servers implemented for e-Business or e-Commerce, Human Capital Management (HCM) systems, Business Intelligence implementing environments, Data Warehouses, Technical and Scientific implementations, Core Banking systems and environments, Messaging servers, and Retail or Point of Sale (POS) systems.
[0016] The server migration index system 102 may be implemented in a variety of
computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, and a blade server. It will be understood that the server migration index system 102 may be accessed by stakeholders through one or more client devices 104-1, 104-2, 104-3….. 104-N, collectively referred to as client devices 104. Examples of the client devices 104 include, but are not limited to, a desktop computer, a portable computer, a mobile phone, a handheld device, a workstation. The client devices 104 may be used by various stakeholders within the migration environment in the enterprise. As shown in the figure, such client devices 104 are communicatively coupled to the server migration index system 102 through a network 106

for facilitating one or more stakeholders to access and/or provide inputs to the server migration index system 102.
[0017] The network 106 may be a wireless network, wired network or a combination
thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and such. The network 106 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the network 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.
[0018] The server migration index system 102 includes an information gathering
module 108 configured for gathering information and/or inputs from the stakeholders over a plurality of parameter queries relating to parameters concerning pre-migration planning and assessment. In said embodiment, the information gathering module 108 may be configured to generate and publish or send various parameter queries to facilitate server pre-migration assessment according to the subject matter described herein.
[0019] The information gathering module 108 can be configured to assign numerical
weight to the various parameter queries based on the relevance and/or importance of the query to the migration scenario. If a parameter is highly relevant and important to the migration, it may be given a high weight and vice versa. For instance, if the range of the weight is 0 to 5, the most important parameters may be assigned weight of 5. In one implementation, the parameter queries may be based on, but not limited to, various parameters from Table-1 shown below.
[0020] In another implementation, the information gathering module 108 can prompt
an administrator or a user controlling the server migration index system 102, and request to assign the numerical weights to the various parameter queries. Hence, the weights may be assigned to the parameter queries based on user inputs. Additionally, in another example, the server migration index system 102 can allow the user to configure and store rules for assigning weights to the parameter queries, and the information gathering module

108 can be configured to assign weights to the parameter queries based on the previously configured rules.
[0021] The information gathering module 108 can then publish the parameter
queries at a central location, say in an online web portal which is accessible by all the stakeholders. The stakeholders can access the parameter queries at the central location, and provide inputs, and save the inputs at the central location. The information gathering module 108 can then access the central location and obtain the inputs and responses provided by each of the stakeholders on the parameters queries.
[0022] In another implementation, the information gathering module 108 can
individually provide the parameter queries to the various stakeholders. In said implementation, the parameter queries can be sent to the stakeholders through various modes, for example, through email, through short messaging service (SMS), or through authenticated online portals providing individual access. In an implementation, the information gathering module 108 can request user information, such as email addresses or phone numbers, from each of the stakeholders through the client devices 104, and accordingly, send the parameter queries.
[0023] It will be understood that the parameter queries can be posed in the form of a
questionnaire, or an opinion poll or other forms of information gathering techniques. In an example, the queries can be formed based on the parameters shown in Table-1 below. As will be understood, the parameters and the parameter queries relate to the migration environment associated with the server migration. For example, the parameter queries can be based on parameters associated with a source server from which data is to be migrated, and parameters associated with a destination server onto which the data is to be migrated.
[0024] In another example, the parameter queries can be based on parameters
relating to endianness, parameters relating to architectural differences between the source server and the target server, hardware specification of the source server and the target server, target server testing parameters, and parameters related to shut down of the source server and cutover to the target server. Additionally, the parameter queries can be based on storage parameters, virtualization parameters, parameters concerning applications hosted by the source server, and parameters relating to execution of the applications on the target server.

[0025] Hence, according to the foregoing examples, the parameters and the
parameter queries can be related to, among other things, to the servers involved in the migration process, and the migration environment supporting the server migration. It will be understood that the parameter queries can be based on few or all of the above mentioned parameters, or a combination thereof.
[0026] As an example, Table-1 shows, but is not limited to, some of the parameters
to which the parameter queries may relate to. In an implementation, the information gathering module 108 can form the parameter queries based on all the parameters shown in Table-1. In another implementation, the information gathering module 108 can be configured to select a few of the parameters from all the parameters in Table-1 to form the parameter queries. Hence, the parameter queries can be formed by various permutations and combinations of the parameters in Table-1. In said example, the selection of the parameters for forming the parameter queries can be based on pre-defined user rules, or on the basis of previous similar activities carried out by the server migration index system 102.
Table-1

S. No. Parameters/Parameters
1 Initial server data collection
2 Initial Scope Definition
3 Server volume for migration
4 Identification of portability constraints on target OS
5 Identification of Pilot Project or POC team
6 Set up lab for Pilot Project
7 Analysis of the POC result
8 Design and design Migration Strategy
9 Risk Management Plan
10 Staffing Management Plan
11 Procurement Plan
12 Scope Management Plan
13 Finalize Scope

14
Work Breakdown Schedule
15 Define Rollback threshold and procedure
16 Publish status register
17 Publish issues & resolution register
18 Application functionality check list preparation
19 Set up Change Management System (CMS)
20 Secure the target OS license
21 Collect virtualization priorities
22 VM sizing
23 Asses current h/w utilization rates
24 Document known performance issues
25 Identification of differences in hardware dependencies
26 Identification of CPU architecture
27 Identification of differences in kernel thread
28 Analyze benchmark results
29 Provisioning method
30 Storage sizing
31 Define file system specifics
32 List security requirements
33 Network sizing
34 Network bandwidth and latency.
35 Interface Connections
36 Physical to VLAN Mappings
37 Available outage windows
38 Server Availability
39 Check application SLAs
40 Identification of Shell scripts
41 Identification of APIs
42 3rd party Libraries Usage
43 Source code availability
44 Source code quality

45
Source language
46 Availability of actual development team
47 Documentation availability
48 Documentation quality
49 Test and qualify Native Applications
50 Test and qualify h/w enablement Applications and Device Drivers
51 Test and qualify alternative s/w
52 Test and qualify Monitoring Tool
53 Test and qualify Remote Management Tools
54 Test and qualify Disaster Recovery Tools
55 Test and qualify Anti-virus s/w
56 Test and qualify Intrusion Detection s/w
57 RPM availability check
58 Vendor's s/w catalog check
59 Test & qualify SAN drivers
60 Test & qualify SAN volume managers
61 SCSI or RAID controllers
62 Compatibility check for middleware
63 Compatibility check for databases
64 Test & qualify JVM
65 Test & qualify C/C++ compiler
66 Test proprietary libraries and APIs
67 Resolve dependency issues
68 OS installation
69 Security & Hardening
70 Patch update
71 Database Installation
72 Build Custom Applications
73 Build Validation
74 Port Native Applications
75 Port ISV Applications

76 Port Scripts
77 Install h/w enablement Applications
78 Install Monitoring Tool
79 Install Remote Management Tools
80 Install Disaster Recovery Tools
81 Install Intrusion Detection s/w
82 Install Anti-virus s/w
83 Functional testing tools
84 Install performance testing tools
85 Migrate Data
86 Check kernel readiness
87 Check file system readiness
88 Validate the server and configuration
89 Validate application functionality
90 Analyze application logs
91 Monitor server event logs
92 Stress testing
93 Customer validation and UAT
94 Defect analysis and fix
95 Dry run with prod data
96 Comparison with source and target systems
97 Prepare decommissioning procedure
98 Ensure backup
99 Defunct server membership and roles
100 Change IP address of the servers
101 Perform data cleansing/destruction
[0027] The server migration index system 102 and further associated functionalities
are explained further with reference to Fig. 2.
[0028] Fig. 2 illustrates the exemplary components of the server migration index
system 102, according to an embodiment of the present subject matter. In one

embodiment, the server migration index system 102 includes at least one processor 202, at least one interface 206, and at least one memory 204 coupled to the said processor(s) 202. The processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
[0029] The interface(s) 206 may include a variety of software and hardware
interfaces, for example, a web interface, a graphical user interface, etc., allowing the server migration index system 102 to interact with the client devices 104 for stakeholders. Further, the interface(s) 206 may enable the server migration index system 102 to communicate with other computing devices, such as web servers and external data servers (not shown in figure). The interface(s) 206 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The interface(s) 206 may include one or more ports for connecting a number of devices to each other or to another server.
[0030] The memory 204 can include any computer-readable medium known in the
art including, for example, volatile memory (e.g., RAM), and/or non-volatile memory (e.g., EPROM, flash memory, etc.). In one embodiment, the memory 204 includes module(s) 208 and data 210. The module(s) 208 usually includes routines, programs, objects, components, data structure, etc., that perform particular task or implement particular abstract data types. In one implementation, the modules 208 can include, but are not limited to, the information gathering module 108, a data analysis module 212, and an index analysis module 214, and other module(s) 216. The other module(s) 216 may include programs or coded instructions that supplement applications or functions performed by the server migration index system 102.
[0031] The data 210 includes a parameter data 218, an analysis data 220, and other
data 222. The other data 222, amongst other things, may serve as a repository for storing data that is processed, received, or generated as a result of the execution of one or more modules in the module(s) 208. Although the data 210 is shown internal to the server

migration index system 102, it may be understood that the data 210 can reside in an external repository (not shown in the figure), which is coupled to the server migration index system 102. The server migration index system 102 may communicate with the external repository through the interface(s) 206 to obtain information from the data 210.
[0032] As explained earlier with reference to Fig. 1, the information gathering
module 108 can be configured to select the parameters for creating the parameter queries, and then provide the parameter queries to the various stakeholders through the client devices 104, in the manner as described before. Further, the information gathering module 108 can receive the inputs regarding the parameter queries from various stakeholders through the client devices 104, for example, via the interface 206.
[0033] According to an implementation, before sending the parameter queries to the
stakeholder, the information gathering module 108 can be configured to assign numerical weight to the each of the various parameter queries, for example, based on the relevance and/or importance of the parameter to the migration scenario. In said implementation, the information gathering module 108 can access the parameter data 218, which can include previously stored weights associated with each of the parameters and the respective parameter queries. Based on the parameter data 218 and the previously stored weights associated with each parameter query or the parameter or both, the information gathering module 108 can assign the numerical weights to each of the parameter queries.
[0034] In another implementation, the parameter data 218 can include user-defined
rules, which can be accessed by the information gathering module 108, for assigning the weights to each of the parameter queries. For example, if the parameter relating to the parameter query is highly relevant and important to the migration, it may be given a high weight and vice versa. For instance, if the range of the weight is 0 to 5, the parameter queries relating to the most important parameters may be assigned weight of 5. In one implementation, as mentioned previously, the parameter queries may be based on, but not limited to, various parameters from Table-1 shown above.
[0035] In yet another implementation, the information gathering module 108 can be
configured to assign the weights to each of the parameter queries based on the inputs provided by the stakeholders on that parameter query. For example, based on the inputs on each parameter query by the stakeholders, the information gathering module 108 can be

configured to determine a relative importance or relevance of that parameter query and accordingly assign a weight to that parameter query. For instance, the information gathering module 108 can assess the parameter queries for which all the stakeholders have provided inputs and may assign a greater weight with such parameter queries associated parameters, the assigned weights decreasing in an order of the number of stakeholders providing the inputs.
[0036] The selected parameters, the configured parameter queries, and the inputs
received from the stakeholders along with the assigned numerical weight are all stored in the parameter data 218. Further, the data analysis module 212 analyses the parameter data 218 using the processor 202. According to an implementation, the data analysis module 212 can be configured to determine a migration index based on the inputs on the parameter queries, and the weights assigned to the parameter queries. In an implementation, the data analysis module 212 can be configured to determine the migration index based on a weighted mean of the weights assigned to the parameter queries. In an example, the data analysis module 212 too can be configured to select a few parameter queries for determining the migration index, the selection of the parameter queries being based on, for example, a user input or user defined rules. In an example, the migration index can be a numerical value, determined by computing a weighted mean of the weights associated with each of the parameter queries on which the inputs from the stakeholders are received.
[0037] The data analysis module 212, after generating the migration index can store
the results in the analysis data 220. The index analysis module 214 can be configured to compare the migration index to a predefined migration index to ascertain whether the obtained value is greater or smaller than the said predefined migration index. The comparison achieved by the index analysis module 214 can be used by the server migration index system 102 to determine the risk associated with the server migration process. The index analysis module 214 can, in an example, provide the results of the comparison of the migration index and the predefined migration index to other associated system operated by, say the administrator, who can use the result in assessing the risk associated with the server migration. In said example, if the value of the migration index is less than the predefined migration index, then the index analysis module 214 can indicate that the risk associated with the server migration is low. On the other hand, if the value of the migration index is greater than the predefined migration index, then the index analysis

module 214 can indicate that the risk associated with the server migration is high. Hence, at a low value of migration index indicates a low risk associated with server migration and vice versa, which can be indicated by the index analysis module 214.
[0038] Fig. 3 describes another embodiment of the subject matter described herein
which is a method 300 for assessment of the risk associated in migration of a server. In an example, the assessment of risk as explained henceforth can be a quantitative assessment of the risk associated with the server migration. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, which perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0039] The order in which the method 300 is described is not intended to be
construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300, or alternative methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0040] At block 302, a plurality of parameters is selected from a set of parameters,
and parameter queries can be configured based on the selected parameters. The parameters and the parameter queries are related to server migration. In an example, the parameters and the parameter queries, can be related to the servers involved in the migration process, and the migration environment in which the migration between the servers is to be carried out. Further, in an implementation, the information gathering module 108 can be configured to select the plurality of parameters from the set of parameters and then configure the parameter queries. The parameter queries, hence configured, can be referred to as selected parameter queries. In another implementation, the information gathering module 108 can configure the parameter queries based on all the parameters.

Subsequently, the information gathering module 108 can select certain parameter queries, referred to as selected parameter queries, from the whole set of configured parameter queries.
[0041] At block 304, a weight is assigned to each of the parameter queries. In an
implementation, the weight, for example, a numerical weight, is assigned to the queries as per the relevance and importance of a query with regard to the migration. If a parameter is highly relevant and important to the migration, it may be given a high weight and vice versa. For instance, if the range of the weight is 0 to 5, the most important parameters may be assigned weight of 5. In an example, the information gathering module 108 is configured to assign weights to the parameter queries.
[0042] After assigning the weight to the parameter queries, at block 306,
stakeholders associated with the migration environment hosting and supporting the server migration, are identified. The stakeholders can be, but not limited to, personnel responsible for hardware inventory, automated testing, governance, version control, planning register, IT knowledge base, etc.
[0043] The parameter queries are, subsequently, provided to the identified
stakeholders at block 308 over the network 106, as discussed with reference to Fig. 1. In an implementation, one or more parameter queries relevant for the migration process are published over the network 106, i.e., provided for access at a central location, say a web portal accessible to all the stakeholders, so that the parameter queries are available to various stakeholders who are party to the migration process. In said implementation, upon publication of the parameter queries, the information gathering module 108 can prompt the various stakeholders, through the client devices 104, to inform that the parameter queries have been published. In another implementation, the information gathering module 108 can send the parameter queries individually to the various stakeholders. The queries may be based on, but not limited to, various parameters from Table-1 shown earlier. The queries may be published or individually sent to various stakeholders in the form of various permutations and combinations of the parameters shown in Table-1.
[0044] At block 310, the inputs on the parameter queries are received from the
stakeholders. The inputs can include responses provided to the parameter queries by the stakeholders.

[0045] At block 312, the inputs received from the stakeholders are processed and a
migration index is obtained based on the inputs from the stakeholders and the assigned weights to the parameter queries. In an example, the migration index can be determined by computing weighted mean of the assigned weight for each parameter query.
[0046] Once the migration index is calculated, the assessment of risk associated with
the server migration can be achieved. For the purpose, in an implementation, computed the migration index is compared with a predefined migration index, and the risk associated with the server migration is determined based on the comparison. In said implementation, at block 314, a determination is made to ascertain whether the obtained migration index is greater than a predefined migration index that corresponds to tolerable risk level for the migration process. If the migration index is less than the predefined migration index (‘Yes’ branch from block 314), then it means the risk associated with the migration is minimal and migration can be said to be viable. Hence, it will be understood that a low value of the migration index represents less risk in achieving the server migration.
[0047] However, if the migration index value is greater than the predefined index
value (‘No’ branch from block 314), then it means that the server migration if carried out would incur a lot of risk and may involve large cost and infrastructural losses during migration. In such a scenario, in an implementation, at block 318, a determination is made as to whether the parameters that are causing a high risk for server migration can be corrected or not. For example, the parameters associated with the parameter queries for which the inputs from the stakeholders are unfavourable are determined and then analyzed to ascertain whether the infrastructural or planning issues associated with these parameters can be corrected. In case, the analysis at block 318 yields that the parameters can be corrected, (‘Yes’ path from block 318), then the method from block 302 is executed again to assess the risk associated with server migration based on corrected parameters.
[0048] Further, in case the analysis at block 320 yields that the parameters, owing to
which the risk associated with server migration is heightened, cannot be corrected (‘No’ path from block 320), an indication is provided to signify that the server migration with the selected parameters would incur a large amount of risk and should not be carried out. Accordingly, a new server for carrying out the migration and accordingly new parameters can be identified and selected. On the basis of the new server, the method can be executed

from block 302 onwards to assess the risk associated with server migration on the new server and based on the new parameters.
[0049] Various embodiments of the above explained method in Fig. 3 are covered by
the present subject matter. These include, but are not limited to, methods involving permutations and combinations of plurality of parameters relating to migration scenario. Such parameters may include, but are not limited to, architechural differences, endianness, storage issues, virtualisation, hardware specification of the source and target servers, applications, execution of applications, testing of target migration environment etc.
[0050] It will be understood that although the above description is provided with
respect to the computation of migration index on the basis of weighted means of the weights assigned to the various parameters, in other implementations, the migration index can be computed using other techniques that can provide a similar assessment of the migration process. In such implementations also, the migration index is based on certain values assigned to each of the parameters. Such values can be weights or other similar values.
[0051] Although implementations for assessment of risk associated with server
migration have been described in language specific to structural features and/or methods, it is to be understood that the present subject matter (and not appended claims) is not necessarily limited to the specific features or methods described. Rather, the specific features and methods for assessment of risk associated with server migration are disclosed as implementations of the present invention.

I/We claim:
1. A method for assessment of risk associated with server migration, the method
comprising:
providing, over a communication network (106), a plurality of parameter queries corresponding to the server migration from a source server onto a target server in a migration environment, wherein a weight is assigned to each of the plurality of parameters queries;
obtaining inputs on each of plurality of parameter queries from one or more stakeholders associated with the migration environment over the communication network (106),; and
determining the risk associated with server migration, based on the inputs from the one or more stakeholders and the weights assigned to each of the plurality of parameter queries.
2. The method as claimed in claim 1, wherein the determining comprises computing a migration index based on the inputs from the one or more stakeholders and the weights assigned to each of the plurality of parameter queries, wherein the migration index is indicative of the risk associated with server migration.
3. The method as claimed in claim 2, wherein the determining further comprises:
comparing the migration index to a predetermined value;
determining the risk associated with the server migration based on the comparing.
4. The method as claimed in claim 1, wherein the parameter queries are based on parameters associated with the migration environment.
5. The method as claimed in claim 4, wherein parameters relate to at least one of endianness, architectural differences between the source server and the target server, hardware specification of the source server and the target server, testing of the target server, and shut down of the source server and cutover to the target server.

6. The method as claimed in claim 4, wherein the parameters relate to at least one of storage issues, virtualization, applications hosted by the source server, and execution of the applications on the target server.
7. A server migration index system (102) for assessment of risk associated with server migration, the server migration index system (102) comprising:
a processor (202); and
a memory (204) coupled to the processor (202), the memory (204) comprising,
an information gathering module (108) configured to,
associate a weight with each of a plurality of selected parameter queries;
provide the plurality of selected parameter queries to at least one stakeholder, wherein the stakeholder is associated with a migration environment hosting the server migration; and
receive inputs from the at least one stakeholder on each of the plurality of selected parameter queries;
a data analysis module (212) configured to obtain a migration index based on the inputs from stakeholders and the weight associated with each of the selected parameter queries, wherein the migration index is indicative of the risk associated with the server migration.
8. The server migration index system (102) as claimed in claim 7, further comprising an index analysis module (214) configured to compare the migration index to a predetermined value for determining of the risk associated with the server migration.
9. The server migration index system (102) as claimed in claim 8, wherein the index analysis module (214) is further configured to:
indicate low risk associated with the server migration when the migration index is less than the predetermined value.
indicate high risk associated with server migration when the migration index is greater than the predetermined value.

10. A computer-readable medium having embodied thereon a computer program for assessment of risk associated with server migration, the method comprising:
assigning a weight with each of a plurality of parameter queries, the plurality of parameter queries being related to the server migration from a source server onto a target server;
providing the plurality of parameter queries to one or more stakeholders, wherein the stakeholders are associated with a migration environment hosting the server migration;
obtaining inputs on each of plurality of parameter queries from one or more stakeholders; and
determining a migration index based on the inputs from the one or more stakeholders and the weights assigned to each of the plurality of parameter queries, wherein the migration index is indicative of the risk associated with server migration.