Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

A Test Failover operation in Site Recovery Manager fails with the SRA message: Failed to create LUN snapshot (1013454)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 22757Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In a datacenter environment where ESX servers in the production and disaster recovery sites are connected to EMC Clariion CX storage arrays and the production site is protected using VMware Site Recovery Manager(SRM) using EMC MirrorView SRA (Storage Replication Adapter), running an SRM Test Failover operation may fail during the preparing storage stage.

The logs from SRM (default location C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Site Recovery Manager\Logs) and the SRA show the message Failed to create Lun snapshots as:

[2009-07-16 18:27:19.874 'SecondarySanProvider' 968 trivia] 'tasteful' returned <Response>
[#3] <Return Code>0</Return Code>
[#3] </Response>
[2009-07-16 18:27:19.874 'SecondarySanProvider' 968 info] Return code for tasteful: 0
[2009-07-16 18:27:19.874 'SecondarySanProvider' 968 trivia] 'Prepare storage for group 'sharecrop' for recovery' took 56.749 seconds
[2009-07-16 18:27:19.874 'BeginImageTest-Task' 968 verbose] Error set to (Dr.San.fault.Execution Error) {
[#3] dynamic Type = <unset>,
[#3] error Message = "Failed to create lun snapshots",
[#3] MSG = ""
[#3] }
[2009-07-16 18:27:19.874 'BeginImageTest-Task' 968 info] State set to error

Note: The highlighted sections indicate the response from the MirrorView SRA and are not from SRM.

Resolution

During a Test Failover operation, SRM makes a request to the SRA to perform a test failover of the datastore LUNs. These are the replicated LUNs that were discovered during the array discovery and LUN discovery stages. For the Test Failover operation, failing over a LUN means creating LUN snapshots for the LUN-replicas that are established on the DR (Disaster Recovery) site. If creating snapshots for these LUNs fails, SRM Test Failover operation will fail.

The error message failed to create lun snapshot reported by the MirrorView SRA can occur in two different but related scenarios. In both scenarios, two parameters are considered: the number of LUNs for which SRM requests the failover and the Consistency Groups (CGs) defined by the SAN administrator as part of the LUN replication configuration.

Scenario 1:

The consistency group defined by the SAN administrator contains a certain number (n) of LUNs and SRM requests the failover of a number of LUN less than the number (n). MirrorView SRA requires that LUN snapshot requests (LUN Failover requests made by SRM) should be made for all the LUNs contained in a consistency group.

For more details on this scenario and for a resolution, see Failure to create LUN snapshots when performing a Site Recovery Manager test failover on a CLARiiON array (1009638).

Scenario 2:

SRM makes a failover request (i.e. snapshot request) for a group of LUNs that are in the same consistency group (CG) and the number of LUNs in this group exceeds a certain maximum allowed by the storage array. For example, in arrays such as Clariion CX4-140, this limit is 8 and in some other CX-arrays, the limit is 16.

In this scenario, the solution enabler reports this message:

A Multi-Lun Consistent operation was attempted that specified more devices than allowed. The limit is either 8 or 16 for this array type, so please inspect your Navisphere documentation on what the correct numbers should be. Please retry the operation using the correct number of devices.

Note: This message is not propagated to the MirrorView SRA. Therefore, you do not see this message in the SRM/SRA logs.

To resolve this issue, limit the number of LUNs in a consistency group to its maximum allowed value. This value would be the maximum number of LUNs in a CG for which you can take simultaneous snapshots. For more information, see the EMC SAN documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
在远程站点的 IP 地址更改后，vCenter Site Recovery Manager 无法连接到远程站点 (2008033)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

Related Versions:

Take Our Survey

Support Assistant