Page tree
Skip to end of metadata
Go to start of metadata

Product Version: 8.5
Last Modified: 15 February 2019

Problem

Slowness with NAKIVO Backup & Replication jobs

Solution

If you experience slowness with NAKIVO Backup & Replication jobs, you can localize the problem and reveal its cause by taking the following steps:

  1. Identify the route that your data takes to get transferred from the source to the destination. Define the source Transporter, the target Transporter, and any other intermediate components such as source disk, target disk, LAN or WAN.
  2. Install a profiler which is a special component developed by NAKIVO for the Transporters involved in the data transfer route. You can download the profiler by following one of the links below: 
    For Transporters installed on Linuxhttps://d96i82q710b04.cloudfront.net/res/product/Profile/Ubuntu/bh
    For Transporters installed on Microsoft Windows: https://d96i82q710b04.cloudfront.net/res/product/Profile/Windows/bh.exe
    For Transporters installed on NAS deviceshttps://d96i82q710b04.cloudfront.net/res/product/Profile/NAS/bh
    For Transporters installed on NAS devices with an ARM v7 processorhttps://d96i82q710b04.cloudfront.net/res/product/Profile/NAS_armv7/bh
    For Transporters installed on NAS devices with an ARM v8 processorhttps://d96i82q710b04.cloudfront.net/res/product/Profile/NAS_armv8/bh

  3. Stop all Transporters involved in your data transfer route. Make sure that these Transporters are not busy with jobs, and there are no repositories attached to them. Please refer to Starting and Stopping Product Services for details.

  4. Locate the original bh file for your platform. The file default location is:

    Linux:/opt/nakivo/transporter/bh

    Windows: C:\Program Files\NAKIVO Backup & Replication\transporter\bh.exe

    Synology NAS: /volume1/@appstore/NBR/transporter/bh

    QNAP NAS:/share/CACHEDEV1_DATA/.qpkg/NBR/transporter/bh

    Note

    If you fail to locate the profiler in the default location on Linux and NAS devices, please use the following search command:

    find / -name "bh" | grep transporter
  5. Move the original bh file to a safe location, or rename it and move the previously downloaded bh file to the original location. Make sure that the file name is bh.

    Note

    If you use SAN transport mode, replace bh-san executable instead of bh.

  6. For Linux, change permissions for the new bh file by running the following commands:

    chmod +x bh

    chown bhsvc:bhsvc bh

  7. When ready, start the Transporter service for all previously stopped nodes.

  8. Run your backup or replication job. 

  9. When the job is complete, create a support bundle and send it to NAKIVO Technical Support. It will take some time to analyze your support bundle and provide you with a technical support summary. Based on the provided technical support summary, you will be able to identify and fix any bottleneck in your virtual infrastructure.

  10. Finally, you will need to revert the previously applied changes back. To do this, follow the procedure below:

    1. Stop the Transporter services.

    2. Replace the profiler bh file with the original bh file.

    3. Start the services.

  • No labels