What is our primary use case?
We implemented Nakivo Backup & Replication as a backup system for our customer. It supports their VMware vSphere environment.
The environment is made up of one director, one onboard transporter, one direct SAN repository, and for offsite backup, it has one transporter and one SAN direct repository.
How has it helped my organization?
Nakivo gives users confidence in knowing that if something happens with their application server, exchange server, or other applications, they can recover it easily and quickly.
The Nakivo scheduled job also provides backup verification that will help us to ensure the backup is running properly and is truly recoverable.
What is most valuable?
One of the key features is the ease in recovering individual files. In the customer environment, often accidentally, files are removed or broken. With Nakivo they can easily be recovered.
Another key feature is the ability to install multiple transporters to increase the backup duration for multiple backup jobs at one time.
What needs improvement?
We want the backup job to consume fewer resources, as the utilization is very high if we choose the "best compression' option.
There was a problem we found regarding the repostory. When we enable the schedule for space reclaimation, once the schedule is trigerred the reclaimation will detach the repository but after 1 week we found that the repository is on detach status so we should detach it manuallu. We didn't know actually the reclaimation is on progress or already finsihed
For how long have I used the solution?
Approximately two years.
What do I think about the stability of the solution?
The stability is good. Provided the overall component is ok, the job runs normally and quickly.
What do I think about the scalability of the solution?
It's good enough that the software can be scaled up and scaled out, depending on your requirements.
Disclosure: I am a real user, and this review is based on my own experience and opinions.