Home > Articles

This chapter is from the book

Failure to Protect a Virtual Machine

Occasionally, you might find that when you create a Protection Group the process fails to register one or more virtual machines at the Recovery Site. It's important not to overreact to this situation as the causes are usually trivial ones caused by the configuration, and they are very easy to remedy. The most common cause is either bad inventory mappings, or a VM that falls outside the scope of your inventory mappings. In this section I will give you a checklist of settings to confirm, which will hopefully fix these problems for you. They amount to the kind of initial troubleshooting you may experience when you configure SRM for the first time.

Bad Inventory Mappings

This is normally caused by a user error in the previous inventory mapping process. A typical failure to protect a VM is shown in Figure 9.51. The error is flagged on the Protected Site with a yellow exclamation mark on the Protection Group, and the virtual machines that failed to be registered.

Figure 9.51

Figure 9.51 A VM failing to be protected because the VM Network port group was not included in the inventory mappings

As a consequence, you will also see errors in the Tasks & Events tab for the affected VMs. The classic clue that a VM has a bad inventory mapping is the "Unable to protect VM <VM name> due to unresolved devices" message shown in Figure 9.52.

Figure 9.52

Figure 9.52 The unresolved devices error that usually indicates a problem with inventory mappings

This error is usually caused by the virtual machine settings being outside the scope of the inventory mapping settings defined previously, and therefore the Protection Group doesn't know how to map the virtual machine's current folder, resource pool, or network membership to the corresponding location at the Recovery Site. A good example is networking, which I just described above.

In the inventory mapping process, I did not provide any inventory mappings for the VM Network port group. I regarded this as a local network that contained local virtual machines that did not require protection. Accidentally, the virtual machine named "fs01" was patched into this network, and therefore did not get configured properly in the Recovery Plan. In the real world this could have been an oversight; perhaps I meant to set an inventory mapping for vlan10 but forgot to. In this case, the problem wasn't my virtual machine but my bad configuration of the inventory mapping.

Another scenario could be that the inventory mapping is intended to handle default settings where the rule is always X. A number of virtual machines could be held within the Protection Group and could have their own unique settings; after all, one size does not fit all. SRM can allow for exceptions to those rules when a virtual machine has its own particular configuration that falls outside the group, just like with users and groups.

If you have this type of inventory mapping mismatch it will be up to you to decide on the correct course of action to fix it. Only you can decide if the virtual machine or the inventory mapping is at fault. You can resolve this match in a few different ways.

  • Update your inventory mappings to include objects that were originally overlooked.
  • Correct the virtual machine settings to fall within the default inventory mapping settings.
  • Customize the VM with its own unique inventory mapping. This does not mean you can have rules (inventory mappings) and exceptions to the rules (custom VM settings). A VM either is covered by the default inventory mapping or is not.

If you think the inventory mapping is good, and you just have an exception, it is possible to right-click the icon in the Protection Group, select Configure Protection in the menu that opens, and offer per-VM inventory settings. If you had a bigger problem—a large number of VMs have failed to be protected because of bad inventory mapping configurations—you can resolve that in the inventory mapping, and then use Configure All to try the protection process again.

I would say the most common reason for this error is that you have deployed a new VM from a template, and the template is configured for a network not covered by the inventory mapping. Another cause can concern the use of SvSwitches. It's possible to rename the port groups of an SvSwitch to be a different label. This can cause problems for both the inventory mapping and the affected VMs. As a consequence, when the Protection Groups are created for the first time the protection process fails because the inventory mapping was using the old name.

Placeholder VM Not Found

Another error that can occur is if someone foolishly deletes the placeholder that represents a VM in the Recovery Site, as shown in Figure 9.53. It is possible to manually delete a placeholder VM, although you do get the same warning message as you would if you tried to edit the placeholder settings. Nonetheless, these placeholder objects are not protected from deletion. If a rogue vCenter administrator deletes a placeholder you will see a yellow exclamation mark on the Protection Group, together with a "Placeholder VM Not Found" error message.

Figure 9.53

Figure 9.53 The "Placeholder VM Not Found" error message caused by accidental deletion of the placeholder in the inventory

The quickest way to fix this problem is to choose either the Restore All link or the Restore Placeholder link in the Protection Group interface. The Restore All option rebuilds all the placeholders within the Protection Group, whereas Restore Placeholder fixes just one selected placeholder in the list.

VMware Tools Update Error—Device Not Found: CD/DVD Drive 1

Occasionally, the Protection Group can have a VM that displays an error on its own. For example, in Figure 9.54 the VM named "db01" has the error message "Device Not Found: CD-DVD drive1." This error is relatively benign and does not stop execution of the plan.

Figure 9.54

Figure 9.54 The old chestnut of connected CD/DVD drives can cause a benign error to appear on the Protection Group.

This issue was created by a faulty VMware Tools update using Update Manager. The CD-ROM mounted was to a Linux distribution where an automatic mounting and update of VMware Tools failed. The Update Manager was unsuccessful in unmounting the .iso file at /usr/lib/vmware/isoimages/linux.iso, but the auto-execution of VMware Tools does not work in the same way with Linux as it does with Windows. With Linux all that happens is that the .iso file is mounted as a CD-ROM device, but it is up to the administrator to extract the .tgz package and install VMware Tools to the guest system. This error was resolved by right-clicking the affected VM, and under the Guest menu selecting "End VMware Tools install." This triggered an unmounting of the VMware Tools .iso image.

Delete VM Error

Occasionally, you will want to delete a VM that might also be a member of a Protection Group. The correct procedure for doing this is to unprotect the VM, which will then unregister its placeholder VMX file, and as a consequence remove it from any Recovery Plan. Of course, there's nothing to stop someone from ignoring this procedure and just deleting the VM from the inventory. This would result in an "orphaned" object in the Protection Group and Recovery Plan, as shown in Figure 9.55.

Figure 9.55

Figure 9.55 The error when a VMware administrator deletes a protected VM without first unprotecting it in SRM

To fix these VMs, select the affected VM and click the Remove Protection button.

It's Not an Error, It's a Naughty, Naughty Boy!

If you can forgive the reference to Monty Python's The Meaning of Life, the confusing yellow exclamation mark on a Protection Group can be benign. It can actually indicate that a new virtual machine has been created that is covered by the Protection Group. As I may have stated before, simply creating a new virtual machine on a replicated LUN/volume does not automatically mean it is protected and enrolled in your Recovery Plan. I will cover this in more detail in Chapter 11, Custom Recovery Plans, as I examine how SRM interacts with a production environment that is constantly changing and evolving.

Hopefully with these "errors" you can begin to see the huge benefit that inventory mapping offers. Remember, inventory mappings are optional, and if you chose not to configure them in SRM when you created a Protection Group every virtual machine would fail to be registered at the Recovery Site. This would create tens or hundreds of virtual machines with a yellow exclamation mark, and each one would have to be mapped by hand to the appropriate network, folder, and resource pool.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020