In the first blog post of this series I have given you an overview of the InMage Scout architecture. For a short recap of what the Process Server is read the following lines.
The Process Server is used for caching, compression and encryption of the data of the Protected VM before the data is send to the secondary site. Typically the Process Server is the second component you have to install and it is placed at your primary site. You can have more than one Process Server at your primary site either for load balancing or for fault tolerance. The Process Server also includes the Push Install service for the remote deployment of the Unified Agent.
Before you start with creating the VM for your Process Server have a look at the Microsoft best practices for sizing the Process Server and the supported OS.
|Data Change Rate||CPU||Memory||Boot Volume Capacity + Cache Directory Disk Size||NICs with 1 Gbit/s|
|<= 300 GB per day||4x vCPUs||8 GB||Minimum of 400 GB||2x with static IP|
|<= 700 GB per day||8x vCPUs||16 GB||Minimum of 790 GB||2x with static IP|
|<= 1 TB per day||8x vCPUs||32 GB||Minimum of 790 GB||2x with static IP|
These values are best practices by Microsoft. You can use lower values for your VM except of the Boot Volume Capacity + Cache Directory Disk Size. But I highly recommend to use the best practices values. If you have a data change rate of more than 1 TB per day Microsoft recommends to deploy additional Process Servers. You can have multiple Process Server in your InMage Scout environment for load balancing and fault tolerance.
Windows Server 2012 R2 is the only supported OS for running the Process Server.
After you have successfully set upped the VM for your Process Server you have to install the dependencies first. The name of the setup file is InMage_CX_TP_188.8.131.52_Windows_GA_26Feb2015_release.exe.
After the dependencies has been installed successfully move on with the Process Server installation. The name of the setup file is InMage_CX_184.108.40.206_Windows_GA_26Feb2015_release.exe.
Before you move on with the installation you have to download the prerequisites or copy the downloaded prerequisites from you Configuration Server installation onto the Process Server VM. Use the links in the setup to download the exact versions of the required software packages. You can skip the MySQL download for the Process Server installation because this software packages is not needed.
Select new installation and enter the details for the notification service.
Select Process Server and on the next page https. If you had selected http during the Configuration Server installation then select http.
Specify the folders where you have saved the installation files of the required software packages.
Specify the NIC which the Process Server should use for communication with its Configuration Server and on the next page specify the IP address of the Configuration Server and the https port you have defined during the Configuration Server installation.
Last but not least you have to enter the username & password for the Push Server and define the installation folder. You can only change the drive for the installation folder but not the name itself. After clicking Next the Process Server will be installed.
The next blog post will be about the vContinuum server installation.