- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- EVA4400, how many mirror clones can we get away wi...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2011 11:44 AM
09-07-2011 11:44 AM
EVA4400, how many mirror clones can we get away with?
We have 4 copies of similar data: our production database, a read-only copy for reporting and two development copies. The production and reporting copies are on an EVA4400. The reporting copy sits on a mirror clone of the production copy and on a nightly basis we shutdown the reporting copy, resync it with production, then fracture it again for a clean, updated reporting database. The other two development envs have been on some old VA's but one is having some serious issues and replacement hardware is getting more difficult to find. We are considering moving these over to the EVA now and trying to figure out the best strategy. The initial thought was to just chunk out space for these databases and restore the data over. I'm wondering though how feasible it would be to make 2 more mirror clones of the production database to be the new development databases. The plus would be that data refreshes would be quicker than the copies or restores we use now however I'm not sure if it would mean a noticeable performance hit on the production database to maintain these additional mirror clones though or if there are other issue that this might cause... Any advice/comments/suggestions?