• Network Configuration: For all servers you wish to protect, whether virtual or physical, you will need host names and IP addresses. You will also need two addresses for each of your onQ Appliances: one for the hypervisor and the other for onQ.

• Operating System: The Operating System on your Protected Nodes must be supported. See Platform Support.

• Data Usage: During setup, onQ will check storage usage for each disk on each server you protect. By default, onQ assigns 1.5 times the amount of space currently in use. You can increase this if you anticipate higher growth in the next few years.

• Memory: onQ uses an algorithm to assign RAM based on how much is used by your server and what is available on the onQ Appliance. If you decide to change this default allocation, consider allocating the minimum memory required for each Recovery Node for adequate operation. Only exceed 2GB per node when you know that it is necessary for that node’s workload.

• Processors: onQ uses an algorithm to assign virtual CPUs based on how many CPU cores are on your server and how many are available on the onQ Appliance. Because there are multiple Recovery Nodes operating concurrently on each onQ Appliance and not all will have peak activity at the same time, more virtual CPUs can be allocated than are physically present. Allocating more virtual CPUs does not necessarily improve performance and can actually hurt performance if Recovery Nodes are reserving CPUs that they do not need.

• Microsoft VSS. Microsoft VSS must be enabled and have adequate snapshot space allocated. For more information, go to Protected Node Parameters.

• Database backups and restores. Verify that your database backup and restore scripts are performing as expected. You should not have any issues using these same scripts in an onQ environment because such operations are independent of onQ. Do not deploy onQ if you are having database backup or restore failures. Resolve these issues before you proceed with your deployment.