Official Moderator

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.

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/

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.

Hi, @Pavels Ruhmans! We are talking about slightly different concepts here. This is a raw speed of uncompressed data transferred. That's why the calculations don't coincide. So, you should pay attention to the speed stated in the report. If you have any other doubts, let me know:)

Hi, @MYG63! NAKIVO build for the Synology DSM 7 is not approved by Synology yet. So, it is unsupported now. However, you can try this workaround: - Deploy a new NAKIVO installation somewhere else as Virtual Appliance (VA) or installing on a supported VM, Physical or NAS; - Share the repository folder on the Synology NAS with DSM7 as NFS / CIFS (SMB) share; - Add this repository as existing to the new NAKIVO installation; - Restore the configuration of old NAKIVO installation from Self-backup from the original repository. If you have additional questions, don't hesitate to contact me.

Hi, @hmmblah! Please create a Support Bundle with a description, and our Support Team will send you an appropriate build. Here is how to create and send a Bundle https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm Let me know if you need any help.

Awesome! Now our support specialist will provide you with the best help for your particular case. If anything, I'm here.

Hi, @Michael Reetz! Please send us a Support Bundle with the main database included. This way, we can investigate your case profoundly. Here is an instruction on how to create and send a Support Bundle https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm Let me know if you have any additional questions.

Hi, @rimbalza! Unfortunately, backing up network shares is not currently supported. However, this feature is in the NAKIVO backlog. As soon as it's out, we will let you know. Stay tuned!

Hi, @JurajZ! For the x86-based CPU QNAP NAS, please update your NAKIVO instance with the following latest build to resolve the issue: 1. Director + Transporter - https://drive.google.com/file/d/1d_3HB1SulpLzb4hTKuDfo-UvRDgQwLfI/view?usp=sharing 2. Transporter only - https://drive.google.com/file/d/1LPnGno2DcYv3r9VQT5H7RutE3h_T_mXj/view?usp=sharing This article could be helpful when updating NAKIVO on QNAP - https://helpcenter.nakivo.com/User-Guide/Content/Deployment/Updating-NAKIVO-Backup-and-Replication/Updating-on-QNAP-NAS.htm#Updating2 For other architecture, please let me know the exact model and firmware version of your QNAP NAS. If you have additional questions, don't hesitate to contact me!

Hi, @calamonici.a! Please create a Support Bundle for further investigation https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm Let me know if you need any help

Hi, @calamonici.a! Could you please clarify if your ESXi host is the free version? If it's right, please contact Nakivo support by creating a Support Bundle https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm Our experts will create a ticket for you and continue investigating it. Let me know if you have additional questions!

Hi, @MLO! You can use this link for Windows-based installation https://maglar.box.com/s/l34lsb0uuv1nc2cg1imzos8hg5depg5p

No problem Please use this reference to update Windows-based installation https://maglar.box.com/s/l34lsb0uuv1nc2cg1imzos8hg5depg5p If you have any additional questions, let me know.

@bhotrock, I'm glad to hear that! You are very much welcome

Hi, @SRA_Admin! Of course, to apply the above-mentioned quick fix, please do the following: - Update NBR with this build that supports the VMware 7.0.3 (https://maglar.box.com/shared/static/1c8x9ekhe10wtaj1mavfndlny5k793fw.sh) - Re-run the job, and let me know the result. Note: If NBR Director runs on a different, not Linux-based platform, just let me know about it to send you the appropriate package.

Hi, @kamal! For particular cases, please send support bundles, including the databases, to our support team for further investigation. Follow these instructions https://helpcenter.nakivo.com/display/NH/Support+Bundles If I can help you with anything else, feel free to contact me!

Hi, @Gavino! We just released the quick fix for the backup and replication. 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 have any additional questions.

Hello, @DaniAvni! Due to the agentless architecture using for the VMware backups mentioned in this request, NAKIVO using VMware CBT as a priority change tracking source. In some cases, VMware CBT can provide incorrect data, or for as some described in this case, the issue caused by massive disk fragmentation of the backup data can be more significant than expected. This behavior is expected for the change tracking based on the changed blocks. The backup size, in this case, is not related to the repository block size (4Mb) and does not impact the transferred data. NAKIVO is not affecting disk fragmentation inside the VM and getting the data "as is." In case if the VMware CBT provides incorrect data can be used "NAKIVO Proprietary CBT" or "Double-check changed blocks provided by CBT." Proprietary change tracking is based on data block change tracking, so if many blocks are changed, it can impact the final backup size. Currently, the simplest way to reduce the backup size is to reduce the amount of the changed blocks. Nevertheless, our Development team is working on improving the change tracking to provide you the best solution. Should you need any further information, please do not hesitate to contact us.

@Jason, According to the latest Synology improvements in DSM7, all installation packages should comply with more strict security requirements than previously. For now, we are working closely with Synology Team to prepare the release, and we are almost on the final stage. However, we expect that we will need a few more weeks to complete it. When DSM7 is officially supported, then it will be possible to install NAKIVO on NAS again. Additionally, you could use the following workaround for DSM 7: Deploying a new NAKIVO installation somewhere else as Virtual Appliance (VA) or installing on a supported VM, Physical or NAS; Share the repository folder on the Synology NAS with DSM7 as NFS / CIFS (SMB) share; Add this repository as existing to the new NAKIVO installation; Restore the configuration of the old NAKIVO installation from Self-backup from the original repository. We sincerely apologize for this temporary inconvenience, yet we hope for your understanding and cooperation.

Hi, @TF RCH! It's an MS API issue that was resolved recently. Please let us know where NBR is installed (or generate a new Support Bundle), and we send you a custom build resolving it. Kindly specify your ticket number #108278 in the ticket description. Let me know if you need anything else.

Hello, @darkhorse! Various factors can cause 503 Service Unavailable error: Some services aren't loaded yet, and as a result, they aren't running (for example, the reverse Proxy or vSphere web client service can be down). vCenter Server can be on maintenance vCenter Server can be overloaded There can be some disk issues on the vCenter server The problem can be with a database used by vCenter There can be network issues Note: You can't fix the error on the client side. Instead, do that on the vCenter server. Please find the detailed guide on how to resolve any possible issue in our blog post https://www.nakivo.com/blog/503-service-unavailable-error-on-the-vsphere-web-client/ Let me know if you need any further help with your issue.

Hi, @Marco Zhang! Yes you can configure Hyper-V replication in a Workgroup. It is done by using certificates. You will have to follow these steps: Start by configuring hostnames on both servers. Make sure your Hyper-V server role is enabled. Enable inbound connections in Windows firewall and HTTPS traffic. Continue by creating and configuring certificates on the first server. After, export and import certificates. Copy these certificates to your second server. Using certificates, configure replication on your second server. After, configure replication on your first server. Note that VMs should have no checkpoints. Please find a detailed description of the workflow in our blog post https://www.nakivo.com/blog/how-to-request-ssl-certificates-for-hyper-v/

Hi, @Tayler Odling! It isn't the best idea, even though it might seem like a simple and effective solution. SharePoint was intended to store the documents centrally. So, it lacks various aspects of a complete database solution, for example: SharePoint doesn't offer an organization that database should have. In SharePoint, one-to-one, one-to-many, many-to-many relationships are impossible. SharePoint can't handle significant volumes of data. It isn't recommended to have more than 2000 items on a list. SharePoint can't roll back changes. It doesn't offer the rollback of transactions. Of course, if you simply need structured storage for a few documents, SharePoint can work well in this case, but it isn't a solution for bigger volumes and crucial data. You can check a more detailed explanation in our blog post https://www.nakivo.com/blog/why-you-shouldnt-use-sharepoint-online-as-a-database/

Hi, @Jim! In a new release (version 10.4), we have updated the UI for the Repository screen. The repository type menu was removed. The "Store backups in separate files" option was added (enabled by default). Backup repositories created in previous versions of the product keep operating in the way they were configured. Background: Storing backups in separate files is recommended. Downside: it has higher space requirements. Upsides: it is more resilient to network, power, and hardware failures; it does not require running space reclaim; it is suitable for enterprise-grade deduplication storage devices; it supports immutable recovery points. Solution: If you still want to use the "forever incremental" repository and built-in data deduplication, please uncheck the "Store backups in separate files" checkbox when creating the backup repository. If you need any further information, please don't hesitate to contact me.