| Getting Started | FAQ | Best Practices | Troubleshooting |
The import operation may fail because the IP address of the primary and secondary storage devices was provided during the array configuration in the CommServe.
The array names should match the hostname of the primary and secondary devices as displayed in the DataFabric Manager.
When you import an external relationship, a dataset is created and its name is determined by the source volume. If a volume has multiple qtrees vaulted/mirrored to the same destination volume and you plan to import the qtrees separately, the first import will create the dataset, and the second import will be skipped because the dataset already exists.
For Fan-In external relations, volumes containing relations vaulted/mirrored to the same destination volume will also skip the second import if you plan to import them separately.
All qtrees relationships should be imported at the same time in order to be imported to a single dataset. If a qtree from the source volume is vaulted/mirrored to a different destination volume, you can import it separately. However, ensure to rename the dataset while editing the XML file during the import operation.
For Fan-In external relations, ensure all relations are imported at the same time as mentioned for qtrees.
External PMV (Primary-Mirror-Vault) relations are expected to be imported as one relation under a single dataset. However, if one of the qtrees does not have a Vault relationship in the Mirror volume, the PMV relations may be imported as two datasets e.g., one dataset for P-M and another for M-V.
You can choose one of the following work arounds: