Using the destination file system for other purposes


Using the destination file system for other purposes

In some cases, you may want to stop replicating data to a destination and use the replicated file system as a read-write file system for applications or to recover some data for the source files system.

The exact steps you take depend on the purpose, but here are some guidelines:

  • First, use the Replication> job disable command to disable the replication job and free the destination file system from replication control.

    If the source cluster is available (for example, in a planned, failover-to-destination situation), run the Replication> job disable command on the source cluster.

    If the source cluster is not available (for example, in a disaster situation), you can run the Replication> job disable command on the destination cluster. If you run the Replication> job disable command from the destination cluster, include both the job_name and the link_name to uniquely identify the job.

    See “Disabling a job on the destination cluster”.

  • Once the replication job is disabled, you can use the destination file system in read-write mode and export writable shares using NFS, CIFS, FTP, and so on.

If you do not want to use destination file system as primary file system, but you want to only restore a small number of files and directories from destination, the simplest approach is to SCP the file from the destination to the restore target. In this case, it does not matter whether the original replication job is enabled or disabled.

When you want to restore large amounts of data (or the entire file system) at the source using the destination file system, do the following:

  • Disable and destroy the original replication job.

  • Create a new replication job using the old destination as the new source and use the old source as the new destination.

  • Enable the new job, then use the Replication> job resync command (or the Replication> job trigger command) to start replication.


    If you already have some data present at source file system, you should use the Replication> job resync command for the first time instead of the Replication> job trigger command to avoid full synchronization (to avoid sending the entire data).

Disabling a job on the destination cluster

  1. Use the Replication> job show all_remote_jobs command to show which jobs use the cluster as a replication destination.

    For example:

    Replication> job show all_remote_jobs
    Remotely-Created Job Definitions
    Job Name   Source repunit   Target repunit  Link Name   Schedule Name
    ========   ==============   ==============  =========   =============
    job1       src_ru           tgt_ru          LA_NewYork  my_tzone
  2. Use the Replication> job disable job_name link_name command to disable a job from the list.

    For example:

    Replication> job disable job1 LA_NewYork
    SFS replication WARNING V-288-1379 WARNING: This command must be used 
    only when a replication job was disabled successfully at the source 
    cluster, but could not be disabled at destination cluster because the 
    destination cluster was unreachable at that time. The right way to 
    disable a job is by using the disable command at the source cluster, 
    and this command must be used only under rare cases.
    Do you still want to continue with job disable 
    command [Enter yes/no ]:yes
    SFS replication SUCCESS V-288-1442 Job disable job1 LA_NewYork 
    command completed successfully.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)