XtremIO: Yerel Çoğaltma özellikli bir XtremIO kümesini farklı bir XMS'e taşıma

Summary: Bazen bir XtremIO kümesini bir XMS'den diğerine taşımak gerekir. Bu işlem genellikle basittir ve XMCLI komutları kullanılarak kümeyi mevcut XMS'den kaldırıp yeni bir XMS'ye ekleyerek gerçekleştirilir. Ancak XtremIO kümesinin yerel uzaktan çoğaltmaya dahil olması durumunda, küme çoğaltma durumunu korumak için birkaç ek adım gereklidir. ...

Bu makale şunlar için geçerlidir: Bu makale şunlar için geçerli değildir: Bu makale, belirli bir ürüne bağlı değildir. Bu makalede tüm ürün sürümleri tanımlanmamıştır.
Diğer kaynaklara göz atın

Instructions

  1. Örnek Yapılandırma
Yordama yardımcı olması için aşağıdaki örneği kullanıyoruz:
  • İlk XtremIO Yerel Çoğaltma kaynağı XMS ve küme: vxms-xbrickdrm918/xbrickdrm918
  • İlk XtremIO Yerel Çoğaltması hedef XMS ve küme: vxms-xbrickdrm919/xbrickdrm919
  • Yeni XMS sistemi: vxms-xbrickdrm912
  1. Prosedürün Amacı
Örneğimizdeki amaç, kaynak xbrickdrm918XtremIO kümesini vxms-xbrickdrm918'denvxms-xbrickdrm912'ye taşımaktır.
  1. İşlemler

Yerel Çoğaltma özellikli XtremIO kümesini farklı bir XMS'e taşımak için izlenecek süreç aşağıda verilmiştir.

  1. Mevcut çoğaltma yapılandırmasını ve durumunu kontrol edin.
xmcli (admin)> show-remote-protection-sessions
Name Index Replication-State Replication-Mode Source-Cluster-ID Source-CG-Id Target-Cluster-ID Target-CG-Id Lag RPO Target-Policy-ID Cycle-Percent-Remaining(Ratio)
REP1 1     active            async            xbrickdrm919 [1]  CG1 [1]      xbrickdrm918 [1]  CG1 [1]      8   60  [0]              0

xmcli (admin)> show-remote-protection-peer-xms
XMS-Alias         Index SW-Version IP-Address    XMS-Connectivity-State
vxms-xbrickdrm919 0     6.3.0-60   10.225.65.xxx connected
vxms-xbrickdrm918 0     6.3.1-5    10.225.65.yyy  connected

xmcli (admin)> show-remote-protection-ip-links
Name                        Index A-End-XMS-ID          A-End-Cluster-ID A-End-IP-Addr     A-End-Port-ID      Z-End-XMS-ID          Z-End-Cluster-ID Z-End-IP-Addr     Z-End-Port-ID      IP-Link-State IP-Link-Consistency-State Certainty
xbrickdrm918-xbrickdrm919_1 1     vxms-xbrickdrm918 [0] xbrickdrm918 [1] 192.168.33.bbb/16 X1-SC2-target1 [6] vxms-xbrickdrm919 [1] xbrickdrm919 [1] 192.168.33.aaa/16 X1-SC2-target1 [6] Up            consistent                ok
xbrickdrm918-xbrickdrm919_2 2     vxms-xbrickdrm918 [0] xbrickdrm918 [1] 192.168.23.bbb/16 X1-SC1-target2 [2] vxms-xbrickdrm919 [1] xbrickdrm919 [1] 192.168.23.aaa/16 X1-SC1-target2 [2] Down          consistent                ok
xbrickdrm918-xbrickdrm919_3 3     vxms-xbrickdrm918 [0] xbrickdrm918 [1] 192.168.34.bbb/16 X1-SC2-target2 [7] vxms-xbrickdrm919 [1] xbrickdrm919 [1] 192.168.34.aaa/16 X1-SC2-target2 [7] Down          consistent                ok
xbrickdrm918-xbrickdrm919_4 4     vxms-xbrickdrm918 [0] xbrickdrm918 [1] 192.168.22.bbb/16 X1-SC1-target1 [1] vxms-xbrickdrm919 [1] xbrickdrm919 [1] 192.168.22.aaa/16 X1-SC1-target1 [1] Up            consistent                ok
  1. Yeni XMS'yi ekleyin.

Yeni XMS'yi, yerel XMS'nin uzak koruma etki alanına ekleyin. Bu örnekte vxms-xbrickdrm912'yivxms-xbrickdrm919 dizinine ekliyoruz.

xmcli (admin)> add-remote-protection-peer-xms remote-ip-addr="10.225.65.zzz" remote-user-password="xxxxxxxx" remote-xms-user="admin" remote-xms-alias-name="xbrickdrm912"
New Remote Protection peer XMS added successfully

xmcli (admin)> show-remote-protection-peer-xms
XMS-Alias         Index SW-Version IP-Address    XMS-Connectivity-State
vxms-xbrickdrm919 0     6.3.0-60   10.225.65.xxx connected
vxms-xbrickdrm918 0     6.3.1-5    10.225.65.yyy  connected
xbrickdrm912      1     6.3.1-5    10.225.65.zzz connected
  1. Kümeyi mevcut XMS'den kaldırın.
Bu örnekte, xbrickdrm918 kümesini vxms-xbrickdrm918 XMS'den kaldırıyoruz. 
xmcli (admin)> remove-cluster cluster-id=1 cluster-psnt="XXXXXXXXXXXXXXX" 
Are you sure you want to remove cluster xbrickdrm918 [1]? (Yes/No): Please enter either Yes or No: yes [###################################################] 100%        (elapsed time 00:00:15) Cluster xbrickdrm918 [1] removed successfully
  1. Orijinal XMS'yi çoğaltma etki alanından kaldırın. 

Bu örnekte, orijinal vxms-xbrickdrm918 XMS'yi vxms-xbrickdrm919 uzak koruma etki alanındaki XMS'den kaldıracağız.

xmcli (admin)> remove-remote-protection-peer-xms xms-alias-name="vxms-xbrickdrm918"
XMS was removed from RM Domain

  1. Yeni XMS'ye küme ekleme.

xbrickdrm918 kümesini vxms-xbrickdrm912 XMS e eklemek için aşağıdaki komutu kullanıyoruz.

xmcli (admin)> add-cluster sc-mgr-host="10.139.88.ccc"
20:26:23 - Collecting cluster information
20:26:38 - Loading data from cluster
Clusters added successfully
  1. Taşıma işleminin başarıyla tamamlandığını onaylayın.
    1. 5 dakika bekleyin ve ardından her iki XMS'den çoğaltma oturumlarını ve IP bağlantıları durumlarını kontrol edin. 
    2. Durumu vxms-xbrickdrm919'dan kontrol edin.
xmcli (admin)> show-remote-protection-session protection-session-id=1
Name: REP1
Index: 1
Replication-State: active
Replication-Mode: async
Replication-State-Details:
Replication-Direction: failover
Block-Access-Type: read_only
Source-XMS-Id:
                Name: xbrickdrm912
                Index: 1
Source-Cluster-ID:
                Name: xbrickdrm918
                Index: 2
Source-CG-Id:
                Name: CG1
                Index: 1
Target-XMS-Id:
                Name: vxms-xbrickdrm919
                Index: 0
Target-Cluster-ID:
                Name: xbrickdrm919
                Index: 1
Target-CG-Id:
                Name: CG1
                Index: 1
Num-Of-Vols: 2
RPO: 60
Max-BW(MB/s): 0
Protection-Window-Num-Copies: 0
Protection-Window-Duration-in-Days: 0.000
Current-Protection-Window-Copies: 1
Source-Retention-Policy-ID:
                Name:
                Index: 0
Target-Retention-Policy-ID:
                Name:
                Index: 0
Number-Of-Target-PITs: 1
Target-Pit-Num-Copies-Status: ok
Target-Pit-Window-Size-Status: ok
Number-Of-Source-PITs: 2
Next-Scheduled-Cycle: 2020-09-16 20:41:06
Lag: 16
BW(KB/s): 0
Transfer-Efficiency-Ratio(Ratio): 1
Cycle-Start-Time(Timestamp): Wed Sep 16 20:40:20 2020
Last-Cycle-Start-Time(Timestamp): Wed Sep 16 20:40:20 2020
Last-Cycle-Completed-Snapshot-Set: be8cf226e64046c3a3092ef3a4ae0689
Last-Cycle-Duration: 1
Last-Cycle-Link-BW(KB/s): 0
Last-Cycle-Effective-Bandwidth(KB/s): 0
Last-Cycle-Transfer-Efficiency-Ratio: 1
Cycle-Number(Count): 76
Num-Missing-Short-Period-Snapshot-Sets: 0
Num-Missing-Middle-Period-Snapshot-Sets: 0
Num-Missing-Long-Period-Snapshot-Sets: 0
Target-Missing-Pits-Alert: enabled
Test-Copy-Mode: False
Snapset-Backup-Snapset-Index: []
Current-Command-Name: start
Current-Command-Status: success
Replication-Session-Consistency-State: consistent
Obj-Severity: information
Verification-Schedule: adaptive
xmcli (admin)>

xmcli (admin)> show-remote-protection-sessions
Name Index Replication-State Replication-Mode Source-Cluster-ID Source-CG-Id Target-Cluster-ID Target-CG-Id Lag RPO Target-Policy-ID Cycle-Percent-Remaining(Ratio)
REP1 1     active            async            xbrickdrm918 [2]  CG1 [1]      xbrickdrm919 [1]  CG1 [1]      23  60  [0]              0
xmcli (admin)>

xmcli (admin)> show-remote-protection-ip-links
Name                        Index A-End-XMS-ID     A-End-Cluster-ID A-End-IP-Addr     A-End-Port-ID      Z-End-XMS-ID          Z-End-Cluster-ID Z-End-IP-Addr     Z-End-Port-ID      IP-Link-State IP-Link-Consistency-State Certainty
xbrickdrm918-xbrickdrm919_1 1     xbrickdrm912 [1] xbrickdrm918 [2] 192.168.33.bbb/16 X1-SC2-target1 [6] vxms-xbrickdrm919 [0] xbrickdrm919 [1] 192.168.33.aaa/16 X1-SC2-target1 [6] Up            consistent                ok
xbrickdrm918-xbrickdrm919_2 2     xbrickdrm912 [1] xbrickdrm918 [2] 192.168.23.bbb/16 X1-SC1-target2 [2] vxms-xbrickdrm919 [0] xbrickdrm919 [1] 192.168.23.aaa/16 X1-SC1-target2 [2] Down          consistent                ok
xbrickdrm918-xbrickdrm919_3 3     xbrickdrm912 [1] xbrickdrm918 [2] 192.168.34.bbb/16 X1-SC2-target2 [7] vxms-xbrickdrm919 [0] xbrickdrm919 [1] 192.168.34.aaa/16 X1-SC2-target2 [7] Down          consistent                ok
xbrickdrm918-xbrickdrm919_4 4     xbrickdrm912 [1] xbrickdrm918 [2] 192.168.22.bbb/16 X1-SC1-target1 [1] vxms-xbrickdrm919 [0] xbrickdrm919 [1] 192.168.22.aaa/16 X1-SC1-target1 [1] Up            consistent                ok
  1. Durumu vxms-xbrickdrm912'den kontrol edin.
xmcli (admin)> show-remote-protection-sessions
Name Index Replication-State Replication-Mode Source-Cluster-ID Source-CG-Id Target-Cluster-ID Target-CG-Id Lag RPO Target-Policy-ID Cycle-Percent-Remaining(Ratio)
REP1 1     active            async            xbrickdrm918 [2]  CG1 [1]      xbrickdrm919 [1]  CG1 [1]      30  60  [0]              0
xmcli (admin)> show-remote-protection-ip-links
Name                        Index A-End-XMS-ID                             A-End-Cluster-ID A-End-IP-Addr     A-End-Port-ID      Z-End-XMS-ID                             Z-End-Cluster-ID Z-End-IP-Addr     Z-End-Port-ID      IP-Link-State IP-Link-Consistency-State Certainty
xbrickdrm918-xbrickdrm919_1 1     vxms-xbrickdrm912.xiodrm.lab.emc.com [0] xbrickdrm918 [2] 192.168.33.bbb/16 X1-SC2-target1 [6] vxms-xbrickdrm919.xiodrm.lab.emc.com [0] xbrickdrm919 [1] 192.168.33.aaa/16 X1-SC2-target1 [6] Up            consistent                ok
xbrickdrm918-xbrickdrm919_2 2     vxms-xbrickdrm912.xiodrm.lab.emc.com [0] xbrickdrm918 [2] 192.168.23.bbb/16 X1-SC1-target2 [2] vxms-xbrickdrm919.xiodrm.lab.emc.com [0] xbrickdrm919 [1] 192.168.23.aaa/16 X1-SC1-target2 [2] Down          consistent                ok
xbrickdrm918-xbrickdrm919_3 3     vxms-xbrickdrm912.xiodrm.lab.emc.com [0] xbrickdrm918 [2] 192.168.34.bbb/16 X1-SC2-target2 [7] vxms-xbrickdrm919.xiodrm.lab.emc.com [0] xbrickdrm919 [1] 192.168.34.aaa/16 X1-SC2-target2 [7] Down          consistent                ok
xbrickdrm918-xbrickdrm919_4 4     vxms-xbrickdrm912.xiodrm.lab.emc.com [0] xbrickdrm918 [2] 192.168.22.bbb/16 X1-SC1-target1 [1] vxms-xbrickdrm919.xiodrm.lab.emc.com [0] xbrickdrm919 [1] 192.168.22.aaa/16 X1-SC1-target1 [1] Up            consistent                ok
xmcli (admin)>

xmcli (admin)> show-remote-protection-session protection-session-id=1
Name: REP1
Index: 1
Replication-State: active
Replication-Mode: async
Replication-State-Details:
Replication-Direction: failover
Block-Access-Type: read_only
Source-XMS-Id:
                Name: vxms-xbrickdrm912.xiodrm.lab.emc.com
                Index: 0
Source-Cluster-ID:
                Name: xbrickdrm918
                Index: 2
Source-CG-Id:
                Name: CG1
                Index: 1
Target-XMS-Id:
                Name: vxms-xbrickdrm919.xiodrm.lab.emc.com
                Index: 0
Target-Cluster-ID:
                Name: xbrickdrm919
                Index: 1
Target-CG-Id:
                Name: CG1
                Index: 1
Num-Of-Vols: 2
RPO: 60
Max-BW(MB/s): 0
Protection-Window-Num-Copies: 0
Protection-Window-Duration-in-Days: 0.000
Current-Protection-Window-Copies: 2
Source-Retention-Policy-ID:
                Name:
                Index: 0
Target-Retention-Policy-ID:
                Name:
                Index: 0
Number-Of-Target-PITs: 2
Target-Pit-Num-Copies-Status: ok
Target-Pit-Window-Size-Status: ok
Number-Of-Source-PITs: 2
Next-Scheduled-Cycle: 2020-09-16 20:43:16
Lag: 19
BW(KB/s): 0
Transfer-Efficiency-Ratio(Ratio): 1
Cycle-Start-Time(Timestamp): Wed Sep 16 20:42:27 2020
Last-Cycle-Start-Time(Timestamp): Wed Sep 16 20:42:27 2020
Last-Cycle-Completed-Snapshot-Set: 6ad2dece48c24402b2551dd532a1eadf
Last-Cycle-Duration: 1
Last-Cycle-Link-BW(KB/s): 0
Last-Cycle-Effective-Bandwidth(KB/s): 0
Last-Cycle-Transfer-Efficiency-Ratio: 1
Cycle-Number(Count): 80
Num-Missing-Short-Period-Snapshot-Sets: 0
Num-Missing-Middle-Period-Snapshot-Sets: 0
Num-Missing-Long-Period-Snapshot-Sets: 0
Target-Missing-Pits-Alert: enabled
Test-Copy-Mode: False
Snapset-Backup-Snapset-Index: []
Current-Command-Name: start
Current-Command-Status: success
Replication-Session-Consistency-State: consistent
Obj-Severity: information
Verification-Schedule: adaptive
xmcli (admin)>
  1. Her iki kümenin de sağlık durumunu onaylamak için HCS komut dosyasını çalıştırın.

NOT: Her zaman olduğu gibi, onaylamak için her iki XMS sisteminde de HCS komut dosyasını çalıştırın.

Etkilenen Ürünler

XtremIO, XtremIO Family, XtremIO X2
Makale Özellikleri
Article Number: 000185755
Article Type: How To
Son Değiştirme: 09 May 2026
Version:  12
Sorularınıza diğer Dell kullanıcılarından yanıtlar bulun
Destek Hizmetleri
Aygıtınızın Destek Hizmetleri kapsamında olup olmadığını kontrol edin.