Jump to content
NAKIVO Community Forum

Official Moderator

Moderators
 View Profile  See their activity

  • Posts

    861

  • Joined

  • Last visited

  • Days Won

    52

 Content Type 

Posts posted by Official Moderator

    Automate testing backups

    in Automation

    Posted

    "Self-healing" and "Verification" guarantee that all backup data in the repository is in the same consistent state as during backup - NAKIVO compares checksums of blocks that were counted during the backup with actual repository data. In this case File level recovery should work fine.

    The only possible issue in this case - bootability of VM in case there are some issues with boot sector, for example. It could be also in case OS updates were installed during the backup. In this case we would recommend to use automated Screenshot verification (or Boot verification) feature or manually run Flash boot to check that VM if booted fine.

    How to avoid unnecessary use of network backing up VMs to a NFS storage

    in VMware backup

    Posted

    In this case we would recommend you the following NAKIVO layout:
    1. Deploy NAKIVO transporter on both ESXI hosts to be able to use HotAdd datatransfer mode.
    2. Install NAKIVO transporter on NFS storage, in case it is supported.
    In this case both involved transporters will perform direct read and write operations on the source and target sides correspondingly and also have direct connection between each other.

    For detailed analysis, please send a support bundle (http://www.nakivo.com/helpcenter/display/NH/Support+Bundles) and the following information to support@nakivo.com :
    - in which way ESXi storages are connected to the corresponding ESXi hosts
    - which hosts are used as NFS repositories

    Cannot Add Linux Physical Server to Invenotry

    in Physical Backup

    Posted

    Based on the described error, we could recommend to check if 9445 and 9446 ports are opened on the affected Linux machine - NAKIVO tries to connect to agent on the first step and then to installed transporter service on these ports.
    Also please check and make sure that all requirements for Linux physical machine are met - https://helpcenter.nakivo.com/display/NH/Supported+Platforms#SupportedPlatforms-PhysicalMachineRequirements
    In case it still fails, please generate a support bundle http://www.nakivo.com/helpcenter/display/NH/Support+Bundles and send it to support@nakivo.com for further investigation.

    Multi-Tenant mode has not logic infraestructure

    in Multi-tenant Mode

    Posted

    With current NAKIVO workflow, the director needs access to all ESXi hosts and transporters for correct management.
    In case the transporter will be deployed on the customer side, then, yes, all the data will be transferred inside the customer site (without using WAN) ,but the director still will need access to the ESXi host and transporter.
    Generally, it is possible to do this in two ways:
    - configure port forwarding at customer's firewall;
    - configure VPN to customer's site to have full network access.

    backup physical server

    in Physical Backup

    Posted

    19 hours ago, Mirek said:

    Is there any step by step manual to do any (workaround) physical recovery? Like booting Windows machine from VHD(x)? We sold Physical Backup to our customer after Ransomware attack, because quick PC recovery, but without P2P recovery it seems useless. Thank you.

    For now it is not possible to perform P2P restore.
    It is possible to restore separate files/folders with File level recovery feature.
    We believe it is possible to clone physical machine data from the exported by NAKIVO virtual disk to physical machine HDD with some third-party software.

    Wrong VM in backup

    in VMware backup

    Posted

    Please let us know if you ran recovery in the "production" or "synthetic" recovery mode. In the "production" mode and all uuids from original VM are used for restored one, that could cause the described situation.

     

    image_2020_09_01T15_44_38_524Z.png

    • Like 1

    Be careful with updates. Nakivo B&R v9.0.0 and QNAP Nakivo Transporter v9.4.0

    in Deployment

    Posted

    Hello Giorgio,

    Thank you for contacting NAKIVO support.

    We sincerely apologize that you faced some issues in the scope of the opened ticket.

    Could you, please specify a ticket ID? We would like to analyze it in more detail to avoid any misunderstandings in further support from our side and provide you more explanations for your statements.

    We glad to hear your issue was fixed.

    You can contact us any time via chat, email (support@nakivo.com), or just send us a support bundle by the following link:  http://www.nakivo.com/helpcenter/display/NH/Support+Bundles

    Thank you for choosing our software.

    We are looking forward to hearing from you.

    Windows 10 install for testing

    in Deployment

    Posted

    Hello!

    Please note that it's not possible to install physical transporter on the same physical server where Onboard transporter has been already installed, because these transporters are different by design and can't be replaced by each other. 

    As a workaround, you can move NAKIVO Full installation with Repository to another physical server, VM, or NAS box and add this physical server to Inventory without any difficulties.

    NAKIVO Backup & Replication v10 Is Here!

    in Announcements (Releases)

    Posted

    Hello Mario,

    In some rare cases, this issue could influence the consistency of backups. It could be checked for some specific VM by running Flash boot of VM/recovery point - whether it will be fine or not.
    Please generate and send us a new support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles). You can copy the forum link into the ticket description and we will send you a link to the necessary updater.

×
×
  • Create New...