Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Configuring a replication with a seed via the vCloud Availability UI does not use the target vApp as a seed in vCloud Availability for Cloud-to-Cloud DR 1.5 (59551)

Last Updated: 11/27/2018Categories: TroubleshootingTotal Views: 3038Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When you configure a replication in the vCloud Availability UI and select a seed vApp from the target VDC, the replication is configured but the target vApp is not used as a seed.

Cause

This issue occurs because of an error in the API call that the UI generates when performing this workflow. When configuring a replication with a seed vApp, the destination type should be set to vapp but the UI workflow sets it to vcloud which is used for replications with no seed.

Resolution

This is a known issue in vCloud Availability for Cloud-to-Cloud DR 1.5.
Currently, there is no resolution.

Workaround

To work around this issue, you can configure a replication with a seed vApp via the vCloud Availability API.

Using an API client, such as Postman, log into the vCloud Availability API:

POST https://c4-fqdn/sessions
Header:
Content-Type:application/json
Example Body:
{
"type": "vcdCredentials",
"vcdUser": "user@org",
"vcdPassword": "password"
}

Using the X-VCAV-Auth response header for authentication, log into the target site:

POST https://c4-fqdn/sessions/extend
Headers:
Content-Type:application/json
X-VCAV-Auth:auth-token
Example Body:
{
"type": "credentials",
"site": "target-site",
"vcdUsername": "user@org",
"vcdPassword": "password"
}

When logged into both sites, configure the replication with the following API call and body:

POST https://c4-fqdn/vapp-replications
Headers:
Content-Type:application/json
X-VCAV-Auth:auth-token
Example Body:
{
"source": {
"type": "vapp",
"site": "source-site",
"vappId": "8733103a-9873-4b8a-9f06-910048108e82"
},
"destination": {
"seedVappId": "1e9132a3-4190-45d5-8902-4fad58be5cc5",
"type": "vapp",
"site": "target-site",
"vdc": "b23d0daf-7939-41a1-9d79-60fb9c3dd33f",
"storageProfile": "a906e827-5a6f-448a-a177-45b5d27110fa"
},
"description": "Protected via VCAV API",
"rpo": 120,
"dataConnectionType": "ENCRYPTED_COMPRESSED",
"quiesced": true,
"targetDiskType": "THIN"
}
Note: The vApp, Organization vDC, and Organization vDC level Storage Policy UUIDs can be obtained from the vCloud Director API. The site names can be obtained from the response bodies in steps 1 and 2.

To obtain the vCloud Director object UUIDs follow the steps below:

Log into the source vCloud Director site via API as described in the Logging In section of the vCloud API Programming Guide for Service Providers.

Find the source vApp with one of the following queries.

When logged in as an Organization level user, run:
GET https://vcd-fqdn/api/query?type=vApp&filter=name==vapp-name
When logged in as a System Administrator user run:
GET https://vcd-fqdn/api/query?type=adminVApp&filter=name==vapp-name

The source vappId is the vApp UUID from the href entry returned by the above API call.

Example:
<VAppRecord creationDate="2018-10-15T16:50:19.360+01:00" isAutoNature="false" isBusy="false" isDeployed="true" isEnabled="true" isExpired="false" isInMaintenanceMode="false" isPublic="false" name="source-vapp" ownerName="org-user" status="POWERED_ON" vdc="https://source-vcd-fqdn/api/vdc/409b74a4-2136-461e-b577-01d033c9c9b2" vdcName="source-vdc" href="https://source-vcd-fqdn/api/vApp/vapp-8733103a-9873-4b8a-9f06-910048108e82" taskStatusName="vappDeploy" isAutoDeleteNotified="false" isVdcEnabled="true" honorBootOrder="false" numberOfVMs="1" cpuAllocationInMhz="1000" numberOfCpus="1" cpuAllocationMhz="1" task="https://source-vcd-fqdn/api/task/2c88c738-bf91-4358-9957-9c794dab25c1" lowestHardwareVersionInVApp="13" memoryAllocationMB="4" storageKB="1048576" pvdcHighestSupportedHardwareVersion="13" isAutoUndeployNotified="false" taskStatus="success" taskDetails=" "/>

Log into the target vCloud Director site via API.

Find the target vApp with the same queries as in step 2, but against the target vCloud Director instance.

The target vappId is the vApp UUID from the href entry returned by the above API call.

The target vdc is the vDC UUID from the vdc entry returned by the same API call.

Example:
<VAppRecord creationDate="2018-11-08T14:39:12.630Z" isAutoNature="false" isBusy="false" isDeployed="false" isEnabled="true" isExpired="false" isInMaintenanceMode="false" isPublic="false" name="seed-vapp" ownerName="org-user" status="POWERED_OFF" vdc="https://target-vcd-fqdn/api/vdc/b23d0daf-7939-41a1-9d79-60fb9c3dd33f" vdcName="target-vdc" href="https://target-vcd-fqdn/api/vApp/vapp-1e9132a3-4190-45d5-8902-4fad58be5cc5" taskStatusName="vdcComposeVapp" isAutoDeleteNotified="false" isVdcEnabled="true" honorBootOrder="false" numberOfVMs="1" cpuAllocationInMhz="1000" numberOfCpus="1" cpuAllocationMhz="1" task="https://target-vcd-fqdn/api/task/33f63504-029e-4e86-a41c-8a721d5dc7af" lowestHardwareVersionInVApp="13" memoryAllocationMB="4" storageKB="1048576" pvdcHighestSupportedHardwareVersion="13" isAutoUndeployNotified="false" taskStatus="success" taskDetails=" "/>

Navigate to the target vDC using the vdc URL above:

GET https://target-vcd-fqdn/api/vdc/b23d0daf-7939-41a1-9d79-60fb9c3dd33f

From the response body, the target storageProfile is the href of the desired VdcStorageProfile in the VdcStorageProfiles section.

Example:
<VdcStorageProfiles>
<VdcStorageProfile href="https://target-vcd-fqdn/api/vdcStorageProfile/a906e827-5a6f-448a-a177-45b5d27110fa" name="iSCSI Storage" type="application/vnd.vmware.vcloud.vdcStorageProfile+xml"/>
</VdcStorageProfiles>

Related Information

For more information on vCloud Availability for Cloud-to-Cloud DR APIs, see the vCloud Availability API Reference section on VMware {code}.

For more information on vCloud Director APIs, see the APIs and SDKs section of the vCloud Director for Service Providers Documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability for Cloud-to-Cloud DR 1.x

Take Our Survey

Support Assistant