For a gigabit network, the bandwidth is about 125 M/s, and the scp speed is about 40 M/s. It takes about 2 hours to restore the database in full mode (about 300 GB, this situation is unacceptable;
To speed up SCP transmission, consider the following:
1. Changes in the ssh encryption algorithm (the weaker the encryption algorithm, the faster it is, the more suitable it can be used in the IDC intranet)
2. The data integrity verification method is changed. (MACs Message authentication code)
3. Whether to enable compression;
4. Disk performance problems;
Most of the adjustable man scp speed is calculated by algorithms. (test-B batch mode has little impact on transmission)
-C cipher-o Integrity Verification
Ssh-v debug ssh connections
For test data on the above issues, refer:
Scp-c aes192-cbc can be used for encryption algorithm
Scp-o 'MACs umac-64@openssh.com' is used for data integrity verification.
It is worth mentioning that compression, as long as the compression saves more transmission time than the compression time;
Compression is often applicable to: slow network speed; a large number of duplicates and holes in data; but for data with low compression ratios, we do not recommend using SSH transmission compression; it is best to perform local parallel compression before transmission;
To speed up compression, refer to the following command:
Scp-c aes192-cbc-o "MACs umac-64@openssh.com"