VMware Virtual Machine Recovery with Dell PowerVault ME5 Snapshots
Wed, 10 May 2023 00:05:43 -0000
|Read Time: 0 minutes
Overview
Dell PowerVault ME5 storage platforms are well suited to support VMware workloads and simplify operations.
This blog highlights leveraging PowerVault native snapshots to recover virtual machines (VMs) in case of disaster or outage. The ME5 storage system can create multiple point-in-time snapshots of virtual volumes and these snapshots are treated like any other volume. The snapshots are read-writable when mounted to hosts.
How-To
Our source volume me5_ds1 is mounted on ESXi host s1244.
The datastore me5_ds1 is in vCenter, with the “VSI-Test02” VM.
To begin the snap process, log in to the ME5 GUI and start by adding data protection to the volume: Select Volumes > volume actions.
Once the volume is selected, configure the data protection type. In this scenario we are using local snapshots.
Select the option to create the snapshot immediately.
Review the Summary of the snapshot configuration.
Under the source volume me5_ds1, we now see that the snapshot is created.
View the properties of the snapshot.
In vCenter, let us simulate a failure by unmounting the source volume and removing the VM from inventory.
Next, we will mount the snapshot to the ESXi hosts. Select Snapshot > Volume Action > Mount Host.
From vCenter, add the snapshot volume to the host. Right-click Host and select Storage > Add Datastore.
.
We want to re-signature the snapshot to create a unique UUID.
Now the snapshot is mounted as a datastore.
To recover the VM, right-click the snapshot datastore and select Register VM.
Select the folder and select the vmx file.
After selecting and restoring the vmx file, the VM is running inside the snapshot datastore. At this point, we can storage vmotion this machine back to production storage.
Conclusion
Dell PowerVault ME5 is the new gold standard for entry-level storage, with blazing speed, high-capacity limits, and simplicity. PowerVault integrates seamlessly with VMware by delivering a platform that is secure, cost effective, and easily managed.
Related Blog Posts
Protecting VMware Workloads with PowerStore Metro Volumes
Mon, 09 Oct 2023 18:14:42 -0000
|Read Time: 0 minutes
PowerStore’s metro volume replication allows storage administrators to create a high availability shared SAN environment across PowerStore clusters. Metro Volume provides symmetric active/active data access to VMware environments for use cases such as: planned migrations, disaster avoidance, and proactive resource rebalancing.
PowerStore supports two different configurations with Metro volume access: non-uniform and uniform. In this blog, our configuration is non-uniform.
Here is our sample non-uniform configuration, where hosts only have access to its local PowerStore system:
Creating the Metro Volume
- Creating the metro volume session is a relatively simple process and involves a few clicks. Log into PowerStore Manager, select Storage, then select the volume (here, VMFS_Test-Demo), then select Configure Metro Volume.
2. On the Configure Metro Volume page, select the remote PowerStore to create the duplicate volume.
3. Now we see the volume switching to metro synchronous.
Creating the Metro Witness
Starting with PowerStore version 3.6, Metro Volume supports a witness server. The witness server is a third party that is installed on a stand-alone host. The witness observes the status of the local and remote PowerStore systems. When a failure occurs, the witness server determines which system remains accessible to hosts and continues to service I/Os. When configuring Metro Witness on a PowerStore appliance, you must generate a unique token.
Note: You must configure the witness on each PowerStore cluster.
1. The following is an example of using the generate_token.sh script to create the token JeBTPIFf:
2. After gathering the token, select Protection > Metro Witness to enter the Metro witness configuration details.
3. Enter the witness details, including the DNS or IP address and security token.
4. Confirm the witness settings.
5. Witness is connected to the metro sessions.
6. The metro session is synced, and the witness is now engaged.
Metro Volume is designed to give VMware environments the ability to operate synchronously without disruption. Metro Volume integrates seamlessly with vSphere Metro Storage Cluster, for our PowerStore customers who must avoid disaster/data unavailability.
For more information, see the following resources.
Resources
- White paper: Dell PowerStore: Metro Volume
- White paper: Dell PowerStore: Replication Technologies
Author: Jason Gates
PowerStore: Lifecycle Management with Virtual Storage Integrator
Thu, 05 Oct 2023 14:39:06 -0000
|Read Time: 0 minutes
The integrated lifecycle management is available starting with virtual storage integrator (VSI) version 10.3. The plugin will upload the code, perform a health check, and update the PowerStore system. PowerStore code version 3.0 or later will be needed to take advantage of this capability.
This blog provides a quick overview of how to deploy Dell VSI and how to perform non-disruptive upgrades of PowerStore systems with the VSI plug-in in vCenter.
Components of VSI
VSI consists of two components—a virtual machine (VM) and a plug-in for vCenter that is deployed when VSI is registered for the vCenter. The VSI 10.3 open virtual appliance (OVA) template is available on the Dell Technologies support website and is supported with vSphere 6.7 U2 (and later) through 8.0.x for deployments with an embedded platform services controller (PSC).
This chart shows VSI supported areas of operation for PowerStore:
Deployment
A deployed VSI VM needs 3.7 GB (thin) or 16 GB (thick) space on a datastore and is deployed with two vCPUs and 16 GB RAM. The VSI VM must be deployed on a network with access to the vCenter server and PowerStore.
When the VM is deployed and started, you can access the plug-in management with https://<VSI-IP>.
Register VSI plug-in in vCenter
A wizard helps you register the plug-in in a vCenter. Initial setup only requires that you set the VSI password for the internal database and supply the vCenter address with username/password. Multiple vCenters can be registered if they are in a linked mode group.
After the VSI VM is configured, it takes a few minutes for the VM to come online.
From the Dell VSI dashboard, select Storage Systems and the + sign to add the PowerStore system.
Perform a non-disruptive upgrade
VSI lifecycle management of PowerStore provides the following benefits:
- Upload the code bundle from the local device to PowerStore from the VSI plug-in to vCenter.
- Run a precheck after the bundle has been uploaded from the VSI plug-in to vCenter.
- Run the upgrade with the uploaded bundle from the VSI plug-in to vCenter.
The non-disruptive upgrade process with the VSI plug-in requires three steps:
- Upload the code bundle.
- Complete a pre-upgrade health check.
- Perform a code upgrade.
To perform the non-disruptive upgrade, do the following:
- From the Dell VSI dashboard, select the PowerStore system.
- After selecting the PowerStore system, select the Upgrades tab.
3. Under the Upgrades tab, select Upload package.
4. After uploading the code, select Run Health Check.
5. When the health check completes, kick off the upgrade process and monitor the status until complete.
Conclusion
Dell PowerStore extends the boundaries of mid-range storage with unmatched capabilities for enterprise storage. PowerStore integrates seamlessly with the VSI plugin. This system integration enables the orchestration necessary to deliver non-disruptive, streamlined PowerStore updates from within VMware vCenter.
Author: Jason Gates