1: The journal lag is that amount of data that has been replicated to the target site but has yet to be "played" back to the actual target volume. As all data being replicated first hits the journal before being written to the target volume.
2: Any writes to the volumes included in your consistency group will be replicated, so for instance if they do a local backup of the database to the same volume all of those writes are replicated to your target.
3: This message could indicate that either a full sweep or a volume sweep has completed and the volumes on the source and target side are now Synchronized.
cshocke
4 Posts
0
March 26th, 2009 13:00
2: Any writes to the volumes included in your consistency group will be replicated, so for instance if they do a local backup of the database to the same volume all of those writes are replicated to your target.
3: This message could indicate that either a full sweep or a volume sweep has completed and the volumes on the source and target side are now Synchronized.
Hopefully this helps.
CleanHarborIT
15 Posts
0
November 4th, 2009 08:00