HP MSA 2040 SAN Storage - Manual (Page 17)

: 17
3 Troubleshooting
VMware vCenter Server uses the SRA to present a detailed error message each time a recovery step fails.
The SRA also creates a log file called sra.log that shows each SRM event and each CLI command that
occurs on the MSA storage systems. Examining the error messages and this log file will often provide
enough information to rectify errors.
Table 1 SRA error messages and suggested actions
Message number Message Suggested action
1002 VMware Site Recovery Manager version 5.0 was
not found on this system.
Install VMware SRM 5.0 or greater and then rerun
the SRA installation procedure.
1003 XML output to "{file}" failed: {error} Ensure that the specified file location exists, has
adequate free space, and is writable.
1004 Install option is not supported on this system Refer to the SRA installation instructions.
1005 A native version of Perl must be used when invoking
this option.
Ensure that you are using the Perl.exe version
installed with the VMware SRM software.
1006 Timed out waiting for volume {volume} to appear on
array {arrayname} at {file}:{line}.
Verify that the specified volume has been created on
the array and retry the operation.
1007 Array '{systemName}' is not licensed for use with
this SRA.
Contact your array vendor to verify that this array is
supported and to request Remote Snap and SRA
license keys.
1008 No WWN found for volume "{primary}". Verify that the specified volume is configured for
replication.
1009 discoverDevices: Could not determine WWN for
temporary snapshot "{serialNumber}" ({name}).
Check to see whether the specified snapshot was
left over from a previous test and can be deleted.
1010 Cannot find recovery point for temporary snapshot
"{serialNumber}" ({name}).
Check to see whether the specified snapshot was
left over from a previous test and can be deleted.
1011 discoverDevices: could not find WWN for promoted
volume "{secondaryName}" ({secondary}).
Check the status of the specified volume and the
health of the array and then retry the operation.
1013 No valid sync point exists for {volume}. In SMU, use the Snapshot Properties table to verify
that the specified volume has been completely
replicated from the protected site. See Chapter 6,
“Using Remote Snap to replicate volumes” in the
MSA SMU Reference Guide.
1014 Could not export a snapshot for volume {vol}. A snapshot previously created by the SRA already
exists for the specified volume. Only one exported
snapshot is allowed per replication destination
volume. Delete the existing snapshot and retry this
operation.
1018 unknown or missing PeerId parameter '{PeerId}' in
{command} request.
Ensure that each array reports the name of its
replication peer(s) correctly, and that the array
names have not changed since SRM was
configured. If the array name has been changed,
delete and recreate remote system entries on each
array as necessary. If the problem continues after
restarting SRM, recreate the array pair
configuration in SRM.
1020 Could not find peer volume for local volume
{localsn}.
Ensure that the specified volume has been set up as
part of a replication set.
1021 Invalid or missing parameters in SRM '{cmd}'
request received by SRA.
Verify that the replication sets, remote systems, and
SRM configuration are correct.