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
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.
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
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
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)
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 ??
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.
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.)
xe2sdc
4 Operator
•
2.8K Posts
0
January 29th, 2008 14:00
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
dynamox
9 Legend
•
20.4K Posts
0
January 29th, 2008 14:00
https://forums.emc.com/forums/thread.jspa?tstart=0&threadID=64573
vtarmo
4 Posts
0
January 29th, 2008 23:00
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
xe2sdc
4 Operator
•
2.8K Posts
0
January 30th, 2008 00:00
members for target device as i had it in source? The
member size has to be bigger then?
One single word. YES
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
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
xe2sdc
4 Operator
•
2.8K Posts
0
February 18th, 2008 02:00
xe2sdc
4 Operator
•
2.8K Posts
0
March 21st, 2008 04:00
cgunner
3 Posts
0
September 18th, 2008 06:00
xe2sdc
4 Operator
•
2.8K Posts
0
September 18th, 2008 06:00
xe2sdc
4 Operator
•
2.8K Posts
0
September 18th, 2008 08:00
cgunner
3 Posts
0
September 18th, 2008 08:00
dynamox
9 Legend
•
20.4K Posts
0
September 18th, 2008 08:00
dynamox
9 Legend
•
20.4K Posts
0
September 18th, 2008 08:00
cgunner
3 Posts
0
September 18th, 2008 08:00
Message was edited by:
cgunner
RRR
4 Operator
•
5.7K Posts
0
September 19th, 2008 12:00
rburry
8 Posts
0
September 22nd, 2008 07:00
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.)