This is an old revision of the document!
Article ID: 8055
Product Version: CloudBacko Go 8.5 or above
Operating System: All platforms
This document contains information on factors that can affect the speed of a backup job.
Factors that can affect the speed of a backup job:
Check on the hardware specification of the client computers (RAM available, processor speed), are the resource sufficient for the backup operation.
Check if the CPU usage is high during the backup.
If the CPU usage is constantly maxed out during the backup, it may suggests that the CPU power of the machine is insufficient for the backup operation.
How many files are selected as the backup source?
Check if the backup source contain a large number of files within a small number of directories.
If the backup source contain a large number of files (e.g. over a million files), you may consider splitting up the backup set into multiple backup sets with a smaller number of files.
Also, alter the amount of memory available to CloudBacko Go.
Check if the backup source is located locally, or over a network.
If the backup source of the backup job is set over a network, the backup speed may be affected depending on the network traffic and speed.
Check if the temporary directory specified for the backup set is located locally, or over a network.
If the temporary directory is specified on a network partition, the backup speed may be affected depending on the network traffic and speed.
Check on encryption key length configured for the backup set in concern.
Backup data can be encrypted with key length of 256-bit, which may slow down the backup operation for machines with insufficient resource.
Also, check on the compression setting for the backup set in concern.
Backup data can be compressed in Normal or Fast compression type. Consider changing the compression type of the backup set to 'Fast' or 'No Compression' if backup speed is a greater concern than quota usage:
How many delta files are being generated, and their size?
The speed of a backup job can be affected if the number to delta files to be generated is large, or if the delta files to be generated is large.
Check on the backup destination backup mode of the backup set:
Click Here for more details on different between these two backup destination backup modes.
Backup job in sequential mode is slower (in comparison to concurrent mode), but will take less resources (e.g. memory, CPU, bandwidth … etc.) of the client computer to complete.
Check on the cloud storage providers setup as backup destination.
CloudBacko Go supports backup to all major cloud storage providers such as Amazon S3, Microsoft Azure, Google Cloud Storage, Dropbox, OneDrive, OneDrive For Business, Rackspace, FTP/SFTP server, AWS Compatible Cloud Storage and OpenStack Compatible Storage.
It is important when choosing a cloud storage provider to consider if they have data centers near your physical location and the storage plan you choose should offer the highest availability and lowest latency in order to provide optimal backup/restore performance.
Check on the Java heap size setting, modify the setting if the currently allocated size is insufficient for the backup operation.
Check on the speed of the connection between CloudBacko Go and the backup destination.
Check if the backup job is being performed over a Local Area Network (LAN) or a Wide Area Network (WAN) environment. Ensure that the bandwidth available is suitable for the amount of data you intend to transfer. It is recommended to use a dedicated Internet connection to ensure optimal backup performance.
As an example, if you need to backup 100 GB of data to a cloud storage with high availability and low latency plan, with no hardware performance bottlenecks:
Use an online file transfer calculator to estimate on the backup time and if the bandwidth available is sufficient.
Finally, if access to Internet is via a proxy server, check for any restrictions on bandwidth on the proxy server.
backup, speed, performance