After all changes have been replicated from the recovery site to the production site, reverse replication again to restore the original replication relationship between the source appliance and replication target.
loader:> shares replication packages loader:shares replication packages> list ID STATE DATA TIMESTAMP SOURCE DATASET package-002 idle 2015-10-02 19:26:37 hostsource berries package-001 idle 2015-10-02 19:26:10 hostsource berries package-004 idle 2015-10-02 20:53:51 hostsource berries/blackberry package-003 recv 2015-10-02 20:59:52 hostsource cherries/maraschino
The package with the most recent data timestamp for this dataset is the one with the most recent, up-to-date data for the corresponding source dataset.
loader:shares replication packages> select package-002
host-prod:shares replication package-002> pkgreverse
host-prod:shares replication package-002 pkgreverse> set new_project_name=new-kmm3 new_project_name = new-kmm3 host-prod:shares replication package-002 pkgreverse> set enable_action_upon_reversal=true enable_action_upon_reversal = true
host-prod:shares replication package-002 pkgreverse> show Properties: new_project_name = new-kmm3 enable_action_upon_reversal = true host-prod:shares replication package-002 pkgreverse> commit This action will move the contents of this package to a new local project configured to replicate back to the source. Any data or metadata changes made on the source since the last successful update will be lost when the new project is replicated back to the source. If replication actions on the source are not disabled, future updates to this package will fail.