Disk I/O is extremely important. By default, Syncrify uses the rsync algorithm, which minimizes the network I/O but at the cost of disk I/O. Therefore, avoid the following when using Syncrify:

• Network drives on Syncrify Server: Mapped, iSCSI and other type of network storage should be avoided when using Syncrify. These technologies introduce another network layer in between the CPU and storage and therefore, tremendously reduces the scalability.
• Network drives on Syncrify Client: Just as the server, you should not synchronize/backup mapped drives. Instead, install Syncrify Client on the machine where the data resides. This will bring the disk closer to the CPU.

Often administrators put a reverse proxy server in front of Syncrify, which adds several disadvantages:

• This tremendously reduces the scalability. Every packet sent from Syncrify Client gets inspected by the proxy server before relaying it to the server.
• You run into network timed-out errors when the proxy server cannot handle the traffic load. Syncrify client opens thousands of HTTP connections in a typical backup session. Moreover, multiple threads open connections simultaneously, exerting additional load.
  
  Syncrify Client will log errors like 503 Gateway Timeout when this happens.

It is important to configure the anti-virus software on both Syncrify Client and Server exclude Packet Level Inspection on the TCP/IP port used for backup. Refer to Effects of Anti-virus Software In Syncrify for details.

Consider enabling SSL in Syncrify Server before connecting from a client.

Syncrify sends reports and alerts via emails. Some of these alerts are very important and needs to be addressed right away. For example if Syncrify detects low disk space, an alert will be sent to the administrator via email.

Therefore, it is very important the SMTP settings are correctly specified and someone looks at the messages generated from your Syncrify server.