Home  Products  Solutions  Downloads  |  Support  |  How to Buy  Partner  |  Press  Contact 


 HA/CDP-Series

  ClusterReplica ENT
 
  ClusterReplica Duo
 
  EzOpenBackup Plus
   
  A Success Story
 
  Order/Price
 

Omni-NFS-Series

 

 

ClusterReplica Duo Edition Support Page
(Part Number: CR-101D)
           

 

Package ClusterReplica Duo Edition Update Patch
Version 2.0
Posted Date 05/02/2008
Build Number D-20080502
Size 20,558 KB
Requirement For version 2.0 Only
Download Link ClusterReplica_duo.exe
Description Enhancements:
  • Add off-group option to failback setup

Fix Bugs:
  • Replication of IIS configuration sometimes hang especially on Win2000.
  • Improve performance for heavy Read/Write with SQL
  • SQL service sometimes is unable to stop at auto-sync.
  • Turn on IIS config auto-update may change the IIS guest account setup on Replica.
  • Unable to delete restore-point folder “Versions” after restarting primary’s service.
  • Improve the performance of Data Restore Point Tool (DPM).
  • Auto-sync a huge file may sometimes cause service faulting.
  • Auto-sync sometimes failed to replicate entire defined source list
  • Replication will fail if DPM is turned on.
  • AppSynchronizer sometimes failed to update data
  • It might lose socket connection when replicating a large file grater than 6G
  •  Fix bug which caused services on Relieved station unable to stop for data replication to proceed.

  • Delay too long for failback when clicking failback manual command from the Relieved Station.

  • Removing filter in a set caused unwanted data replication.

  • prevent the Secondary station using too much CPU time during auto-sync.

  • Failover by DNS failed to add IP

  • UI has bug in DNS failover dialog page.

  • The failback with data replication option sometimes does not work properly.

  • Failback sometimes got 'IP conflict' message.
  • Highly frequent updating IIS configuration in IIS replication set may cause IIS server out of service.
  • IIS configuration backup schedule caused the memory leaking due to failing to close handles for using windows COM components.
  • Apply a solution to avoid a Win2003 x64 tcp bug which is causing 'lost socket connection'.
  • Memory leaking in replicating data change and scheduled sync