Resolving Duplicate Domain Names In A Mirrored Or Disaster Recovery (Dr) Cluster; Renaming A Domain In Its Source Cluster (Dr Cluster Conflict Only) - Dell DX6000 Administration Manual

You must provide the domain name or IP address as the Host in the request.
For example, to recover a bucket named mybucket with an alias UUID of
75edd708dc250137849bbf590458d401 in the domain named cluster.example.com, enter:
curl -i --post301 --anyauth -u "admin:ourpwdofchoicehere" -X POST
--data-binary @cluster_example_com_mybucket --location-trusted
"http://172.16.0.35/mybucket?domain=cluster.example.com&admin
&recreatecid=75edd708dc250137849bbf590458d401"
In the example, cluster_example_com_mybucket is the name of the user list to upload to
mybucket.
D.2. Resolving Duplicate Domain Names in a Mirrored or Disaster Recovery
(DR) Cluster
This section discusses how to resolve duplicate domain names in a mirrored or disaster recovery
(DR) cluster. These optional configurations with DX Content Router work as follows:
• A DR cluster enables you to copy one or more clusters and their contents in another physical
location.
• A mirrored configuration copies the contents of cluster 1 to cluster 2, and copies the contents of
cluster 2 to cluster 1.
In either type of configuration, if two source clusters contain two domains with the same name,
DX Content Router duplicates the domain names in the DR or mirrored cluster. This results in
indeterminate access to objects in the duplicated domains; in other words, sometimes a request to a
particular object in one of the duplicate domains succeeds, but other times it fails.
When DX Content Router detects a duplicate domain, it logs a Critical error to its DX Storage Admin
Console. If you are alerted to such an error, Dell suggests the following resolutions:
• Recommended for a DR cluster conflict. Rename either domain in its source cluster.
This method is recommended because it solves the issue and prevents it from happening in the
future. You can perform this task using the source cluster's Admin Console.
Note
This method does not work in a mirrored configuration because both clusters have
duplicates. Instead, use the procedure discussed in the next bullet.
• Rename either conflicting domain.
For a DR cluster conflict, this method is not as desirable because the next time the same domain
is replicated to the DR cluster, the domain name duplicate still exists.
This is the only method you can use in a mirrored cluster conflict but it solves the issue and
prevents it from reoccurring.
D.2.1. Renaming a Domain in its Source Cluster (DR Cluster Conflict Only)
This section discusses how to rename a domain in its source cluster, where the name of the domain
is assumed to be unique. After you rename the domain, it replicates without errors to the DR cluster.
Copyright © 2010 Caringo, Inc.
All rights reserved 61
Version 5.0
December 2010