public:5038_faq:factors_affecting_backup_performance_on_ahsayobm_or_ahsayacb_version_7
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
public:5038_faq:factors_affecting_backup_performance_on_ahsayobm_or_ahsayacb_version_7 [2019/04/30 11:36] edward.chan |
public:5038_faq:factors_affecting_backup_performance_on_ahsayobm_or_ahsayacb_version_7 [2020/04/29 11:57] (current) ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== FAQ: Factors affecting backup performance on AhsayOBM or AhsayACB version 7? ===== | ||
| - | This article only applies to Ahsay software version 7 | ||
| <html> | <html> | ||
| - | <br> | + | <script type="text/javascript"> |
| - | <br> | + | window.location.replace("https://wiki.ahsay.com/doku.php?id=public:faq:v7:5038_factors_affecting_backup_performance_on_ahsayobm_or_ahsayacb_version_7"); |
| - | <b> | + | </script> |
| - | Article ID:</b> 5038 | + | |
| - | <br/> | + | |
| - | <b> | + | |
| - | Reviewed: | + | |
| - | </b> | + | |
| - | 08/09/2015 | + | |
| - | <br/> | + | |
| - | <br/> | + | |
| - | <b> | + | |
| - | Product Version: | + | |
| - | </b> | + | |
| - | <br/> | + | |
| - | AhsayACB / AhsayOBM: 7.3 or above | + | |
| - | <br/> | + | |
| - | OS: All platforms | + | |
| </html> | </html> | ||
| - | |||
| - | |||
| - | |||
| - | ===== Description ===== | ||
| - | <html> | ||
| - | This document contains the information on factors that can affect speed of a backup job. | ||
| - | </html> | ||
| - | |||
| - | |||
| - | |||
| - | ===== Overview ===== | ||
| - | <html> | ||
| - | </b> | ||
| - | Factors that can affect the speed of a backup job: | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Hardware specification | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the hardware specification of the client computers and backup server (RAM available, processor speed), are the resource sufficient for the backup operation. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Check if the CPU usage is high during the backup. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | For computer running on Windows, you can view the CPU usage with the Windows Task Manager. | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | For computer running on Linux / Mac OS X, you can view the CPU usage with the command: | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <table border="0" cellpadding="0" cellspacing="1" width="500"> | ||
| - | <td bgcolor="#000000" valign="top"> | ||
| - | <font color=#FFFFFF> | ||
| - | >top | ||
| - | </font> | ||
| - | </td> | ||
| - | </table> | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | |||
| - | 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 | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Backup source data size (number of files and size of files) | ||
| - | </b> | ||
| - | <br/> | ||
| - | How many files are selected as the backup source? | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Check if the backup source contain a large number of files within a small number of directories. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Also, alter the amount of memory available to AhsayOBM. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Location of the backup source (local / network drive) | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check if the backup source is located locally, or over a network. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Location of the temporary directory (local / network drive) | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check if the temporary directory specified for the backup set is located locally, or over a network. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | If the temporary directory is specified on a network partition, the backup speed may be affected depending on the network traffic and speed. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Encryption and compression setting | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on encryption key length configured for the backup set in concern. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Backup data can be encrypted with key length of 256-bit, which may slow down the backup operation for machines with insufficient resource. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Also, check on the compression setting for the backup set in concern. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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: | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <img style="width:60%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5038_0.png"/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | I/O utilization and location of the user home volumes (only applies to backup set with backup destination to CBS) | ||
| - | </b> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | For AhsayCBS with 'local' user home (e.g. locally attached disk): | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | Check on the local disk I/O utilization of the User Home volume. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | For computer running on Windows, you can view the I/O utilization with the Performance Monitor (perfmon.msc). | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | For computer running on Linux / Mac OS X, you can view the I/O utilization with the command: | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <table border="0" cellpadding="0" cellspacing="1" width="500"> | ||
| - | <td bgcolor="#000000" valign="top"> | ||
| - | <font color=#FFFFFF> | ||
| - | >iostat 1 | ||
| - | </font> | ||
| - | </td> | ||
| - | </table> | ||
| - | or | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <table border="0" cellpadding="0" cellspacing="1" width="500"> | ||
| - | <td bgcolor="#000000" valign="top"> | ||
| - | <font color=#FFFFFF> | ||
| - | >vmstat 1 | ||
| - | </font> | ||
| - | </td> | ||
| - | </table> | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | If the I/O utilization of the disk in concern is high during the backup, consider performing the backup job a an alternate time. | ||
| - | <span> | ||
| - | </span> | ||
| - | Also, consider to add additional user home volumes, and then spreading the backup accounts onto the user home volumes evenly. | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | For AhsayCBS with remote user home (e.g. network shared path): | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | Check on the I/O utilization of the Network Attached Storage (NAS) or Storage Area Network (SAN). | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Number of delta to be generated | ||
| - | </b> | ||
| - | <br/> | ||
| - | How many delta files are being generated, and their size? | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Sequential or Concurrent backup mode | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the <a href="http://wiki.ahsay.com/doku.php?id=public:5026_faq_on_backup_destination">backup destination</a> backup mode of the backup set: | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <img style="width:60%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5038_1.png"/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | Sequential Mode | ||
| - | <br/> | ||
| - | The backup job will upload the backup data to the selected backup destination one by one (e.g. sequentially). | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Data will be first uploaded to the first backup destination in the list (list in the destination setting of the backup set), and once that is completed, data will be uploaded to the next backup destination. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | Concurrent Mode | ||
| - | <br/> | ||
| - | The backup job will upload the backup data to the selected backup destination at the same time (e.g. concurrently). | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | <a href="http://wiki.ahsay.com/doku.php?id=public:5026_faq_on_backup_destination#What%20is%20the%20different%20between%20backup%20mode%20'Sequential'%20and%20'Concurrent'?"> | ||
| - | Click Here | ||
| - | </a> | ||
| - | or more details on different between these two backup destination backup modes. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Note: | ||
| - | <br/> | ||
| - | 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. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Cloud storage provider | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the cloud storage providers setup as | ||
| - | <a href="http://wiki.ahsay.com/doku.php?id=public:5026_faq_on_backup_destination">backup destination</a>. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | AhsayCBS supports backup to all major cloud storage providers such as Amazon S3, Microsoft Azure, Google Cloud Storage, Dropbox, OneDrive, OnDrive For Business, Rackspace, FTP/SFTP server, AWS Compatible Cloud Storage and OpenStack Compatible Storage. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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 | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Cloud storage region setting | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the region setting of the cloud storage selected if applicable. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | For example, if wish to backup your data to Amazon S3 and the backup client computer is located in a Europe. | ||
| - | <span> | ||
| - | </span> | ||
| - | The 'Location' setting of the corresponding <a href="http://wiki.ahsay.com/doku.php?id=public:5026_faq_on_backup_destination">backup destination</a> must be set to a location nearest (e.g. EU (Ireland): | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <img style="width:60%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5038_2.png"/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Amount of memory (Java heap size) available | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the Java heap size setting, modify the setting if the currently allocated size is insufficient for the backup operation. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <a href="http://wiki.ahsay.com/doku.php?id=public:5003_faq:how_do_i_modify_the_java_heap_size_setting_of_ahsayobm_or_ahsayacb">FAQ: How do I modify the Java heap size setting of AhsayOBM or AhsayACB?</a> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | <b> | ||
| - | Internet connection speed | ||
| - | </b> | ||
| - | <br/> | ||
| - | Check on the speed of the connection between the AhsayOBM / AhsayACB client and the | ||
| - | <a href="http://wiki.ahsay.com/doku.php?id=public:5026_faq_on_backup_destination">backup destination</a>. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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 dedicate Internet connection to ensure optimal backup performance. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | 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: | ||
| - | <br/> | ||
| - | <br/> | ||
| - | <ul> | ||
| - | <li><font color=black> | ||
| - | Using a 10 Megabytes/s (MB/s) upstream with 50% overhead, the initial backup job will take 4 Hours, 16 Minutes to complete. | ||
| - | <br/> | ||
| - | </font> | ||
| - | </li> | ||
| - | <li><font color=black> | ||
| - | Using a 10 Mbit/s (mbps) upstream with 50% overhead, the initial backup job will take 34 Hours, 08 Minutes to complete. | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | Use an <a href="http://techinternets.com/copy_calc?do">online file transfer calculator</a> to estimate on the backup time and if the bandwidth available is sufficient. | ||
| - | <br/> | ||
| - | <br/> | ||
| - | Finally, if access to Internet is via a proxy server, check for any restrictions on bandwidth on the proxy server. | ||
| - | </font> | ||
| - | </li> | ||
| - | </ul> | ||
| - | <br/> | ||
| - | </html> | ||
| - | |||
| - | |||
| - | |||
| - | ===== Keywords ===== | ||
| - | obc, obs, backup, speed, performance | ||
| - | |||
public/5038_faq/factors_affecting_backup_performance_on_ahsayobm_or_ahsayacb_version_7.1556595391.txt.gz · Last modified: 2019/04/30 11:36 by edward.chan