Leaderboard

Alright, let me explain my scenario I have a couple of Esxi hosts with 6 VMs on each I have 2 NFS Linux Storages ( storage1 an storage2) and nakivo running in one of those storages (storage2) locally Right now, if I want to backup a VM, it goes something like this: VMs get snapshotted, and new files are created on their respective storages Nakivo starts copying the files to the repository, BUT, its goes like this storage1 -> esxi host -> nakivo repository (storage2) storage2 -> esxi host -> nakivo repository (storage2) Instead of going directly like this storage1 -> nakivo repository storage2 -> local nakivo repository (without using the network at all) So, right now, nakivo is creating backups at around 50-60MB/sec but they are using all the bandwidth available on the esxi hosts, completely wrecking their performnce while backups are running. wouldn't make sense for nakivo to pull the snapshot files directly from the esxi storages? is that posible? maybe adding the storages directly on the nakivo admin panel and indicating were each VM is stored?

Do the "Self-healing" and "Verification" tasks guarantee that the backups are restorable?

Hi, I installed nakivo on a CnetOS7 Linux machine. Next I want to create the Backup of this machine. Add the transporter works, but after that: An internal error has occurred. Reason: There was an error when collecting the host info. Error: Internal error (PhysicalDiscoveryServiceException). Machine: CentOS7 8GB DDR3 RAM Two RAID1 build with Linux Softraid SSH, Management Port, Transporter Port are opened in firewall.