To use Virtual Volumes with Site Recovery Manager, you must configure your Virtual Volumes environment first. Prerequisites Follow the guidelines in Before you enable Virtual Volumes in the vSphere Storage guide. What to read next Procedure Register Storage Providers for Virtual VolumesYour Virtual Volumes environment must include storage providers, also called VASA providers. Typically, third-party vendors develop storage providers through the VMware APIs for Storage Awareness (VASA). Storage providers facilitate communication between vSphere and the storage side. You must register the storage provider in vCenter Server to be able to work with Virtual Volumes. Create a Virtual Volumes Datastore You use the New Datastore wizard to create a Virtual Volumes datastore. Review and Manage Protocol EndpointsESXi hosts use a logical I/O proxy, called protocol endpoint, to communicate with virtual volumes and virtual disk files that virtual volumes encapsulate. Protocol endpoints are exported, along with associated storage containers, by the storage system through a storage provider. Protocol endpoints become visible in the vSphere Client after you map a storage container to a Virtual Volumes datastore. You can review properties of protocol endpoints and modify specific settings. Change the Path Selection Policy for a Protocol EndpointIf your ESXi host uses SCSI-based transport to communicate with protocol endpoints representing a storage array, you can modify default multipathing policies assigned to protocol endpoints. Use the Edit Multipathing Policies dialog box to change a path selection policy. Parent topic: Using Virtual Volumes with Site Recovery Manager
