- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- eva3000 upgrade.
Disk Enclosures
1753511
Members
4923
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО07-13-2003 11:38 PM
тАО07-13-2003 11:38 PM
eva3000 upgrade.
Hi all,
I need help in the following questions:
a) eva3000 upgrade to eva5000. Does it require controller swap?
b) Refer to eva3000. Is snap clone the mirror copy of production database? If yes, are we able to break the mirror to create a test database?
I need help in the following questions:
a) eva3000 upgrade to eva5000. Does it require controller swap?
b) Refer to eva3000. Is snap clone the mirror copy of production database? If yes, are we able to break the mirror to create a test database?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2003 10:58 PM
тАО07-14-2003 10:58 PM
Re: eva3000 upgrade.
In order for you to upgrade the EVA3K to an EVA5K, presently there is no upgrade kit.
You need to replace the controllers as the EVA3K uses HSV100, and the EVA5K uses HSV110 controllers.
The VCS software should also be replaced to version 3, resulting in an appliance upgrade to a newer version of the Command View EVA.
The IO Modules in the disk shelves also need replacing as the cables used are fibre channel copper, the new modules use fibre channel optics. The cables should also be replaced from fc copper to fc optics.
So it's quite a major upgrade you might say.
Regards
Christian
You need to replace the controllers as the EVA3K uses HSV100, and the EVA5K uses HSV110 controllers.
The VCS software should also be replaced to version 3, resulting in an appliance upgrade to a newer version of the Command View EVA.
The IO Modules in the disk shelves also need replacing as the cables used are fibre channel copper, the new modules use fibre channel optics. The cables should also be replaced from fc copper to fc optics.
So it's quite a major upgrade you might say.
Regards
Christian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2003 12:08 AM
тАО07-15-2003 12:08 AM
Re: eva3000 upgrade.
To b)
The snap functionality (Business Copy EVA) of EVA3000 and EVA5000 are the same.
A snapclone LUN is immediately accessible for use i.e. for a test database. A full copy is performed in the background. When the cloning has finished the relation between the source and target volume gets abolished!
Out of the BC QuickSpecs at: http://h18006.www1.hp.com/products/quickspecs/11616_div/11616_div.pdf
Snapshots: A standard snapshot is a point-in-time virtual copy of the data, created in seconds and usable immediately, providing maximum flexibility for user applications. Disk capacity is reserved to accommodate the original size of the source volume.
Vsnaps: Virtually capacity free snapshots (Vsnaps) allow the user to create a point-in-time copy, or snapshot, of a specified Virtual Disk (LUN). This Vsnap is similar to the standard snapshot except that it does not reserve the same amount of disk capacity as the production volume being copied. The amount of disk capacity used by the copy volume will grow as data in the production volume changes over time or if Vsnap is set to read/write, as changes are recorded to the Vsnap. The result is that no capacity is wasted using snapshots and the user avoids paying for storage that is not used.
Snapclones: A Snapclone is a complete clone copy of a specified Virtual Disk (LUN). With traditional arrays, a clone can take hours to build depending on its size. Snapclones are available virtually immediately. Within a few moments of when the Snapclone is taken, the entire clone copy is available for use. The Snapclone normalizes in the background so that no time is wasted waiting for the copy to complete. Enterprise Snapclones can also be taken in any redundancy level (RAID 0,1,or 5).
Snapclones provide the ability to take and use a clone without extensive advance preparation. Long ???re-synch??? times are also eliminated with Snapclones since a current clone copy can be available for use in minutes, not hours.
More BC Info: http://h18006.www1.hp.com/products/storage/software/bizcopyeva/index.html
Cheers
Peter
The snap functionality (Business Copy EVA) of EVA3000 and EVA5000 are the same.
A snapclone LUN is immediately accessible for use i.e. for a test database. A full copy is performed in the background. When the cloning has finished the relation between the source and target volume gets abolished!
Out of the BC QuickSpecs at: http://h18006.www1.hp.com/products/quickspecs/11616_div/11616_div.pdf
Snapshots: A standard snapshot is a point-in-time virtual copy of the data, created in seconds and usable immediately, providing maximum flexibility for user applications. Disk capacity is reserved to accommodate the original size of the source volume.
Vsnaps: Virtually capacity free snapshots (Vsnaps) allow the user to create a point-in-time copy, or snapshot, of a specified Virtual Disk (LUN). This Vsnap is similar to the standard snapshot except that it does not reserve the same amount of disk capacity as the production volume being copied. The amount of disk capacity used by the copy volume will grow as data in the production volume changes over time or if Vsnap is set to read/write, as changes are recorded to the Vsnap. The result is that no capacity is wasted using snapshots and the user avoids paying for storage that is not used.
Snapclones: A Snapclone is a complete clone copy of a specified Virtual Disk (LUN). With traditional arrays, a clone can take hours to build depending on its size. Snapclones are available virtually immediately. Within a few moments of when the Snapclone is taken, the entire clone copy is available for use. The Snapclone normalizes in the background so that no time is wasted waiting for the copy to complete. Enterprise Snapclones can also be taken in any redundancy level (RAID 0,1,or 5).
Snapclones provide the ability to take and use a clone without extensive advance preparation. Long ???re-synch??? times are also eliminated with Snapclones since a current clone copy can be available for use in minutes, not hours.
More BC Info: http://h18006.www1.hp.com/products/storage/software/bizcopyeva/index.html
Cheers
Peter
I love storage
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP