Вы находитесь на странице: 1из 5

SimpliVity Demo Script - v0.

9
Elias.Benarroch@VM-2020.com February, 2014

Overview of UI. Simplivity tabs of federation and Datacenters

First I will provide you with an overview of our UI then we will get into the product functionality. Top views as well as granular views have SimpliVity tabs which is where the focus of this demo will be. What you are seeing is the Federation view. Here you can see 2 separate DCs. At the top level you can see the capacity utilization which I will come back in about a minute or so to explain. But right below that you can see all of the VM that are running within this datacenter. As I scroll down we are going to be using this VM named VMNAME for our demonstration. This VM has 466GB of used capacity Below we have the datastores that have been created for this datacenter and to the left you can see the OmniCube Systems that form this datacenter within the overall Federation Now back to the top. As you can see, VMware believes that 8.0 TB of data has been consumed on disk. If you follow my mouse all the way to the right you can see that I have effectively only consumed 1.6TB of physical disk. This means that based on our inline deduplication, compression and optimization that 6.4TB of data was never consumed on disk. While this is extremely efficient, there is one more important component that is a derivative of our technology. In fact, because data is being deduped and compressed, inline 6.4TB of Write IOPS have also never occurred. This may seem unimportant however consider that the highest cost of a storage infrastructure is supporting IOPS and not capacity and Simplivity is unique in the industry at delivering this specific functionality. So let me show you how So we are going to go ahead and invoke a SimpliVity move operation. We will be using the VM I spoke of earlier which has about 466 GB of used capacity. Lets pull the SimpliVity Clone function from the VM MarioWin02 o As you can see we automatically date and time stamp the operation and the task of adding the VM to inventory is practically automated. This would have been the next natural step and administrator would have had to do The SimpliVity Clone process of this 466GB VM has started at about 33%, as displayed on the recent tasks below. The task is completed and we now wait for vCenter to register the VM.

Federation View

DataStores

Data Usage and Deduplication

Clone a VM and power up

As you can see, the cloning process is very fast. Now lets power up the VM

View changes in Capacity utilization after Clone

Next lets go back to the capacity utilization. VMware believes that now 8.6TB of data has been consumed on disk. Once again just follow my mouse all the way to the right and as you can see there has not been any data written physically to disk. The VM is on, up and running fully deduped and compressed. Any questions so far?

OK now lets look at the view from a VM perspective: VM view analytics and used Capacity As you can see there are some analytics about this VM, IOPS and MB through etc. As you can see this VM has 466 GB of used capacity Below you are seeing every backup for this particular VM. SimpliVity Backups Every backup that we do is a full BU. It is NOT an incremental or differential. Inline dedup and compression enables these backups to occur VERY fast as you will see during our demonstration There is a policy tied to this particular VM. Lets go ahead and create a new BU policy We will name the policy. Keep in mind that once created this policy can be shared throughout the Federation. Now lets create our Rules. Rules determine the Frequency, destination, retention start and end times for a particular back, what days of the month you want that backup to run as well as whether or not this will be an application consistent backup. Creating Backup policies Lets create our first rule, a simple rule. Lets create a second rule. Now keep in mind we can create up 16 rules here, however we will just create a few for demo purposes. Lets create a final rule and this could be an archive rule. Please keep in mind that when we pick a remote datacenter, we are not configuring any dedicated backup pools, we are not shutting off PCIe cards, we are not telling you which backup server, LUN, or IP address. We are just giving the datacenter option. This is important if you ever decide to change the underlying infrastructure at any remote datacenter you never have to change your backup policy Ok once done we hit close and apply as the new backup policy. Based on our Global Federated Architecture that we spoke of earlier, if now I want this new policy applied to any VM I can do so. Lets just pick another VM and apply the newly created backup policy to it. This applies to any VM within the Federation. So from this point forward this VM will be protected based this new policy we created however if you want to invoke a manual backup this is how you would do it. From the VM, right click and choose SimpliVity Manual Backup. We automatically date and time stamp the backup as we want it to be unique. You can name it whatever you want as long as it has a unique name. Lets pick the destination to a remote datacenter and click backup. The backup will start. In a matter of seconds I just backed up this 466GB VM from one DC to another. This was a full backup. So now lets restore a VM. Before we do so lets first walk through the traditional method to restore a VM with standard backup applications: You spawn the backup application, crawl the catalog, pick the VM restore the VM, once completed add VM to inventory then you finally turn on the VM We believe these are too many steps. This is how a restore should look like: Right click on the backup, click restore, decide if you want to rename the restore, and click

Apply new BU policy to a VM in another DC

Manually BU a VM to a remote DC

Restore a BU from a remote DC

restore. Now keep in mind that we backed up this VM to a remote DC; which can be seen in the backups list. Now I will restore it back to its original DC. Once restored VM will automatically be added to inventory so you can proceed with your restore functionality. There we restored of a VM from a remote DC and automatically added to inventory. Lets go ahead and power it on.

Now lets go back and see what our capacity effectiveness looks like: View Capacity after Clone and BU I have now used about 900GB of data: first with the CLONE and now with a RESTORE. VMware continued to show that a lot more data has in fact been consumed. Follow my mouse all the way to the right and as you can see no physical data has been written to disk. This restore is once again running fully deduped and compressed, reducing write IOPS Any questions so far? Next we will show you what a SimpliVity Move looks like We originally developed this for a specific client that has developers around the globe and required that they develop on the same VMs. With our technology we facilitated this which essentially allows us to move VMs between DCs very fast and efficiently. We also determined that this is also a fantastic feature to allow for datacenter migrations. We have a partner that acquired a client and needed to replicate and migrate about 25TB of data and 50 VMs. We deployed our technology locally so they could migrate VMs to OmniCubes, then with backups and moves we were able to move an entire DC with less than 2 hours of downtime. This would have traditionally taken over 30 days to accomplish with at least 2 full weeks of downtime So how do we do this? Lets go ahead and create a quick clone of this same VM Once completed lets go ahead and right click on VM and invoke a SimpliVity Move. We will automatically remove from inventory on primary DC and re add it to destination DC. AS you can see this is done VERY fast. Lets go ahead and power on the VM. Any questions so far? Now lets show you how to create, resize and manage datastores with OmniCube inside our Federation with more than one datacenter. DataStores With SimpliVity you can manage your entire infrastructure with our SimpliVity plugin within vCenter. You can see we are running 2 separate datacenters. At a high level the Free usable space as well as the consumed space is visible. Space, Capacity, and IO metrics and Efficiency Under the logical capacity you are also seeing our De-duplication, Compression, and overall efficiency in with our federation. This efficiency translates not only into capacity savings but it also in Write IO operations that did not have to occur as a result of our deduplication and compression. As we drill down into the datacenter view, in this case the London Datacenter you can see all of

Move a VM

the VMs running, as well as the datastore associated with London. London has a datastore that is 4TB in size. In the San Francisco Datacenter, although the capacity numbers are slightly different all of the functionality is identical We will move to London at this time and from there we will create a datastore in Both London as well as San Francisco, without leaving the London datacenter. As we click in our Configuration wheel you can see all of the available options you can have in terms of functionality but for today we will show you only how to create, resize and delete a datastore From this menu let click on Create Datastore In the London datacenter I am going to create a 2 TB datastore: Next, we will name that datastore sample-1 Creating a DataStore

Apply a default backup policy to that datastore.


To learn more about creating and managing our VM centric backup policies please see our other OmniCube videos entitled VM Centric Back up and replication with SimpliVity

Next we will determine the size of the datastore. We will just create a 2Tb store and finally click create. Within a few seconds you can see the tasks taking place below. All of the actions that would otherwise be a manual processes such as creating datastores, Scanning, presenting them to all the individual hosts is an automated process managed by Simplivity. Datastore is now ready to ingest new VMs or migrate others. Next we will do that same thing but instead will create a Datastore in San Francisco from London From this menu let click on Create Datastore From the pull down menu change it to San Francisco. We will create a 2 TB datastore in San Fran remotely We will name that datastore SanFran_02 Apply the same backup policy to that datastore. We can create as many backup policies here as you want. Next we will determine the size of the datastore. We will just create a 2Tb store and finally click create. Datastore is now ready to ingest new VMs or migrate others. Within a few seconds you can see the tasks taking place below. Once again all of the actions that would otherwise be a manual processes such as creating datastores, Scanning, presenting them to all the individual hosts were automated by Simplivity We just created 2 separate datastores on 2 different datacenters from one location without ever leaving our SimpliVity Tab inside of vCenter Simple

Create a DataStore in Remote DC from current DC

Simplivity Datastore summary

Next we will resize each of the datastores we have just created: In the London Datacenter I will right click on the 2TB datastore we just created, select Online Resize and increase that datastore to a total of 3TB by either typing it in or using the up and down arrows to increase or decrease the datastore. We will increase this to 4TB, select resize and quickly you can see the action being completed I am going to go ahead and do the same thing for the SanFrancisco Datacenter. Right click on the datastore change the capacity to 3TB and click resize Now lets assume that you need to delete these same or any other datastores. Obviously you need to make sure that any required data has either been migrated to other datastores before deleting Since there is no data I can choose then from this screen to delete the datastore or go the our plug in TAB and do it from there. I am going to choose the latter. Deleting DataStores Within the London datacenter and within the datastores view I can just right click on the datastore I want to delete, in this case I am going to pick the ones we just created named sample1 and select delete. Pop up window essentially telling you that you are about to do a significant activity ! Select delete. This will delete the datastore from the London datacenter. I will do the same thing for the San Francisco Datacenter There its done !

Resizing Datastores