8.0

These files contain the all the data (Authorization and Tagging) from the vCenter Server on which
this command was run.
If a secondary vCenter Server is provided using the -dvf or --dest-vc-fqdn option, any
conflicts are also exported to the same folder:
n Conflicts_Roles.json
n Conflicts_TagCategories.json
n Conflicts_Tags.json
The following is a sample conflicts file:
<---- Sample Conflict file code block --->
{
"global" : {
"resolution" : "MERGE|SKIP|COPY",
"description" : "Default resolution option used to resolve Role Conflicts is COPY. The
conflicts list describes the differences between Role entities on source and target vCenter
Server. If
the source information represents an empty JSON array, it simply means that all the entity
attributes from source and target are identical. If the source lists few entries, it means
that only these entity attributes are missing from the target. If the target lists few
entries,
it means that only these entity attributes are missing from the source. Though a global
resolution
can be set, it can also be overridden at each conflict level by providing individual
resolution
mode."
},
"conflicts-count" : 1,
"conflicts-list" : {
"NoCryptoAdmin" : {
"source" : {
"privileges" : "[]"
},
"target" : {
"privileges" : "[Group-1.SamplePriv-1, Group-1.SamplePriv-4, Group-2.SamplePriv-10,
Group-2.SamplePriv-3, Group-2.SamplePriv-7, Group-3.SamplePriv-2, Group-3.SamplePriv-9]"
},
"resolution" : ""
}
}
<----- End of code block --->
The parts of the sample conflict files are:
n description. Provides the details on how the respective conflicts file is read and understood.
n source and target. JSON objects that list only the differences between the source and target
vCenter Server objects.
n resolution. User supplies one valid resolution. Valid resolutions are MERGE, COPY, and SKIP.
vCenter Server Installation and Setup
VMware, Inc. 81