HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Was /CRC always in OpenVMS BACKUP command?
Operating System - OpenVMS
1827845
Members
1169
Online
109969
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
Forums
Discussions
Discussions
Discussions
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
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
01-14-2006 09:17 PM
01-14-2006 09:17 PM
Re: Was /CRC always in OpenVMS BACKUP command?
> That looks a lot like the argument I have been getting for about 10 years on minimerge'
Well, that _is_ the argument. No WHL in the SCSI devices and the existing VMS software could not do mini-merges.
Compaq even spent time to implement history logging in the HSG controller's firmware, but when it was almost ready for release the product became End-Of-Life.
Well, that _is_ the argument. No WHL in the SCSI devices and the existing VMS software could not do mini-merges.
Compaq even spent time to implement history logging in the HSG controller's firmware, but when it was almost ready for release the product became End-Of-Life.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2006 03:42 AM
01-15-2006 03:42 AM
Re: Was /CRC always in OpenVMS BACKUP command?
Uwe wrote . . .
Compaq even spent time to implement history logging in the HSG controller's firmware, but when it was almost ready for release the product became End-Of-Life.
----
Not quite correct. The HSG80-with-WHL capability was never "almost ready for release". At the time when that project was
halted, we were at least 9-12 months away from shipping a finished product. Before that development effort was scrubbed, the HSG80 had already been declared at end-of-life, but we were still planning on releasing the HSG80 firmware change *after*
the EOL designation.
The WHL implementation on the HSG80 differed
significantly from the WLG implementation
on the MSCP-speaking controllers. A key difference is that the write history logging
was kept on the members of the shadow set itself, not inside the controller. We discovered rather late in the development of WHL that this created some theoretical synchronisation issues that were nearly impossible to solve.
After an extensive review of the WHL design,
we decided to start from scratch with HBMM.
Given that WHL would not have ever been extended to any of the new controllers (EVA, etc...), we are pleased that the HBMM
solution is controller-independent!
-- Rob
Compaq even spent time to implement history logging in the HSG controller's firmware, but when it was almost ready for release the product became End-Of-Life.
----
Not quite correct. The HSG80-with-WHL capability was never "almost ready for release". At the time when that project was
halted, we were at least 9-12 months away from shipping a finished product. Before that development effort was scrubbed, the HSG80 had already been declared at end-of-life, but we were still planning on releasing the HSG80 firmware change *after*
the EOL designation.
The WHL implementation on the HSG80 differed
significantly from the WLG implementation
on the MSCP-speaking controllers. A key difference is that the write history logging
was kept on the members of the shadow set itself, not inside the controller. We discovered rather late in the development of WHL that this created some theoretical synchronisation issues that were nearly impossible to solve.
After an extensive review of the WHL design,
we decided to start from scratch with HBMM.
Given that WHL would not have ever been extended to any of the new controllers (EVA, etc...), we are pleased that the HBMM
solution is controller-independent!
-- Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2006 04:37 AM
01-15-2006 04:37 AM
Re: Was /CRC always in OpenVMS BACKUP command?
Now, that is interesting, because:
take a look at document EK-G80CL-RA.B01 (HSG80 Array Controller V8.7 Command Line Interface Reference Guide) - for example: on page 54, which describes the "ADD UNIT" command:
""WRITE_LOG
NOWRITE_LOG (default)
Marks the defined unit as an OpenVMS Host Based Volume Shadowing shadow set member.
IMPORTANT: This switch is only supported with ACS version 8.7R or version 8.7W code. NOTE: The specified unit is only marked and not enabled.
To enable a unit as an OpenVMS Host Based Volume Shadowing shadow set member, a single controller or both controllers of a dual redundant pair must be restarted. During the restart, the additional memory structures required for GWHL are allocated and initialized. Once enabled, the unit can only be disabled as an OpenVMS Host Based Volume Shadowing shadow set member by use of the NOWRITE_LOG command. When the log unit is disabled, it is not necessary to restart the controllers - this needs to be done only when a log unit is enabled. Log units can be JBODs, stripesets, RAIDsets, or mirrorsets. However, this unit cannot be a member of a Snapshot or Remote Copy set.
...""
To me, that looked like the product was almost ready ;-)
Thanks for the update, anyway.
take a look at document EK-G80CL-RA.B01 (HSG80 Array Controller V8.7 Command Line Interface Reference Guide) - for example: on page 54, which describes the "ADD UNIT" command:
""WRITE_LOG
NOWRITE_LOG (default)
Marks the defined unit as an OpenVMS Host Based Volume Shadowing shadow set member.
IMPORTANT: This switch is only supported with ACS version 8.7R or version 8.7W code. NOTE: The specified unit is only marked and not enabled.
To enable a unit as an OpenVMS Host Based Volume Shadowing shadow set member, a single controller or both controllers of a dual redundant pair must be restarted. During the restart, the additional memory structures required for GWHL are allocated and initialized. Once enabled, the unit can only be disabled as an OpenVMS Host Based Volume Shadowing shadow set member by use of the NOWRITE_LOG command. When the log unit is disabled, it is not necessary to restart the controllers - this needs to be done only when a log unit is enabled. Log units can be JBODs, stripesets, RAIDsets, or mirrorsets. However, this unit cannot be a member of a Snapshot or Remote Copy set.
...""
To me, that looked like the product was almost ready ;-)
Thanks for the update, anyway.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2006 01:43 PM
01-15-2006 01:43 PM
Re: Was /CRC always in OpenVMS BACKUP command?
To me, that looked like the product was almost ready ;-)
----
Oh yes, I agree -- the ACS software was certainly near release. It was the work within the shadowing driver that still had a long way to go.
-- Rob
----
Oh yes, I agree -- the ACS software was certainly near release. It was the work within the shadowing driver that still had a long way to go.
-- Rob
- « Previous
-
- 1
- 2
- 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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP