Skip to main content

Hybrid Deployment Requirements

Mike Avon
  • Updated

Important: This article is only relevant to customers who have chosen the "Hybrid" deployment option.

NOTE: These environments must be deployed by the customer in their own datacenter.  

There are six distinct environments that need to be provisioned for the Hybrid deployment option:

  1. A Linux VM to host the Syniti Agent and associated services

    • The requirements for the Linux VM as well as well as common troubleshooting tips can be found here.

  2. A database instance to host the Migrate 'Working Databases' where customer data that is to be processed is persisted. Three database technologies are currently supported for the Working Database Environment:
    • Microsoft SQL Server 2019 or later, and SQL Managed Instance on Azure
      • 100+ GB hard drive space
      • 1600MB/s disk throughput (or 200MB/s per CPU Core)
        • Note: The disk subsystem performance on this system significantly impacts overall migration performance
      • 8 - 16 available processing cores
      • 32 - 64GB memory
    • Oracle Release 12.2 or later
      • 100+ GB hard drive space
      • 1600MB/s disk throughput (or 200MB/s per CPU Core)
        • Note: The disk subsystem performance on this system significantly impacts overall migration performance
      • 8 - 16 available processing cores
      • 32 - 64GB memory
    • SAP HANA
      • RAM = (size of uncompressed business data / compression factor) x 2

        Compression factor varies based on actual data; 2 - low, 4 - medium, 8 - high

        For example, 100GB of business data using a medium compression factor is (100 / 4) x 2 = 50GB. On SAP HANA Cloud this would require an instance of 60GB as RAM is allocated in 15GB blocks. CPU and disk sizing is determined automatically from the RAM size.

         

  3. The Replication Engine runs on Windows architecture with the following recommended hardware requirements:

    • 8 core CPU
    • 16 GB RAM
    • 150 GB hard disk space
    • 125MB/s disk throughput

    Microsoft Windows Server 2019 or later is required with .NET Framework 4.8 or higher installed.

     

  4. The Construct WebApp Database runs on Microsoft SQL server.  The recommended hardware requirements are:

    • 4 core CPU
    • 16GB RAM
    • 500GB Disk
    • 200MB/s disk throughput
    • Note: The disk subsystem performance on this system significantly impacts overall Construct performance.

    All versions of Microsoft SQL Server 2019 or later are supported.

Note: The Windows Server used to run the Replication Engine listed above can also be used to house the Construct WebApp Database. In that case we recommend the following:

    • 8 core CPU
    • 24GB RAM
    • 1TB disk
    • 300MB/s disk throughput
      • Note: The disk subsystem performance on this system significantly impacts overall Construct performance.
  1. AWS Hardware Requirements
    The following are the currently approved instances to host the SST Application and SQL Database roles.
  • Application Server: C5d.4XL, R5d.4XL, i3.4XL, R5dn.4XL
  • Database Server: R5d.4XL, i3.4XL, R5dn.4XL
  • AWS RDS

NOTE: If using AWS RDS as a hosted database backend for the Stewardship Tier:

    • The application database user account must be the same as the RDS administrator user account. This user account is set up when creating an RDS instance and is the only user that has access to database creation and other permissions that the Stewardship Tier requires to function.

    • The created RDS instance for use with the Stewardship Tier must be an instance type that supports at least 100 databases.

    • The Stewardship Tier does not support Multi-AZ Database Mirroring as AWS limits the database number for that type of deployment. This may be subject to change in the future at Amazon’s discretion. See this AWS documentation link for details: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html#SQLServer.Concepts.General.FeatureSupport.Limits

    • Users are responsible for their own security configuration to allow the needed communication between the RDS instance and their Stewardship Tier application instance.

    • The RDS instance must be set to the same timezone as the application server.

      NOTE: For the 7.4.6 version of the Stewardship Tier, the source and target for CTS and Promote must both be RDS or both be non-RDS databases.

         Disk Configuration:

  • Disk SpeedType must be GP2 or faster

  • OS Disk must be at least 250GB

  • Application Disk must be at least 500GB

  • Database Disk must be at least 1TB per Disk

    • SQL Server is required to be configured with multiple disks to support transaction log files and multiple Database data files.

NOTE: Hardware Profile Ephemeral Storage/Temporary Storage is required and will be used for TempDB, OS PageFile, and other temporary files.

  1. Azure Hardware Requirements
    The following are the currently approved instances to host the SST Application and SQL Database roles.

  • App Server: Standard_DS13_v2 3, Standard_DS14_v2 3, Standard_E32s_v3 1, Standard_F32s_v2

  • DB Server: Standard_E16s_v3 1, Standard_DS14_v2 3, Standard_L16s_v2, Standard_E32s_v3 1, Standard_L32s_v2

    Disk Configuration:

  • Disk Speed must be SSD Performance or faster. P30 Profile for Application and Data minimum. P15 Profile for OS minimum.

  • OS Disk must be at least 250GB

  • Application Disk must be at least 500GB

  • Database Disk must be at least 1TB per Disk

    • SQL Server is required to be configured with multiple disks to support transaction log files and multiple Database data files.

      NOTE: Hardware Profile Ephemeral Storage/Temporary Storage is required and will be used for TempDB, OS PageFile, and other temporary files.

Network Latency

Network Latency between the four systems (Linux virtual machine with Agents & Connectors, Migrate working database server, Windows virtual machine running Replicate, Construct WebApp database on SQL Server) should be less than 5ms.
Warning: If latency drifts to a larger number, systems will appear slower and some applications may have trouble communicating. Syniti expects all four of these systems to be connected on a local network LAN, not across WAN links or across VPN tunnels to each other.

Related articles