- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA Continuous access
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
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
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
тАО06-19-2006 10:07 AM
тАО06-19-2006 10:07 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 05:39 AM
тАО06-20-2006 05:39 AM
Solution> how is it kept uncorrupted/in tact
By properly keeping track of the internal meta data.
> synchronized during datatransfer during CA operations?
That is a function of the controller firmware - if it does not - that would be a bug in the software.
> I wouldn't know the block count to ensure my DR disk is the correct size to copy to if I don't know where the data is precisely.
Sorry, I don't understand - the EVA firmware makes sure that the destination virtual disk has the same size like the source disk. In fact, it creates the destination virtual disk for you when you set up a copy-set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 05:50 AM
тАО06-20-2006 05:50 AM
Re: EVA Continuous access
That clears many things up for me. So the firmware handles most of the operations. If its not to much to ask, might you expand on "properly keeping track of the internal meta-data"... just a brief note would suffice...is there a tool,script, or section in the GUI I should familiarize myself with ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 06:06 AM
тАО06-20-2006 06:06 AM
Re: EVA Continuous access
What I meant is: the integrity of the user data is ensured by not making programming errors in the controller firmware.
If you will be responsible for managing / implementing CA EVA, I suggest you make yourself familiar with:
- Command View EVA - the main management GUI
- SSSU (Storage System Scripting Utility)
-- for simple automation tasks
- RSM (Replication Solutions Manager)
-- a framework for Business Copy and Continuous Access management tasks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 06:08 AM
тАО06-20-2006 06:08 AM
Re: EVA Continuous access
Much Obliged