HP Volume Shadowing for OpenVMS

HP Volume Shadowing for OpenVMS SPD 27.29.21
HARDWARE REQUIREMENTS
Volume Shadowing for OpenVMS does not depend on
specific hardware to operate. Basic shadowing func-
tions can be performed on any supported system. Mem-
bers of a shadow set can be located on any single
system or anywhere in an OpenVMS Cluster system.
There are no restrictions on the location of shadow set
members beyond the valid disk configurations defined in
the HP OpenVMS Operating System for Alpha Version
7.3-1 and 7.3-2, and VAX Version 7.3 Software Product
Description (SPD 25.01.xx) or the HP OpenVMS for Al-
pha and Integrity Servers Version 8.3 Software Product
Description (SPD 82.35.xx), and the OpenVMS Cluster
Software Software Product Description (SPD 29.78.xx).
Disk Controller Support
Volume Shadowing for OpenVMS supports all disk con-
trollers listed as supported in the HP OpenVMS Oper-
ating System for Alpha Version 7.3-1 and 7.3-2, and
VAX Version 7.3 Software Product Description (SPD
25.01.xx) or the HP OpenVMS for Alpha and Integrity
Servers Version 8.3 Software Product Description (SPD
82.35.xx), with the exception of VAX SCSI controllers
and IDE controllers.
Volume Shadowing for OpenVMS can be used with
controllers that do not support READL (read long) and
WRITEL (write long) subject to the restriction that all
OpenVMS devices that are to be used as shadow set
members are composed of fault tolerant devices, such
as:
• RAID 1—otherwise known as controller-based mir-
roring, or
• RAID 5—which is striping with a parity device, or
• Advanced Data Guard, which is striping with multiple
parity devices
• Any XP Storage Array controller
• Any SmartArray-family of Backplane RAID controller
Disk Drive Support
Volume Shadowing for OpenVMS supports all disk
drives listed as supported in the HP OpenVMS Oper-
ating System for Alpha Version 7.3-1 and 7.3-2, and
VAX Version 7.3 Software Product Description (SPD
25.01.xx) or the HP OpenVMS for Alpha and Integrity
Servers Version 8.3 Software Product Description (SPD
82.35.xx), with the following constraints and exceptions:
• RF35 and RF73 disk devices must use at minimum
firmware version T392F.
• RF36 and RF74 disk devices must use at minimum
firmware version V427P.
• KDM70 controllers must be at minimum microcode
revision 4.3.
• Disks attached to a local VAX SCSI controller on
VAX 4000 and VAX 3000 series systems are not sup-
ported.
• IDE devices.
OpenVMS Cluster Environment
Volume Shadowing for OpenVMS is fully supported in
an OpenVMS Cluster when installed on any valid and li-
censed configuration. Volume Shadowing for OpenVMS
allows shadowing of disks that are locally connected to
the system on which this software is installed. In ad-
dition, Volume Shadowing for OpenVMS allows a user
on an OpenVMS system to shadow disks connected to
other systems within the same OpenVMS Cluster. In a
mixed architecture cluster of Alpha and Integrity server
systems or Alpha and VAX systems, the capability ap-
plies to both system architectures.
An OpenVMS Cluster quorum disk cannot be shad-
owed.
For additional information, refer to the OpenVMS Cluster
Software Software Product Description (SPD 29.78.xx).
SOFTWARE REQUIREMENTS
Volume Shadowing for OpenVMS is a System Inte-
grated Product that, as described in this SPD, requires
OpenVMS Alpha Version 7.2-2 and higher, or OpenVMS
for Integrity servers V8.2 and higher.
For additional information, and minimum software and
firmware revisions for storage subsystems, refer to the
HP OpenVMS Operating System for Alpha Version 7.3-1
and 7.3-2, and VAX Version 7.3 Software Product De-
scription (SPD 25.01.xx) or the HP OpenVMS for Alpha
and Integrity Servers Version 8.3 Software Product De-
scription (SPD 82.35.xx).
OPTIONAL SOFTWARE
Optional products that may be useful when running Vol-
ume Shadowing for OpenVMS include:
• OpenVMS Cluster Software (SPD 29.78.xx)
• DECram for OpenVMS (SPD 34.26.xx)
• RAID Software for OpenVMS (SPD 46.49.xx)
GROWTH CONSIDERATIONS
The minimum hardware and software requirements for
any future version of this product may be different from
the requirements for the current version.
4