Skip to main content

How Swing Migration Works for exchange server Just for Egypt Engineers

 How Swing Migration Works


Swing Migration is a process to accomplish either a version upgrade or server replacement migration without giving up the domain, or the server name, or the Exchange Information Store in the process, all while working offline with an open time line.
You get a clean server installation retains all the critical Active Directory domain information and predictable results. It's the most transparent method for bringing all versions of SBS, NT4, Win2K, or Win2003-based domains as upgrades to SBS 2003. This methodology works for non-SBS projects as well. You can learn a process flexible enough for most any project in any production environment regardless of the hardware changes involved.
Swing Migration solves technical issues, business interruption, and scheduling challenges. Construction is performed almost entirely offline, with an open-ended timeline. No repairs are needed if a problem halts the upgrade. Swing migration minimizes the preparations and changes to the production server, and that server remains in operation during the upgrade. Only during the final transition do you move the data and Exchange Stores to the fully constructed new server, which you then slide into service to replace the previous server. The domain accounts remain unchanged, you can keep the server name, and alternate paths in the process use the previous hardware. These upgrades have predictable outcomes; they are safe even for entry level technicians.
What is shown below is a diagram of the process, and further below is a simple outline of the process.

  • [TempDC] Clean install a Windows 2003 Server (using SBS media) as a workgroup server only.
  • Manually join it to the existing SBS domain, preparing this server as a Temp DC.
  • Install DNS, perform DCpromo and designate as a Global Catalog Server.
  • Replicate DNS and AD then shutdown and disconnect
  • Seize all FSMO roles
  • Purge the Active Directory metabase and DNS of all previous Domain Controllers, Exchange and DNS Server references
  • [FinalDC] Clean install Windows 2003 Server just as before, reuse the original SBS Server name and IP. This server will look just like the previous SBS for name, IP, AD, and UNC/URL paths.
  • Install DNS, perform DCpromo, designate as Global Catalog Server.
  • Replicate DNS and AD.
  • Seize all FSMO roles, purge the Temp DC from DNS and AD
  • Finish normal SBS Setup using this Server
  • Complete the balance of migration of Exchange, all Data, and shared resources
  • If desired, perform a migration of the intact Exchange Information Store as a direct mount of the previous Information Store as if it were an offline restore. Reconnect mailboxes.
  • Perform a direct substitution of the new server for the old SBS
  • Deploy Applications as normal for SBS.

Comments

Post a Comment

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more