Elastifile AsyncDr How to

OVERVIEW

The following document details the deployment procedure for Elastifile AsyncDR
 

Goals

Provide general guidance on the Elastifile AsyncDr

 

Environment Preparation:

In order to deploy Elastifile AsyncDr please use the following procedure

Firewall port 22 must be open between both VPC on each cluster. The Replication agents need to communicate with each other on port 22. 


Prerequisites :

  • 2 X ECFS Systems
  • 2 X EMS external Ip's (Src - DST )

 

network replication DR diagram

Instructions

Once you have Active Elastifile System, Please the following steps to Enable RA on both Source and Destination systems:

1. Install  and Configure Replication Agent (A.K.A RA)  

 

  1. Navigate to SystemView and add Replication Service :

    add a replication service
     
  2. Please check the HA

    Note: External IP s used for connecting to remote site over VPN. Check only if needed.

    add replication service select high availability
     
  3. Wait for RA creation completion both source and target

    replication services added successfully page

    replication service nodes added

     
  4. Once RA installed on Both systems, please Pair the Source & Remote sites:

    Elastifile remote sites page Click the plus sign to open menu and add Remote Site

     
  5. Pair with remote site, Please use the EMS Username & Password.
    Please validate that you enter the relevant IP (Remote & Local)
    pair with remote site add information: site IP, user, password

    paired successfully notification page


2. Elastifile Data Container (DC) Replication using AsyncDR 

 

  1. Navigate to Data Container page
  2. Choose the DC that you want to replicate
  3. Choose Replicate 
  4. Config the replication :



    data container replication setup page
     
  5. Select the Remote site
  6. Config the RPO
  7. Select the snapshot retention 
  8. Select the ACL replication settings
  9. Press Connect and wait for completion.
  10. Press Close.
  11. Check Status :

    dc-src-1 status
     
  12. Check that initial sync started  and the amount of snapshot created :

    remote replication menu
  13. Please Check that Data container created on the Destination Elastifile system

  14. Please wait for Initial sync to complete and that snapshot created according to the retention that configured in step 2.7

    async menu

3. Replication Validation

 

In order to validate that the data replicated please use the following procedure

 

  1. On the remote site, navigate to the relevant Data Container (The  replicated  Data Container - Should have the same name as Source Data Container)
  2. choose one of the snapshots and create Share :

    snapshot menu
     
  3. Modify the relevant settings

    snapshot settings
  4. Copy the share path
  5. mount the new share on Linux machine

    mount command
     
  6. Check the relevant data exist ( That is a Read Only Copy)

4. AsyncDr FailOver to remote Site 

** Failover should be consider carefully since we are making the Destination (DR) as an Active Data Container 

 

  1. Navigate to remote site EMS
  2. Choose the Relevant DC that you want to make as an Active Filesystem, Check the make active


    async menu
     
  3. Choose the relevant snapshot to revert from :


    choose snapshot drop down
     
  4. Navigate to the Source and make the Chosen Dc as Passive
  5. Create An export
  6. mount the Data Container on the destination site and continue to work


    *** Now the Remote site is Active and you can replicate the data to the Production site

5. AsyncDr FailBack to Production  Site 

There can be two options to fail back to the production site:

Scenario 1  - New Production Site 

 

  1. Deploy new cluster in the new production site.
  2. Delete all previous asyncDR pairings.
  3. Pair a new AsyncDR configuration between the DR site to the new production site.
  4. Sync back the data between the DR site to the new production site.
  5. unmount the DC from the DR site. 
  6. Make the production active, this will trigger the final sync.
  7. Choose the production DC and make sure it's active.
  8. Navigate to DR site and make sure that the DC as passive
  9. Check that Replication started and new snapshot created on both Production an DR systems

 

Scenario 2 - FailBack to the existing production site 
 

  1. Bring up the crashed production cluster.
  2. Make the DC passive.
  3. Sync back from the DR site to the production site.
  4. Unmount the DC from the DR site.
  5. Make the production active, this will trigger the final sync.
  6. Choose the production DC and make sure it's active.
  7. Navigate to DR site and make sure that the DC as passive
  8. Check that Replication started and new snapshot created on both Production an DR systems

    async menu

    make active


    make active confirmation
Was this helpful?
How can we improve it?
true
Search
Clear search
Close search
Google apps
Main menu
Search Help Center
true
true
false
false
false