After a failure occurs at the production site, perform a reverse replication at the recovery site, and then redirect client operations to the recovery site.
host-offsite:> shares replication
host-offsite:shares default replication> sources
In this example, source-001 is the source appliance number, and host-prod is the source appliance name. kmm2 is the local project name in replication package number package-001.
source-001 host-prod PROJECT STATE LAST UPDATE package-000 <unknown> idle unknown package-001 kmm2 idle Wed May 01 2015 20:06:27 GMT+0000(UTC)
host-offsite:shares default replication sources> select source-001
host-offsite:shares default replication source-001> select package-001
host-prod:shares replication source-005 package-000> pkgreverse
The pkgreverse command preserves the properties of the original replication action, including schedules.
host-prod:shares replication source-000 package-000 pkgreverse> set new_project_name=new-kmm2 new_project_name = new-kmm2 host-prod:shares replication source-000 package-000 pkgreverse> set enable_action_upon_reversal=true enable_action_upon_reversal = true
host-prod:shares replication source-000 package-000 pkgreverse> show Properties: new_project_name = new-kmm2 enable_action_upon_reversal = true host-prod:shares replication source-000 package-000 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.
Depending on the protocol used, map (SMB clients) or remount (NFS clients) the shares using the IP address or name of the appliance at the recovery site.