'"`例如，您的指令碼可能如下所示：`db2 "catalog storage access alias DB2AWSS3 vendor S3 server s3.us-east-1.amazonaws.com container 'hadrmig-db2'" ` | DBA |
| 設定預備區域。 | 建議使用 `DB2_ENABLE_COS_SDK=ON`、 `DB2_OBJECT_STORAGE_SETTINGS=EnableStreamingRestore`和程式`awssdk`庫的連結，略過資料庫備份和還原的 Amazon S3 預備區域：#By root:
cp -rp /home/db2inst1/sqllib/lib64/awssdk/RHEL/7.6/* /home/db2inst1/sqllib/lib64/
#By db2 instance owner:
db2set DB2_OBJECT_STORAGE_LOCAL_STAGING_PATH=/db2stage
db2set DB2_ENABLE_COS_SDK=ON
db2set DB2_OBJECT_STORAGE_LOCAL_STAGING_PATH=/db2stage
db2stop
db2start
| DBA |
| 從備份映像還原資料庫。 | 從 S3 儲存貯體中的備份映像還原 Amazon EC2 上的目標資料庫：db2 create db sample on /data1
db2 restore db sample from DB2REMOTE://DB2AWSS3/hadrmig-db2/SAMPLE_backup replace existing
| DBA |
### 在內部部署中設定沒有 HADR 的 HADR
| 任務 | Description | 所需的技能 |
| --- | --- | --- |
| 將內部部署 Db2 伺服器設定為主要伺服器。 | 將 HADR on `db2-server1`（內部部署來源） 的資料庫組態設定更新為主要伺服器。`HADR_SYNCMODE` 設定為 `SUPERASYNC` 模式，其交易回應時間最短：`db2 update db cfg for sample using HADR_LOCAL_HOST db2-server1 HADR_LOCAL_SVC 50010 HADR_REMOTE_HOST db2-ec2 HADR_REMOTE_SVC 50012 HADR_REMOTE_INST db2inst1 HADR_SYNCMODE SUPERASYNC DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully`現場部署資料中心和 AWS 之間預計會發生一些網路延遲。（您可以根據網路可靠性設定不同的`HADR_SYNCMODE`值。 如需詳細資訊，請參閱[相關資源](#migrate-db2-for-luw-to-amazon-ec2-with-high-availability-disaster-recovery-resources)一節）。 | DBA |
| 變更目標資料庫日誌封存目的地。 | 變更目標資料庫日誌封存目的地以符合 Amazon EC2 環境：db2 update db cfg for SAMPLE using LOGARCHMETH1 'DB2REMOTE://DB2AWSS3//SAMPLE_LOGS/' LOGARCHMETH2 OFF
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully
| DBA |
| 在 Amazon EC2 伺服器上設定 Db2 的 HADR。 Amazon EC2 | 將 上的 HADR 資料庫組態更新`db2-ec2`為待命：`db2 update db cfg for sample using HADR_LOCAL_HOST db2-ec2 HADR_LOCAL_SVC 50012 HADR_REMOTE_HOST db2-server1 HADR_REMOTE_SVC 50010 HADR_REMOTE_INST db2inst1 HADR_SYNCMODE SUPERASYNC DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully` | DBA |
| 驗證 HADR 設定。 | 驗證來源和目標 Db2 伺服器上的 HADR 參數。若要驗證 上的設定`db2-server1`，請執行下列命令：db2 get db cfg for sample|grep HADR
HADR database role = PRIMARY
HADR local host name (HADR_LOCAL_HOST) = db2-server1
HADR local service name (HADR_LOCAL_SVC) = 50010
HADR remote host name (HADR_REMOTE_HOST) = db2-ec2
HADR remote service name (HADR_REMOTE_SVC) = 50012
HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1
HADR timeout value (HADR_TIMEOUT) = 120
HADR target list (HADR_TARGET_LIST) =
HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC
HADR spool log data limit (4KB) (HADR_SPOOL_LIMIT) = AUTOMATIC(52000)
HADR log replay delay (seconds) (HADR_REPLAY_DELAY) = 0
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
HADR SSL certificate label (HADR_SSL_LABEL) =
HADR SSL Hostname Validation (HADR_SSL_HOST_VAL) = OFF
若要驗證 上的設定`db2-ec2`，請執行下列命令：db2 get db cfg for sample|grep HADR
HADR database role = STANDBY
HADR local host name (HADR_LOCAL_HOST) = db2-ec2
HADR local service name (HADR_LOCAL_SVC) = 50012
HADR remote host name (HADR_REMOTE_HOST) = db2-server1
HADR remote service name (HADR_REMOTE_SVC) = 50010
HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1
HADR timeout value (HADR_TIMEOUT) = 120
HADR target list (HADR_TARGET_LIST) =
HADR log write synchronization mode (HADR_SYNCMODE) = SUPERASYNC
HADR spool log data limit (4KB) (HADR_SPOOL_LIMIT) = AUTOMATIC(52000)
HADR log replay delay (seconds) (HADR_REPLAY_DELAY) = 0
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
HADR SSL certificate label (HADR_SSL_LABEL) =
HADR SSL Hostname Validation (HADR_SSL_HOST_VAL) = OFF
`HADR_LOCAL_HOST`、`HADR_REMOTE_HOST`、 `HADR_LOCAL_SVC`和 `HADR_REMOTE_SVC` 參數指出一個主要和一個待命 HADR 設定。 | DBA |
| 啟動 Db2 HADR 執行個體。 | 首先在待命伺服器上啟動 Db2 HADR 執行個體`db2-ec2`：db2 start hadr on db sample as standby
DB20000I The START HADR ON DATABASE command completed successfully.
在主要 （來源） 伺服器 上啟動 Db2 HADR`db2-server1`：db2 start hadr on db sample as primary
DB20000I The START HADR ON DATABASE command completed successfully.
Db2 on 內部部署和 Amazon EC2 之間的 HADR 連線現已成功建立。Db2 主要伺服器`db2-ec2`會即時`db2-server1`開始將交易日誌記錄串流至 。 | DBA |
### 當內部部署存在 HADR 時設定 HADR
| 任務 | Description | 所需的技能 |
| --- | --- | --- |
| 在 Amazon EC2 上新增 Db2 作為輔助待命。 Amazon EC2 | 如果 HADR 在內部部署 Db2 執行個體上執行，您可以在 上執行下列命令`HADR_TARGET_LIST`，使用 新增 Amazon EC2 上的 Db2 做為輔助待命`db2-ec2`： Amazon EC2 `db2 update db cfg for sample using HADR_LOCAL_HOST db2-ec2 HADR_LOCAL_SVC 50012 HADR_REMOTE_HOST db2-server1 HADR_REMOTE_SVC 50010 HADR_REMOTE_INST db2inst1 HADR_SYNCMODE SUPERASYNC DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. db2 update db cfg for sample using HADR_TARGET_LIST "db2-server1:50010\|db2-server2:50011" DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.` | DBA |
| 將輔助待命資訊新增至內部部署伺服器。 | `HADR_TARGET_LIST` 在兩個內部部署伺服器上更新 （主要和待命）。在 `db2-server1`上執行下列程式碼：`db2 update db cfg for sample using HADR_TARGET_LIST "db2-server2:50011\|db2-ec2:50012" DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, the database must be shutdown and reactivated before the configuration parameter changes become effective.`在 `db2-server2`上執行下列程式碼：`db2 update db cfg for sample using HADR_TARGET_LIST "db2-server1:50010\|db2-ec2:50012" DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, the database must be shutdown and reactivated before the configuration parameter changes become effective.` | DBA |
| 驗證 HADR 設定。 | 驗證來源和目標 Db2 伺服器上的 HADR 參數。在 `db2-server1`上執行下列程式碼：db2 get db cfg for sample|grep HADR
HADR database role = PRIMARY
HADR local host name (HADR_LOCAL_HOST) = db2-server1
HADR local service name (HADR_LOCAL_SVC) = 50010
HADR remote host name (HADR_REMOTE_HOST) = db2-server2
HADR remote service name (HADR_REMOTE_SVC) = 50011
HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1
HADR timeout value (HADR_TIMEOUT) = 120
HADR target list (HADR_TARGET_LIST) = db2-server2:50011|db2-ec2:50012
HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC
HADR spool log data limit (4KB) (HADR_SPOOL_LIMIT) = AUTOMATIC(52000)
HADR log replay delay (seconds) (HADR_REPLAY_DELAY) = 0
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
HADR SSL certificate label (HADR_SSL_LABEL) =
HADR SSL Hostname Validation (HADR_SSL_HOST_VAL) = OFF
在 `db2-server2`上執行下列程式碼：db2 get db cfg for sample|grep HADR
HADR database role = STANDBY
HADR local host name (HADR_LOCAL_HOST) = db2-server2
HADR local service name (HADR_LOCAL_SVC) = 50011
HADR remote host name (HADR_REMOTE_HOST) = db2-server1
HADR remote service name (HADR_REMOTE_SVC) = 50010
HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1
HADR timeout value (HADR_TIMEOUT) = 120
HADR target list (HADR_TARGET_LIST) = db2-server1:50010|db2-ec2:50012
HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC
HADR spool log data limit (4KB) (HADR_SPOOL_LIMIT) = AUTOMATIC(52000)
HADR log replay delay (seconds) (HADR_REPLAY_DELAY) = 0
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
HADR SSL certificate label (HADR_SSL_LABEL) =
HADR SSL Hostname Validation (HADR_SSL_HOST_VAL) = OFF
在 `db2-ec2`上執行下列程式碼：db2 get db cfg for sample|grep HADR
HADR database role = STANDBY
HADR local host name (HADR_LOCAL_HOST) = db2-ec2
HADR local service name (HADR_LOCAL_SVC) = 50012
HADR remote host name (HADR_REMOTE_HOST) = db2-server1
HADR remote service name (HADR_REMOTE_SVC) = 50010
HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1
HADR timeout value (HADR_TIMEOUT) = 120
HADR target list (HADR_TARGET_LIST) = db2-server1:50010|db2-server2:50011
HADR log write synchronization mode (HADR_SYNCMODE) = SUPERASYNC
HADR spool log data limit (4KB) (HADR_SPOOL_LIMIT) = AUTOMATIC(52000)
HADR log replay delay (seconds) (HADR_REPLAY_DELAY) = 0
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
HADR SSL certificate label (HADR_SSL_LABEL) =
HADR SSL Hostname Validation (HADR_SSL_HOST_VAL) = OFF
`HADR_LOCAL_HOST`、`HADR_LOCAL_SVC`、`HADR_REMOTE_HOST`、 `HADR_REMOTE_SVC`和 `HADR_TARGET_LIST` 參數指出一個主要和兩個待命 HADR 設定。 | |
| 停止和啟動 Db2 HADR。 | `HADR_TARGET_LIST` 現在已在所有三個伺服器上設定 。每個 Db2 伺服器都知道另外兩個伺服器。停止並重新啟動 HADR （短暫中斷），以利用新的組態。在 `db2-server1`上執行下列命令：db2 stop hadr on db sample
db2 deactivate db sample
db2 activate db sample
在 `db2-server2`上執行下列命令：db2 deactivate db sample
db2 start hadr on db sample as standby
SQL1766W The command completed successfully
在 `db2-ec2`上執行下列命令：db2 start hadr on db sample as standby
SQL1766W The command completed successfully
在 `db2-server1`上執行下列命令：db2 start hadr on db sample as primary
SQL1766W The command completed successfully
Db2 on 內部部署和 Amazon EC2 之間的 HADR 連線現已成功建立。Db2 主要伺服器`db2-server1`會開始即時串流交易日誌記錄到 `db2-server2`和 `db2-ec2` 。 | DBA |
### 在切換時段將 Amazon EC2 上的 Db2 設為主要 Amazon EC2
| 任務 | Description | 所需的技能 |
| --- | --- | --- |
| 確定待命伺服器上沒有 HADR 延遲。 | 從主要伺服器 檢查 HADR 狀態`db2-server1`。當 `HADR_STATE` 處於 `REMOTE_CATCHUP` 狀態時，請勿發出警示，當 `HADR_SYNCMODE`設為 時，這是正常的`SUPERASYNC`。`PRIMARY_LOG_TIME` 和 `STANDBY_REPLAY_LOG_TIME`顯示它們處於同步狀態：db2pd -hadr -db sample
HADR_ROLE = PRIMARY
REPLAY_TYPE = PHYSICAL
HADR_SYNCMODE = SUPERASYNC
STANDBY_ID = 2
LOG_STREAM_ID = 0
HADR_STATE = REMOTE_CATCHUP
.....
PRIMARY_LOG_TIME = 10/26/2022 02:11:32.000000 (1666750292)
STANDBY_LOG_TIME = 10/26/2022 02:11:32.000000 (1666750292)
STANDBY_REPLAY_LOG_TIME = 10/26/2022 02:11:32.000000 (1666750292)
| DBA |
| 執行 HADR 接管。 | 若要完成遷移，請執行 HADR 接管命令來建立`db2-ec2`主要資料庫。使用 命令`db2pd`來驗證`HADR_ROLE`值：db2 TAKEOVER HADR ON DATABASE sample
DB20000I The TAKEOVER HADR ON DATABASE command completed successfully.
db2pd -hadr -db sample
Database Member 0 -- Database SAMPLE -- Active -- Up 0 days 00:03:25 -- Date 2022-10-26-02.46.45.048988
HADR_ROLE = PRIMARY
REPLAY_TYPE = PHYSICAL
若要完成遷移至 AWS，請將應用程式連線指向 Amazon EC2 上的 Db2。 Amazon EC2 | |
## 疑難排解
| 問題 | 解決方案 |
| --- | --- |
| 如果您因防火牆和安全原因而使用 NAT，主機可以有兩個 IP 地址 （一個內部和一個外部），這可能會導致 HADR IP 地址檢查失敗。`START HADR ON DATABASE` 命令將傳回下列訊息：`HADR_LOCAL_HOST:HADR_LOCAL_SVC (-xx-xx-xx-xx.:50011 (xx.xx.xx.xx:50011)) on remote database is different from HADR_REMOTE_HOST:HADR_REMOTE_SVC (xx-xx-xx-xx.:50011 (x.x.x.x:50011)) on local database.` | 若要[在 NAT 環境中支援 HADR，](https://www.ibm.com/docs/en/db2/11.5?topic=support-hadr-nat)您可以使用內部和外部地址`HADR_LOCAL_HOST`來設定 。例如，如果 Db2 伺服器具有內部名稱 `host1`和外部名稱 `host1E`，則 `HADR_LOCAL_HOST` 可以是 `HADR_LOCAL_HOST: "host1 \| host1E"`。 |
## 相關資源
+ [不同作業系統和硬體平台之間的 Db2 備份和還原操作](https://www.ibm.com/docs/en/db2/11.5?topic=dbrs-backup-restore-operations-between-different-operating-systems-hardware-platforms)
+ [設定 Db2 STORAGE ACCESS ALIAS 和 DB2REMOTE](https://www.ibm.com/docs/en/db2/11.5?topic=commands-catalog-storage-access)
+ [Db2 高可用性災難復原](https://www.ibm.com/docs/en/db2/11.5?topic=server-high-availability-disaster-recovery-hadr)
+ [hadr\$1syncmode - 用於對等狀態組態參數中日誌寫入的 HADR 同步模式](https://www.ibm.com/docs/en/db2/11.5?topic=dcp-hadr-syncmode-hadr-synchronization-mode-log-writes-in-peer-state)