@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!
I have done those steps, unfortunately the specific transport items are still greyed out.
EDIT: I found out that the items are greyed out, if the transporter has been configured with the "Enable Direct Connect for this transporter" option. Would you mind to explain the benefits of using this option + Automatic selection, vs unselecting this option and manually configure the transporter on the backup job level?
@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: email@example.com.