Virtual Standby Export Error with Hypervisor CPU Count Invalid After Upgrading to Rapid Recovery 6.3 (4044885)

After an upgrade from Rapid Recovery version 6.2.x to version 6.3, existing and new Virtual Standby export jobs fail to queue with the error:

Error
The value '4' for 'CPU count' is invalid. It must be in the range from '1' to '2'. 

Server side:
System.ArgumentException: The value '4' for 'CPU count' is invalid. It must be in the range from '1' to '2'.
   at Replay.Common.Implementation.Utilities.RangeValidator.CheckInRange[T](T value, T min, T max, String propertyDisplayName)
   at Replay.Core.Implementation.Export.Validation.ExportingCpuSettings.ExportingAgentCpuSettingsValidatorBase.Validate()
   at Replay.Core.Implementation.Export.ExportSchedulerService.ValidateVmConfiguration(AgentExportConfiguration configuration)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetVolumes(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetExportJobRequest(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.OnRecoveryPointAdded(Object sender, RecoveryPointEventArgs args)

UI side:
   at Replay.Common.Implementation.Utilities.RangeValidator.CheckInRange[T](T value, T min, T max, String propertyDisplayName)
   at Replay.Core.Implementation.Export.Validation.ExportingCpuSettings.ExportingAgentCpuSettingsValidatorBase.Validate()
   at Replay.Core.Implementation.Export.ExportSchedulerService.ValidateVmConfiguration(AgentExportConfiguration configuration)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetVolumes(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetExportJobRequest(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.OnRecoveryPointAdded(Object sender, RecoveryPointEventArgs args)

Or the jobs may fail to queue with the message:

Error
Wrong Cores per CPU parameter. The Cores per CPU count for Virtual Machine export must be a power of 2 or a power of 2 multiplied by 3 (e.g., 1, 2, 3, 4, 6, 8, 12, 16).

Server side:
System.ArgumentException: Wrong Cores per CPU parameter. The Cores per CPU count for Virtual Machine export must be a power of 2 or a power of 2 multiplied by 3 (e.g., 1, 2, 3, 4, 6, 8, 12, 16).
   at Replay.Core.Implementation.Export.Validation.ExportingCpuSettings.ExportingAgentCpuSettingsValidatorBase.Validate()
   at Replay.Core.Implementation.Export.ExportSchedulerService.ValidateVmConfiguration(AgentExportConfiguration configuration)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetVolumes(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.GetExportJobRequest(Guid agentId, AgentExportConfiguration configuration, RecoveryPointIdsCollection recoveryPointIds, Boolean keepUpdated, ExportJobPriority priority)
   at Replay.Core.Implementation.Export.ExportSchedulerService.OnRecoveryPointAdded(Object sender, RecoveryPointEventArgs args)

A validation process has been added to Rapid Recovery to ensure that the processor count on virtual exports do not exceed the total processor count on the hypervisor host receiving the export. For instance if the export job has been set to have 2 processors and 4 cores and the hypervisor host only has 1 processor with 4 cores, the job will fail because processor count on the export is greater than the number of processors available in the host.

In previous versions of Rapid Recovery exports were allowed to create virtual machines with processor counts that exceeded the total number of processors available on the hypervisor host. Re-configuration is necessary for all new and existing jobs that have processor counts that exceed the maximum number of processors available on the hypervisor host or this export failure occurs. The purpose of the validation is to ensure the exported VM has a valid processor count and can boot up after completion.

1. Verify the number of sockets and cores on the hypervisor host you are exporting to (this can be found in Task Manager on the Hyper-V host and in the ESXi management console in VMware)
2. Set the export job to export the same or fewer processors and the same or fewer cores than the hypervisor host has.

For existing virtual standby jobs:

1. Open the core console and go to the virtual standby page
2. Click the actions button next to the configured virtual standby and "edit" the configuration
3. Set the job to have the correct number of processors and cores and save the configuration
4. Force an export of the machine to ensure that the job will run without failing