- Joined
- Mar 27, 2017
- Messages
- 27
- Reaction score
- 4
I recently upgraded my Google Compute hosted dev and prod 3CX systems to v16.4 and dutifully deployed an SFTP server, also up at GC. I'm perplexed by the amount of time it takes for 3CX to write the backup to the SFTP server for this roughly 3GB backup file. Here are the results of my backup tests for each destination:
3CX application backup:
Local drive: 3 minutes
Google Drive: 10 minutes
GC SFTP server: 1.5 hours
Manual copy of the backup file:
Copy the 3GB backup file from local 3CX server drive to SFTP server using native debian SFTP client: 2 minutes
I can understand the 3CX backup process taking longer to complete than a straight file copy from one server to another because it has more processing to do as it generates the zip file. But why would the SFTP backup be SO much slower than a Google Drive backup or a direct file copy?
3CX application backup:
Local drive: 3 minutes
Google Drive: 10 minutes
GC SFTP server: 1.5 hours
Manual copy of the backup file:
Copy the 3GB backup file from local 3CX server drive to SFTP server using native debian SFTP client: 2 minutes
I can understand the 3CX backup process taking longer to complete than a straight file copy from one server to another because it has more processing to do as it generates the zip file. But why would the SFTP backup be SO much slower than a Google Drive backup or a direct file copy?