Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

NetApp OnCommand Workflow Automation in an Oracle environment

0 (0 Likes / 0 Dislikes)
Hello and welcome to the latest OnCommand Workflow Automation video where we will focus on orchestrating clustered Data ONTAP. This video covers creation of a new Oracle gold environment, creation of a backup configuration leveraging Snap Creator, and cloning out an entirely new Oracle environment. First, we'll create our Oracle gold environment. Logging into OnCommand Workflow Automation, we are placed in the WFA Portal where we are shown all of the workflows we are allowed to initiate. Since we want to manage our Oracle applications, we'll select our Oracle Application Management category. This helps limit the workflows we see to 4 workflows, and we'll select the create new Oracle gold environment for cloud and clustered ONTAP. Clicking on the workflow we bring up our user inputs. The first thing we can enter is our Storage Information. We can select the cluster we want to use and select an existing Storage Virtual Machine on that cluster, or we can identify a new Storage Virtual Machine (SVM) to create. In this case, let's create a new SVM and call it Oracle01. Now let's expand the Storage Networking section. We see we have default inputs already pre-populated for us. Since we are creating a new SVM for our application we can identify the IP address for the Data Logical Interface (LIF). We can also select to create a Management Interface to use with Snap Creator. Since that is what we want to do, we'll leave the check mark in the box. The rest of the inputs match our defaults so we'll leave those "as is". Looking at the Application Information we have pre-populated user inputs to make things easier. This workflow creates a new virtual appliance in our VMware environment in this case, the Demo1 environment. Our new application will be created using the application name and Oracle System ID. Since we are using a workflow, we know that our volumes will be provisioned using our standards and best practices. So we only need to specify the size of the volumes, and how many volumes of each type we would like to create. Let's create a new application of "oracle_demo" and we're done with our inputs, so let's click on execute. The first action of the workflow is to create a new virtual appliance or vApp for our application, based off of a pre-defined template. Once the vApp is created, the Virtual Machine and vApp need to be connected to a network. Once our network configuration is in place, we need to start the vApp so we can continue with the other tasks of the workflow. The next step is the creation of a new SVM as well as configuring it with the necessary NFS options required to run our Oracle application. The workflow will also enable the default NFS export policy in addition to creating a new export policy specifically for the application. The workflow also creates new Management and Data LIFs for the SVM per our user inputs. The volumes are provisioned per our best practices, and to the size we requested. Next the workflow creates DNS records for our new vApp. Since we want to bring up the application as part of this workflow, WFA will initiate a custom script that is on the Virtual Machine in order to configure the storage on the host. Once the script configures the hostname and DNS information it will mount all of the newly provisioned storage to the host. The last step of the workflow is to restart the vApp to bring up the environment. We've successfully deployed a new golden Oracle vCloud environment leveraging clustered Data ONTAP. Now that we've set up our Oracle Environment, let's set up a new backup configuration leveraging Snap Creator. Since we're still in OnCommand Workflow Automation and in our Oracle Application Management category, let's just select our workflow to 'add Snap Creator Oracle backup capabilities' We can provide our Storage Information. We'll use the application name, Oracle SID, and management interface information from the Oracle Environment we just deployed. We then have to identify the Snap Creator server we want to use and since this is Oracle, we need to add a check mark in order to enable the agent. Enter the fully qualified domain name for the Oracle environment just deployed, select the Snap Creator backup policy we want to use and click on execute. The workflow creates a new Snap Creator profile based on the SVM name, creates a new backup configuration dedicated to the application updates the Snap Creator agent configuration to allow the Oracle database to be placed into hot backup mode, and updates the Snap Creator policy schedule configuration. The workflow also discovers all of the volume for our application, so we can perform actions against them in our workflow. Next the workflow creates a new Snap Creator role for our SVM and assigns that role to a new user The Snap Creator configuration is then updated with the application volume and configuration details discovered earlier and the application backup is added to Snap Creator. We've successfully added the Snap Creator backup capability to our golden Oracle database environment. The next demonstration let's you see how easy it is to clone an Oracle environment. We are still in WFA and in our Oracle application management category, and we'll select the workflow to "clone and configure an Oracle environment". The workflow identifies the customer information it sees in our environment, and we can specify the Application Name and the Oracle SID we wish to clone, and the new Oracle SID we wish to create. The workflow will find all of the applicable storage objects for our environment based on the naming standards employed by the workflow. That's all, so let's click execute. Since we're creating a new environment the first step is to create a new virtual appliance (vApp). Next we connect the vApp to the network we identified in the user inputs, and start the vApp and virtual machine. Once the virtual machine is started we create a new export policy for our cloned environment. The workflow then creates a new Snap Creator backup based on the configuration we created previously. After a new temp volume is created for the new en01 environment, each of the application volumes is cloned using the backups we created in the previous step and exports each of the volumes after they've been cloned. After the volumes have been cloned and exported, the workflow updates DNS for the newly cloned environment, configures the storage on the host by leveraging the custom perl script, then restarts the vApp to bring everything up and online. To recap, we saw NetApp's OnCommand Workflow Automation quickly provision out a new golden Oracle vCloud environment leveraging clustered Data ONTAP. Add a new backup configuration, with Snap Creator, to the golden Oracle environment, and then deploy a cloned Oracle vCloud environment based on the golden Oracle environment AND it's Snap Creator backup configuration. Pretty cool, right? Wondering where to go for more information? Visit the OnCommand Workflow Automation community site. Go to and click on the Workflow Automation space. You will find additional documentation, videos, examples, discussions, and much more to get started. Thank you very much, we hope you found this helpful. Have a great day.

Video Details

Duration: 7 minutes and 34 seconds
Country: United States
Language: English
Producer: Kevin Hill
Director: Kevin Hill
Views: 155
Posted by: kristina.brand on Jan 6, 2014

This OnCommand Workflow video includes three demos on how to create a new Oracle gold environment, backup using Snap Creator and clone a new environment.

Caption and Translate

    Sign In/Register for Dotsub above to caption this video.