Home > Articles

This chapter is from the book

Assigning Placeholder Datastores

As we will see later in this chapter, an important part of the wizard for creating Protection Groups is selecting a destination for placeholders for the Recovery Site. This is a VMFS or NFS volume at the recovery location. When you create a Protection Group at the production site, SRM creates a VMX file and the other smaller files that make up the virtual machine from the Protected Site to the Recovery Site using the placeholder datastore selected in the wizard. It then preregisters these placeholder VMX files to the ESX host at the Recovery Site. This registration process also allocates the virtual machine to the default resource pool, network, and folder as set in the inventory mappings section. Remember, your real virtual machines are really being replicated to a LUN/volume on the storage array at the Recovery Site. You can treat these placeholders as an ancillary VM used just to complete the registration process required to get the virtual machine listed in the Recovery Site's vCenter inventory. Without the placeholder VMs, there would be no object to select when you create Recovery Plans.

If you think about it, although we are replicating our virtual machines from the Protected Site to the Recovery Site, the VMX file does contain site-specific information, especially in terms of networking. The VLAN and IP address used at the recovery location could differ markedly from the protected location. If we just used the VMX as it was in the replicated volume, some of its settings would be invalid (port group name and VLAN, for example), but others would not change (amount of memory and CPUs).

The main purpose of placeholder VMX files is that they help you see visually in the vCenter inventory where your virtual machines will reside prior to executing the Recovery Plan. This allows you to confirm up front whether your inventory mappings are correct. If a virtual machine does not appear at the Recovery Site, it's a clear indication that it is not protected. It would have been possible for VMware to create the virtual machine at the Recovery Site at the point of testing the Recovery Plan, but doing it this way gives the operator an opportunity to fix problems before even testing a Recovery Plan.

So, before you begin configuring the array manager of Protection Groups, you should create a small, 5–10GB volume on the storage array of your choice and present that to all the ESX hosts that will perform DR functions. For example, on my EMC NS-120 array I created a 5GB LUN visible to my Recovery Site ESX hosts (esx3/4), called using EMC's Virtual Storage Console formatted with VMFS, and giving it a friendly volume name of SRM_Placeholders. It's a good practice to keep the placeholder datastores relatively small, distinct, and well named to stop people from storing real VMs on them. If you wish, you could use datastore folders together with permissions to stop this from happening.

It's worth stating that if you ever want to run your Recovery Plan (failover) for real, either for planned migration or for disaster recovery, you would need a placeholder datastore at the Protected Site as well for returning to the production location as part of any reprotect and automated failback procedure. This has important consequences if you want to easily use the new automatic failback process or reprotect features. I'd go so far as to say that you might as well create a placeholder volume at both locations at the very beginning.

This placeholder datastore needs to be presented to every ESX host in the cluster that would act as a recovery host in the event of DR. The datastore could be used across clusters if you so wished, so long as it was presented to all the hosts that need to have access to it in the site. For me, each cluster represents an allocation of memory, CPU, network, and storage. In my case, I created placeholder datastores at New Jersey used in the process of protecting VMs in New York, and similarly I created placeholder datastores at New York used in the process of protecting VMs in New Jersey. In most cases you will really need only one placeholder datastore per cluster. As I knew at some stage I would need to do a failover and failback process in SRM it made sense to set these placeholder datastores at this stage, as shown in Figure 9.15.

Figure 9.15

Figure 9.15 Placeholder datastores should be on nonreplicated datastores available to all hosts in the datacenter or clusters where SRM is in use.

Remember, the smallest VMFS volume you can create is 1.2GB. If the volume is any smaller than this you will not be able to format it. The placeholder files do not consume much space, so small volumes should be sufficient, although you may wish to leverage your storage vendor's thin-provisioning features so that you don't unnecessarily waste space—but hey, what's a couple of gigabytes in the grand scheme of things compared to the storage footprint of the VMs themselves? On NFS you may be able to have a smaller size for your placeholder datastore; much depends on the array—for example, the smallest volume size on my NetApp FAS2040 is 20GB.

It really doesn't matter what type of datastore you select for the placeholder VMX file. You can even use local storage; remember, only temporary files are used in the SRM process. However, local storage is perhaps not a very wise choice. If that ESX host goes down, is in maintenance mode, or is in a disconnected state, SRM would not be able to access the placeholder files while executing a Recovery Plan. It would be much better to use storage that is shared among the ESX hosts in the Recovery Site. If one of your ESX hosts was unable to access the shared storage location for placeholder files, it would merely be skipped, and no placeholder VMs would be registered on it. The size of the datastore does not have to be large; the placeholder files are the smaller files that make up a virtual machine, they do not contain virtual disks.

But you might find it useful to either remember where they are located, or set up a dedicated place to store them, rather than mixing them up with real virtual machine files. It is a good practice to use folder and resource pool names that reflect that these placeholder virtual machines are not "real." In my case, the parent folder and resource pool are called "NYC_DR" at the New Jersey Recovery Site. Once the placeholder datastore has been created, you can configure SRM at the Protected Site and use it to create the "shadow" VMs in the inventory.

  1. In SRM, select the Protected Site; in my case, this is the New York site.
  2. Select the Placeholder Datastores tab (see Figure 9.16).

    Figure 9.16

    Figure 9.16 The Placeholder Datastores tab

  3. Click the Configure Placeholder Datastore link.
  4. In the subsequent dialog box, select the datastore(s) you created.

The dialog box in Figure 9.16 does allow you to add multiple placeholder datastores for each cluster that you have. The choice is yours: one placeholder datastore for all your clusters, or one placeholder datastore for each cluster in vCenter. Your choice will very much depend on your storage layer and policies within your organization. For example, if you are using IP-based storage it will be very easy to present an iSCSI or NFS volume across many VMware clusters. If you're using Fibre Channel, this could involve some serious work with zoning and masking at the switch and storage management layer. It may be your storage team's policy that each ESX host in a VMware cluster represents a block of storage or a "pod" that cannot be presented to other hosts outside the cluster.

If you look closely at the screen grab you can see that from New York Site (Local), I am browsing the datastores in the New Jersey vCenter. From there I can locate the datastore I called "NYC_SRM_Placeholders" as the location for the placeholder files. I configured a similar setup at the New Jersey location to facilitate the new automatic failback and reprotect features in SRM.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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