HP StorageWorks XP Remote Web Console Software - Manual (Page 16)

You can use XP Remote Web Console computers to delete journal volumes.
Cautions:
◦ If you delete a mainframe journal volume from a journal group where a data volume pair
has ever been registered, the deleted volume (LDEV) will be blocked. To reuse the volume
as a data volume, you must format the volume by using Virtual LVI/LUN (VLL). Unless you
format the volume, data in the volume will not be guaranteed.
◦ Assume that you have performed the following actions in this order:
– register a journal volume in the disk subsystem whose microcode version is 50-07-XX,
– downgrade the microcode version to 50-06-XX or earlier,
– use the downgraded disk subsystem to create a URz pair that uses the journal volume,
and
– delete the URz pair.
Given the above situation, if you upgrade the microcode version back to 50-07-XX and
then delete the journal volume, the volume will not be blocked. However, note that you
must format the volume if you want to reuse the volume as a data volume.
For instructions on formatting volumes, see the Virtual LVI/LUN and Volume Shredder user's
guide. The volume does not need to be formatted in order to register the deleted volume as
a journal volume again.
•
Access from hosts to journal volumes:
If a path is defined from a host to a volume, you cannot register the volume as a journal
volume.
You cannot define paths from hosts to journal volumes. This means that hosts cannot read from
and write to journal volumes.
Journal Volume Areas
The journal volume consists of the metadata area and the journal data area. The ratio of metadata
area to journal data area is common in the journal volumes within the journal group.
In the metadata area, the metadata that manages the journal data is stored. For further information
on the metadata area, see
Table 3 (page 21) . The journal data that the metadata manages is
stored in the journal data area.
If the metadata or the journal data cannot be stored for a given length of time because the metadata
or journal data areas have become full with the metadata or the journal data that had not been
discarded, the pair is suspended according to a failure. Users can use an XP Remote Web Console
computer to specify this timeout period (Data overflow watch) as a journal group option. This
timeout period must be within the range of 0 to 600 seconds. For details on journal group options,
see
Changing Options for a Journal Group .
Remote Copy Connections
The remote copy connections are the physical paths used by the primary storage systems to
communicate with the secondary storage systems. Remote copy connections enable communication
between the primary and secondary storage systems. The primary storage systems and secondary
storage systems are connected via Fibre Channel interface cables. You must establish paths from
the primary to the secondary storage system, and also from the secondary to the primary storage
system. Up to eight paths can be established in both of these directions.
When Fibre Channel interface (optical multimode shortwave) connections are used, two switches
are required for distances greater than 0.5 km (1,640 feet), and distances up to 1.5 km (4,920
feet, 0.93 miles) are supported. If the distance between the primary and secondary sites is greater
than 1.5 km, the optical single mode long wave interface connections are required. When Fibre
16 Overview of Universal Replicator for Mainframe Operations