As far as migrations, you might ask EMC about Open Replicator. I'm not sure how well it plays with Veritas (you may have to do an export/import of the LVM groupings) but it is really nice.
But if you want to keep it simple like Dynamox says, I would use LVM mirroring. I've done a few of these w/ Veritas on Windows and it worked great.
Have you purchased Thin Provisioning? There are some thing you can do with Thin Luns to solve your 'meta device' concerns. I.E. create a large pool out of tdats and present out of there whatever size tdev you need to the host. You can even choose to fully allocate these luns if you deam appropriate. Probably want to ask if you purchased FAST/VP as well.
Different disk sizes to Veritas shouldn't matter as long as the target lun is equal or greater in size than the source. I always like to give a few extra GB's of space just to make sure anyway...
dynamox
9 Legend
•
20.4K Posts
0
October 12th, 2011 07:00
i would use native veritas LVM mirroring functionality, don't have to take downtime for migration.
boydbria
54 Posts
0
October 12th, 2011 08:00
As far as migrations, you might ask EMC about Open Replicator. I'm not sure how well it plays with Veritas (you may have to do an export/import of the LVM groupings) but it is really nice.
But if you want to keep it simple like Dynamox says, I would use LVM mirroring. I've done a few of these w/ Veritas on Windows and it worked great.
Have you purchased Thin Provisioning? There are some thing you can do with Thin Luns to solve your 'meta device' concerns. I.E. create a large pool out of tdats and present out of there whatever size tdev you need to the host. You can even choose to fully allocate these luns if you deam appropriate. Probably want to ask if you purchased FAST/VP as well.
Different disk sizes to Veritas shouldn't matter as long as the target lun is equal or greater in size than the source. I always like to give a few extra GB's of space just to make sure anyway...
Hopefully this helps.
yaribhas
2 Intern
•
134 Posts
0
October 12th, 2011 12:00
Are you using thin provisioning on VMAX? LUN wrapping problem is not as serious in thin luns.
Also if you have to stick to max 16 hypers per meta and thick luns you might have to increase your hyper size.
SAN copy and open replicator are simple and do the job really well.