Jump to content
NAKIVO Community Forum

Bedders

Members
  • Posts

    25
  • Joined

  • Last visited

  • Days Won

    11

Bedders last won the day on January 5 2025

Bedders had the most liked content!

Recent Profile Visitors

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

Bedders's Achievements

Cyber Shield Apprentice

Cyber Shield Apprentice (3/14)

  • Secure Conversation Starter Rare
  • React Securely Rare
  • First Post of the Backup Hero Rare
  • Collaborative Defender Rare
  • Dedicated Defender Rare

Recent Badges

20

Reputation

  1. And to update it now says this, although no functionality we use appears to have been affected. Free usage period has expired The current promotion period for agent-based QEMU/KVM VM data protection has expired.
  2. Good morning, Upon logging into our NAKIVO appliance today, I saw the following warning at the top: Free usage period will expire in 8 days 15 hours Dec 23 at 8:39 Dismiss The current free usage period for agent-based QEMU/KVM VM data protection will expire in 8 days 15 hours (on 2025 Jan 01 at 0:00 (UTC +00:00)). As far as I know we don't use this but is there any way to determine whether this will affect our installation? Thanks in advance
  3. I hope I can explain this correctly. When in the NAKIVO Web Interface, I open windows like the 'Issues' window on a job. Then I want to move to the next job to check its' status. So I click on it to the left under 'Job Overview', but the Issues window is still open. I have to manually click the cross in the top-right to close the Issues window first, then move back over to the left. A lot of interfaces now support you clicking in the faded dark area behind the open window, and it closes the open window, taking you back to the main page you were just on. The attached image may help to explain what I mean.
  4. Hi Moderator, Thanks for linking the article, but that only provides download links for the Director on Synology. We have just the Transporter role installed on the Synology. Do I still follow the same process as linked in the article, using the script for the Director? Thanks.
  5. Is there any way to update only our transporter on Synology DSM 7.1.1-42962 Update 6? The article linked shows how to replace the Director, and we have the Director installed elsewhere. When I try to do a Manual Install via the Synology Package Manager, it says "This package requires DSM 7.0-4000 or older".
  6. 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
  7. Can we run the 10.9 installation on the Synology using the 'Manual Install' in the Package Centre instead of using SSH?
  8. 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?
  9. Yes thanks, I have a 10.2 SPK file now.
  10. 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.
  11. 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.
  12. 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!
  13. 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?
  14. 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!
  15. 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.
×
×
  • Create New...