NOTE TO READER: This post is a post from guest blogger Chris Lawless, VP of Product Management at Dbvisit.
If you have been reading this blog you know that my co-workers and I here at Dbvisit are passionate about Disaster Recovery (DR). We believe that every Oracle database should have a Disaster Recovery Plan (DRP) and a solution in place. As one co-worker recently told me… it is just common sense. We are also very involved in the cloud world. Many of our customers run their production databases in the cloud and many more run their standby DR systems in the cloud. Again… it is just common sense. So how can one get started?
Organizations should look at the different cloud vendors and see what is important to them regarding which vendor makes the most sense for them. It could be pricing, it could be having a managed database, it could be the ability to spin up databases from existing templates, it could be the location of the data center or a variety of other reasons. Most of the vendors out there have free trial accounts that will allow DBAs to experiment with their services. This can seem daunting at first but once you get past the initial vendor interfaces you then reach the familiarity of Microsoft Windows or Linux or the other platform that you are used to seeing. From that point, DBAs will feel right at home and it will be like working with another database on-premises.
Once you have your cloud set up you are ready to go. Simply treat that cloud server as your target for your standby database. If you are using Oracle Enterprise Edition that means setting up Oracle Data Guard and having the on-premises production database point to the cloud. If you are using Oracle Standard Edition that means Dbvisit Standby can transfer your data to the cloud. Each product works the same whether the database is on-premises or in the cloud. That is the beauty of all of this. There is nothing extra (besides the front interfaces to start your cloud databases) to learn or set up.
This is one of the easiest ways for DBAs to get their hands on experience with cloud providers without moving their production databases to the cloud. Of course it doesn’t end there. Having a standby database in the cloud is not the end. At this point it is imperative that it be tested. Can you switchover your database to the cloud? Have you ensured that the application is pointing to the right TNSNAMES? Have you documented all of the steps needed in the event of a disaster?
At Dbvisit, we are big fans of “test Test TEST”. Before putting anything in production, it is well worth testing things out. This means that DBAs should test Graceful Switchover and Failover in the cloud so that they are comfortable with the steps involved.
If you are thinking about moving from on-premises to the cloud, learn more about this method of DR and about the various vendors for cloud computing on the way. Get extra protection for that on-premises database, find out how easy it is to install and configure Dbvisit Standby on the Oracle Cloud and discover the instructions to make the leap to the cloud today.