Jump to content
NAKIVO Community Forum

All Activity

This stream auto-updates

  1. Yesterday
  2. Hello, It looks like it's not possible to add more than one schedule per attach and detach operation. I know I can do that with CLI but that means a script with readable password have to be stored somewhere. So it would be nice to have the same facility to add schedules as we can do for backup jobs. If there is really no way to do that, is it planned in the roadmap ? Thanks.
  3. Hi, @ozarktech! NAKIVO waits for Synology approval to be included in the list of supported software: https://kb.synology.com/en-uk/DSM/tutorial/supported_third_party_packages_beta Synology will mark it as support when they add the support of NAKIVO Backup & Replication to DSM 7.
  4. Last week
  5. I did that already. It's not that simple, I have 5hr+ into getting that done. Then I'll still have to switch it back once Nakivo is supported on DSM 7. There needs to be a better solution.
  6. Hi, @Jlopez! It is expected behavior. We just released the quick fix for the backup and replication, which is available on 10.4. However, the new feature introduced by VMware (new hardware support, etc.) is not supported. The full v7.0U3 will be implemented in v10.5, which we expect at the end of October. Let me know if you need any other assistance.
  7. Today we tested 10.5 beta version and still having "The VM cannot be processed. cannot find field: vmOpNotificationToAppEnabled (NoSuchFieldException)" issue, no backup at all.
  8. Hi, Many thank's, now inventory works but the advice of vcenter not supported version still, hero, i hope the backup works tonight. Thank you very much
  9. Hi, @Agustín Luis Estévez! Here is the .spk installer for Synology x86: https://maglar.box.com/shared/static/ukcubab15dlqyzgxscq3jnwnhsli5wdx.spk If you need any further information, don't hesitate to contact me
  10. @Official Moderator, thank you bunch! Will check the options they offer.
  11. @Official Moderator Thank you a lot for the response! I reset the memory values and now it works.
  12. @sanches.romero, Yes, you're right. During the free trial, you get all the features of the most advanced editions (vSphere Enterprise Plus and vCenter Server Standard). The trial license has a duration of 60 days. Note: you can use these 60 days when needed. Let's say you start using vCenter in the trial version for 30 days, and only after the evaluation month you buy the license. It means you will have 30 days remaining to go from the licensed to the evaluation mode. You can switch back to the evaluation mode any time you want. At the same time, if your trial period expires and you have no license assigned, all the hosts will be disconnected from the vCenter. If you buy a license afterward, the ESXi hosts you added before will be reconnected automatically. There is a comprehensive guide on the VMware licensing options, in case you are confused. https://www.nakivo.com/blog/vmware-vcenter-server-licensing-options/Official
  13. @Official Moderator, now I get it. Thanks for the blog post link! Just one more question. All the limitations you mentioned don't apply to the free trial, right?
  14. Hi, @sanches.romero! The free version works on a standalone ESXi host. However, there are a lot of limitations you should consider: 1. There isn't any official support. If you have any troubles, you can consult with the VMware community. However, there is no guarantee someone will solve your problem. 2. If you have a VM with more than eight virtual processors, the VM will most likely fail as the maximum of the vCPU for each VM is eight. 3. One of the most significant disadvantages is that you can't add the free ESXi host to vCenter. That's why you won't be able to migrate machines or use clustering features. 4. There is no vStorage API available. vStorage Application Program Interface (API) is a data protection framework for centralized backup of VMs on a host level. It makes VM backup efficient, offloading CPU, storage and network. Check more information about the free version of VMware ESXi in the NAKIVO blog https://www.nakivo.com/blog/free-vmware-esxi-restrictions-limitations/
  15. Hi, @Lu.taiand @orlando! You can do the import without any third-party solutions with the Microsoft native tools alone. Most likely, you will find all the PST files here C:\Users\user-name\Documents\Outlook Files (depending on the OS and Outlook versions). The general procedure of the import goes as follows: 1. Start by setting permissions. Your Microsoft 365 account needs proper permissions for the PST files import. For this, the user account has to have the Mailbox Import Export role assigned. You can check and update the permissions in the Exchange admin center. 2. Then goes the import. The first stage of it would be uploading files to the Azure cloud storage. 3. Verification. Before migrating PST files to Microsoft 365, check if they were successfully uploaded to Azure storage. 4. After you're done with verification, create the PST mapping file. It will specify to which Microsoft 365 accounts PST files have to be imported. Note: The mapping files will be saved in a CSV format. 5. The final stage is creating an import job Of the PST files. The procedure requires some time and knowledge, but you can quickly go through it by yourself with this detailed guide https://www.nakivo.com/blog/migrating-pst-files-to-office-365/ You will find all of the needed screenshots that significantly facilitate the import. Let me know if you have any questions.
  16. Hi, @rico.tiko! What is probably causing an error is precisely the fact that you have Hyper-V installed. In your case, VirtualBox is a Type 2 hypervisor, while Hyper-V is a type 1. The main difference is that a type 2 hypervisor is deployed on the OS which is running on your hardware. At the same time, a Type 1 hypervisor is deployed directly on the hardware. And this is where the problem occurs. All of the hypervisors need processor virtualization extensions. It is a set of instructions set for the hardware virtualization (AMD-V. or Intel VT-x). Hyper-V takes complete control of the extensions, making them not available for the VirtualBox because only one software component is able to use Intel VT-x or AMD-V at the same time. Now let's see how to make them work together. You have several methods to deal with the incompatibility issues: 1. You can uninstall Hyper-V in the GUI. 2. Alternatively, you could utilize PowerShell to disable the Hyper-V feature. 3. There is one more method using PowerShell. You can uninstall the Hyper-V role with dism.exe 4. Another way to disable Hyper-V is by using BCDedit. 5. You can disable Device Guard and Credential Guard. Note: VirtualBox can function with Hyper-V, Device and Credential Guard, only from VirtualBox 6.0. Check the detailed guide on how to work with every method in this blog post https://www.nakivo.com/blog/virtualization-applications-with-hyper-v-device-guard-and-credential-guard/
  17. Hi, @heyho! One of the most typical reasons for poor VM performance is insufficient hardware resources. It would be best if you avoided the memory and CPU overcommitment. What should you have in the account? 1. CPU resources. Suppose your VM lags: consider using more CPU cores or adding virtual processors. In case your processor is old, think of upgrading the hardware of a host machine. 2. RAM for the VM. Ensure setting a sufficient amount of RAM for your VM. If there isn't enough memory, the guest OS will have to actively rely on swap files, leading to slow performance. However, assigning too much memory to a VM isn't the best idea because you should leave some RAM for the host. 3. RAM for the host machine. Assigning excessive memory to a VM usually means a lack of RAM for the host OS. In this case, the host OS will use swap files intensively, which leads to the degradation of the performance. How to find the right amount of memory? For this, you should check system requirements for the OS and applications. However, you can rely on the perfect ratio. For instance, your host machine has 8 GB of memory while running Windows 10 or ESXi 7.0 with VMware Workstation (Windows Server 2019 VM). If you set 4 GB of RAM for a VM, 4 GB is left for your host OS. It is more than enough for decent functioning. Note: This example doesn't include additional applications that might consume significant resources. In this case, the ratio is 1:2 (meaning 4 GB to 8 GB). What we get is 1/2-1= -0.5. -0.5 is the current MEM overcommit average value. Remember to keep the balance, because if you provide 2 GB of RAM for the same VM, VM performance will be poor. On the other hand, if you set 6 GB of RAM for the VM, the host machine won't get enough memory. As a result, both physical and virtual machines will degrade. You also have to take into account the heavy applications you run on VMs (e.g., databases). You might adjust VM configuration and add additional memory and CPU resources. If you require more information on performance problems, check our blog post https://www.nakivo.com/blog/a-full-overview-of-vmware-virtual-machine-performance-problems/ and don't hesitate to contact me, in case you have any questions.
  18. Thanks! Support got me sorted after I sent the bundle like you suggested.
  19. Hello, i need the quick fix for Nakivo 10.4 Synology NAS package. Please!!, many thanks
  20. What are the disadvantages of using a free version of VMware ESXi. Are there any limitations?
  21. I would also be interested if someone has an easy solution for this type of file import.
  22. Hey! Recently we migrated to Microsoft 365. And now have to import data from PST files. Is it possible without using any third-party tools? Any help would be appreciated.
  23. Hello everyone! I installed VirtualBox on a Windows machine, but it doesn't work. I get the following error VT-x is not available (VER_VMX_NO_VMX). E_FAIL (0x80004005). I think that maybe it is because of the Hyper-V I have deployed. However, it wasn't running when I tried to start the VirtualBox VM. What is wrong? Any ideas?
  24. @heyho, I guess 2 GB of RAM isn't really enough. You should check the CPU and RAM requirements because overload is the most typical reason for slow performance.
  25. Hello everyone! I have a VM running Windows Server 2019, and it started to run extremely slow. First, I thought that the cause could be some memory issues. So I checked it. It turned out I have almost 2 GB of RAM for the host VM. Isn't it enough? If so, what else should I check? Because I'm really tired of this slow performance.
  1. Load more activity
  • Create New...