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. On 4/8/2021 at 2:46 AM, JPCArch said:

    Hello,

     

    I would also like the updater package for Synology. x86 Architecture, no other transporters. Please and thank you!

    @JPCArchThank you for getting back to us! Could you please clarify the Synology model that required NAKIVO update action, what kind of package (full or Transporter only) needed for the update, and which version of NAKIVO software has been installed now? Thank you so much for your attention and participation. We are looking forward to hearing from you.

  2. 3 hours ago, mango said:

    The difference is that VMware offers dynamic memory support for any guest OS, and Hyper-V has historically supported dynamic memory only for VMs that run Windows. However, Microsoft added dynamic memory support for Linux VMs in Windows Server 2012 R2 Hyper-V.

    Hello @mango, thank you for this information. It could be very important for users of Hyper-V older than 2012R2. And based on this, we could say that any comparison should be done based on specific use case.

    If you need any further information, please do not hesitate to contact our support team.

  3. 16 hours ago, Mr.Ed said:

    I noticed that on Windows server, I can only run one job at a time. When I backup to tape or Wasabi, I cannot run my scheduled backups.

    QNAP says that Nakivo does not have this limitation when running on a Intel or AMD based QNAP NAS.

    I assume that on QNAP the Backup Copy jobs are running from a snapshot freeing the primary backup to be used at the same time?

    What other repositories allow replication or backup copy jobs while source backups are running? Synology? FreeNAS? Linux?

    - Ed Hammond

    @Mr.Ed Thank you for your question. Let me explain your issue. NAKIVO software cannot use the backup object as a source or target only for one active Job. This limitation is a warranty that the object will not be changed when used by a different Job. This workflow provides only consistent backup data transfer. This limitation is global for any NAKIVO version. If you need further assistance, please contact NAKIVO support. Do not forget to collect new support bundle logs and attach screenshots.

  4. On 4/2/2021 at 9:01 AM, NetworkWise said:

    Hello,

    I think it would be great if you all could add a report feature to the product. Nakivo is a key part in my DR strategy and being able to have reports that show for example how long it took to restore backups, perform backups etc. would help when talking to business stakeholders.

    Hello, @NetworkWise The current NAKIVO version is able to create only the build-in reports. Also, we have the integration with Aptare IT Analytics that provide the ability to build custom reports: https://helpcenter.nakivo.com/display/NH/Aptare+IT+Analytics+Integration

    Our product development team works to improve this feature. We will forward your request to them. Thank you for the suggestions.  

  5. On 4/2/2021 at 10:10 AM, Marko said:

    Hi. Do you maybe have package for synology also ? (for version 7.0.2)

     

    Best regards

    Marko

    Hello, @Marko We need to know the CPU architecture to provide you with an appropriate updater for x86, ARMv7 or ARMv8 package. Also, you may have additional transporters on other platforms that may also need a manual update. Because of this, it is reasonable to recommend you to contact NAKIVO support directly. Our support team will provide you with required updaters. Thank you for understanding.

  6. On 3/30/2021 at 12:17 AM, NetworkWise said:

    I know it's possible to encrypt the backup data during the transfer but is it possible to encrypt the backups?

    Hello @NetworkWise, thank you for getting back to us! The Repository data "Encryption" feature is available only if the Backup Repository is created locally on the machine on which the Assigned Transporter is installed, and the machine is running a Linux OS. Select  Enabled from the drop-down list and specify an encryption password. (The password will be required for importing the Backup Repository into a new instance of the product).

    The product will encrypt the repository destination (using ecryptfs for folders and cryptsetup (crypt-md) in LUKS mode for devices/partitions) prior to creating the Backup Repository.

    Please, keep in mind that this option can be enabled only when you create the Repository. Thank you so much for your attention and participation. We are looking forward to hearing from you. Best regards

    unnamed.png

  7. On 3/28/2021 at 9:24 AM, NetworkWise said:

    I'm running 10.2.0.52518 and it seems to be not compatible with vmware 7.0.2 i get the error An internal error has occurred. Reason: cannot find field: statelessNvdsMigrationReady (NoSuchFieldException).

    When will we have a release that is compatible with vmware 7.0.2 ?

    NAKIVO software released the version that is compatible with the latest VMware. Please make sure that no NAKIVO activities are running and update our product with this custom build:

    - For Windows-based OS:

    https://maglar.box.com/s/mz87we5pinsgwhyvc5rejy5ul6th502v

    - For Linux-based OS:

    https://maglar.box.com/s/uey1vqo5q91m77a6udru371ywvfprynq

     

    Please let us know the results.

    We are looking forward to hearing from you. 

     

  8. Hello, thank you for your questions. Please perform the following steps to resolve the issue and add the machine to the NBR Inventory correctly:

    1. Update the Windows to the latest MS Updates. 

    2. Repair MS VC++ 20125 x64 redist as described here (https://social.msdn.microsoft.com/Forums/sqlserver/en-US/6b33af51-efd3-400f-83da-4bb63d791187/vcredistx64msu-installation-error-0x80240017kb2999226msu-windows81?forum=vssetup )

    3. Reboot the machine.

    4. Add it to  NBR again.

    If you have any other questions, don't hesitate to contact our Support team or just write here and I will help you.

     

  9. @TonioRoffo Hello, Thank you for getting back to us! 

    If I set up a backup with incremental & weekly full backups, my S3 costs will surely below because I don't download anything. However, my weekend backups will be fulls and take considerable time. Correct? >>>>> yes, this is correct.

    If I set up a backup with incremental & synthetic fulls, does that work well with S3?  Will my backups be faster, or will S3 use my local transporters to merge the backups and create high costs due to downloading from S3? >>>>> With S3, we highly recommend using Active full backups:

    - With Synthetic full, there will be read operations from S3 -> increasing of costs.

    - Simultaneous read/write operations with S3 during Synthetic full backups show significantly lower performance than during Active full backup.

    To create a Synthetic Full backup, NAKIVO needs to read repository data, create full backup locally on a transporter and write it to S3.

    In a local test (not to S3), I saw that backup copy jobs ignore the synthetic setting and revert to full backups - in normal backup jobs, it works. Is this true for S3 also? >>>>>

    Please clarify your test in detail, as I do not completely understand what was done/compared. Using a few separate repositories/jobs, they have completely independent rules for full/incremental backups. The best solution for you would be to create and send a support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) to support@nakivo.com for further investigation of the issue. Thank you for understanding.

  10. 21 hours ago, TonioRoffo said:

    Way overdue response maybe, but for future people looking this up...

    "Second HDD is independent permanently (sdb1)"

    Independent disks do not get snapshotted by Vmware, hence they can't be backed up.  Not just a Nakivo issue, Competitor will also just ignore these disks in backup.  Be warned about this!

    I do believe backup software should mention an error or warning if such a disk is present and that it is not included in the backup.

     

    Hello, @TonioRoffo Thank you for your question. Note that NAKIVO Backup & Replication relies on VMware VM snapshots to perform backup and replication. Certain VM disk types, such as independent or RDM disks in physical compatibility mode, are not affected by snapshots. VMs that have unsupported disk types are disabled in the wizard and cannot be selected for backup or replication. For more details, please, refer to the Feature Limitations subsection of the latest Release Notes. 

  11. 22 hours ago, TonioRoffo said:

    Restore bare metal backups back to bare metal (via bootdisk)

    Backup up bare metal machines is a bit useless if we can't restore to the same hardware.  Usually these machines are on bare metal for a reason or we'd P2V them already.

     

     

    Hello, @TonioRoffoThank you for your question. The physical host's backups made by NAKIVO software are file-oriented: you can use it for the individual file|folder|disks restore action. Also, it can be used for the P2V Migration. But, it is not possible to restore the physical host backup to the bare metal in the current NAKIVO version. If you have any other issues, don't hesitate to contact our Support team or just write here and I will help you.

  12. 6 hours ago, ANTOXSZZ said:

    I am a user who wants to try using the Nakivo application
    I have fully evaluated it, my only problem is when the data backup to the physical server cannot be pulled

    image.thumb.png.eefbc1e4b957f089498830d128b9645f.png

    To find out the reason for the issue we need to check logs. Please send us a support bundle http://www.nakivo.com/helpcenter/display/NH/Support+Bundles so we can further investigate the issue you’ve experienced. We are looking forward to hearing from you.

×
×
  • Create New...