Jump to content
ON-DEMAND Webinar: The Ultimate Guide to VM Backup and Recovery ×
NAKIVO Community Forum

Official Moderator

Moderators
  • Posts

    861
  • Joined

  • Last visited

  • Days Won

    52

Posts posted by Official Moderator

  1. Hello Billy,

    Thanks for your question.  Please expect beta in June, and GA in July. 

    Should you need any further information, please do not hesitate to contact us. 

  2. We cannot tell for sure why you're receiving those errors without investigation of the log files. So could you please generate a support bundle ( https://helpcenter.nakivo.com/display/NH/Support+Bundles ) with enabled option "Include Main Database" and send is to support@nakivo.com (or upload to https://upload.nakivo.com/ ) so our 2nd Level Support Team can take a look and provide you with a proper solution.

  3. Asynchronous replication is a data storage backup technique where data is not immediately backed up during or immediately after the primary storage acknowledges write complete, but rather done over a period of time. This method results in a system with good performance and lesser bandwidth requirement, but the backups are not immediately available if something happens to the primary storage.

    Synchronous vs. Asynchronous Replication Strategy: https://www.nakivo.com/blog/synchronous-vs-asynchronous-replication-strategy/

  4. Hello!

    Currently, this function is not yet implemented in NAKIVO Backup&Replication. 
    However, our Product Team is already working on this feature so it will be added in the next releases.
    Stay tuned in order not to miss our latest updates!

  5. Just now, Michael.du said:

    I see "out of Disk Space on Drive C” error message on my Virtual Machine. Please, help

    Hi, Michael, just as with physical servers, virtual machines (VM) require a large storage capacity to function properly. If your VM starts running low on disk space, the solution is to increase your computer’s storage capacity, which can be done by adding another internal or external hard drive. However, Hyper-V has made this process even easier and faster. To increase your storage capacity, you can increase disk size in Hyper-V in just a few clicks.

    In a nutshell, to successfully expand a Hyper-V virtual hard disk, you should do the following:

    • Expand the virtual hard disk using the Edit Virtual Hard Disk Wizard
    • Extend the volume size through launching the Disk Management utility inside the VM

    To learn more details, please, read our blog post: https://www.nakivo.com/blog/increase-disk-size-hyper-v-complete-guide

    Thank you for your question and have a great day!

    • Like 1
  6. 52 minutes ago, Bedders said:

    In future versions, would it be possible to see how much space each VM is taking on a backup repository individually? It'd be useful to know which VM's are taking up the most space, per repository.

    Actually, that is possible for the "Incremental with Full backup" repository type. NOTE: It is impossible to change it after the repository creation.

  7. With Microsoft Hyper-V gaining more market share and coming of age, VMware administrators are finding themselves having to administer Hyper-V alongside vSphere in their environments. There are certainly similarities in administering the various hypervisors, including VMware and Hyper-V, but there are also subtle (if not more major) differences as well. Often, out of habit, we apply what we know to things that we do not know, or that are new to us. While certain methodologies or best practices extend past the boundaries of VMware vSphere and apply to Hyper-V as well, there are differences in the administration and management of Hyper-V that VMware administrators will want to make note of and understand. These differences also can affect backup processes in the administration of Hyper-V vs. VMware. 

    👉 Let’s take a look at some of the key differences between Hyper-V and VMware, and how these can affect your backup methodologies: https://www.nakivo.com/blog/hyper-v-backup-guide-vmware-administrators

  8. During backup (it does not matter VM or physical) all data is divided for blocks and stored in the repository. In case some blocks appear to be similar, deduplication works and only one block is saved in the repository. It seems that in this case saved data from VMDK file and directly from VM disk has different layout (contains some additional service information or shift for example). In this case saved blocks are different and will not be deduplicated.

    • Like 1
×
×
  • Create New...