This is a quick script, SVT-Fed-Capactiy.ps1, I put together using Powershell and the SimpliVity REST API to report available, free, and used capacity information for OmniStack Clusters in a SimpliVity Federation, and the OmniStack hosts in each Cluster.
Tag Archive: SimpliVity
This is a White Paper I worked with SimpliVity Product Management on to provide details on how to implement and operate a Windows Failover Cluster on SimpliVity OmniStack systems. It also details how availability is provided across different failure scenarios
SimpliVity Backups are Policy-based and VM-Centric. SimpliVity Backup Policies automate the protection of virtual machines in order to meet Recovery Point Objectives (RPO). Full virtual machines or individual files/folders with virtual machines can be quickly restored to the point in time when the backup was taken. This post provides a solution for using the REST API to schedule SimpliVity backups outside of the standard options available when creating backup policy rules.
Policy based SimpliVity backups have a retention period defined in the backup policy. When the retention period expires the backup is removed from the system. When a Manual SimpliVity Backup is taken, no retention period is set and the backup will never expire. This post provides some details on how to locate Manual SimpliVity Backups using the vSphere Web Client or the SimpliVity REST API.
In a two node SimpliVity deployment there is no requirement for 10 GbE switching. The SimpliVity nodes are directly connected to provide connectivity for the SimpliVity Data Virtualization Platform (DVP) between nodes. As the environment grows adding addition SimpliVity nodes or compute nodes may be required. This requires 10 GbE switching for SimpliVity Storage traffic between SimpliVity nodes within the same datacenter and/or between SimpliVity nodes and compute nodes.
Great time at VMworld 2016 with the SimpliVity Team!!! Had a fantastic time with the SimpliVity team talking with our partners, current customers, future customers, and the AWESOME people in the VMware community. Even some great chats with competitors. VMworld 3 word: Educational, fun, exhausting… 🙂
VMworld 2016 is just a little over a week away. I am very much looking forward to it. Most of my time at VMworld this year will be spent at the SimpliVity Booth, #1911, in the Solutions Exchange. Looking forward to meeting new folks, catching up with many who I have not seen in a while (since last year), drinking lots of coffee, and talking about how SimpliVity’s continues to provide the most innovative and complete hyper-converged infrastructure solution.
In this post I am going to look at the two most common methods: using vMotion to migrate both the storage and running state of the vCenter virtual machine to a SimpliVity host, and using Storage vMotion to move storage and then removing and re-adding the vCenter virtual machine to inventory on a SimpliVity host.