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
тАО02-12-2009 05:02 AM
тАО02-12-2009 05:02 AM
Boot
The disk is visible from >>> prompt.
The SAN disk which is also the system disk of Server A will also be shared by Server B,C and D.
The servers will be members of the same cluster.
I need to setup multiple roots on the same disk.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 05:14 AM
тАО02-12-2009 05:14 AM
Re: Boot
if the disk is currently 'empty', boot from the OpenVMS operating system CD and install OpenVMS onto the $1$DGAn: disk.
Set up and configure system A. Root will default to [SYS0].
Make the system a cluster member using @CLUSTER_CONFIG_LAN.
Then configure the other systems (roots) from system A by again using @CLUSTER_CONFIG_LAN and adding additional nodes to your system disk.
Once the roots for the other systems have been configured, use WWIDMGR on the other nodes to configure the path to the system disk and make sure to select the correct root in BOOT_OSFLAGS, i.e. BOOT_OSFLAGS 1,0 will boot from [SYS1]
Always be careful to NOT boot any of the other systems with VAXCLUSTER=0, if another system is already running from that disk.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 05:17 AM
тАО02-12-2009 05:17 AM
Re: Boot
clusters are a bit of large topic, see chapter 5 in the vms cluster manual here :-
http://h71000.www7.hp.com/doc/731final/documentation/pdf/ovms_731_cluster_systems.pdf
but a good read of it generally will be useful to you as well as the guidelines for clusters here :-
http://h71000.www7.hp.com/doc/82final/6318/aa-q28lh-tk.pdf
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 05:33 AM
тАО02-12-2009 05:33 AM
Re: Boot
Let me give you the entire picture....
The SAN disk is not empty,I need to upgrade the OS to 7.3-2 from 7.3-1 which is having multiple roots and are shared by 4 systems in a cluster.
My question is : How do I upgrade..?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 05:38 AM
тАО02-12-2009 05:38 AM
Re: Boot
you cannot upgrade that disk, while other systems are actively running from it.
If you cannot shut down all the system at the same time, you need to perform a 'rolling update':
Make a BACKUP/IMAGE copy of the disk to an empty disk, then upgrade that disk to V7.3-2 (plus patches !) and then boot the other systems from that updated disk.
Easier said than done...
If you have no experience with this kind of operation, consider to get professional help.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 05:56 AM
тАО02-12-2009 05:56 AM
Re: Boot
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 06:03 AM
тАО02-12-2009 06:03 AM
Re: Boot
If there is something to do for the node-specific parts, the upgrade procedure will look into all system roots.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 06:03 AM
тАО02-12-2009 06:03 AM
Re: Boot
an OpenVMS cluster system disk contains only ONE copy of the operating system. The data in the specific roots is just NODE-specific data.
After you've shutdown all your nodes booting from that disk, just boot ONE node (maybe the one which boots from [SYS0]) from the CD and upgrade the system disk. Once you're done, boot that node from the updated disk and also boot all other nodes from that disk. They will run an @AUTOGEN during the first boot and reboot automatically. After that you're done with your cluster upgrade to V7.3-2. Don't forget to install the current patches.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 06:24 AM
тАО02-12-2009 06:24 AM
Re: Boot
While it is common to update a system volume in-place, it is not the best approach.
As Volker said, far better to create a copy of the system disk, update the copy, and then re-boot each node in turn so that they are operating off of the new version of the system.
OpenVMS has an excellent record for few problems with updates. However, "few" is not the same as "none". On a production system, backups, particularly with the current costs of disks, are far cheaper than the alternatives.
Basically, the best approach is to create two system disk images, ALFA and BRAVO, and see-saw between them as the cluster is upgraded. When the new version is considered sufficiently stable that a retreat is not necessary, reverse the process and have two sets of the current system image.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 06:33 AM
тАО02-12-2009 06:33 AM
Re: Boot
But,I can find the following :
Directory SYS001:[000000]
SYS1.DIR;1 SYS10.DIR;1 SYS11.DIR;1 SYS12.DIR;1
SYS2.DIR;1 SYS3.DIR;1 SYS4.DIR;1 SYS8.DIR;1
SYS9.DIR;1 SYSLOST.DIR;1 SYS_BATCH.DIR;1
Total of 11 files.
There is no sys0..so if I upgrade the disk it should create sys0 by default which is (I suppose) is going to be a new installation.
Thanks