The production and remote copies of a Consistency Group are hosted on XtremlO arrays. During application testing of the remote copy, the Image Access log capacity
does not advance.
Why is the Image Access log capacity static?
A.
Failover has not completed so the writes have not been distributed to the Journal
B.
Application writes are to an XtremlO snapshot and are not stored in the Journal
C.
Journals on XtremlO arrays are virtual and do not track the writes
D.
Application writes are stored in RPA memory when using the XtremlO array
Snapshot Writes: When application testing is performed on a remote copy, writes are directed to an XtremIO snapshot. This snapshot is a point-in-time image of the data.
Journal Behavior: These writes do not advance the Image Access log capacity because the snapshot operates independently of the Journal.The Journal is used for logging changes to the production data, not the snapshot data1.
Static Image Access Log: As a result, the Image Access log capacity remains static during the testing of the remote copy, as it is not affected by the writes to the snapshot1.
It’s important to understand that the Image Access log is designed to track changes to the replicated data in real-time.However, when operating on a snapshot, these changes are not logged in the same way, hence the Image Access log capacity does not change1.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit