The cost saving dilemma

The cost saving dilemma

Every IT team is looking for ways to cut costs. How can this be done without affecting the level of service to the business owners?

In my previous blog, I discussed how enterprises are compromising between quick recovery time (minimal RTO) and Zero Data Loss (RPO=0). Which of the two is more critical to the business owners? There is no one correct answer and it was very challenging, until Axxana arrived on the scene, to maintain both. Organizations had to choose, based on the nature of the application, whether Zero Data Loss was more critical than potential down time when switching to the disaster recovery site after a serious failure at their main site. We already established the fact that with Axxana, there is no need to compromise anymore. Axxana’s Phoenix System for Oracle cuts down time to the absolute minimum, by maintaining full application consistency and lowering data reconciliation efforts to zero.

Obviously, this dilemma was more critical in financial organizations that deal with transactional applications. Traditionally, these financial organizations had to resort to using synchronous replication between data centers to protect against loss of data, regardless of the cost involved.

Dilemma

In today’s economy, when every IT department is requested to design for lowest TCO and reduced OPEX, questions such as the following, pop up; Do all the applications require RPO=0? When has the last disaster that justified this huge investment in synchronous replication occurred?

We see more and more enterprises that are considering moving their Tier II applications from High-end Storage systems with synchronous replication to alternative solutions with asynchronous replication. This change represents significant cost savings in both CAPEX and OPEX but also impacts the level of service offered by the organization to the application owners. These Tier II application owners are being forced to choose between cost savings and a significant increase in the risk of down time and data loss.

Since we are discussing Tier II applications, it might be common to argue that RPO=0 isn’t needed for this type of applications. The question is, why settle for less if you can have the best of both worlds? Enjoy both cost savings, by moving to asynchronous replication, and still maintain zero transaction loss!

How can this be done?

Well, with the Phoenix System for Oracle, organizations can do just that — using any type of storage system with whichever replication solution they choose and still maintaining Zero Transaction Loss, database consistency and the quickest recovery.

Sounds impossible?

Please watch the following video, explaining how it can be done with our new and innovative solution – http://www.axxana.com/resources/videos/#vwHstEqris0

Dreamer

In addition, Oracle has published a very interesting white paper on how to achieve cost effective zero data loss with Oracle Active Data Guard Far Sync and Axxana. You may find it here: http://www.oracle.com/technetwork/database/features/availability/partner-maa-155391.html