The Official Moderator

@Daniel Baessler, for now, it is not possible to back up the physical machine on which NAKIVO Backup & Replication is installed because of a conflict between the already installed Transporter and the physical agent needed for backing up the machine. The good news is that our development team is actively working on a Universal Transporter feature to resolve scenarios like the one you're facing. Our quality assurance engineers are currently testing the Universal Transporter functionality. Once testing completes and the feature meets our release criteria, it will be included in an upcoming version update. I don't have an exact release date to share yet, but please keep an eye out for this capability. In the meantime, feel free to reach out to support if any other questions come up: support@nakivo.com. Thank you for being a NAKIVO customer and participating in our community!

Hello, @perrcla, as of December 2023, the latest version is 10.10.1, and it can be downloaded here: https://www.nakivo.com/resources/download/update/ You can find the instructions for updating an existing NAKIVO Backup & Replication installation are available in our documentation here - make sure to detach any Microsoft 365 or CIFS/NFS repositories beforehand if configured: https://helpcenter.nakivo.com/User-Guide/Content/Deployment/Updating-NAKIVO-Backup-and-Replication/Updating-NAKIVO-Backup-and-Replication.htm If you have our solution installed on a Synology NAS with DSM 7, follow these instructions for a manual update: https://helpcenter.nakivo.com/Knowledge-Base/Content/Installation-and-Deployment-Issues/Updating-Manually-on-Synology-NAS.htm Unfortunately, we do not have hosted downloads for older versions like 10.9 available. We recommend keeping your NAKIVO instance updated to the latest available build for enhancements, compatibility updates, and critical fixes. Please let me know if you have any other questions.

@Leij, when adding an ESXi host/cluster with the Direct Connect feature enabled, only a specific transporter (Direct Connect) will be used as the source. If the ESXi host/cluster is added without enabling Direct Connect, you can manually specify the transporter to be used as the source. This allows for a balanced load distribution between Jobs. Here's an overview of Direct Connect: https://helpcenter.nakivo.com/User-Guide/Content/Overview/Direct-Connect.htm Let us know if you need more information.

Beta testing for NAKIVO Backup & Replication v10.11 is now underway, with new features for infrastructure monitoring, granular recovery and workflow optimization. Here are the highlights of this release: Alerts and Reporting for IT Monitoring: Create custom alerts for suspicious activity and get detailed reports about VMware VMs, hosts and datastores. Backup for Oracle RMAN on Linux: Protect your Linux-based Oracle databases using the same unified interface. File System Indexing: Quickly locate specific files/folders in your backups to save time during granular recoveries. Backup from HPE Alletra and HPE Primera Storage Snapshots: Boost performance using native storage snapshots for VM backups. In-Place Archive Mailbox, Litigation Hold and In-Place Hold Support: Protect additional categories in your Exchange Online mailboxes for easier compliance. Universal Transporter: Improve efficiency and reduce network load with a single Transporter for multiple workload types on the same host. Try v10.11 Beta now, and share your feedback about the new features to get a $30 Amazon eGift Card!

@Jorge Martin San Jose , thank you for reaching out to us. In the current NAKIVO implementation, we support two types of repositories: forever incremental and incremental with full. The incremental with full repository type requires more space due to separate full recovery points but generally exhibits better reliability during emergencies such as power outages or hardware failures. The forever incremental repository has a different structure and may require occasional maintenance, similar to a "defragmentation" process. Both repository types are compatible with the ReFS filesystem, although we are currently investigating potential performance differences compared to other file systems like NTFS or FAT. For larger repository sizes, especially those exceeding 10 TB, we recommend using the "Incremental with full repository" type. However, it's still feasible to create multiple repositories, each ranging from 8-10 TB, in the described scenario. If you opt for the Incremental with full repository type, we suggest using Active full backups instead of Synthetic full backups. Although the final backup size remains the same for both types, they differ in how a full backup is created. Synthetic full backups leverage previous backup information, requiring consistency checks, while active full backups pull data directly from the VM. Feel free to explore these options and test the described layout, different repository types, and overall NAKIVO performance using our Free trial version. Should you require further assistance, please don't hesitate to reach out us on the Forum or using this email: support@nakivo.com.

Hello @conalhughes, the "download to browser or send via email' recovery method is supported in all editions of NAKIVO Backup & Replication. At the Files step of the recovery wizard, select the files you want to recover and then select "Forward via Email" or "Download" for "Recovery type". For more details, please refer to: https://helpcenter.nakivo.com/User-Guide/Content/Recovery/Granular-Recovery/File-Recovery/File-Recovery-Wizard-Options.htm#Forwardi If you have any questions about licensing or features, please feel free to reach out.

Hello Pol, Yes, it is possible. To create a full backup copy from NAS to tape every day: 1. Create a backup copy job to tape: https://helpcenter.nakivo.com/User-Guide/Content/Backup/Backing-Up-to-Tape/Backing-Up-to-Tape.htm 2. At the Schedule step of the wizard, set the job to start after the original job with a 5-minute delay. 3. At the Options step, set the full backup option to "Always: https://helpcenter.nakivo.com/User-Guide/Content/Backup/Backing-Up-to-Tape/Tape-Backup-Wizard-Options.htm Let us know if you need further assistance.

@Leslie Lei, currently the solution workflow for EC2 instances and physical machines is similar with proprietary change tracking. NAKIVO Backup & Replication reads the whole disk(s) and compares them with existing backup data to identify changes. In some cases, a backup can take longer and there may zero data transfer during a job run when data is being checked but not written. The difference in transfer rate for VMware vSphere and Hyper-V VMs has to do with NAKIVO Backup & Replication leveraging native change tracking technologies for backup jobs. These technologies allow for faster job runs. Our Dev Team is working on enhancing change tracking for physical machines to increase the speed of physical machine backup. However, we cannot provide an exact ETA at this time. Thank you again for sharing your feedback. Let us know if you have any other questions.

Hello, @Leslie Lei I've forwarded your message to our Level 2 Support Team. Can you please provide me with the original ticket number associated with your support request? This will help us track the progress of your case and understand if the ticket is still open or has been closed without resolution. Thank you for your feedback!

@Dmytro The best way would be to generate and send a support bundle ( https://helpcenter.nakivo.com/display/NH/Support+Bundles ) to support@nakivo.com so our Technical Support team can investigate it and forward your feature request to our Product Development team for possible future implementation.

@Slawomir We understand that timely support is crucial to your workflows, and we want to ensure that we do everything possible to resolve this matter. Please get in touch with us if you have any additional information or updates regarding the issue. Our Support Team is here to help you in any way we can, and we are committed to finding a solution as quickly as possible. support@nakivo.com Thank you for choosing NAKIVO. We look forward to hearing from you soon.

@Slawomir NAKIVO 10.10.1 is still unavailable at the Synology Package Center, and we have no ETA yet since we are awaiting approval from their end. However, installation may be available for certain devices via SSH; please provide us with the following information from the version/model of your NAS (a screenshot as attached may be useful).

@Leslie Lei Thank you for your patience. Unfortunately, it is not currently possible to configure "Forever incremental" and "Incremental with full" options within the same job schedule. This is because they are two completely different types of repository. However, we appreciate your feedback and have filed a feature request for this capability. We will consider it for implementation in future releases based on customer demand and other factors. In the meantime, please let us know if you have any other questions or concerns.

@Leslie Lei Thank you for your valuable contribution to the NAKIVO Forum. Your insightful post has been duly noted and has been forwarded to our esteemed Product Development team for thorough consideration. Such requests hold significant weight in shaping the future of our product, and we are committed to exploring its feasibility for potential implementation.

@Babis Regarding your screenshot, we see in the source tab of "Microsoft Office 365 - Mailbox Backup Job" that the root level "ArcwareMS365" account is selected. Thus, it will include all of the items inside this account. If you only want to backup Mailboxes, please unselect the "ArcwareMS365" account and only select the "Mailboxes" container. We are looking forward to hearing from you.

@Babis, the best way would be to generate and send a support bundle ( https://helpcenter.nakivo.com/display/NH/Support+Bundles ) to support@nakivo.com so our Technical Support team can investigate it and forward your feature request to our Product Development team for possible future implementation.

@Elia Please provide the community with an update regarding the resolution of your issue. Thank you.

@Elia Please, check the article below, Section 2: https://helpcenter.nakivo.com/Knowledge-Base/Content/Frequently-Asked-Questions/Backup-Repository/Extending-Backup-Repository-on-Virtual-Appliance.htm?Highlight=increasing We are looking forward to hearing from you.

@Elia, your information has been received and forwarded to our 2nd Level Support Team. We will follow up with you shortly. Thank you for using NAKIVO Backup & Replication as your backup solution.

NAKIVO Backup & Replication v10.10.1 is now available for download! This release delivers full support for the new VMware vSphere 8 Update 2, which introduced improvements to lifecycle management, GPU-based workloads, vCenter patching, DevOps and more. Download v10.10.1 now to ensure uninterrupted data protection and disaster preparedness for your vSphere 8.0 U2 workloads. Update now: https://www.nakivo.com/resources/download/update/

@Leij I would recommend you perform the following steps: - Edit the Job and set the Transporters to "Automatic" on the "Options" tab. Save a Job; - Edit the Job again, set the Transporters to "Manual," and set the required Transporter on the "Options" tab, save a Job. We are looking forward to hearing from you.

@Leij, your information has been received and forwarded to our 2nd Level Support Team. We will follow up with you shortly. Thank you for using NAKIVO Backup & Replication as your backup solution.

@slabrie The best way would be to generate and send a support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) to support@nakivo.com so our Technical Support team can investigate it and forward your feature request to our Product Development team for possible future implementation.

>>I ran a test, and it worked fine, except that all the old recovery points copied by the backup copy job in step #4 had their retention set to "Keep Forever." This happened when I deleted the copy job but told it to keep the backups. Is this the intended behavior? It all depends on the NAKIVO retention policy used to create the recovery points in the repositories. If a new retention policy is used, the recovery points on both the source and target repositories will expire. >>With 200 VMs, each having 9-11 recovery points, manually resetting the retention on 2,200 recovery points to fix this is not feasible. I understand why it might have changed when the backup copy job was deleted, but the Director wouldn't allow me to re-point the backup job until those copied backups were no longer referenced by another job object. I can use the "delete backups in bulk" to manually enforce my original retention policy, but that will take three months to complete the cycle. >>I discovered that detaching the repository before deleting the backup copy job (in step #5 above) will retain the original retention dates. I plan to use this process when moving my production data over in a few weeks. If the retention dates get messed up, I'll use the "Delete backups in bulk" functionality once a week to clean my repository storage. The new arrays have a much larger storage capacity, so leaving a few extraneous recovery points around for a few weeks shouldn't cause any issues. In this case, the best option is to use the "Delete backups in bulk" functionality. Thank you so much for your attention and participation in our community. We are looking forward to hearing from you.

@cmangiarelli, your information has been received and forwarded to our 2nd Level Support Team. We will follow up with you shortly. Thank you for using NAKIVO Backup & Replication as your backup solution.