| INFORMATION |
| Published : |
Feb 18, 2009 |
| Length : |
6 |
| Type : |
White Paper |
|
| |
|
|
|
| Overview : |
|
Replication has become a catchall phrase that while gaining in allure is also gaining in confusion – especially in the mid-tier where data is just as important as the high-end, but IT staffing and budgets are far more limited. IT people as well as vendors have a tendency to lump all data movement functions together as replication, regardless of the method or the reason. |
|
 |
 |
|
|
| View All Items By This Company |
| Browse Related Categories : |
|
Application Integration
,
Data Management
,
Data Protection
,
Data Quality
,
Database Development
,
Database Security
,
Enterprise Applications
|
|
|
|
|
|
|
|
Replication has become a catchall phrase that while gaining in allure is also gaining in confusion – especially in the mid-tier where data is just as important as the high-end, but IT staffing and budgets are far more limited. IT people as well as vendors have a tendency to lump all data movement functions together as replication, regardless of the method or the reason. The goal of this paper is to understand the differences in current replication methods as well as the application, or reason, for implementing a given replication schema. The most common use of replication technologies as it relates to the storage sector has been, and will continue to be for Disaster Recovery (DR) purposes. Traditional Content Distribution applications peaked in the late 90’s during the Internet bubble, but are now experiencing a comeback in the global enterprise – predominately for Intranet applications. Replication is also widely used for local (non-remote) applications such as application testing. Remote office backup and remote office IT consolidation (or elimination) are this year’s hot applications for replication.
|
|
|
|
 |
|
