Imorgon 2.0 Upgrade Information

Upgrade Server Specifications


Server Hardware


Please note that ALL Imorgon 1.0 production sites presently own 64-bit compatible servers that meet the requirements. There is no real need to upgrade the hardware at all and all the disks and storage will be used exactly as they are.
  • 64-Bit Compliant Server with a minimum of 8 GB RAM capacity, 16 GB capacity recommended.
  • A minimum of a RAID-1 configured 160 GB (i.e. 160 GB x 2 Drives) Base OS Local Disk Partition
  • Additional RAID-5 or better redundant storage disks, iSCSI or equivalent attached SAN storage. All Imorgon 1.0 configuration will be fine.
  • A minimum of 8-GB RAM
  • Note if you are using a Fibre-Channel SAN or having a SAN Host-Bus Adapter please check with your vendor to make sure that there is a Windows 2008 Server 64-bit compatibility support in terms of the driver.

System Software Requirements

  • Microsoft Windows Server 2008 Standard Edition R2, 64-Bit Edition
    • Note, the Standard Edition is sufficient, however higher grade OS such as Enterprise and Data Center editions are also acceptable.
  • Necessary Windows Client Access Licence (CAL) two for servers plus per workstation installed. For example if you own 8 workstations, you will need a total of 10 CALs be complaint.
  • Microsoft SQL Server 2008 Standard Edition, 64-Bit Version
    • The standard edition is sufficient.
  • Necessary SQL Server Client Access Licence (CAL) two per server plus per workstation installed. For example if you own 8 workstations, you will need a total of 10 CALs be complaint.

What Existing Customer Sites Really Need To Do

  • Acquire the Windows 2008 Standard R2 64-bit and SQL 2008 64-bit as described.
  • You already have 4 GB RAM in the servers, you will need to buy 4 GB more memory for each server. Or buy 2 x 4 GB memory. Note that there are many different kinds of DDR memories that cannot be mixed and matched. Please check what's already in the system before making additional purchases.
  • Before installing the new OS, install the memory one server (from the secondary) at a time make sure it works.
  • When the server is upgraded, your 1.x workstation should continue to operate therefore we will upgrade the workstation after the servers go into a full production. Workstations can be upgraded at your own pace.


Rolling 2.0 Upgrade Process Overview


Yes, this is a rolling upgrade so this should minimize your downtime, if we follow the steps outlined in the spreadsheet below.

For more detailed information, please see THIS SPREADSHEET (CLICK).

Overall Information

 Phase TimingProduction Downtime Work Description
 Prep1 ore more days priorless than a minuteUpload the product installation material to the servers and prepare workstation installer download area (Imorgon).

Add the memory to each server and make sure that the hardware has taken the memory.

Designate a test workstation, and ready it to install new version (Customer and Imorgon).

Fail-over the server and make sure all the workstations can access the server without a problem. If there is a problem correct the workstation configurations before committing the upgrade.

Fail-back to normal production.

Update SecondaryDay of updateless than a minuteInstall the Windows 2008 OS, Install the SQL Server 2008 in 64-bit environment.

Install and pre-configure the 2.0 software.

Roll back the current database.

Lauch all services.
Manually assign the cluster IP.

Fail-over the server to the Secondary server.

Push any studies that were off synch with the secondary from the primary.

Upgrade the test workstation, point it to the secondary server. Check with the customer for functionality.
Go/NoGo  We will leave the system running in production with the new server for a day or so to make sure there is no unexpected.
=== GO/NO-GO DECISION ===
If everything is fine then we can move on to next step, otherwise rollback.
Update Primary less than a minuteInstall the Windows 2008 OS, Install the SQL Server 2008 in 64-bit environment.

Install and pre-configure the 2.0 software.

Mirror the database.

Lauch all services.
Re-Enable automatic IP clustering.

Fail-back the Principal to the Primary.

    


Comments