Hi,
Regarding the High Availability (HA) of Nintex Reporting components, your allocations of the services would meet the needs of a HA environment for Nintex Reporting.
Please note that in version 1.2 of Nintex Reporting we introduced support for load balancing the Data Management Service (DMS), this would allow you to have two DMS services installed and running concurrently. This has the added advantage of zero downtime when one of the DMS servers are taken offline. We currently recommend that a maximum of two DMS’s are installed per Nintex Reporting farm, we have previously worked with another large customer with a similar SharePoint environment size and have found that two DMS’s more than adequately handles the process load for the farm.
Regarding the Active Directory Collector (ADC) and User Profile Collector (UPC), both of these services do not support load balancing. Our recommendation for both of these services for HA is to have a predefined/identified standby server that can be used to install a new instance of the service in case of a outage. However, because both of these services are lightweight and are only actively operating for a small period during the day you could elect to use anyone of your existing servers in the farm (including web frontend server) as a standby server for these services.
The ADC and UPC are what we call profile services, they both perform the same job role and as such we do not support the installation of both of the services concurrently in the one Nintex Reporting farm. The only difference between the ADC and UPC is where they collect their respective profile information from. As you expect the ADC collects its information from a Active Directory source, and supports multiple import sources which can be configured via the configuration screen in Central Administration.
The UPC requires the MOSS User Profile Database (UPD) to be installed and the Share Services Provider (SSP) to be running in the SharePoint farm. The UPC leverages the advanced import and merging scenarios supported by MOSS. When using the UPC you can take full advantage of your current MOSS UPD investments and have the same profile data automatically imported into Nintex Reporting. By using the UPC you are able to leverage the MOSS UPD ability to import from Active Directory (LDAP) and the Business Data Catalog and maintain one source of import settings that is shared between MOSS and Nintex Reporting.
We recommend that you use the UPC if you have an investment already in MOSS’s UPD. One reason to not use the MOSS UPD is if you require profile information for accounts not currently in your MOSS UPD and the corporate policy does not allow you to update the scope of accounts being imported into the MOSS UPD, this however is a very uncommon restriction.