[an error occurred while processing this directive]

HP OpenVMS Systems

High Availability/Disaster Tolerance
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

OpenVMS Galaxy FAQs

Q What is the maximum number of soft partitions or Instances of OpenVMS that are supported on the EV7 AlphaServer platforms?
A

Each system model has different limits for the maximum number of instances:

  • ES47 is up to 2 instances of OpenVMS.
  • ES80 is up to 4 instances of OpenVMS.
  • GS1280 is up to 16 instances of OpenVMS.
  • Models 8, 16 and 32 is up to 8 instances of OpenVMS.
  • Model 64 is up to 16 instances of OpenVMS
  • This requires at least two 32P hard partitions with 8 instances in each hard partition.
Q Do I need to buy a Galaxy license for each soft partition or instance of OpenVMS?
A No, OpenVMS Galaxy is licensed by the number of CPUs in an AlphaServer system or in a hard partition. For example, the GS1280 Model 16, with 16 CPUs, would require 1 OpenVMS Galaxy license for 16 CPUs. This allows maximum flexibility for the number of soft partitions that you may require as your business needs change.
Q Will I need to buy separate layered product application licenses for each soft partition of OpenVMS on the AlphaServer system?
A No, the OpenVMS Galaxy license terms allow the HP layered product application licenses to be used for the entire system, regardless of the number of soft or hard partitions. Again, this is for maximum flexibility as your business needs change.
Q If I already have an AlphaServer, what do I need to run OpenVMS Galaxy on it?
A All you should need is the OpenVMS Galaxy license for the number of CPUs in your system. You do need to review the hardware requirements in the HP OpenVMS Partitioning and Galaxy Guide, which is posted at http://h71000.www7.hp.com/availability/galaxy.html.
Q Can I transfer my OpenVMS Galaxy license from my current AlphaServer to my new EV7 AlphaServer?
A Yes. The OpenVMS Galaxy licenses are fully transferable to the new AlphaServer systems for investment protection.
Q How can I manage the resources in an AlphaServer system with Galaxy?
A The Galaxy Configuration Utility (GCU) provides many views of the system; it also facilitates changing the assignment of resources. As simple as dragging and dropping a CPU, the GCU is truly elegant in its ability to graphically represent the system's configuration.
Q Should I use OpenVMS Galaxy on a single system rather than clustering multiple smaller systems?
A The key consideration is that soft partitions can provide higher levels of availability in a single system than with a single instance of the operating system. However, this is not as highly available as multiple systems clusters together. To take advantage of the flexibility of partitioning, but still offer higher availability, partitioning and clustering technologies can be combined.
Q Will OpenVMS Galaxy be available on the HP Integrity Servers when OpenVMS is ported?
A Yes. OpenVMS plans to be part of the HP Partitioning Continuum to support hard and soft partitions on the Integrity Servers in 2005.