Jump to content
NAKIVO Community Forum

All Activity

This stream auto-updates

  1. Yesterday
  2. Last week
  3. I'm currently managing a VMware VM with a substantial disk size of around 10 TB. Our backup operation demands daily execution to ensure data integrity, with the added requirement of maintaining three recovery points. We have configured to take Full backup every 30 days. However, the process of conducting full backups is time-consuming and resource-intensive. I'm seeking recommendations and best practices from the community on how to optimize our backup strategy to meet these demands effectively. Is it possible to take only full backup once and incremental backup forever maintaining only last 3 recovery points?
  4. Hello @RandyTic, while end-to-end encryption for Wasabi is on our roadmap, I can't share an exact timeline yet. So keep your eyes on our website: https://helpcenter.nakivo.com/Release-Notes/Content/Release-Notes.htm for updates. Please note that NAKIVO Backup & Replication sends data to WASABI storage using SSL protocol, which is a secured protocol for data transfer.
  5. Earlier
  6. Is Nakivo considering implementing end-to-end encryption for backups stored on Wasabi cloud storage? How secure are current backup solutions on Wasabi and what measures can be taken to enhance data protection?
  7. Thanks, I really, appreciate your aportatation, for this problem and I have resolved. Again, thak you.
  8. @Ana Jaas, to update NAKIVO on your Synology DS1621+ with an AMD Ryzen 1500B, please follow our manual update guide here: https://helpcenter.nakivo.com/Knowledge-Base/Content/Installation-and-Deployment-Issues/Updating-Manually-on-Synology-NAS.htm?Highlight=DSM At step 6, download PKG for AMD Ryzen 1500B CPU here: https://maglar.box.com/shared/static/drpedy89j4652zfcagspxqe8jtydnwc7.sh For any further assistance, feel free to request a remote support session. Best
  9. Dear @Argon, Thank you for your honest feedback. This helps us understand what our users need and how to improve our product moving forward. We have tried to be as clear as possible that this is only an agent-based approach to backing up Proxmox VE, and wanted to inform users who may not be aware of this approach in NAKIVO Backup & Replication. As for the native Backup Server Tool, it may have some advantages but it lacks several important capabilities such as multiple backup targets (for example, cloud) or recovery options (for example, granular recovery of app objects). We are continuously working on improving our software solution, and we are investigating native Proxmox support. Thank you once again for your input. Best regards
  10. @Ana Jaas, I'm sorry to hear about the difficulties you're experiencing. Please share your Synology device model, CPU version, and RAM to help our support team provide a swift resolution. You can also reach out directly to our support team at support@nakivo.com.
  11. I really like Nakivo but your support for Proxmox is shameful. You do not support Proxmox, you just suggest that we install your Linux agent on it, which has in fact been compatible for a long time since it is a Debian Linux and which involves making a backup of the entire system in his outfit. Are you riding the wind of industry panic with VMWare? This does not support HV Proxmox and this backup should be classified under physical backup of a linux host. But the worst thing is to say that this way of doing things is better than Proxmox Backup Server... I believe that you have not studied the competitor very well before trying to sell your product as "compatible". Your solution does not at all allow you to make a serious backup of VMs and CTs independently of the HV.
  12. Hello, thanks for answering... I was able to upload a transporter version on my QNAP device, it worked and is currently working. I tried to do the same with the sysnology transporter, download the updater and upload it for manual installation, but the following text box appeared... "This package requires DSM 7.0-40000 or later." My sysnology device has dsm 7.2.1 update 4. I think this error should not appear on my DSM version is within the DSM range that appears in the message. The updater that I downloaded is from the official nakivo website. I downloaded and tried two updaters and with both I got the same message. Sysnology Transporter package. Sysnology ARMv7 Transporter package. Help me pleaseeeee :(
  13. Hello, @LRAUS, We acknowledge the need for agentless support for Proxmox VE and plan to add this feature to our roadmap after investigation. However, we don't have an ETA yet. We'd appreciate knowing how important this is for you, so we can prioritize it accordingly. Your input is valuable in shaping our development efforts. Best
  14. Hello, @Clemilton. For the export and import of settings between Nakivo versions, it's important to note that we generally support the N-1 version approach and don't maintain a public repository of older releases. However, to assist with your specific situation, we can provide a link to download the Linux version of NAKIVO Backup & Replication 10.2. Please use the following link to access the installer: https://maglar.box.com/shared/static/ljsx7h9fyjko62nigfxqv98mqezcz82q.sh If you need further assistance, please contact our support team directly: support@nakivo.com
  15. Hello, @Clemilton, VMware vSphere 7.0.3 is officially supported in NAKIVO Backup & Replication starting from version 10.5.1 onwards. To ensure compatibility and to access the latest features and fixes, updating your NAKIVO software instance to a supported version is recommended. For more details on version compatibility and features, please refer to the Release Notes available in the Help Center: https://helpcenter.nakivo.com/Release-Notes/Content/Release-Notes.htm If you need further assistance, please contact our support team directly: support@nakivo.com
  16. Hi @Clemilton, the error "Import has failed: invalid LOC header (bad signature) (ZipException)" suggests data corruption in the export/import of configuration file data. To troubleshoot this, please provide: 1) Steps to reproduce the issue 2) The exported system configuration file from Nakivo 10.2 3) A support bundle from the new Nakivo 10.11 installation https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm Upload the files at https://upload.nakivo.com/c/uploadPackage, mentioning ticket ID #245373 in the description. As a workaround, try copying the "userdata" folder from your Nakivo 10.2 installation to the same location on the 10.11 Director server: Linux: /opt/nakivo/director/userdata We'll review the provided data and work to identify the cause of the import failure. If you need further assistance, please contact our support team directly: support@nakivo.com
  17. Hi, Is agentless support coming as well? Large clusters can't use agent-based backups due to multiple VLANs, etc.
  18. We’re excited to announce that NAKIVO has expanded the range of supported platforms to include Proxmox VE! The agent-based backup support for Proxmox VM data features: • Full and incremental, image-based backups of Proxmox VM data, applications and operating system • Backup copy to remote sites, public clouds, other S3-compatible platforms and tape • Full VM data recovery to an identical VM on the same hypervisor using bare metal recovery • Instant recovery of files and app objects to the original or a custom location Download the full-featured Free Trial of NAKIVO Backup & Replication and start protecting your Proxmox VM data today. DOWNLOAD NOW
  19. Hi guys. I've been searching for a few days and I can't find any reference to this error. I'm trying to import the configuration of a Nakivo 10.2 server to a new installation with Nakivo 10.11. Thanks.
  20. Hi Guys I'm having trouble exporting settings from Nakivo 10.2 and importing to version 10.11. I would like to reinstall version 10.2 to perform this action, but I can't find any repository of old versions. Is there no possibility to download previous versions of Nakivo?
  21. Hey guys. I run nakivo 10.2 with vCenter 6.7. I updated vCenter to version 7.0u3 and after the update, I receive the following error. I noticed that a few years ago there was a .sh file that was made available to fix this problem without the need to update to newer versions. I would like to know if anyone still has this file and could provide it to me.
  22. Hello @Ana Jaas, thanks for reaching out. To be able to provide the steps to take, we need more information about your NAS devices. Could you please provide us with the specifications of your NAS devices? We'll need details such as the model, operating system version, and CPU version. This information will enable us to guide you through updating the Transporter to match the version of the Director. Alternatively, you can navigate to Expert Mode: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Expert-Mode.htm?Highlight=expert mode and enable system.transporter.allow.old to address the compatibility issue. If you find these steps challenging or would prefer direct assistance, we're more than willing to schedule a remote session to help you navigate through the process: support@nakivo.com. Looking forward to your response.
  23. Hi, I have a problem, apparently of incompatibility of versions, I am working on the most recent version of nakivo, that is 10.11 and I have two nas devices, one with transporter version 10.8 and another with version 10.5, when I try to add them to the nodes, I get the following error. My solution is to downgrade the version to 10.8 or similar, but I can't find the resources on the official website. Could you help me get past versions of nakivo? If you guys have any other solution ideas or suggestions, I'm open to trying.
  1. Load more activity
×
×
  • Create New...