Jump to content
NAKIVO Community Forum
  • Welcome to NAKIVO Community Forum!

    Sign up to start a discussion!

  1. General Discussions

    1. 45
      posts
    2. 33
      posts
  2. Deployment

    1. 34
      posts
  3. Configuration

    1. 6
      posts
    2. 8
      posts
    3. 46
      posts
  4. Backup

    1. 22
      posts
    2. 28
      posts
    3. 20
      posts
    4. 9
      posts
    5. 17
      posts
    6. 2
      posts
    7. 24
      posts
  5. Replication

    1. 4
      posts
    2. 2
      posts
    3. 4
      posts
    4. 10
      posts
  6. Recovery

    1. 6
      posts
    2. 2
      posts
    3. 12
      posts
    4. 6
      posts
  7. Integration

    1. 15
      posts
  8. Automation

    1. 12
      posts
  9. Multi-tenant Mode

    1. 4
      posts
  • Member Statistics

    361
    Total Members
    483
    Most Online
    fbarrio
    Newest Member
    fbarrio
    Joined
  • Posts

    • "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.
    • 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
    • Do the "Self-healing" and "Verification" tasks guarantee that the backups are restorable?
    • Hello! In this case, we suggest you check the following article on Physical machine requirements - https://helpcenter.nakivo.com/display/NH/Supported+Platforms#SupportedPlatforms-PhysicalMachineRequirements If nothing helps, please send us a support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) for further investigation. 
    • Alright, let me explain my scenario I have a couple of Esxi hosts with 6 VMs on each I have 2 NFS Linux Storages ( storage1 an storage2) and nakivo running in one of those storages (storage2) locally   Right now, if I want to backup a VM, it goes something like this: VMs get snapshotted, and new files are created on their respective storages Nakivo starts copying the files to the repository, BUT, its goes like this storage1 -> esxi host -> nakivo repository (storage2) storage2 -> esxi host -> nakivo repository (storage2) Instead of going directly like this storage1 -> nakivo repository storage2 -> local nakivo repository  (without using the network at all) So, right now, nakivo is creating backups at around 50-60MB/sec but they are using all the bandwidth available on the esxi hosts, completely wrecking their performnce while backups are running. wouldn't make sense for nakivo to pull the snapshot files directly from the esxi storages? is that posible?  maybe adding the storages directly on the nakivo admin panel and indicating were each VM is stored?    
  • Forum Statistics

    • Total Topics
      107
    • Total Posts
      1227
×
×
  • Create New...