Page 2 of 2
Re: CPG, Volumes, Virtual Volumes Best Practices
Posted: Mon Jul 14, 2014 11:31 am
by hdtvguy
slink wrote:hdtvguy wrote:It helps that our databases got peeled off onto their own 7400.
This is OT but can I ask what the reasons were for doing that? Business, technical or both?
I'm working on a consolidation project and we've had several heated discussions around whether to adopt a common platform approach with our SQL DBs on the same storage as the Hyper-V VMs.
We've reached a consensus now and we're going for all the eggs in one basket with a view to using Priority Optimization so I'd be interested to hear your experiences and what has driven you to split out your workloads.
Thanks
The big reason for moving databases to a dedicated 7400 was remote copy. We had about 300 Remote Copy groups and with all the volumes and the 3par having a limitation of only being able to replicate 20 volumes concurrently we had issues meeting our SLAs so by moving the DBs to the 7400 they replicate every 15 minutes, it is easy to meet SLAs without a large number of volumes hogging the 20 slots.
Re: CPG, Volumes, Virtual Volumes Best Practices
Posted: Tue Jul 15, 2014 12:03 pm
by RitonLaBevue
the 3par having a limitation of only being able to replicate 20 volumes concurrently
Can you explain this ?
Re: CPG, Volumes, Virtual Volumes Best Practices
Posted: Tue Jul 15, 2014 12:17 pm
by Schmoog
RitonLaBevue wrote:the 3par having a limitation of only being able to replicate 20 volumes concurrently
Can you explain this ?
No matter how many vv's or rc groups you have, 3par is only able to
actively replicate 20 at a time; that is send data.
So if you have 300 vv's set to replicate in one RC group set to replicate at say 3:00 PM. then starting at 3:00 PM the sync will start, but the vv's will only replicate in batches of 20.
The issue with this is that it can delay the sync, and cause missed SLA's depending on the number of vv's, and the frequency of the sync.
Re: CPG, Volumes, Virtual Volumes Best Practices
Posted: Tue Jul 15, 2014 12:22 pm
by RitonLaBevue
Ok you are talking about async replication
This is what i missed ^^
Did you ever sync replication with some software like 3PAR Recovery Manager for SQL Server ?
In sync mode it allows you to create consistent snapshots on primary and secondary volumes at same time.