Is host level migration an option. We use that for frame migrations and that would work for this as well. With good volume management software you can migration to anything that has enough capacity and online too. Mirror the volume, then break the mirror once in sync.
Yes Host level migration is an option. We have licenses for both open migrator and open replicator. We also have 2 frames one DMX-4 with a hyper size of 33G and one DMX-2 with a hyper size of 8G.
We have to migrate 10 8G hypers from DMX-2 to DMX-4. If we have 1 Meta of size 80G (10*8)and have to migrate we would need 330G(10*33) Meta volume in DMX-4 to use Open Replicator. Is this correct?
If we used Open Migrator, as it is a host based and logical volume level migration we just need 80G to migrate, in our scenario 99G( 33 * 3 ). Is this correct
Hi Protoss- We have to migrate 10 8G hypers from DMX-2 to DMX-4. If we have 1 Meta of size 80G (10*8)and have to migrate we would need 330G(10*33) Meta volume in DMX-4 to use Open Replicator. Is this correct?
No. that is not correct. For Open Replicator,you just create 99GB(3*33) and copy your all 80GB to 99GB. you don't have to use same number of hypers (just target meta needs to be larger than source).
I have copied 107.8GB metas made of 9.8 GB hypers to 111.2 GB metas made of 27.8 GB hypers. I would go with Open Replicator option because it is block level array based copy which is faster too
Let me know if you need any help with open replicator.
In the command file that we give as input to the Open Replicator session we just give 1 destination lun's(3*33G) and 1 source lun(10*8). And the session would take this file and copy the data from 1 smaller size meta device to 1 larger size Meta device. .... I got that,
now if we have 8 Lun's each of 8G size (which is the standard hyper size in our scenario for DMX-2) and need to migrate data to a DMX that has 33G hyper volumes then we have to use 10 33G lun's to migrate in case of open replicator and in this scenario we ought to use open migrator to save the rest 24G on each hyper volume. Is this correct?
What O/S are we talking about? Windows and a few others have online lun expansion capablilities which - when you perform a migration from a smaller lun to a larger lun, you can take advantage of this space.
open Migrator in windows - theoretically - expands the luns for you on reboot. I have seen on occaion when this isnt the case and need to use diskpart to extend the volume.
In this case, migrating to the larger hypers will not be a waste of space
I am sorry I put my question in wrong words. By waste of space I mean even if the servers do not need it we are forced to giving it to them.
We have windows and Unix systems in our environment but I was refering to the difference between Open Replicator/ Migrator in general.
Guess my question was to ask you guys if you would choose replicator/migrator if the scenario I explained.
we have 10, 8GB lun's and hyper size is 33GB on new Symm. if we migrate using open replicator we are giving the host extra storage it does not need and if we used open migrator with Veritas volume manager or similar tools we need not present the host with excess storage.
I migrated symdevs and metas to another DMX many times and the fact that the target symdev or meta is larger is no problem, since the source DMX is acting as a host and the target will only write all data to the target symdev or meta. The fact that this target piece of storage is somewhat larger, means you have to enlarge the partition in your host's OS. For windows this would be with the use of diskpart (only for basic disks), on other OS's you need similar actions or simply create a new partition on the extra free space.
xe2sdc
4 Operator
•
2.8K Posts
0
October 15th, 2008 22:00
sagle
90 Posts
0
October 16th, 2008 06:00
protoss
2 Intern
•
128 Posts
0
October 16th, 2008 07:00
We have to migrate 10 8G hypers from DMX-2 to DMX-4. If we have 1 Meta of size 80G (10*8)and have to migrate we would need 330G(10*33) Meta volume in DMX-4 to use Open Replicator. Is this correct?
If we used Open Migrator, as it is a host based and logical volume level migration we just need 80G to migrate, in our scenario 99G( 33 * 3 ). Is this correct
Message was edited by:
protoss
AmolMahajan
108 Posts
0
October 16th, 2008 08:00
We have to migrate 10 8G hypers from DMX-2 to DMX-4. If we have 1 Meta of size 80G (10*8)and have to migrate we would need 330G(10*33) Meta volume in DMX-4 to use Open Replicator. Is this correct?
No. that is not correct.
For Open Replicator,you just create 99GB(3*33) and copy your all 80GB to 99GB. you don't have to use same number of hypers (just target meta needs to be larger than source).
I have copied 107.8GB metas made of 9.8 GB hypers to 111.2 GB metas made of 27.8 GB hypers.
I would go with Open Replicator option because it is block level array based copy which is faster too
Let me know if you need any help with open replicator.
MarkF4
39 Posts
0
October 16th, 2008 15:00
** EDIT and then moved thread back to "Other EMC Software", probably the best place after all. Anyway, they say a change is as good as a holiday. **
Mark Foreman
Host Systems Forum Admin
Message was edited by:
Mark
protoss
2 Intern
•
128 Posts
0
October 16th, 2008 19:00
now if we have 8 Lun's each of 8G size (which is the standard hyper size in our scenario for DMX-2) and need to migrate data to a DMX that has 33G hyper volumes then we have to use 10 33G lun's to migrate in case of open replicator and in this scenario we ought to use open migrator to save the rest 24G on each hyper volume. Is this correct?
tonydcdi-ymiT1
70 Posts
1
October 17th, 2008 07:00
What O/S are we talking about? Windows and a few others have online lun expansion capablilities which - when you perform a migration from a smaller lun to a larger lun, you can take advantage of this space.
open Migrator in windows - theoretically - expands the luns for you on reboot. I have seen on occaion when this isnt the case and need to use diskpart to extend the volume.
In this case, migrating to the larger hypers will not be a waste of space
hope this helps
AmolMahajan
108 Posts
0
October 17th, 2008 07:00
First, I never used Open migrator
As far as I know you can't copy two or more smaller hypers to one large hyper or meta by using Open migrator.
It will overwrite your data at target.
Please refer
http://knowledgebase.emc.com/emcice/documentDisplay.do?docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docPropValue=emc192195&passedTitle=null
You can use veritas VxVM for your UNIX systems.
And Robocopy for windows but not a good choice if you got milions of files.
protoss
2 Intern
•
128 Posts
0
October 20th, 2008 12:00
We have windows and Unix systems in our environment but I was refering to the difference between Open Replicator/ Migrator in general.
Guess my question was to ask you guys if you would choose replicator/migrator if the scenario I explained.
we have 10, 8GB lun's and hyper size is 33GB on new Symm.
if we migrate using open replicator we are giving the host extra storage it does not need and if we used open migrator with Veritas volume manager or similar tools we need not present the host with excess storage.
Message was edited by:
protoss
AmolMahajan
108 Posts
0
October 22nd, 2008 08:00
Unfortunately, either Open replicator or open migrator can't save space for you.
for Unix you have option to use veritas mirroring instead of Open Replicator and OM
RRR
4 Operator
•
5.7K Posts
0
February 2nd, 2009 02:00
I migrated symdevs and metas to another DMX many times and the fact that the target symdev or meta is larger is no problem, since the source DMX is acting as a host and the target will only write all data to the target symdev or meta. The fact that this target piece of storage is somewhat larger, means you have to enlarge the partition in your host's OS. For windows this would be with the use of diskpart (only for basic disks), on other OS's you need similar actions or simply create a new partition on the extra free space.
Is your anser now answered ?