[VERITAS数据中心标准化.pptVIP

* * * * * VVR (Veritas Volume Replicator) - Replication beyond a campus environment For asynchronous replication over IP networks – think about VVR No distance limitations Extension of SF – license option Replicate over TCP/IP and it will replicate synchronously or asynchronously Up to 32 locations with 1:many; many:1; many::many architectures – basically it’s up to how creative the organization wants to be in designing their disaster recovery strategy Fully integrated with VCS for wide area fail-over Can be managed by SFMS Advanced capability – if you replicate synchronously – transactions are committed on both sites before you continue; if network link comes down, VVR is intelligent enough not to failover entire site but rather just switch to asynchronous mode and begin logging transactions at primary site When network link comes back, it will synch both sites without application ever coming down and switch back to synchronize mode When you hear SRDF or Trucopy asynchr – think of VVR – we maintain write-order fidelity for asynchronous replication which is very important (not everyone does this) means that every transaction is committed in exact same order at 2nd site as 1st – you’ll have consistent data when you have a failure; when you have inconsistent data, you will have problems By adding VVR to your environment you are really only adding 3 components: Rlink (Replication Link): Link defines the relationship between one host and another. Can create up to 32 Rlinks in environment Can define each Rlink with a different replication mode. You can replicate NY to NJ synchronously and with the same host replicate NY to SF asynchronously RVG: Replicated Volume Group: Groups consistency volumes together so write order is preserved. For example, Oracle tends to span volumes so this groups all Oracle requests together to make sure they get to the secondary site consistently. The RVG lets customer choose the data, based on volume, that they want to replicate. This