Replica.pptVIP

Copyright ? 2006 EMC Corporation. Do not Copy - All Rights Reserved. Some LVM vendors provide remote replication at the Volume Group level Duplicate Volume Groups need to exist at both the local and remote sites before replication starts This can be achieved in a number of ways – Over IP, Tape backup/restore etc. All writes to the source Volume Group are replicated to the remote Volume Group by the LVM Typically the writes are queued in a log file and sent to the remote site in the order received over a standard IP network Can be done synchronously or asynchronously Synchronous – Write must be received by remote before the write is acknowledged locally to the host Asynchronous – Write is acknowledged immediately to the local host and queued and sent in order Copyright ? 2006 EMC Corporation. Do not Copy - All Rights Reserved. Production work can continue at the source site if there is a network failure, the writes that need to replicated will be queued in the log file and sent over to the remote site when the network issue is resolved. If the log files fill up before the network outage is resolved a complete resynchronization of the remote site would have to be performed. Thus the size of the log file determine the length of network outage that can be tolerated. In the event of a failure at the source site (e.g. server crash, site wide disaster), production operations can be resumed at the remote site with the remote replica. The exact steps that need to performed to achieve this depend on the LVM that is in use. Copyright ? 2006 EMC Corporation. Do not Copy - All Rights Reserved. A significant advantage of using LVM based remote replication is the fact that storage arrays from different vendors can be used at the two sites. E.g. At the production site a high-end array could be used while at the remote site a second tier array could be used. In a similar manner the RAID protection at the two sites could be different as well. Most of the LVM based remote replica