For VMware details, refer to VMware Support.
The maximum number of users for a single node cluster is 50,000. .. _multinode_cluster_hardware_specification: Multinode Cluster Hardware Specification '''''''''''''''''''''''''''''''''''''''''''' .. index:: voss;voss db_collection_cap Virtual machine requirements are specified in the table below. .. tabularcolumns:: |p{1.5cm}|p{1.5cm}|p{2cm}|p{3cm}|p{2.5cm}|p{3.5cm}|p{1.5cm}| +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | Node type | Quantity | VM | Memory | CPU | Disk | Network | +===========+==========+===============+==============================+=====================+================================+==================+ | | | | | | | | | Unified | 4 or 6 | >= VMware 5.1 | 16 GB with 16 GB reservation | 4 vCPU @ 2 GHz | 370 GB partitioned: | 1 Gbit/s minimum | | | | | | with 4000 MHz | | | | | | | | reservation | * 20 GB for OS | | | | | | | | * 50 GB for application: | | | | | | | | 10 GB for logs, | | | | | | | | 40GB for our apps | | | | | | | | * 50 GB for compressed backups | | | | | | | | * 250 GB for database | | | | | | | | | | +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | | | | | | | | | WebProxy | 2 | >= VMware 5.1 | 4 GB with 4 GB reservation | 2 vCPU @ 2 GHz | 70 GB partitioned: | 1 Gbit/s minimum | | | | | | with no reservation | | | | | | | | | * 20 GB for OS | | | | | | | | * 50 GB for application | | | | | | | | | | +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ For Memory and CPU, the Resource Allocation Reservation on VMware is indicated in the table. Hyper-threading is supported. .. note:: If memory allocations are customized, ensure that the memory reservation remains equal to the allocated memory in order to prevent possible negative side-effects due to memory reclamation. The OS disk requirement is fixed and logs are rotated to ensure that 10 GB is sufficient. 40 GB for applications is a generous allocation and does not scale with the number of users. The Database storage partition is sized to support 250 K users. Database backups are compressed and the partition is sized to ensure that sufficient space available to support backup of 250 GB database. .. note:: To change the TRANSACTION_LOG cap size to greater than 10GB at larger providers for operational reasons, for example for diagnostics and a longer transaction replay window, the **voss db_collection_cap TRANSACTION_LOG <10-50GB>** command can be used from the command line. .. raw:: htmlRefer to Database Commands for more details.
.. raw:: latex Refer to Database Commands in the Platform Guide for more details. The resize operation will impact the usage on the disk size allocated for the database (typically, 250GB is reserved upon installation). Consider a larger database disk size allocation upon installation if a larger cap size is set. The backup disk should be Thick Provisioned and Eager Zeroed for better performance immediately after installation. Web Proxies are optional, but if Web Proxies are used, then they form part of the cluster to allow sharing of static data and other content as needed (for example, themes). To set up the disk requirements, the disk should be set up on the VMware GUI Resources tab where a disk can be created. This task should be done after the OVA import but prior to the boot of the system. .. raw:: latex For VMware details, refer to the VMware Support topic in the Compatibility Matrix. .. raw:: htmlFor VMware details, refer to VMware Support.
.. _two_node_cluster_hardware_spec: 2 Node Cluster Hardware Specification ''''''''''''''''''''''''''''''''''''''' .. _19.1.1|VOSS-475: Virtual machine requirements are specified in the table below. .. tabularcolumns:: |p{1.5cm}|p{1.5cm}|p{2cm}|p{3cm}|p{2.5cm}|p{3.5cm}|p{1.5cm}| +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | Node type | Quantity | VM | Memory | CPU | Disk | Network | +===========+==========+===============+==============================+=====================+================================+==================+ | | | | | | | | | Unified | = 2 | >= VMware 5.1 | 16 GB with 32 GB reservation | 4 vCPU @ 2 GHz | 370 GB partitioned: | 1 Gbit/s minimum | | | | | | with 4000 MHz | | | | | | | | reservation | * 20 GB for OS | | | | | | | | * 50 GB for application: | | | | | | | | 10 GB for logs, | | | | | | | | 40GB for our apps | | | | | | | | * 50 GB for compressed backups | | | | | | | | * 250 GB for database | | | | | | | | | | +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | | | | | | | | | WebProxy | >= 0 | >= VMware 5.1 | 4 GB with 4 GB reservation | 2 vCPU @ 2 GHz | 70 GB partitioned: | 1 Gbit/s minimum | | | | | | with no reservation | | | | | | | | | * 20 GB for OS | | | | | | | | * 50 GB for application | | | | | | | | | | +-----------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ For Memory and CPU, the Resource Allocation Reservation on VMware should correspond with these requirements. .. note:: If memory allocations are customized, ensure that the memory reservation remains equal to the allocated memory in order to prevent possible negative side-effects due to memory reclamation. .. raw:: latex For VMware details, refer to the VMware Support topic in the Compatibility Matrix. .. raw:: htmlFor VMware details, refer to VMware Support.
Modular Cluster Hardware Specifications ............................................ .. _multinode-modular-cluster-hardware-specification: Multinode Modular Cluster Hardware Specification ''''''''''''''''''''''''''''''''''''''''''''''''''' Virtual machine requirements are specified in the table below. .. tabularcolumns:: |p{1.5cm}|p{1.5cm}|p{2cm}|p{3cm}|p{2.5cm}|p{3.5cm}|p{1.5cm}| +-------------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | Node type | Quantity | VM | Memory | CPU | Disk | Network | +=============+==========+===============+==============================+=====================+================================+==================+ | | | | | | | | | Application | 3 | >= VMware 5.1 | 16 GB with 16 GB reservation | 4 vCPU @ 2 GHz | 80 GB partitioned: | 1 Gbit/s minimum | | | | | | with 4000 MHz | | | | | | | | reservation | * 20 GB for OS | | | | | | | | * 50 GB for application: | | | | | | | | 10 GB for logs, | | | | | | | | 40GB for our apps | | | | | | | | | | +-------------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | | | | | | | | | Database | 3 | >= VMware 5.1 | 32 GB with 32 GB reservation | 4 vCPU @ 2 GHz | 380 GB partitioned: | 1 Gbit/s minimum | | | | | | with 4000 MHz | | | | | | | | reservation | * 20 GB for OS | | | | | | | | * 50 GB for compressed backups | | | | | | | | * 50 GB for application: | | | | | | | | | | | | | | | | * 10 GB for logs | | | | | | | | * 40GB for our apps | | | | | | | | * 250 GB for database | | +-------------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ | | | | | | | | | WebProxy | 2 | >= VMware 5.1 | 4 GB with 4 GB reservation | 2 vCPU @ 2 GHz | 70 GB partitioned: | 1 Gbit/s minimum | | | | | | with no reservation | | | | | | | | | * 20 GB for OS | | | | | | | | * 50 GB for application | | | | | | | | | | +-------------+----------+---------------+------------------------------+---------------------+--------------------------------+------------------+ For Memory and CPU, the Resource Allocation Reservation on VMware is indicated in the table. Hyper-threading is supported. .. note:: If memory allocations are customized, ensure that the memory reservation remains equal to the allocated memory in order to prevent possible negative side-effects due to memory reclamation. The OS disk requirement is fixed and logs are rotated to ensure that 10 GB is sufficient. 40 GB for an applications role node is a generous allocation and the size will not have to be increased with the number of users. The Database storage partition is sized to support 250 K users. Database backups are compressed and the partition is sized to ensure that sufficient space is available to support backup of 250 GB database. .. note:: To change the TRANSACTION_LOG cap size to greater than 10GB at larger providers for operational reasons, for example for diagnostics, the **voss db_collection_cap TRANSACTION_LOG <10-50GB>** command can be used from the command line. .. raw:: htmlRefer to Database Commands for more details.
.. raw:: latex Refer to Database Commands in the Platform Guide for more details. The resize operation will impact the usage on the size of the disk allocated for the database (typically, 250GB is reserved upon installation). Consider a larger database disk size allocation upon installation if a larger cap size is set. The backup disk should be Thick Provisioned and Eager Zeroed for better performance immediately after installation. Web Proxies are optional, but if Web Proxies are used, then they form part of the cluster to allow sharing of static data and other content as needed (for example, themes). To set up the disk requirements, the disk should be set up on the VMware GUI Resources tab where a disk can be created. This task should be done after the OVA import but prior to the boot of the system. .. raw:: latex For VMware details, refer to the VMware Support topic in the Compatibility Matrix. .. raw:: htmlFor VMware details, refer to VMware Support.