Part 6 – Site Recovery Manager Inventory Mappings
This stage is all about configuring the Inventory Mappings. This includes resource mappings, folder mappings, network mappings and placeholder datastores. This is basically linking the resources being used at the protected site with the resources to be used at the recovery site.
- Make sure that you are in the ‘Site Recovery Manager’ section of the vSphere client and looking at the ‘Sites’ section.
- Click on the primary site (the source site) and then select the ‘Resource Mappings’ tab.
- You should now see a list of the resource pools configured in your environment, in our environment we currently do not have any resource pools.
- Click the ‘Configure Mapping’ link
- You should now see the destination listed, expand the environment down to the cluster and then click ‘OK’
- You will now see the source and destination locations listed together.
- Click on the ‘Folder Mappings’ tab
- You will now see a list of the available folders in your environment.
- Select the cluster level or a folder
- Click ‘Configure Mapping’, you will see the secondary location appear… again select the destination cluster or folder or create the relevant folders to be selected and then click ‘OK’
- You will now see that the mapping is configured.
- Click on the ‘Network Mappings’ tab
- Select the VM Network to be mapped and then click ‘Configure Mapping’
- Select the equivalent network from the destination location and then click ‘OK’
- Repeat the process for the remaining networks
- You should see all of the networks are mapped.
- You should make sure that there are some placeholder datastores created, these need to be created at both locations… they will hold a file approximately 1KB in size for each virtual machine protected.
- Click the ‘Placeholder Datastores’ tab
- Click the ‘Configure Placeholder Datastore’ link
- Select the appropriate placeholder datastore from the destination location, click ‘OK’
- Select the destination location and perform the same task again
- The reason that this is performed on both sites is to allow for failback