Migration Plan from UNIX to Microsoft Server

Migration Plan from UNIX to Microsoft waiterselective information Migration is the process of transferring entropy between antithetic storage types, servers or formats. Its not just ab by copying data, but also about validating the data according to constraints and since several(predicate) databases uses different data types, this step also accept modifying the data as per the cross server. One essential requirement is that the data migrated should verify the production line logic to run applications smoothly on target server.Migrating from angiotensin-converting enzyme server to another can be a tricky situation. There ar divers(a) ch anyenges while migration of full data from UNIX server to Microsoft server. First of all the user should completely understand the data sources and their beseeming formats. Usually, too many spreadsheets or excel files, or redundant data may affect proper migration. Wherever possible, instead of manual, automated systems should be used. Mic rosoft offers MAP (Microsoft Assessment and Planning) tool to identify the various constraints, or issues that might occur while migrating from UNIX platform to Microsoft server. Moreover, SSMA (SQL Server Migration Assistant) can further answer in performing the migration. SSMA can create mapped schemas to UNIX server, which helps in easy migration of data.It is essential that the all applications like email, finance systems, personal records, computer-aided design/CAM engineering facilities, production systems, Sales Marketing databases, nettsite etc. should run smoothly after migration. There are various underlying steps that need to be taken care of for easy and error-free migration, as explained belowRecognizing the pattern-Template Creation To begin migration, first well have to understand the schema of UNIX database. Well create a template consisting of sweep over data key objects. The template has following two sectionsSection 1 Key Data Fields In the first section of t he template user forget provide the key determine, such as storage objects material, address etc. Usually, in key field columns, drop-down lists are provided for accurate and easy presentation of data.Section 2 Derived and Default FieldsBased on the key field values, various fields can be derived based on the Business translational logic. For example, using the production unit key field the template depart determine the employee names working in it. For different production units, different employee names will be automatically derived by the template.The default fields like, currency used will be automatically updated.Process of Migration The process of migration is summarized on the figure belowFigure-1 (Source Ranga Rao Davala, Nikhil Singh, 2011, A Case Study on Data Migration Strategy, The Data Administration Newsletter, Robert Seiner Publishers.)Select SourceDue to various applications running on UNIX server, the data will be spread across many sources like different DBs, e xcel files or spreadsheets. In this step, user will identify the various data sources that are to be migrated. The selection of sources will be based upon the requirements in the project, according to which what data needs to be migrated can be identified.Data Fields MappingThis is an essential step, where the schema or key fields from source system are mapped to target system. The field names in target schemas should be kept similar to source schema for easy mapping. This step is usually done manually for error-free mapping. Usually the different database servers will have different underlying data types. For example, Integers maximum and minimum limit in UNIX server is different from in SQL Server. The mapped data, therefore, should be transformed according to end server data types.Data TransformationThis is where the template we created will come in picture. User will manually enter the key field values in the template and based on that all the derived and default field values w ill be generated automatically. Moreover, in this step, the user will transform the data based on the difference between data types of both servers.Validations and ConstraintsThis step is to ensure that the data entered in the template is accurate. The template will gray out the field which are entered wrong or doesnt qualify the constraints, such as mandatory fields, null values etc. This step will help in minimizing errors and improving the quality of data.Extract FilesOnce the data is entered into the template, the master data objects are extracted or generated.Load filesThe load files are in textual matter format, and they can be generated in single click by macro-enabled extract files system. This step ensures that data present in the text file is in scarcely the same format as we require in the Microsoft system.Loading data in Microsoft ServerThe data is loaded in batches. Since there are nonuple applications running on UNIX system that are to be migrated, this step may tak e several hours to complete.Web server migration (FTP or HTTP Websites)Once we have faultless the initial steps of creating a template and selecting the proper migration tools, we can begin full migration from UNIX to Microsoft server i.e. IIS. We must follow following stepsAssessment of ironware requirements and acquiring late hardware if required.We can begin migrating FTP or HTTP websites by copying their content to destination server.Next step is to replicate Web application files to destination.Migration of log files.Migration of Web server configuration settings.The last step is to create security settings and user permission and roles.DHCP/DNS MigrationThe process of migrating UNIX server DHCP/DNS services to Microsoft Windows Server DHCP/DNS servers requires the following stepsInstall Microsoft Windows Server DHCP/DNS Services ManuallyConfigure Microsoft Windows Server DHCP/DNS ServicesCreate Forward and Reverse Lookup Zones Creating lookup zones will gift sure that Micr osoft server is authoritative for the DHCP/DNS names for local resources and forwards other queries to an ISP or performs recursive resolutions.Add secondary zones to Microsoft Windows Server DHCP/DNS for the existing zones that are hosted on UNIX based DHCP/DNS servers.In this step well initiate zone transfers at the Microsoft Windows Server-based DHCP/DNS servers to transfer the zones from the UNIX servers.After the transfers are successful we will convert secondary zones into basal zones.In the last step, well point client configurations to Microsoft Windows based DHCP/DNS Servers.Avoiding downtime while migratingWe can avoid the downtime while migration by reconfiguring our sites to connect to our new database remotely. Using this way, our users or visitors will be redirected to new site and all the updates will be saved to new server. This technique is, though, very complex, but it will minimize the downtime to a nifty extent. We can summarise this process in following stepsT ransfer the files, DBs and important settings to the new server.Then we can test our site on the new server to check if its working as expected.After two steps are successfully completed, we will change the various database settings on our site, to make sure that the old server accesses the DB from the new server.Then well modify the name servers and DNS and point them to the new server.