- Notes, cautions, and warnings
- Introduction
- Revision history
- Initial configuration and setup
- Performing common tasks
- Displaying system information at a glance
- Managing block storage
- Protection domains
- Fault sets
- Storage data servers
- Storage pools
- Acceleration pools
- Devices
- Volumes
- NVMe targets
- Hosts
- Managing file storage
- Overview of configuring NAS servers
- About file system storage
- File protection
- Create a protection policy
- Create snapshot rules
- Create a snapshot
- Assign a protection policy to a file system
- Unassign a protection policy
- Modify a protection policy
- Delete a protection policy
- Modify a snapshot rule
- Delete a snapshot rule
- Refresh a file system using snapshot
- Restore a file system from a snapshot
- Protecting a block storage environment
- Snapshots
- Create snapshots
- Overwrite volume content from a snapshot
- Set bandwidth and IOPS limits for snapshots
- Lock and unlock snapshots
- Delete snapshots
- Map snapshots
- Unmap snapshots
- Increase the size of a snapshot
- Migrate a snapshot vTree
- Pause snapshot vTree migration
- Roll back snapshot vTree migration
- Set snapshot vTree migration priority
- Snapshot policies
- Remote protection
- Extract and upload certificates
- Journal capacity
- Add a peer system
- Restart the replication cluster
- SDRs
- Replication consistency group
- Replication direction and mapping
- Create an RCG
- Map RCG target volumes to hosts
- Unmap a host from RCG target volumes
- Set the target to inconsistent mode
- Set the target to consistent mode
- Modify RPO
- Add a replication pair to an RCG
- Pause replication for an RCG
- Resume replication for an RCG
- Create a snapshot of an RCG volume
- Add an RCG snapshot policy
- Perform a failover
- Reverse replication
- Restore replication
- Test Failover
- Stop a failover test
- Freeze an RCG
- Unfreeze an RCG
- Activate an RCG
- Terminate replication in an RCG
- Delete an RCG
- Pause creation of an initial copy
- Resume creation of initial copy
- Set copying priority
- Unpair from RCG
- Snapshots
- Performing lifecycle operations for a resource group
- Deploying a resource configuration in a resource group
- Basic tasks
- Deploying a resource group
- Adding an existing resource group
- Updating a resource group with new firmware and software
- Viewing a compliance report
- Entering and exiting service mode
- Replacing a drive
- Replacing NVDIMM node or battery
- Reconfiguring MDM roles
- Migrating vCLS VMs to shared storage
- Adding components to a resource group
- Resize a volume
- Removing resources from a resource group
- Adding NVMe/TCP storage access
- Additional resource group management tasks
- Basic tasks
- Preparing a template for a resource group deployment
- Basic tasks
- Additional template management tasks
- Deploying a resource configuration in a resource group
- Managing resources
- Basic tasks
- Additional resource management tasks
- Monitoring events and alerts
- Configuring system settings
- User management
- Repositories
- Getting started
- Networking
- Events and alerts
- License management
- Security
- Serviceability
- Software upgrade
- PowerFlex Manager user interface reference
- Additional administration activities
- Retrieving logs for the PowerFlex nodes
- Retrieving logs for PowerFlex components
- Retrieving additional PowerFlex logs
- Enabling audit logging
- Managing storage devices using CloudLink
- Understanding NVMe over TCP load balancing
- Managing NAS server configuration
- Migrating to NVMe/TCP on ESXi
Dell PowerFlex 4.5.x Administration Guide
Migrating to NVMe/TCP on ESXi
This section contains instructions for migrating a VMFS datastore from SDC to NVMe/TCP using Storage vMotion.
PowerFlex offers the following options for migrating from SDC to NVMe/TCP on ESXi:
- Online migration using Storage vMotion (VMFS only), as described in this section
The standard way of using Storage vMotion to move storage now also supports switching protocols by migrating to a new Datastore.
- Offline conversion (VMFS only)
Offline conversion is a new option for converting an existing VMFS datastore from SCSI (SDC) to NVMe/TCP without having to copy all the data over the network. This option is covered in this KB: https://www.dell.com/support/kbdoc/en-us/000213232
Dell Technologies recommends using VMware Storage vMotion to migrate data from a volume that is presented by SDC to one presented by NVMe/TCP.
This migration is intended for VMDK (noncluster) customers who want to convert their SDC to NVMe/TCP.
Linux environments, ESXi clusters, and RDMs are not included in this section.
Requirements
See the following VMware product documentation links for information about Storage vMotion requirements and limitations: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-A16BA123-403C-4D13-A581-DC4062E11165.html
See the following VMware product documentation links for information about requirements and limitations of VMware NVMe Storage: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-9AEE5F4D-0CB8-4355-BF89-BB61C5F30C70.html
See the following VMware KB article for more details about Storage migration (Storage vMotion), with the virtual machine powered on: https://kb.vmware.com/s/article/1005241
Ensure that you satisfy these requirements before you begin the migration:
- Ensure the ESXi version is 7.0u3 or later.
- Ensure the PowerFlex version is 4.5 .x.
Workflow
The following steps summarize the workflow that you need to follow to migrate fro SDC to NVMe/TCP using Storage vMotion:
- Create and map a new volume of equal or greater size than the current VMFS datastore via NVMe/TCP to the same host.
- Scan for the newly mapped volume.
- Create a new datastore on the NVMe/TCP volume.
- Perform the standard data migration using Storage vMotion by using a non-disruptive process.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\