Please share with the community what you think needs improvement with Oracle Data Guard.
What are its weaknesses? What would you like to see changed in a future version?
One thing that can be improved is the GUI. It would be good to have a very nice GUI to easily configure and administer, providing different presentations to the database administrator. The feature that can be included is the integration with third-party monitoring systems, that is, monitoring systems from other vendors, not only from Oracle.
I'm not really sure about what needs improvement because we use all Data Guard's features successfully. Pricing is expensive and can use improvement.
The pricing of the solution is quite high. They should do what they can to bring it down so that it is more reasonable for customers like us. The response times for technical support can be quite slow. They should work to lower these wait times so there are fewer delays in assistance.
Oracle is not easy to implement, and you cannot find clear documentation on the internet or, unfortunately, on the Oracle website. You have to do a lot of research yourself and spend a lot of time seeking out all of the best documents that are related to Oracle on other websites. If they could create more documentation and improve their library of resources, it would be very helpful. The IP implementation and maintenance are a little bit hard to manage across Oracle solutions, including Oracle Data Guard.
When the data replicates into the standby database there is a possibility of having a microsecond amount of data loss. The data loss occurs when there is a network disconnection between the primary and secondary standby database located in the data centers or if there is a crash in the primary database. The data is generated on the primary database which is configured to the standby database to duplicate it on a real-time basis. So if there is a system crash or disconnection and in the time it takes to get it back up, you can lose a microsecond amount of data. When I experienced a small crash, I compared the data between the primary database and the standby database and found that there was a small difference in the amount of data. Not all of it was replicated or backed up. It creates issues with synchronizing the data. Because the focus in Data Guard is in the backup and restore, there hasn't been much with the interface. In the next release, if there could be more focus on the interface to include add-on features that would be an added advantage going forward.
It is a rather complex solution, so it could be more user-friendly.
Once you get used to it, you get to know what to do when certain things happen. However, for a person who's just jumping into it, the management of it and how to implement it probably would be something that could be improved upon. The GUI could be better.
The database administration needs improvement. With Oracle, we have a lot of features for administrating data, but it might be too many. It needs to be simplified. It should be automated. Looking at Enterprise Manager, there are too many KPIs in place. Directly on-site, we do not need to choose all of them. Administration, generally speaking, needs to be improved. Oracle should also continue to simplify the upgrade using Data Guard. We have already seen reduced outage timing any time we are doing upgrade, so maybe they are heading in that direction, but it can always be improved.
A disadvantage is that the available disk space must be doubled. This is because Data Guard is made of two databases, one primary and one as a standby running permanently. We must pay the Oracle license on the second server. For every standby server you have, you must pay a licensing fee, which is the main disadvantage.
If you were talking to someone whose organization is considering Oracle Data Guard, what would you say?
How would you rate it and why? Any other tips or advice?
Currently using R1Soft and have major issues. We need the software to work with OVM, Linux, Windows, Sql server, Exchange, and Sharepoint. We also need bare metal recovery functionality.