-
Posts
110 -
Joined
-
Last visited
-
Days Won
5
Posts posted by The Official Moderator
-
-
16 hours ago, brywhi said:
Also needing proxmox support!
-
On 3/22/2024 at 11:32 PM, Ana Jaas said:
Of course...
Device model: DS1621+
CPU: AMD Ryzen 1500B
@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
-
7 hours ago, Argon said:
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.
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
-
3
-
1
-
-
On 3/20/2024 at 1:15 AM, Ana Jaas said:
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
@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.
-
18 hours ago, LRAUS said:
Hi,
Is agentless support coming as well?
Large clusters can't use agent-based backups due to multiple VLANs, etc.
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
-
On 3/15/2024 at 7:01 PM, Clemilton said:
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?
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
-
On 3/15/2024 at 6:55 PM, Clemilton said:
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.
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
-
On 3/15/2024 at 7:36 PM, Clemilton said:
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.
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
-
On 2/28/2024 at 1:01 PM, tommy.cash said:
Does anyone know if NAKIVO is planning to support Proxmox backup? I'm looking for an alternative to the built-in Proxmox Backup Server
We’re excited to announce that NAKIVO has expanded the range of supported platforms to include Proxmox VE:
-
2
-
2
-
-
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 locationDownload the full-featured Free Trial of NAKIVO Backup & Replication and start protecting your Proxmox VM data today.
-
17 hours ago, Ana Jaas said:
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.
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.
-
1
-
1
-
-
On 3/11/2024 at 9:28 AM, SysErr said:
I am encountering a significant issue with a "Clone Backup to Backblaze" job that I've set up. The task is designed to transfer all my backups, totaling 1.4 TB, to Backblaze using a 275mbit/s internet connection. Based on my calculations, I anticipated the job would complete within 13-14 hours. However, after 43 hours and 30 minutes, the progress is only at 88.5%.
Initially, the transfer rate peaks between 200-300mbit/s, which aligns with my expectations. But, a few hours into the job, the speed dramatically drops to as low as 0.01 mbit/s and stays minimal for extended periods, vastly underutilizing my available bandwidth as confirmed by speedtest.net results.
Additionally, there's a scheduling conflict that exacerbates the situation. While the "Clone Backup to Backblaze" job is ongoing, the original backup process starts, writing data to the same source targeted by the clone job. I've tried to mitigate this by scheduling the clone job to run over the weekend, ensuring it has ample time to complete before the original backup resumes on Monday. Despite these adjustments, the issue persists.
Could you please provide guidance or solutions to address the following concerns?
- The drastic fluctuations in data transfer speed, particularly the periods of significantly reduced speed.
- Strategies to prevent scheduling conflicts between the clone and original backup jobs, ensuring both can complete without interference.
Thank you for your assistance.
@SysErr Thank you for your patience as we looked into your backup copy job to Backblaze B2. We've reviewed the logs and found no errors with the "Clone-Nakivo-to-Backblaze" job.
With backups to S3 storage types like AWS, Backblaze, or Wasabi, there may be periods of time when no data transfers are happening. This typically happens at the end of the backup process. At this stage, NAKIVO makes an API call to move data from a temporary "transit" folder to the repository. Depending on how much data there is, this moving step can take a while, and during this time, you won't see any data transfers happening on our side.
To help with this and improve your backup job performance, we recommend setting your backup jobs to the "active" full backup type for any backups to S3 storage. Also, to prevent any overlap and ensure both your clone and original backup jobs run without issues, it's a good idea to schedule them with more time in between.
This gives the clone job enough time to finish up, considering the extra time needed for data to move to the cloud storage. We're here if you need more help or have other questions.
Your feedback helps us make our service better for everyone.
-
7 hours ago, SysErr said:
I am encountering a significant issue with a "Clone Backup to Backblaze" job that I've set up. The task is designed to transfer all my backups, totaling 1.4 TB, to Backblaze using a 275mbit/s internet connection. Based on my calculations, I anticipated the job would complete within 13-14 hours. However, after 43 hours and 30 minutes, the progress is only at 88.5%.
Initially, the transfer rate peaks between 200-300mbit/s, which aligns with my expectations. But, a few hours into the job, the speed dramatically drops to as low as 0.01 mbit/s and stays minimal for extended periods, vastly underutilizing my available bandwidth as confirmed by speedtest.net results.
Additionally, there's a scheduling conflict that exacerbates the situation. While the "Clone Backup to Backblaze" job is ongoing, the original backup process starts, writing data to the same source targeted by the clone job. I've tried to mitigate this by scheduling the clone job to run over the weekend, ensuring it has ample time to complete before the original backup resumes on Monday. Despite these adjustments, the issue persists.
Could you please provide guidance or solutions to address the following concerns?
- The drastic fluctuations in data transfer speed, particularly the periods of significantly reduced speed.
- Strategies to prevent scheduling conflicts between the clone and original backup jobs, ensuring both can complete without interference.
Thank you for your assistance.
Hello @SysErr, to assist you with your request, please send us a support bundle. It contains log files and system information that will help us identify the problem and provide a resolution.
Please remember to include the main database and specify your ticket ID #244546.
The instructions on how to generate and send a support bundle can be found in the NAKIVO Help Center at the following link:
https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm
We look forward to your reply and assisting you further.
-
Live Webinar: The Ultimate Guide to VM Backup and Recovery with NAKIVO
Special Offer for Attendees
*Attend the webinar and get a chance to win:
- $50 Amazon eGift Card in one of three lucky draws during the webinar.
- $25 Amazon eGift Card for completing a quick post-webinar survey.
Protecting data in virtual environments requires a thorough understanding of potential threats and vulnerabilities and a dedicated data protection solution for virtualized workloads.
Register for our upcoming webinar, where we discuss the threat landscape and best practices you need to protect your VMs. Discover how NAKIVO backup for virtualization platforms can provide the optimal solution for your data protection needs.
What it covers:
-
Overview: Potential threats to virtual environments
-
Tools: NAKIVO backup for virtualization platforms
-
Tips: Best practices for data protection in virtual environments.
-
Real-life Scenarios: Case studies of customers achieving their VM data protection goals.
-
Technical Demo: Showcasing NAKIVO Backup & Replication capabilities for virtual workload protection.
-
Q&A session: Insights from experts in virtual environment protection.
When to attend
Tuesday, March 5, 2024
-
Americas: 11 AM – 12 PM EST
-
EMEA: 5 PM – 6 PM CET
*Terms and conditions apply
-
1
-
-
Yes, native support for Proxmox VMs is under investigation. However, you can already use agent-based backup for Proxmox. This should allow you to back up and recover Proxmox data the way you would back up your Windows or Linux machines. We’ll share the workflow here soon. Stay tuned!
-
2
-
1
-
3
-
-
Special Offer for Attendees
*Attend the webinar and get a chance to win:
-
$50 Amazon eGift Card in one of three lucky draws during the webinar.
-
$25 Amazon eGift Card for completing a quick post-webinar survey
Virtualization technologies like VMware and Hyper-V enable businesses to optimize their resources and reduce costs associated with hardware and maintenance. However, they also come with potential security risks to data that require precautions to be taken.
Register for this upcoming webinar to learn the strategies and tools you need to combat data loss threats in virtual environments. Learn why NAKIVO Backup & Replication is the ultimate solution for your virtual backup and recovery needs.
What it covers:
-
Overview: Potential threats to virtual environments
-
Tools: NAKIVO backup for virtualization platforms
-
Tips: Best practices for data protection in virtual environments.
-
Real-life Scenarios: Case studies of customers achieving their VM data protection goals.
-
Technical Demo: Showcasing NAKIVO Backup & Replication capabilities for virtual workload protection.
-
Q&A session: Insights from experts in virtual environment protection.
When to attend
Tuesday, March 5, 2024
-
Americas: 11 AM – 12 PM EST
-
EMEA: 5 PM – 6 PM CET
*Terms and conditions apply
-
-
2 hours ago, NiclasE said:
OK thanks. Will do.
Following up on your query, we recommend that you set up NAKIVO Backup & Replication in multitenant mode and create remote tenants for managing multiple customers through one central Director.
Here's a quick guide:
- To add customers as remote tenants, you should install an independent instance of NAKIVO Backup & Replication with its own license at each remote site.
- Ensure the cloud-based multitenant NAKIVO Backup & Replication is accessible via a public IP and two ports for remote access.
- Manage all tenants from the central multitenant installation. Each remote site remains independent, ensuring jobs continue even with connectivity issues.
- No need to open any ports on the customer's side.
- This setup addresses your concerns about firewall configurations while offering centralized management.
Please don't hesitate to contact our engineers if you need a demo or assistance.
-
1
-
-
3 hours ago, NiclasE said:
Hi,
I'm new to this forum so excuse me if this topic already have been discussed (didn't find any though). My company is hosting and helping multiple customers, both in our hosting and onprem environments. I've been working with Nakivo before but only on onprem installations with one setup per customer (local vcenter and esxi access). But what I now would like to be able to do is to have one central director that we manage multiple customers in.
From what I can see in the docs the setup should then consist of a Director with transport and repos centrally, transport agent at the customer site with Direct connect enabled. Agents on physical machines.
But the main problem is that we need to open ports in the customer FW to the transport agent server. And if we have a customer that doesn't allow access to vCenter and only allow agent based backups we still need to add a transport and open FW to that. Is that correct?
Is there no alternative to have agents talk to our transport and/or director centrally without opening any firewall inbound on the customer side?
Hope my question makes sense.
Hello @NiclasE, To address your questions and provide you with a tailored solution that meets your specific needs, we highly recommend booking a live demo with a NAKIVO engineer. During this 30-minute session, you can get answers to your questions and assistance if needed to set up the solution in a way that works best for your requirements: https://www.nakivo.com/how-to-buy/request-demo/
Best regards
-
On 2/16/2024 at 6:17 PM, asecomputers said:
Hi, We are setup with the multi tenant director and are constantly selling our services to our customer base - is there a way, or a plan on the roadmap etc to enable us to increase our number of licenses without having to do it over email with you guys? Whilst they are quick, it wouldn't be as quick as doing it myself etc.
Cheers
Alex@asecomputers Hello Alex, thank you for reaching out with your suggestion regarding self-service license management.
Currently, we don't have this feature in our roadmap, but we see the value it could bring to our partners. I'll forward your request to our Product Development Team for consideration. We appreciate your feedback and are always looking for ways to improve. Best regards.
-
7 hours ago, mururoa said:
Hi there,
I'm optimizing my nakivo configuration right now.
I wonder how to determine what is the best max load for a transporter.
I guess bottleneck will not be the network because network speed is usually under 5 Gb and max speed I saw is 16 Gb (once).
Cpu usage is like 25%.
Free memory is over 2 GB.
I/O seems not so high but activity is low for now.
So using a dedicated transporter with 4 vcpu and 4 GB of ram, what is the optimum load ?
Regards
@mururoa A Transporter consumes approximately 256MB of RAM per task, such as one VM disk.
For ten concurrent tasks, the consumption would be around 2 CPUs and 2.5 GB of RAM, plus the CPU and RAM usage of the operating system where the Transporter is installed.
Therefore, with your setup of 4 CPUs and 4 GB of RAM, it is estimated that you can efficiently handle about 8-12 concurrent tasks running simultaneously. Should you require any further clarification or have additional questions, please do not hesitate to reach out, and the Support Team will be more than happy to assist you further, use the email support@nakivo.com. Thank you.
-
13 hours ago, Gavino said:
+1 for enabling Nakivo to work with XCP-NG/XOA. I really want to get off the vSphere platform now that Broadcom keep tightening the screws. By the looks of things, there are a lot of people in the same boat (life raft!). This is a huge business opportunity for Nakivo to get the early mover advantage on XCP support, and would help Nakivo keep their existing user base of those users leaving, or looking to leave, VMware.
@Gavino, thank you for your feedback and your vote for XCP-NG/XOA support in NAKIVO Backup & Replication. We understand the importance of this feature for our users who are seeking alternatives to the vSphere platform, especially in light of recent developments. Your comment, alongside @Alex.cartus's request, has been taken into consideration and forwarded to our product team.
-
On 2/7/2024 at 11:31 PM, Alex.cartus said:
Hello to everyone
like many others, we are currently looking for alternatives to vmware. Our current favorite and that of many others we have seen is XCP-NG in combination with XOA.
Is there any support planned from Nakivo?
Kind regards
Alex
Dear @Alex.cartus, thank you for your query. Currently, NAKIVO does not support XCP-NG in combination with XOA. We've noted your interest and have created a feature request for future versions. Keep an eye on our updates for any news on this. For any questions, feel free to reach out to our support team.
-
15 hours ago, raymond.tuleweit said:
It looks like it is not possible to store the M365 backups to a cloud repository as S3 or Wasabi.
Or did I miss something?
The thought storing the M365 data on-premise is different as some competitors and a nice option.
But the time has come where hybrid worlds and cloud-to-cloud "backups" make sense.
Is a cloud repository for M365 in the pipeline?
I don't think the workaround storing M365 data to a local windows repo and making an additional "backup" of that repo to the cloud is a good idea...
@raymond.tuleweit Thank you for bringing up the topic. We're working on adding cloud support for Microsoft 365 backups, allowing storage in cloud repositories like S3 or Wasabi. This feature is planned for release in the near future. Stay tuned for updates and thank you for your feedback!
Slow O365 first Backup
in Microsoft Office 365 Backup
Posted
Dear @Krisko Liva, We apologize for the issues you've encountered with your O365 backup. To help resolve your issue, please contact our NAKIVO Support Team directly (support@nakivo.com) and send us a support bundle: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm
This will allow our team to investigate your situation and try to provide a fix. Please let me know if you need more information. Best regards