about
disclaimer
The old maxim 'You get what you pay for!' applies to this blog. It is neither a support tool nor represents my employer's views. Read the site policies for more information.
© Copyright 2009
The old maxim 'You get what you pay for!' applies to this blog. It is neither a support tool nor represents my employer's views. Read the site policies for more information.
© Copyright 2009
Well, as promised, I spent several days putting together a plan to start rolling out some information and a first pass at Best Practices for OpenVMS. Since I have a subfocus of Storage with OpenVMS, I will start to use that as the launching point. And frankly, it’s one of the most complicated areas to support due to the numerous changes we see in storage technology.
Remember, though I will roll out my first cut at this, I hope this will become a community effort. I will propose various ideas, thoughts and presentations. I will welcome your input. Though I might decide not to include your changes, remember that by sharing your experience you will help other members of the OpenVMS community.
In fact, I offered three different sessions. These include:
I will first present these to the members of the OpenVMS Profession community within HP. Frankly, this will allow me to “dry run” the material before you see it. Then I will offer a more detailed presentation through the HP Technical Online Seminar program.
Then, as I normally do, I will make certain this information will be available through another external distribution mechanism, such as working with the webinar program that the Connect Community organization provides:
http://www.connect-community.org/
So, until I roll more out on that, enjoy. And remember, I welcome your input.
If you enjoyed this post, make sure you subscribe to my RSS feed!
More Options ...
Categories
Tag Cloud
Blog RSS
Comments RSS
Void « Default
Life 
Earth 
Wind 
Water 
Fire Light
Previous 
Comment Meta:
Last 50 Posts
Back
I look forward to reading these, especially around the HP offerings of CA and Business Copy. We’re kind of working without a net right now.
If I’m not mistaken, there are some Best Practices for both CA and Business Copy. I will try to track down the documents on the web.
Of course, with OpenVMS customers for replication within a Metroplitan Area, I also highly recommend they consider HP Volume Shadowing for OpenVMS. This allows synchronous replication between arrays and (more importantly) the ability to transparently handle loss of any single component. For example, you might loose an array, but OpenVMS can continue to work – as long as the data is shadowed to another array.
But for longer distances, there is no doubt that HP CA and Business Copy are the best approach. I am busy working on some a Best Practice presentation for Volume Shadowing. This first presentation will then be presented as a Technical Online Seminar (TOS). About the same time I will start to post articles here.
Anyway, it’s good to hear it wil help.
I was probably a little vague about my statement. You’re absolutely right that CA and Business Copy have best practice documents.
However, a best practice guide for exactly what you’re talking about – when is CA the right choice vs volume shadowing, or when does Business Copy make more sense than splitting shadowsets in an OpenVMS environment – these are things I would love to have HP publish best practice on.
So replication options and preferred methods around storage and backups on VMS are the topics I’m most interested in hearing about.
Thanks for your work on this!
Bingo! Wel, you will be very happy to know that the first three Best Practice presentations and white papers will focus on Best Practices for OpenVMS:
… with Host Based Volume Shadowing
… with Extended SANs
… with Volume Shadowing and Disaster Tolerant Clustering
And as you note, I will try to answer “when is CA the right choice vs volume shadowing, or when does Business Copy make more sense than splitting shadowsets in an OpenVMS environment” and so on.
The presentation / white paper will focus on two area – performance and reliability. It will help you see how to weigh one against the other.
And I’m happy to share my experience and thoughts! : )