Issues addressed in this hotfix are listed at the bottom of this TechFile. VERITAS Volume Manager/Volume Replicator 3.0 for Windows 2000 Service Pack 1 is required to be installed prior to installing this hotfix. Please review the Readme for additional instructions on installing and uninstalling the hotfix, and for more details on the issues addressed by this hotfix.
Use the following steps to download and extract this hotfix:
1. Scroll to the bottom of this TechFile and click Download Now.
2. When prompted, select Save This Program To Disk and click OK.
3. At the next screen, select a location to save the file and click Save.
4. After the download completes, click Open to open the VERITAS Self-Extractor. Optionally, click Close if you prefer to extract the file at a later time. When you are ready to extract it, navigate to the location where it was saved and double-click the file to open the VERITAS Self-Extractor.
5. Select a location to save the extracted files, and then extract the contents by clicking the Extract button. The package contains the following files:
Note: Installing VERITAS Volume Replicator 3.0 for Windows 2000 HotFix04 precludes installing VERITAS Volume Manager (tm) 3.0 for Windows 2000 HotFix04, since they are the same.
While Synchronous replication is occuring, the secondary toggles between connected and disconnected state.
Invalid error message displayed when the primary RVG is stopped while replication is occuring.
Can't do rlink -f or -a att after restoration from configuration mismatch of a detached secondary
Offlining the RVG resource in a MSCS cluster set up fails to stop the primary RVG.
A RVG in a failed state cannot be stopped.
Recovery of Mirrored Striped volumes which are under a RVG fails after disk group deport and import.
A Migrate operation, followed by a Takeover operation and deport of the disk group on the new primary causes the the secondary host to crash with stop code 0x1E
"Operation timed out configuration server may be busy or down" is displayed when srl becomes inconsistent
Under heavy I/O, a primary host that has a RVG made up of Mirrored Striped data and SRL volumes crashes with BAD_POOl_CALLER.
With the primary clustered, attaching the secondary may cause the secondary RVG to go into a configuration error state.
System crashes when a disk containing a non-mirrored DCM is offlined while autosync of the secondary was in progress and a Rescan was done.
Associating a volume using vxrvg assoc command does not disallow RAID-5 volume.
Secondary may crash with STOP 0x1E error after a migrate operation is done.
Migrate failed with Error "Unable to perform operation. Please stop replication and try again."
A Primary host having all Mirrored Striped volumes in the RVG would crash with stop code 0xD1 during heavy write operations.
vxrlink recover fails to recover an unrecovered rlink.
Creation of a single plex DCM not allowed.
DG has to be deported and imported multiple times for the harddisk to be identified as made online
Blue screen with stopcode d1 on pulling out the disk containing srl
After growing volumes using VVR explorer does not show correct capacity
SQL Dumps are extremely slow if VVR is installed and an RDS is created
Changing packet_size attribute on connected RLINK causes data corruption
Data loss in autosync of vol w/regsz > 512 blks & rlink
Rate this Article