- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- VCS Upgrade and CA
HPE EVA Storage
1752808
Members
6033
Online
108789
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
тАО01-21-2011 01:17 PM
тАО01-21-2011 01:17 PM
VCS Upgrade and CA
Hi
Is it possible to do a VCS Code upgrade in the following way when using CA.
Two EVA5000 VCS 3028 at present, CA Between the two.
All hosts are Windows and have the latest Basic and full DSM MPIO for the EVA 5000 installed.
All relevant CV version 7 Licences are installed and working.
Command View version 7.01 will be used as it support both VCS 3.028 and VCS 4.100
Procedure
1: Suspend CA to destination EVA (no other host access)
2: Perform VCS update to VCS 4.100
3: Perform Disk firmware upgrade.
4: change fibre cable config for Active/Active FW
5: Update Zoning config.
6: Restart Command View Server (check updated EVA is operational)
7: Resume CA replication. (wait for logs to flush etc)
8: shutdown host, failover CA for a particular host (check replication direction has changed)
9: Start Host (check storage availability and MPIO path management etc)
10: repeat steps 8 and 9 on all hosts
11: Once the initial source EVA is only a destination for CA Repeat steps 1 to 7.
Is it possible to do a VCS Code upgrade in the following way when using CA.
Two EVA5000 VCS 3028 at present, CA Between the two.
All hosts are Windows and have the latest Basic and full DSM MPIO for the EVA 5000 installed.
All relevant CV version 7 Licences are installed and working.
Command View version 7.01 will be used as it support both VCS 3.028 and VCS 4.100
Procedure
1: Suspend CA to destination EVA (no other host access)
2: Perform VCS update to VCS 4.100
3: Perform Disk firmware upgrade.
4: change fibre cable config for Active/Active FW
5: Update Zoning config.
6: Restart Command View Server (check updated EVA is operational)
7: Resume CA replication. (wait for logs to flush etc)
8: shutdown host, failover CA for a particular host (check replication direction has changed)
9: Start Host (check storage availability and MPIO path management etc)
10: repeat steps 8 and 9 on all hosts
11: Once the initial source EVA is only a destination for CA Repeat steps 1 to 7.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2011 03:09 PM
тАО01-22-2011 03:09 PM
Re: VCS Upgrade and CA
i could not understand why you change the replication direction in between the operation,
just suspend CA, upgrade source, upgrade destination, resume CA,
if you want to check CA that can be done after upgrade also.
your steps 1-7 for upgrade seems OK, btw.
just suspend CA, upgrade source, upgrade destination, resume CA,
if you want to check CA that can be done after upgrade also.
your steps 1-7 for upgrade seems OK, btw.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-25-2011 02:31 AM
тАО01-25-2011 02:31 AM
Re: VCS Upgrade and CA
Thanks for your answer.
The Rational behind the failover is we are not going to be able to take all the hosts down for an extended period whilst we upgrade the VCS Code on both arrays.
As this is a campus CA solution the plan was to upgrade the destination array to VCS 4.100 re-cable and resume CA.
Once CA is synced again failover the hosts to the upgraded array (VSC4.100). Then upgrade the other . There is no requirement to failback to the original source at the end of the process.
I guess the pertinent question is will CA operate as expected with one EVA on VCS 3.028 and one on VCS 4.100 (ie Can we conduct a successful failover). Both EVAs will be upgraded to 4.100 within HPs 1 week supported time frame.
The Rational behind the failover is we are not going to be able to take all the hosts down for an extended period whilst we upgrade the VCS Code on both arrays.
As this is a campus CA solution the plan was to upgrade the destination array to VCS 4.100 re-cable and resume CA.
Once CA is synced again failover the hosts to the upgraded array (VSC4.100). Then upgrade the other . There is no requirement to failback to the original source at the end of the process.
I guess the pertinent question is will CA operate as expected with one EVA on VCS 3.028 and one on VCS 4.100 (ie Can we conduct a successful failover). Both EVAs will be upgraded to 4.100 within HPs 1 week supported time frame.
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