Bedders

Ok, thank you for the information. That's disappointing as now I need to find a download for the Windows version of NAKIVO, https://d96i82q710b04.cloudfront.net/res/product/NAKIVO Backup_Replication v10.9.0.76010 Updater.exe but the one that matches the transporter version available on Synology. Alternatively do you have the download link like above but for just the Synology Transporter version so I can install it via SSH? Specifically it's transporter version 10.8.0.n72947 Thanks in advance

Can we run the 10.9 installation on the Synology using the 'Manual Install' in the Package Centre instead of using SSH?

We are seeing the issue described in https://helpcenter.nakivo.com/display/KB/Cannot+Open+Database+During+Microsoft+Exchange+Mailbox+Recovery, that is when I go to Exchange Recovery, I select a server & a date to restore from, expand the database and click on a user - I see this error: Database cannot be opened. Generic error happened while opening. Failed to complete recovery. Exception calling 'AutodiscoverUrl' with '2' argument(s): 'The Autodiscover service couldn't be located.' Export Exchange certificates from the Exchange admin center and add them to Trusted Root Certification Authorities Store via MMC. I have tried the first recommended fix on the other page (https://helpcenter.nakivo.com/display/KB/Mailbox+Processing+Failed+Because+Autodiscover+Service+Could+Not+Be+Located), adding the security certificates to the certificate store, and it still isn't working. I'm hoping to avoid entering the registry key suggested because I understand it opens up additional vulnerabilities on our Exchange server (see https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-8581) Is there any other possible way to allow us to restore specific Exchange objects?

Yes thanks, I have a 10.2 SPK file now.

Updating this thread for information. NAKIVO Support have kindly provided me with a 10.2 version of the Synology Director. I upgraded the Director over the weekend successfully, but still have other Transporters and offsite copy jobs to check.

Hi all, I'm hoping someone can help me. I'm looking for an older build of NAKIVO Backup & Recovery, specifically 10.2.0 (build 51253), for Synology NAS (so the SPK file). Basically we're having an issue with a VM backup and support are advising we upgrade to 10.5.1 Every time historically we've updated there have been issues, so I would like our current version to have on hand in case I need to revert to a known "almost working" configuration. I know this is a long shot! Thanks in advance.

Feeding back that changing q to -q worked, many thanks! It's probably worth mentioning that the email you sent round contained this error, as well as the forum post - in case you've not been inundated with support calls about it already!

I get the following error when I try this: root@SynologyNAS:/volume1/@appstore/NBR/libs# zip q -d log4j-core*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class zip warning: q.zip not found or empty zip warning: name not matched: org/apache/logging/log4j/core/lookup/JndiLookup.class Should I contact Support or am I doing something wrong?

Seconded please - I recall NAKIVO uses Java in their Synology install. It would be great to get something official because if I have to update our NAKIVO version I need to start planning!

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.

Ah, we are using Forever incremental. Thanks for the reply.

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.

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

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/Transporter/Repository is running a newer version than the receiving Transporter/Repository? Thanks in advance.

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.

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.

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.

Hi thanks for the response. It's static memory at 32GB.

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 to just fail, or will it spill over to the configured page file? Or is there any way I can set it to have a lesser amount of RAM when it does the Flash Boot? Thanks in advance.