This is one stop global knowledge base where you can learn about all the products, solutions and support features.
This sheet lists all of the common Site Recovery Manager management or recovery operations and the relevant SRA operations initiated by them. The location of the respective log for the SRA operation is listed, is one of the following:
The SRM logs are located at:
/var/log/vmware/srm/
The SRA logs are located at:
/var/log/vmware/srm/SRAs/sha256{RandomCharacters}
SRM logs are located at:
C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\vmware-dr*
SRA logs are located at:
C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\SRAs\purestorage\
The SRM logs are located at:
/var/log/vmware/srm/
The SRA logs are located at:
/var/log/vmware/srm/SRAs/sha256{RandomCharacters}
SRM logs are located at:
C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\vmware-dr*
SRA logs are located at:
C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\SRAs\purestorage\
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
SRA Discover |
QueryInfo |
Initiating SRM server |
↓ |
QueryCapabilities |
↓ |
↓ |
QueryConnectionParameters |
↓ |
↓ |
QueryErrorDefinitions |
↓ |
↓ |
DiscoverArrays [i] |
↓ |
↓ |
DiscoverDevice [ii] |
↓ |
↓ |
QueryReplicationSettings [iii] |
↓ |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Arrays |
DiscoverArrays |
Initiating SRM server |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Arrays |
DiscoverArrays |
Initiating SRM server |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Devices |
DiscoverDevices |
Both |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Devices |
DiscoverDevices |
Both |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Synchronize Storage |
QueryReplicationSettings [iv] |
Protected |
↓ |
SyncOnce [v] |
Protected |
↓ |
QuerySyncStatus [vi] |
Protected |
Create Writeable Storage Snapshot |
TestFailoverStart |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Discard test data and reset storage |
TestFailoverStop |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Pre-synchronize Storage |
QueryReplicationSettings |
Protected |
↓ |
SyncOnce |
Protected |
↓ |
QuerySyncStatus |
Protected |
Prepare Protected VMs for Migration |
PrepareFailover |
Protected |
↓ |
DiscoverDevices |
Protected |
Synchronize Storage |
SyncOnce |
Protected |
↓ |
QuerySyncStatus |
Protected |
Change Recovery Site Storage to Writeable |
Failover |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Configure Storage to Reverse Direction |
ReverseReplication |
Former Recovery Site |
↓ |
DiscoverDevices |
Both |
Synchronize Storage |
QueryReplicationSettings |
Former Recovery Site |
↓ |
SyncOnce |
Former Recovery Site |
↓ |
QuerySyncStatus |
Former Recovery Site |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
SRA Discover |
QueryInfo |
Initiating SRM server |
↓ |
QueryCapabilities |
↓ |
↓ |
QueryConnectionParameters |
↓ |
↓ |
QueryErrorDefinitions |
↓ |
↓ |
DiscoverArrays [i] |
↓ |
↓ |
DiscoverDevice [ii] |
↓ |
↓ |
QueryReplicationSettings [iii] |
↓ |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Arrays |
DiscoverArrays |
Initiating SRM server |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Arrays |
DiscoverArrays |
Initiating SRM server |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Devices |
DiscoverDevices |
Both |
SRM Operation |
SRA Operation |
Log Location |
---|---|---|
Discover Devices |
DiscoverDevices |
Both |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Synchronize Storage |
QueryReplicationSettings [iv] |
Protected |
↓ |
SyncOnce [v] |
Protected |
↓ |
QuerySyncStatus [vi] |
Protected |
Create Writeable Storage Snapshot |
TestFailoverStart |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Discard test data and reset storage |
TestFailoverStop |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Pre-synchronize Storage |
QueryReplicationSettings |
Protected |
↓ |
SyncOnce |
Protected |
↓ |
QuerySyncStatus |
Protected |
Prepare Protected VMs for Migration |
PrepareFailover |
Protected |
↓ |
DiscoverDevices |
Protected |
Synchronize Storage |
SyncOnce |
Protected |
↓ |
QuerySyncStatus |
Protected |
Change Recovery Site Storage to Writeable |
Failover |
Recovery |
↓ |
DiscoverDevices |
Recovery |
SRM Recovery Plan Step |
SRA Operation |
Log Location |
---|---|---|
Configure Storage to Reverse Direction |
ReverseReplication |
Former Recovery Site |
↓ |
DiscoverDevices |
Both |
Synchronize Storage |
QueryReplicationSettings |
Former Recovery Site |
↓ |
SyncOnce |
Former Recovery Site |
↓ |
QuerySyncStatus |
Former Recovery Site |
This section lists all of the relevant SRM to SRA operations. Each operation has a definition in accordance to what SRM expects to happen and then also a definition of what the Pure Storage SRA actually does to fulfill SRMs expectations.
[i] Only is created if there are already existing array managers created in SRM for the Pure Storage SRA.
[ii] Only is created if one or more array pairs are enabled
[iii] Only is created if one or more array pairs are enabled
[iv] Only created if “Replicate Recent Changes” is selected at the start of the test recovery
[v] Only created if “Replicate Recent Changes” is selected at the start of the test recovery
[vi] Only created if “Replicate Recent Changes” is selected at the start of the test recovery
vSphere reports the following error while attempting to format a VMFS datastore using a Pure Storage iSCSI LUN:
"HostDatastoreSystem.CreateVmfsDatastore" for object "<...>" on vCenter Server "<...>" failed
The LUN will report as online and available under the "Storage Adapters" section in the vSphere Client.
This error can be due to improper configuration in the network path causing jumbo frames to be fragmented from the ESXi Host to the FlashArray.
How to confirm Jumbo Frames can pass through the network
Run the following command from the ESXi Host in question via SSH:
vmkping -d -s 8972 <target portal ipaddress>
If no response is received, or the following message is returned, then jumbo frames are not successfully traversing the network:
sendto() failed (Message too long)
sendto() failed (Message too long)
sendto() failed (Message too long)
There is an L2 device between the ESXi host and FlashArray that is not allowing jumbo frames to properly pass. Please have the customer check virtual and physical switches on the subnet to ensure jumbo frames are configured from end-to-end.
Make sure all network devices allow jumbo frames to pass from the ESXi host to the Pure Storage FlashArray.
Enabling CHAP authentication leads to ESXi hosts disconnecting and they are unable to reconnect.
The array has CHAP authentication enabled and is unable to reconnect after configuring CHAP on the ESXi host.
Purity does not support Dynamic Discovery with CHAP.
Follow this blog post for a more detailed guide.
Configure the ESXi host to use static CHAP, confirm Dynamic CHAP is not set up, and inherit from parent is not checked.
Two methods of configuring CHAP to the pure array:
When trying to increase an existing volume you will see the new volume size in vCenter. However, when the increase button is clicked for the datastore, the available capacity on the volume does not show up.
If the correct volume size is not being reflected, the management services on the ESX hosts that aren't reflecting the volume size correctly may need to be restarted and storage rescanned.
Please refer to VMware support for this recommendation as restarting management services has the potential to impact tasks that are running on the ESXi host at the time of the restart.
There are a few reasons this may be happening, you may have one fo the following issues , please refer to the following:
If none of these references fix the issue, please open a VMware Support case and reach out to Pure Storage Support for further assistance.
The Pure Storage FlashArray is consistently used with VMware environments and there's a good chance that Support will have cases where they need to troubleshoot and diagnose how the FlashArray interacts with the VMware environment.
During live troubleshooting, both the customer and Pure Support can look at the logs live as needed, however for an investigation into events that have already occurred VMware Support Logs will need to be provided to Support to move that investigation forward.
VMware has a detailed KB on how to Gather vCenter and ESXi Logs. Please review VMware's documentation.
With vCenter 6.7 release, there has been more adoption of the HTML5 Client now. There is no export option in the monitor tab, so the process is a little different.
Here is an example of the HTML5 Client.
Right Click on the vCenter and Select Export System Logs |
---|
Check the box to include vCenter logs. If the Support case is related to vVols, SRM or Plugins, this is very important to gather. |
---|
Then you can export the logs. The default selections for the hosts are usually enough for Pure Support. |
---|
Keep in mind, the HTML5 Log exports will be named a little different then the from the flash client. |
---|
Then here is an example of the Flash client and the monitor tab.
Navigate to the vCenter that the logs are being gathered for.
Go to the Monitor tab and click on system logs. Then click on export system logs. |
---|
Check the box to include vCenter logs. If the Support case is related to vVols, SRM or Plugins, this is very important to gather. |
---|
Then click Finish. Another window will pop up asking where to save the compressed file. |
---|
Once the logs are downloaded, they can be uploaded via Pure1 for Support.
There is a Uploading Files to a Support Case KB that outlines that process.