Sometimes, when a new version comes, it seems that it has not been tested enough because I usually find some bugs in it. They have changed the way the product is licensed, and there is a lot of confusion. Its licensing has become complex since last December. Legacy systems should be virtualized, and if they're virtualized, then the backup is not an issue with Veeam, but some customers like the physical setup, and they don't want to have it virtual." "The Cloud version is not ready, they need maturity and ease of deployment in terms of management." "Its licensing needs to be improved. They don't support physical workloads that are really old, which a major challenge, but they do have a point. The other not so major thing is that they don't support legacy systems because Veeam is a new company. Veeam Backup Replication should also support the automation of Nutanix backups from the backup server, not from the proxy.
Currently, we install the plug-in inside Oracle VMs and then use crontabs to handle the task schedule on each machine for scheduling the backups.
We should be able to schedule, control, and deploy them from the backup server rather than relying on scripts and/or the system you are backing up to perform the backup. In addition, we should be able to handle the automation of Oracle backups from the backup server. It would be great to have agents for Linux be cluster-aware, just like the Windows agents. "There is a lot of room for improvement, but the primary issue we have is that it's not built for the cloud." "Veeam Backup Replication has agents for Linux, but they are not supporting Cluster Shared Volumes.
0 kommentar(er)
