- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Rolling upgrade V7.3-2 to V8.3 problems
Operating System - OpenVMS
1753821
Members
8590
Online
108805
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
Go to solution
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
тАО05-30-2007 10:05 PM
тАО05-30-2007 10:05 PM
Re: Rolling upgrade V7.3-2 to V8.3 problems
I will formally contact the local HP support centre, thanx Robert. That seems the most obvious to do now.
To answer the other questions:
$ directory sys$system:setshoshadow/date/size=all
Directory SYS$COMMON:[SYSEXE]
SETSHOSHADOW.EXE;1 603/604 29-JUN-2006 18:19:09.69
Total of 1 file, 603/604 blocks.
$
so just 1 image luckily.
The HBMM kit is VMS732_HBMM-V0200 from september 2004 which is in the VMS732_UPDATE-V1100 consolidated kit.
And Thomas, a non-rolling upgrade could be more safe, but the concept of rolling upgrade is so nice and tempting: upgrading easily while users can keep on working.
By the way, what you mean by: "Our layered products installations and patch installations are always in batch mode." ?
To answer the other questions:
$ directory sys$system:setshoshadow/date/size=all
Directory SYS$COMMON:[SYSEXE]
SETSHOSHADOW.EXE;1 603/604 29-JUN-2006 18:19:09.69
Total of 1 file, 603/604 blocks.
$
so just 1 image luckily.
The HBMM kit is VMS732_HBMM-V0200 from september 2004 which is in the VMS732_UPDATE-V1100 consolidated kit.
And Thomas, a non-rolling upgrade could be more safe, but the concept of rolling upgrade is so nice and tempting: upgrading easily while users can keep on working.
By the way, what you mean by: "Our layered products installations and patch installations are always in batch mode." ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2007 11:23 AM
тАО05-31-2007 11:23 AM
Re: Rolling upgrade V7.3-2 to V8.3 problems
Jan, this link shows how one can batch patches and installs. Some products can only be installed interactively. We run 4 system disks in our four node cluster and one so called common disk. If you have many patches to install the batch approach makes work easy.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1073507
Here is an example of installing a patch in batch mode. Notice we check to ensure the system account is used.
$ username = f$edit(f$getjpi("","USERNAME"),"COLLAPSE")
$ if username .nes. "SYSTEM"
$ then
$ write sys$output "Use the SYSTEM account."
$ exit 1
$ endif
$ saved_directory = f$environment("DEFAULT")
$ set default kits73:[vms731_ecos]
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ DEFINE/JOB ARCHIVE_OLD NO
$!
$ PROD INSTALL VMS731_SHADOWING/PRODUCER=DEC/BASE=AXPVMS-
/VER=V2.0/SAVE_RECOVERY_DATA
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ set def 'saved_directory'
$ prod show history
$ exit 1
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1073507
Here is an example of installing a patch in batch mode. Notice we check to ensure the system account is used.
$ username = f$edit(f$getjpi("","USERNAME"),"COLLAPSE")
$ if username .nes. "SYSTEM"
$ then
$ write sys$output "Use the SYSTEM account."
$ exit 1
$ endif
$ saved_directory = f$environment("DEFAULT")
$ set default kits73:[vms731_ecos]
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ DEFINE/JOB ARCHIVE_OLD NO
$!
$ PROD INSTALL VMS731_SHADOWING/PRODUCER=DEC/BASE=AXPVMS-
/VER=V2.0/SAVE_RECOVERY_DATA
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ set def 'saved_directory'
$ prod show history
$ exit 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2007 01:31 AM
тАО08-07-2007 01:31 AM
Re: Rolling upgrade V7.3-2 to V8.3 problems
There was a small bug and a workaround from HP.
Before the upgrade, on the 7.3-2 side, remove the HBMM policies with these kind of commands:
$ set shadow /policy=HBMM=(master=*) /name=DEFAULT /delete
and
$ set shadow /disable=hbmm dsa
$ set shadow /policy=hbmm /delete dsa
Check with $ show log/table=h* that no logicals remain.
Then do a rolling upgrade of the first node to 8.3 and re-define the default policy on 8.3:
$ set shadow /policy=HBMM=(master=*) /name=DEFAULT
Then boot the other nodes from the upgraded system disk.
I tested it, problems solved!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2007 01:36 AM
тАО08-07-2007 01:36 AM
Re: Rolling upgrade V7.3-2 to V8.3 problems
Thanx for all help.
- « Previous
- Next »
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