Isilon: Error "SyncIQ policy failed. Failback prep cannot be done for a policy which has not finished initial or upgrade sync"

Summary: SyncIQ policy failed. Failback prep cannot be done for a policy which has not finished initial or upgrade sync.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



Re-sync prep job failing with the below error:
 
Error : SyncIQ policy failed. Failback prep cannot be done for a policy which has not finished initial or upgrade sync.
 
After allow-writes on target cluster, there was a policy reset done on source and a re-sync prep job was initiated right after, hence policy failed with the above mentioned error.
Verify if the policy in question has successfully finished its initial sync after reset : -

1) Verify the status of the policy using the command below:
deep1-1# isi sync policies view test
                         ID: 471554d7d8cb72d1e57bf5c489fd64aa
                       Name: test
                       Path: /ifs/data
                     Action: sync
                    Enabled: Yes
                     Target: 192.168.65.9
                Description: abc
            Check Integrity: Yes
 Source Include Directories: -
 Source Exclude Directories: -
              Source Subnet: -
                Source Pool: -
      Source Match Criteria: -
                Target Path: /ifs/data
    Target Snapshot Archive: No
    Target Snapshot Pattern: SIQ_%{SrcCluster}_%{PolicyName}_%Y-%m-%d_%H-%M
 Target Snapshot Expiration: Never
      Target Snapshot Alias: SIQ_%{SrcCluster}_%{PolicyName}
Target Detect Modifications: Yes
    Source Snapshot Archive: No
    Source Snapshot Pattern: -
 Source Snapshot Expiration: Never
      Snapshot Sync Pattern: *
     Snapshot Sync Existing: No
                   Schedule: Manually scheduled
                  Job Delay: -
Skip When Source Unmodified: No
                  Rpo Alert: -
                  Log Level: notice
          Log Removed Files: No
           Workers Per Node: 3
             Report Max Age: 1Y
           Report Max Count: 2000
            Force Interface: No
    Restrict Target Network: No
Target Compare Initial Sync: No
                Disable Stf: No
          Expected Dataloss: No
               Disable Fofb: No
         Disable File Split: No
Changelist creation enabled: No
       Accelerated Failback: No
                   Priority: 0
            Cloud Deep Copy: deny
             Last Job State: failed
               Last Started: 2019-05-30T12:56:35
               Last Success: 2019-05-30T12:50:11
               Password Set: No
                 Conflicted: No
             Has Sync State: No

             
2) Verify the latest report for the policy:
 
deep1-1# isi sync reports list
Policy Name  Job ID  Start Time          End Time            Action  State
-----------------------------------------------------------------------------
test         2       2019-05-30T12:51:10 2019-05-30T12:56:36 run     failed
test         1       2019-05-30T12:50:11 2019-05-30T12:50:17 run     finished
-----------------------------------------------------------------------------
Total: 2

3) The policy was reset and post which a re-sync prep job was initiated which failed because policy did not finish its initial sync post resetting:
 
deep1-1# isi sync reports view test 2
                 Policy Name: test
                      Job ID: 2
                  Start Time: 2019-05-30T12:51:10
                    End Time: 2019-05-30T12:56:36
                      Action: run
                       State: failed
                          ID: 2-test
                   Policy ID: 471554d7d8cb72d1e57bf5c489fd64aa
                   Sync Type: fofb
                    Duration: 5s
                      Errors: (policy name: test target: 192.168.65.9) SyncIQ policy failed. Failback prep cannot be done for a policy which has not finished initial or upgrade sync., deep1.test cannot run during Failover/Failback. (unrunnable), deep1.test cannot run during Failover/Failback. (unrunnable)
  Source Directories Visited: 0
  Source Directories Deleted: 0
  Target Directories Deleted: 0
  
Subreports:
Policy Name  Job ID  Subreport ID  Start Time          End Time            Action      State
---------------------------------------------------------------------------------------------
test         2       1             2019-05-30T12:51:10 2019-05-30T12:51:12 run         failed
test         2       2             2019-05-30T12:52:39 2019-05-30T12:52:41 run         failed
test         2       3             2019-05-30T12:56:35 2019-05-30T12:56:36 resync_prep failed
---------------------------------------------------------------------------------------------
Total: 3

4) Verify the sub-report for the re-sync prep job:
 
deep1-1# isi sync reports subreports view test 2 3
                 Policy Name: test
                      Job ID: 2
                Subreport ID: 3
                  Start Time: 2019-05-30T12:56:35
                    End Time: 2019-05-30T12:56:36
                      Action: resync_prep
                       State: failed
                   Policy ID: 471554d7d8cb72d1e57bf5c489fd64aa
                   Sync Type: fofb
                    Duration: 1s
                      Errors: (policy name: test target: 192.168.65.9) SyncIQ policy failed. Failback prep cannot be done for a policy which has not finished initial or upgrade sync.

Cause

A re-sync prep job was initiated for a policy right after resetting it. The policy was not run again after resetting causing the job to fail.
The basic requirement before proceeding with Failover/Failback is to ensure that the policy has a successful last sync state. If that is not the case then re-sync prep job will fail.

Resolution

Disclaimer: The resolution is to break the target association for the policy using the below commands. Please note that breaking the target association will require one to reset the replication policy before you can run the policy again, hence causing initial sync. This can be performed either from the GUI or the CLI.

On GUI:
  1. On the target cluster navigate to:
Data Protection > SyncIQ > Local Targets 

Select the policy in error and click More, select Break Association. This will break the target association for this policy.
  1. On the source cluster navigate to :
Data Protection > SyncIQ > Policies

Select the policy in error and click More, select Reset Sync State. This will reset the sync status for this policy. 
  1. Run the job again. (Initial sync) 

On CLI:
  1. Break the target association for policy using the below command on target cluster:
# isi sync target break --policy=test
  1. Reset the policy from Source cluster:
# isi sync policies reset test
  1. Start the new job for the policy. (Initial sync) 

Affected Products

Isilon H400

Products

Isilon H400
Article Properties
Article Number: 000055629
Article Type: Solution
Last Modified: 11 Oct 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.