Overall Satisfaction with Druva inSync
We use Druva Phoenix across the whole organization. The scope of application is 3 of our file servers. It has been operating without any major problems so far, and backup and restore can be operated without any problems.
We operated many servers on-premises. The backup also used on-premises storage and backup tape. By changing to Druva Phoenix, our work cost for backup and restore can be reduced.
- Everything is completed in the cloud. I can operate all the things from my desk, and I don't need to go to the server room anymore. I can do it even I go outside or at home if needed.
- Operation is very simple, both the setup agent and backup schedule and restore.
- Admin console is only in English, and I'd like to use my local language (Japanese).
- We need to purchase backup storage in advance, but it is little complicated currently around how many volumes we used before and how many we can use in the future.
- Reduced IT working cost for backup and restore operation by being able to operate whole function in the cloud.
- No need to purchase hardware, etc. regarding our backup solution (e.g. servers, tapes, backup software, licenses).
- The cost of solution seems a little bit high against on-premise backup solution if we are using Druva Phoenix long term. But, this does not include human cost, so cost merit would need to be thought of from all perspectives.
When I inquired to Druva Japan, the country manager's response was very quick. The solution is adapted to what we want.
If cloud backup is acceptable per corporate IT policy, I think it is the best solution for backup and restore.
Druva Data Resiliency Cloud Feature Ratings
Druva inSync Support
In Japan, a support company is operating for solution support. I sometimes ask them and they always reply with an exact answer.