- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Upgrade EVA 5000
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
тАО07-05-2006 12:36 PM
тАО07-05-2006 12:36 PM
Our firmware and software needs to be upgraded.
Currently, our cloning procedures do not use "container" technology which means long delays in deleting clones as well as creating.
The newer firmware/software for the EVA allows for clone creation using containers for which creation and deletion (we have been told) is nearly instantaneous.
My questions are directed to those in the forum that have had the upgrade performed.
1. We are told the upgrade will take 8 hours. What have others experienced?
2. What were other "gothchas" you encountered.
Thanks for any and all input.
No points will be issued until the thread is ready to be closed, thus feel free to add to any posts you see appropriate.
Regards,
-dl
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2006 06:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 04:24 AM
тАО07-06-2006 04:24 AM
Re: Upgrade EVA 5000
I should have stated:
We are currently on VCS 3.025 which is EOL.
We can upgrade to VCS 3.028 with minimal down time.
We were told we need to get to VCS 4.XXX in order to take advantage of the use of containers, but that would mean an 8 hour time.
That said, anyone have experience in the down time required to got from VCS 3.XXX to VCS 4.XXX?
Thanks.
-dl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 05:24 AM
тАО07-06-2006 05:24 AM
Re: Upgrade EVA 5000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 05:36 AM
тАО07-06-2006 05:36 AM
Re: Upgrade EVA 5000
I have done three upgrades to VCS 3.038 yet.
Depending on our environment it can take up from 5 to 8 hours.
The whole environment must be down, because all the drivers and version off the server connected to the san must be upgraded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 06:06 AM
тАО07-06-2006 06:06 AM
Re: Upgrade EVA 5000
Let me add that we have HP-UX and windows on the san.
I realize the attached servers will be affected by the down time, but I was not aware of driver changes that needed to occur on the servers for the process.
I was hoping someone might have been able to find ways to reduce the down time.
More input please as this is great.
Thanks.
-dl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 07:24 AM
тАО07-06-2006 07:24 AM
Re: Upgrade EVA 5000
> The newer firmware/software for the EVA
> allows for clone creation using containers
> for which creation and deletion (we have
> been told) is nearly instantaneous.
A 'Container' is a preallocated Virtual Disk which does not contain any data. You can also turn an existing Virtual Disk into a Container - this saves you from deletion and re-allocation.
> Let me add that we have HP-UX
In that case you need to remove Secure Path (Compaq) for Active/Passive controllers. Licensewise, I think you can replace it with SecurePath (HP AutoPath) for Active/Active controllers, but you now have to deal with all device paths instead of a single pseudo LUN.
Well, if you stick with PVlinks you have to deal with multiple device files anyway ;-)
V4 uses a slightly different cabeling rule. This could result in different device paths.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 12:29 PM
тАО07-06-2006 12:29 PM
Re: Upgrade EVA 5000
We recently upgraded our EVA5K from 3.026 to 3.028 t0 v4.004.
We also added a bunch of disk enclosures and disks to the system at the same time.
The outage for us was approx 8hours including the disk work.
As mentioned in a previous post, you will need to update the HBA drivers as well as any HA software you may have (it is advisable).
We only have proliant servers connected, running W2K & W2K03. We had to run a full update of all the Insight agents / foundation packs to ensure we had correct drivers and other utilities worked ok with the controllers.
You may also need to upgrade your Fibre Switch versions. There are reccommended minimum versions for those too. (may be related to the A/A controllers)
We actually took the oportunity to move our hosts form Secure Path to MPIO.
All in all our outage was between 8 & 12 hours including servers; but we took our time to ensure there were no mess-ups.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 12:32 PM
тАО07-06-2006 12:32 PM
Re: Upgrade EVA 5000
I don't know what the likelyhood of a failed upgrade is, but you should be aware of this to ensure that you have sufficient backups!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2006 05:49 AM
тАО07-07-2006 05:49 AM
Re: Upgrade EVA 5000
I did forget the very basic principle of doing a search before asking for input. When serching for VCS upgrade I found a multitude of hits, many of which reference my concerns.
Thus I am closing this thread and thanking all contributors.
Regards,
-dl