What is LanderSync?
LanderSync is a software with byte-size synchronous replication. Work on
the driver layer of
operating system, any write operation to disc can be caught. Be able to
‘push’ the changeable bytes the users concern to the target equipment by IP
network, realize real-time data synchronization between source address
and destination address.
The
so-called synchronous replication of LanderSync is that any data changes
from source are ‘pushed’ to the destination synchronously. If the data
fail to be delivered to the destination because of network jam, the
replication is unreal-time.
Understand LanderSync from the following aspects:
1. Platform support : Windows 2000 or above;
2. Application scope: all data replication, including databases and files;
3. Size of replication: byte-size level;
4. Synchronous mechanism: Push;
5. Replicate strategy: one-way
What is LanderSync able to do?
The problem LanderSync is able to solve is that the data change can be replicated in byte-size. On the basis of the feature, it usually has application in mirror high availability (MirrorHA) and data disaster recovery. MirrorHA is a solution using mirror technology to synchronize data between the two servers, which have no shared storage. The data in one server is replicated to another server synchronously, which is to ensure the consistency of data between two servers after cluster shifting.
In data disaster recovery, when the productive system meets with disaster, the production center will be taken over by disaster recovery center, which then will provide related application services. As a rule, because of the long distance between the production center and the disaster recovery center, the consistency of data relys on the data replicator software, such as LanderSync, which synchronizes data by network.
Technical Innovation in LanderSync :
Byte-size monitoring
Initiative PUSH mechanism
Data manipulation based on bare equipment
Advantages of LanderSync:
1. High-level security
2. Fast speed of replication
3. Low resource occupancy
4. Easy implementation
5. Easy management
6. Integration with Cluster slitlessly
Technical Indexs of LanderSync:
|
Description |
Index |
|
Supported synchronous links |
3 |
|
Supported nodes |
2～256 |
|
Supported repliacate tasks |
8，256 |
|
Type of replicate tasks |
Volumn/Catalog/File/Database |
|
Size |
Byte-size level |
|
Replicate thread |
Single-thread,multi-thread |
|
Data reduction |
Optional |
|
Supported platform |
Windows2000 or above |
|
Supported cluster software |
All |
|
Language |
English,Chinese |
|
Graphic management monitor |
Support |
|
Direction of replication |
one-way, multi-way |
Comparison of LanderClusterMirrorHA and LanderClusterHA:
LanderClusterMirrorHA: a solution using mirror technology to synchronize data between the two servers.
LanderClusterHA: a solution using shared storage.
|
Comparison |
LanderClusterMirrorHA |
LanderClusterHA |
|
Requirements for maintaining |
High,Complicated |
Low,Simple |
|
Data storage |
Business data are stored in active and standby servers. |
Business data are stored in shared storage. |
|
Speed of application shifting |
Fast(related with sync stress) |
Fast(<30s) |
|
Suitable system |
Low rate of data increment, the long distance between servers |
High rate of data increment, fast fault shifting |
|
The influence on the performance of active equipment |
The occupancy of CPU is 0－30％(related with sync stress). |
The occupancy of CPU is less than 5%. |
|
Influence on network |
The using of bandwidth is less than 40%. |
The using of bandwidth is less than 1%. |
|
Requirements for storage |
Active and standby equipments must have enough storage space, which can store business data and affairs log. |
It needs shared storage array, which satisfies the business storage. |
|
Requirements for network |
Each server need one network card at least. |
Each server need two network cards at least. |
|
Requirements for distance |
TCP/IP is connected, no distant limitation. |
TCP/IP is connected, and take the distance of storage into consideration. |
|
Total cost |
Low |
It needs storage.High |
|
Requirements for servers |
The capability of the two servers is agree with each other. |
The capability of the two servers could not agree with each other. |
