Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1690

February 5th, 2010 09:00

Centera Migration Options

We purchased 40 Centera 4 LP nodes for each of our new production and DR data centers. The new Centera arrays will also have (2) nodes dedicated for the HA CUA environment. We need to migrate our existing Centera storage arrays which are located at different data centers. We also have bi-directional replication. There are (2) applications writing to the HA CUA nodes at data center #1 and (2) applications writing directly to the Centera at data center #2. The data is replicated bi-directionally both ways. We want to migrate all (4) application data to the Centera located at the new production data center and then replicate the data to the new DR data center. There is 1GB IP connectivity between all (4) of the data centers. We also don't want to extend any of VLANs between any of the data centers. What are the options for migrating the (2) existing data centers to the production data center?

124 Posts

February 9th, 2010 08:00

Replication and restore will use what available bandwidth is needed for the operation being performed. The clip exporters (thread count) can be adjusted by EMC service.

By lowering the thread count (even to single threaded) does not mean that the bandwidth utilization will decrease. While true that less threads equals less concurrent traffic, a thread will consume whatever bandwidth is available that is required for the action being performed. A single thread can consume significant bandwidth providing the bandwidth is available.

This cannot be throttled by Centera but can be via QoS network configurations outside of Centera.

124 Posts

February 5th, 2010 09:00

You could use "restore" to restore all the data. Restore operates from a time slice with a start period and end period where any data that was written between the start and end dates will be restored. To restore all data, use unix epoch time (1/1/1970) for a start date. You may want to modify your existing replication to be a chain so any new data written after the restore end date will be copied over.

EMC professional services can also migrate this data using c2c

3 Posts

February 5th, 2010 10:00

Can you please explain what you mean by modifying the current replication to be a chain. Do you know the pros/cons for using CICM vs. C2C.

I was told that CICM the Centera Clusters had to be on the same VLAN. Do you know if the restore of C2C migration options require the Centera Clusters to reside at the same data center or be on the same VLAN?

124 Posts

February 5th, 2010 11:00

If I understand things correctly you currently have

cluster A replicating to cluster B

cluster B replicating to cluster A

cluster C replicating to cluster D

cluster D replicating to cluster C

You have 2 applications writing to cluster A and 2 applications writing to cluster C - no applications writing to clusters B or D.

You now have 2 new clusters

cluster E replicating to cluster F

cluster F replicating to cluster E

You want all the data that resides on cluster A and C migrated to cluster E and F

You can modify your existing replication setup

cluster A replicates to cluster B which replicates to cluster E

cluster C replicates to cluster D which replicates to cluster E

This will require breaking replication between E and F

You run a restore from cluster A to cluster E

You run a restore from cluster C to cluster E

Once everything is on E, you reset replication to the way it was previously and run restore from E to F

This requires that the replication nodes are on the same network

CICM is used to migrate data from one cube accross the cluster and is primarily used when replacing old generation hardware with new generation hardware in the same cluster.

c2c iterates the source cluster and then copies all the clips to the target - requires that source and target access nodes are on the same network

restore uses a time based query to determine the objects to migrate. This requires a healthy source cluster with complete databases.

c2c iterates the filesystem and thus is less dependant on the health of the source

Hope this help clear things up - If further questions, it would help if I knew what your ultimate end objective is

February 9th, 2010 04:00

Hi all

Be aware that if you choose restore to migrate all your data the network will be heavily used. Restore like replication consume all the bandwidth they can get. C2C allows for the number of threads to be configured.

Holger

No Events found!

Top