PowerFlex：复制中断后重新初始化复制

在命令行中，我们可以找到警告消息，指出“卷处于断开的复制一致性组中”。

# scli --query_all_replication_pairs
query_all_replication_pairs returned 0 Replication Pairs.
WARNING: The System contains 2 volumes in broken replication consistency groups
 
# scli --query_all_replication_consistency_groups
Protection Domain aef4ce8300000000 Name: RHEL7-PD
WARNING: The Protection Domain contains 2 volumes in broken replication consistency groups

在用户界面中，复制一致性组 （RCG） 状态显示以下错误“RCG was deleted by the system”（RCG 被系统删除）。

这些日志文件的用途是启用站点之间复制的平滑重新初始化。日志文件用于在中断原因得到解决后快速重新启动复制过程。
 

可能导致复制中断的原因示例：
a.源站点和目标站点
之间的长期网络故障湾。源站点或目标站点上的容量突然减少 — 例如在数据不可用 （DU） 情形中

复制中断后，MDM 将自动删除源站点和目标站点之间的所有复制一致性组 （RCG）。它会生成复制日志文件，其中包含与已删除 RCG 相关的所有信息。

一个。使用以下格式在主 MDM 下找到自动生成复制中断日志文件 - 

Auto-DeletedOnEndOfJournalCapacityRplCg_<RCG_ID>_<RCG_name>

示例：

# cd /opt/emc/scaleio/mdm/logs
# ls -l AutoDelete*
-rw-r--r-- 1 root root 953 Apr 14 12:15 AutoDeletedOnEndOfJournalCapacityRplCg_4ca1bc9600000000_Rep_Beta1

b.验证导致复制中断的问题是否已修复。

c.c. 通过以下两种方法 之一 重新初始化复制：使用脚本或手动。
 

使用脚本：

1. 生成一个文件，其中包含来自自动生成的日志文件的所有相关命令，以便重新初始化复制

   示例：

   for i in `ls /opt/emc/scaleio/mdm/logs/AutoDeletedOnEndOfJournalCapacity*`;do sed -e '1,/Recreation CLIs/d' $i >> full_replication_restore_$(date +%s); done

    

2. 验证文件是否已成功创建及其内容

   示例：

   [root@112AX-7 logs]# cat full_replication_restore_1587387678 scli --add_replication_consistency_group --replication_consistency_group_name rcg_sanity --destination_system_object_id 416af83800000000 --protection_domain_id b3dd0a5900000000 --remote_protection_domain_id 4ff0744e00000000 --rpo 60 --target_volume_access_mode no_access scli --add_replication_pair --replication_consistency_group_name rcg_sanity --source_volume_id 0da61f0d00000003 --destination_volume_id 1981bbaf00000005 --copy_type full scli --add_replication_consistency_group --replication_consistency_group_name rcg_SANITY2 --destination_system_object_id 416af83800000000 --protection_domain_id b3dd0a5900000000 --remote_protection_domain_id 4ff0744e00000000 --rpo 60 --target_volume_access_mode no_access scli --add_replication_pair --replication_consistency_group_name rcg_SANITY2 --source_volume_id 0da61f2500000000 --destination_volume_id 1981bbb000000006 --copy_type full scli --add_replication_consistency_group --replication_consistency_group_name rcg_sanity3 --destination_system_object_id 416af83800000000 --protection_domain_id b3dd0a5900000000 --remote_protection_domain_id 4ff0744e00000000 --rpo 60 --target_volume_access_mode no_access scli --add_replication_pair --replication_consistency_group_name rcg_sanity3 --source_volume_id 0da61f2600000001 --destination_volume_id 1981bbb100000007 --copy_type full [root@112AX-7 logs]#

    

3. 使生成的文件可执行，然后以管理员身份登录到主 MDM 并运行创建的文件。

   示例：

   # scli --login --username admin --password xxxxxxxxxx Logged in. User role is SuperUser. System ID is xxxxxxxxxxxxxxx # # chmod +x full_replication_restore_1587387678 ; ./full_replication_restore_1587387678 Successfully created Replication Consistency Group rcg_sanity. Object ID 357a6c4f00000001 Successfully created the Pair, ID = a1f1819900000001 Successfully created Replication Consistency Group rcg_SANITY2. Object ID 357a6c5300000003 Successfully created the Pair, ID = a1f1819a00000002 Successfully created Replication Consistency Group rcg_sanity3. Object ID 357a6c5500000005 Successfully created the Pair, ID = a1f1819b00000003

    

4. 通过运行以下命令验证复制是否已成功创建：

   1. scli --query_all_replication_consistency_groups
      scli --query_all_replication_pairs

手动：

1. 检查自动删除的每个 RCG 是否具有自动生成的日志文件：

   示例：

   # ls /opt/emc/scaleio/mdm/logs/AutoDeletedOnEndOfJournalCapacity* /opt/emc/scaleio/mdm/logs/AutoDeletedOnEndOfJournalCapacityRplCg_357a454600000001_rcg_sanity /opt/emc/scaleio/mdm/logs/AutoDeletedOnEndOfJournalCapacityRplCg_357a6c4b00000002_rcg_SANITY2 /opt/emc/scaleio/mdm/logs/AutoDeletedOnEndOfJournalCapacityRplCg_357a6c4c00000003_rcg_sanity3

    

2. 对上述
   
   步骤 1 中的每个文件重复后续步骤 a。检查是否生成了 CLI 命令，并验证其在“Recreation CLIs”下具有相关信息

   示例：

   #cat AutoDeletedOnEndOfJournalCapacityRplCg_357a6c4900000001_rcg_sanity
   
   REPLICATION CONSISTENCY GROUP
   LocalId:357a6c4900000001
   RemoteId:4ca1e3ab00000001
   Name:rcg_sanity
   PeerMdmId:416af83800000000
   RpoSeconds:60
   Direction:LOCAL_TO_REMOTE
   DRState:NONE
   DeletionDecisionTime:20/04 08:37:35
   DeletionReason:AUTOMATIC_ON_END_OF_CAPACITY
   FailureDomainId:b3dd0a5900000000
   RemoteFailureDomainId:4ff0744e00000000
   PAIR 0
   LocalId:a1f1819600000001
   RemoteId:2dfad1c100000001
   LocalVolumeId:0da61f0d00000003
   LocalVolumeName:test1
   RemoteVolumeId:1981bbaf00000005
   RemoteVolumeName:test1
   Recreation CLIs:
   scli --add_replication_consistency_group --replication_consistency_group_name rcg_sanity --destination_system_object_id 416af83800000000 --protection_domain_id b3dd0a5900000000 --remote_protection_domain_id 4ff0744e00000000 --rpo 60 --target_volume_access_mode no_access
   scli --add_replication_pair --replication_consistency_group_name rcg_sanity --source_volume_id 0da61f0d00000003 --destination_volume_id 1981bbaf00000005 --copy_type full

    

   b.运行“Recreation CLIs”部分下显示的所有命令

   示例：

   # scli --add_replication_consistency_group --replication_consistency_group_name rcg_sanity --destination_system_object_id 416af83800000000 --protection_domain_id b3dd0a5900000000 --remote_protection_domain_id 4ff0744e00000000 --rpo 60 --target_volume_access_mode no_access Successfully created Replication Consistency Group rcg_sanity. Object ID 357a6c4f00000001 [root@112AX-7 logs]# scli --add_replication_pair --replication_consistency_group_name rcg_sanity --source_volume_id 0da61f0d00000003 --destination_volume_id 1981bbaf00000005 --copy_type full Successfully created the Pair, ID = a1f1819900000001 [root@112AX-7 logs]#

3. 通过运行以下命令验证复制是否已成功创建：

   1. scli --query_all_replication_consistency_groups
      
      scli --query_all_replication_pairs