Jump to content
NAKIVO Community Forum

Official Moderator

  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Official Moderator

  1. Hi, @Manuel Rivera!

    I see that you've done quite a research by yourself. However, just NAKIVO software has no speed limitation for the backup|replication|recovery action that can be set in the license. Please keep your attention that the NAKIVO Job speed depends on the speed of the source data read action, the speed of the data transfer, and the speed of the data write action. All those stages are affected by the NAKIVO Job workflow.

    Also, remember that NAKIVO Backup & Replication uses the routing table from the system where it is hosted to transfer the data.

    You may try using the instruction from this article to identify the bottleneck of the backup infrastructure:


  2. Hi, @mcwild!

    For the current version of NAKIVO, we don't support DSM v7 yet.

    In DSM version 7.0, Synology changed the installation policy, and now it requires additional signs for each application. In other words, unsigned for DSM 7.0 applications can not be installed on it. Now the NAKIVO application is in the final approval stage by Synology. The ETA for the approval totally depends on the Synology side.

    As soon as the NAKIVO app will be signed and approved by Synology, NAKIVO installation on DSM 7.0 will be possible. As a temporary workaround, you can make-instance reconfiguration to use the existing repository on the NAS as CIFS or NFS shares. This instance can be temporarily reconfigured to run on other supported platforms.

    Let me know if you need any further assistance. 

  3. Hi, @justzikle!

    NAKIVO Backup & Replication offers backup, replication, failover, backup to the cloud, backup to tape, backup copy, backup data reduction, instant verification, granular restore, and disaster recovery orchestration for virtual, physical, cloud, and SaaS environments - all in one convenient web interface.

    You can backup data and afterward export backups to standard formats that are compatible with various platforms. You can check more details here https://helpcenter.nakivo.com/User-Guide/Content/Recovery/Full-Recovery/Performing-Cross-Platform-Recovery/Performing-Cross-Platform-Recovery.htm

    You can check the Free Edition (https://www.nakivo.com/resources/download/free-edition/) or the Free Trial (https://www.nakivo.com/resources/download/trial-download/) of NAKIVO Backup & Replication if you are looking for a free solution.

    Answering your other question, you don't need to shut down the applications before taking backup.

    Let me know if you have any additional questions.


  4. Hi, @gianni!

    It looks like you are trying to use individual file recovery action for the "domain controller 2019" VM. In case that some folders have special permissions, they are not shown in the listing. Could you please use the "Universal object recovery" wizard to check this?

    For the "exchange server 2019" recovery action, please deselect the "Automatically locate application databases" option to be able to select the required DB manually:


    Let me know if it works for you.

  5. Yes, it is. Currently, NAKIVO already has deployed the transporter in the physical with Hyper-V Server role you can check in the Inventory. Accordingly, you can not deploy one more transporter in the same physical with the Physical Server role again. In this case, we suggest keeping the current status to backup VMs from the Hyper-V Server role better than you back up the Physical Server. 


    Since NAKIVO doesn't support the features below:

    1. Recovery from Physical to Physical.

    2. Recovery from Physical to Hyper-V 


    On the other hand, NAKIVO is planned for:

    1. Backup and Recovery from Physical to VMWare 

    2. Backup and Recovery from Hyper-V to Hyper-V 


    Please let me know if you have any further questions.

  6. Hi, @Gavino!

    In a new release, we have updated the UI for the Repository screen. The repository type menu was removed. "Store backups in separate files" option was added (enabled by default). Backup repositories created in the previous versions of the product keep operating in the same way they were configured.

    Storing backups in separate files is recommended. Downside: it has higher space requirements, no built-in deduplication. Upsides: it is more resilient to network, power, and hardware failures; it does not require running space reclaim; it is suitable for enterprise-grade deduplication storage devices; it supports immutable recovery points.

    If you still want to use the "forever incremental" repository and built-in data deduplication, please uncheck the "Store backups in separate files" checkbox when creating the backup repository.

    Please let me know if you have further questions or concerns.

    • Like 1
  7. @Hallm,

    I'm afraid this question is too specific for the forum. Please send us a support bundle so that our Support Team can perform a detailed investigation. If needed, our support specialist will also involve the Development department.

    Check how to send the support bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles

    Let me know if I can assist you with anything else.


  8. @Jason,

    This request was already escalated to the Product Team. If you want to get a personal response, please provide the following information:

    - Name
    - Contact Name
    - Email
    - Type (Install-base, reseller, prospect, etc.)
    - Value (Deal amount, $)

    You can send it to me via personal messages or email directly to support@nakivo.com 

    If I can help you with anything else, please let me know.

  • Create New...