Jump to content
NAKIVO Community Forum

Bedders

Members
  • Content Count

    11
  • Joined

  • Last visited

  • Days Won

    3

Bedders last won the day on October 23

Bedders had the most liked content!

Community Reputation

5 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My apologies, I forgot to reply here. Updating for anyone in the future. We upgraded NAKIVO B&R to v10.0.0 which resolved the issue. VM's are now all on Server 2019 hosts and boot verification is working as expected.
  2. Ah, we are using Forever incremental. Thanks for the reply.
  3. 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.
  4. Just as an addition to this, it looks like in the Release Notes for NBR 9.0 it says the below. I suspect that, since I'm on V 8.5.2, this is the issue. I'll confirm in a couple of weeks. Microsoft Hyper-V 2019 Support The new version of NAKIVO Backup & Replication provides full Microsoft Hyper-V 2019 support
  5. Hi, We have a Synology NAS as our Director, which is also a Transporter, and has a Repository onboard. We have a second Synology NAS that is offsite and accessed via a WAN. This second NAS has the Transporter role installed and is also a Repository. It is used as the target for a Backup Copy job. When I upgrade our Director from NAKIVO V 8.5 up to V 9.1, I understand that it will automatically update all of the Transporters that it can see. Unfortunately it cannot see the Offsite transporter. Are we likely to run into issues with the Backup Copy job if the sending Director
  6. Hi Trevorr, Apologies for not getting back as promised! As per my other thread (linked below) I can't even enable Screenshot Verification. NAKIVO support has advised upgrading to version 9.1 but we can't do this for another couple of weeks unfortunately. Once I do, I will update both threads.
  7. I'm trying to enable Screenshot Verification for a newly added host & VM. When I try to enable Screenshot Verification I cannot select the current host, apparently due to a mismatch with the virtual hardware version. But it's the current host therefore I don't see how? Both the host and guest are running Windows Server Standard 2019. The Virtual Machine version is 9.0 NAKIVO is still on version 8.5.2 (build 32767) and I can't upgrade it for at least a couple of weeks.
  8. Ok, thank you for the reply. I'm going to be adding it to NAKIVO prior to the weekend, so I will update this thread with results in case anyone else comes across it.
  9. Hi thanks for the response. It's static memory at 32GB.
  10. Hi, A bit of background relevant to the question; We have a hypervisor with 48GB RAM. This is intended for only 1 virtual machine, a very high volume MS SQL server on the underlying SSD storage. The guest VM will be using 32GB RAM, so 75% of the RAM on the host. It is not yet backed up by NAKIVO (I will be adding it this weekend to give it time to perform the initial backup). I would like to enable screenshot verification on the VM when I do add it, but this will take the memory usage over what the host has when it does a Flash Boot to verify the screenshot. Is it likely t
×
×
  • Create New...