VMware Site Recovery Manager 5 Configuring Inventory Mappings
In Part 6 of this VMware Site Recovery Manager 5 Tutorial Series, we will be running through the configuration of our Site Recovery Manager 5 Inventory Mappings. This includes Resource Mappings, Folder Mappings, Network Mappings and the Placeholder Datastores.
VMware Site Recovery Manager 5 – Resource Mappings
1. Open up vCenter if it’s not already open and enter into Site Recovery Manager. Click on the Primary Site. Click on the Resource Mappings Tab. As you can see for my Primary Site I have 2 Resource Groups, Web 1 and Web 2. We will be mapping these Resource Groups to Resource Groups on the Secondary Site.
2. Make sure you have your Primary Site selected on the right hand side and I will also have my Web 1 Resource Group selected. Click on Configure Mapping. The Secondary Site is displayed with the available Resource Groups. I want to map Web 1 to the Web 1 Recovered Resource Group. When the server is recovered on the secondary site, it will be placed into this resource group. In my lab, Web 1 Resource Groups have a high priority and Web 2 Resource Groups have a normal priority. If you need to create a new Resource Group, simply click on New Resource Group.
3. As you can see my Web 1 Resource Group on my Primary Site is now mapped to Web 1 Recovery Resource Group on the Secondary Site.
4. I will now do the exact same steps to map my Web 2 Resource Group on the Primary Site to the Web 2 Recovered Resource Group on the Secondary Site. Once you are finished it will look like this
VMware Site Recovery Manager 5 – Folder Mappings
5. On my Primary Site I have named the folders the same as the resource groups, Web 1 and Web 2 as you can see below.
6. Click on Configure Mapping. On the Secondary Site, I have created 2 folders Web 1 Recovered and Web 2 Recovered. I will be mapping Web 1 on the Primary Site to Web 1 Recovered on the Secondary Site. Select Web 1 Recovered and click Ok. Once again, if you need to create a folder you can simply click the New Folder button.
7. As you can see my Web 1 to Web 1 Recovered Folder mapping is now complete.
8. I will now map Web 2 on the Primary Site to Web 2 Recovered on the Secondary Site. Both folders are now mapped.
VMware Site Recovery Manager 5 – Network Mappings
9. Click on the Network Mappings Tab. As you can see below my Virtual Machine network is simply called VM Network on the Primary Site.
10. Click Configure Mapping. On the Secondary Site I have 2 networks setup. VM Network Recovered, which will be used in the event of an actual disaster recovery and VM Network Testing, which is the network that will be used when we wish to test our disaster recovery. Here we will select the network that we will use on the Secondary Site in the event of an actual disaster. Click Ok.
11. As you can see the below my VM Network is now mapped to VM Network Recovered.
VMware Site Recovery Manager 5 – Placeholder Datastores
12. Click on the Placeholder Datastores. Make sure you have your Primary Site Selected on the right hand side.
13. Click Configure Placeholder Datastore. We will now select a placeholder datastore on the Secondary Site. In this case i’m using vmware_placeholder. Click Ok.
14. This datastore is now the placeholder for Primary Site virtual machines.
15. Now we will do the same on the Secondary Site. Click the Secondary Site on the left hand side.
16. Click Configure Placeholder Datastore. I’ve also named the datastore on the Primary Site as vmware_placeholder. I will select it and click ok.
17. The placeholder datastore for the secondary site is now set. The reason for select a placeholder for the secondary site, is for failback.
Continue onto Part 7 VMware Site Recovery Manager 5 Protection Group
If you have any technical questions about this tutorial or any other tutorials on this site, please open a new thread in the forums and the community will be able to help you out.
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.