Scenario for Using a Watermark

Consider performing a full migration from a source DR to a test RR environment. The Integration Workspace in the source might be "int_May_2022" and on version 19. When a full migration is executed, the target RR environment will have a MAIN Workspace version of "0" and the information that it came from (int_May_2022) will also be stored.

At some point in the future, after a few features have been delivered and some bugs fixed, int_May_2022 might be on version 27 and you want to migrate only the changes to the test RR environment. To do this:

• You need to determine what was sent the last time that migration occurred. You do this by querying the target environment for the watermark.

• The RR environment responds (in this case) that it was last updated from the int_May_2022\19 Integration Workspace, and the migration execution on the DR environment packages up the correct contents accordingly.

Note: This is tracked in the target RR environment rather than in the DR environment because there is no way to know for certain if a particular export job was ever imported to the target environment. For example, you export some version X with the "intent" to import it into some target environment, but never actually do so. In the case of asynchronous migration, there is no way for the DR environment to know if the import ever occurred. Only the target environment knows for sure what was imported.