Some general questions
Posted: Tue Aug 02, 2011 4:18 am
Hi there,
I'm pretty new with 3par and I'm still in the process of trying and testing. I'm pretty experienced with emc² CX3-40 therefore I'm trying to understand the 3par concept for planning the migration.
In advance I have to say that I'm still a bit unsatisfied with our current technical support here in Germany. Hard to get a SE with knowledge that fits our needs - there really seems to be lack of resources after the 3par -> HP merger.
1. Need to migrate AIX/HACMP clustered Database (Informix - but that's not the point) from CX3-40 to 3par. I discovered the Open Migrator on emc²'s PowerLink and it looks good for our needs. Any experience with that tool?
2. Would it make sense in *ANY case to have thin provisioned VV's for databases? As said: we have Informix (using symbolic links to raw logical volumes) and we also have Oracle RAC using ASM (which ales need to be migrated of course).
3. Our main system is a F400 with 96 Spindles (15k FC only). Does it make sense to separate spindles for let's say Informix and Oracle? Is it really a good idea to have full-wide-spreading with all spindles for all "areas": Informix, Oracle, NFS Shares and vSphere datastores?
4. Our backup system is a smaller F400 with "only" 48 spindles. We are going to use RC copy via RCIP (1 GB bandwidth). The first write performance tests show up a ~3,5times decreased I/O rate (for massive seqential writes via 'dd if= of=' test) when using synchronous RC. Using periodic RC there was no difference. What are the Pro's and Cons's ?
In general I'm still a bit disappointed when I compare KnowledgeBase/guidelines betwen my beloved emc² PowerLink and emc² s support in general compared to poor 3par documentation. From my point of view there are worlds between.
But anyway... we have to live with the descision and try to make the best of it.
Joerg
I'm pretty new with 3par and I'm still in the process of trying and testing. I'm pretty experienced with emc² CX3-40 therefore I'm trying to understand the 3par concept for planning the migration.
In advance I have to say that I'm still a bit unsatisfied with our current technical support here in Germany. Hard to get a SE with knowledge that fits our needs - there really seems to be lack of resources after the 3par -> HP merger.
1. Need to migrate AIX/HACMP clustered Database (Informix - but that's not the point) from CX3-40 to 3par. I discovered the Open Migrator on emc²'s PowerLink and it looks good for our needs. Any experience with that tool?
2. Would it make sense in *ANY case to have thin provisioned VV's for databases? As said: we have Informix (using symbolic links to raw logical volumes) and we also have Oracle RAC using ASM (which ales need to be migrated of course).
3. Our main system is a F400 with 96 Spindles (15k FC only). Does it make sense to separate spindles for let's say Informix and Oracle? Is it really a good idea to have full-wide-spreading with all spindles for all "areas": Informix, Oracle, NFS Shares and vSphere datastores?
4. Our backup system is a smaller F400 with "only" 48 spindles. We are going to use RC copy via RCIP (1 GB bandwidth). The first write performance tests show up a ~3,5times decreased I/O rate (for massive seqential writes via 'dd if= of=' test) when using synchronous RC. Using periodic RC there was no difference. What are the Pro's and Cons's ?
In general I'm still a bit disappointed when I compare KnowledgeBase/guidelines betwen my beloved emc² PowerLink and emc² s support in general compared to poor 3par documentation. From my point of view there are worlds between.
But anyway... we have to live with the descision and try to make the best of it.
Joerg