Start a Conversation

Unsolved

This post is more than 5 years old

1667

January 29th, 2008 14:00

Migrating data from smaller to larger metas

Hi,
Would it be possible to migrate data from metadevice to larger metadevice (within one system)? I would have used TimeFinder Clone myself, but i think it does not allow to do it. Well ideally i'd go also from striped meta to concatenated, but this is more like optional. I don't want to expand metas because i need also to change spindles. Is the host based copy the only way?

This is an open systems environment and DMX3 with 5771 code on it.

Regards
Tarmo

Message was edited by:
Tarmo Katmuk

2 Intern

 • 

2.8K Posts

January 29th, 2008 14:00

I have also to add that since S.E. 6.4.2 it's possible to have source devices smaller then target devices. But you have a lot of restrictions ..

To use larger target with symclone you have to set the following environment variable (not in options file):

SYMCLI_CLONE_LARGER_TGT = ENABLED

You can have a look at the output of symcli -env to see a brief description.
Now that you enabled larger target, remember that

Restore is not allowed
Full Copy support only; cannot use -differential
Concatenated metadevices are not supported
Number of members must match for striped metadevices

And now have fun :D

9 Legend

 • 

20.4K Posts

January 29th, 2008 14:00

4 Posts

January 29th, 2008 23:00

Hi Stefano,
Thanks for your post. I am trying to use it for migration, so restore is not question for me. Neither the differential copy. I am pretty sure i could survive without concatenated metas too. But the last point is a bit not clear for me. So i have to have 10 members for target device as i had it in source? The member size has to be bigger then? Let's say I have 10 members 8GB each striped metas at source and if i'd like to go for a larger device i have to have e.g. 10 members 10GB each striped metadevices?
If it is so, then it does not help me. I need to copy data to metas that has more members, but created with same size hyperdevices as the source.

Regards
Tarmo

2 Intern

 • 

2.8K Posts

January 30th, 2008 00:00

But the last point is a bit not clear for me. So i have to have 10
members for target device as i had it in source? The
member size has to be bigger then?


One single word. YES :D

Let's say I have 10 members 8GB each striped metas at source
and if i'd like to go for a larger device i have to have
e.g. 10 members 10GB each striped metadevices?


Yes .. that's exactly how it works .. You need the same number of bigger meta members :D

If it is so, then it does not help me. I need to copy
data to metas that has more members, but created with
same size hyperdevices as the source.


Symclone won't work .. You need something else (an host that can copy data from a lun to another lun)

-s-

Message was edited by:
Stefano Del Corno

2 Intern

 • 

2.8K Posts

February 18th, 2008 02:00

Tarmo are you still working on this issue ?? Did we solve your problems ?? Did you receive usefull answers and informtions from this thread ?? Can we help more ??

2 Intern

 • 

2.8K Posts

March 21st, 2008 04:00

Tarmo can we assume your question have been answered ??

3 Posts

September 18th, 2008 06:00

I have the same problem. We constantly move data from smaller to larger devices. Why don't EMC provide a tool to move data quickly? We have to resort to host based copies between the devices.

2 Intern

 • 

2.8K Posts

September 18th, 2008 06:00

AFAIK you can always buy (and use) OpenMigrator... :D

2 Intern

 • 

2.8K Posts

September 18th, 2008 08:00

Think about asking an RFE .. Maybe someone else needs what you are asking for ;-)

3 Posts

September 18th, 2008 08:00

We have tried Open Migrator/LM but it has a limit of 10 drives at a time. We move up to 48 at a time. It also is not supported on IA64.

9 Legend

 • 

20.4K Posts

September 18th, 2008 08:00

too bad you edited your post :)

9 Legend

 • 

20.4K Posts

September 18th, 2008 08:00

Stefano ..i like your new nickname ..the Bergamo man ...has a good sound to it :) hahahha

3 Posts

September 18th, 2008 08:00

Thanks. I think this might be the best route. I have found nothing that will move muti-terabytes of data quickly from smaller devices to larger.

Message was edited by:
cgunner

2 Intern

 • 

5.7K Posts

September 19th, 2008 12:00

:( missed it

8 Posts

September 22nd, 2008 07:00

Why not just use a symconfigure convert command?

add dev 1553:1554 to meta 0f76 protect_data=true bcv_meta_head=092f; (This can be used to expand the volume)

convert meta 186c, config=concatenated, protect_data=false;(This could be used to convert from striped to concat, you can also use the protected mode.)
No Events found!

Top