DM: add -archive to the URL of archived DM docs (pingcap#22890) (pingcap#22891)

Author: ti-chi-bot

dm/dm-release-notes.md

@@ -12,26 +12,26 @@ Since DM v5.4, the Release Notes of TiDB Data Migration have been merged into Ti
 
 ## 5.3
 
-- [5.3.0](https://docs.pingcap.com/tidb-data-migration/v5.3/5.3.0/)
+- [5.3.0](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/5.3.0/)
 
 ## 2.0
 
-- [2.0.7](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.7/)
-- [2.0.6](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.6/)
-- [2.0.5](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.5/)
-- [2.0.4](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.4/)
-- [2.0.3](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.3/)
-- [2.0.2](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.2/)
-- [2.0.1](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.1/)
-- [2.0 GA](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.0-ga/)
-- [2.0.0-rc.2](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.0-rc.2/)
-- [2.0.0-rc](https://docs.pingcap.com/tidb-data-migration/v5.3/2.0.0-rc/)
+- [2.0.7](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.7/)
+- [2.0.6](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.6/)
+- [2.0.5](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.5/)
+- [2.0.4](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.4/)
+- [2.0.3](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.3/)
+- [2.0.2](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.2/)
+- [2.0.1](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.1/)
+- [2.0 GA](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.0-ga/)
+- [2.0.0-rc.2](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.0-rc.2/)
+- [2.0.0-rc](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/2.0.0-rc/)
 
 ## 1.0
 
-- [1.0.7](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.7/)
-- [1.0.6](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.6/)
-- [1.0.5](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.5/)
-- [1.0.4](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.4/)
-- [1.0.3](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.3/)
-- [1.0.2](https://docs.pingcap.com/tidb-data-migration/v5.3/1.0.2/)
+- [1.0.7](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.7/)
+- [1.0.6](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.6/)
+- [1.0.5](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.5/)
+- [1.0.4](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.4/)
+- [1.0.3](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.3/)
+- [1.0.2](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/1.0.2/)

dm/manually-upgrade-dm-1.0-to-2.0.md

@@ -110,7 +110,7 @@ For [data migration task configuration guide](/dm/dm-task-configuration-guide.md
 
 ## Step 3: Stop the v1.0.x cluster
 
-If the original v1.0.x cluster is deployed by DM-Ansible, you need to use [DM-Ansible to stop the v1.0.x cluster](https://docs.pingcap.com/tidb-data-migration/v1.0/cluster-operations#stop-a-cluster).
+If the original v1.0.x cluster is deployed by DM-Ansible, you need to use [DM-Ansible to stop the v1.0.x cluster](https://docs-archive.pingcap.com/tidb-data-migration/v1.0/cluster-operations#stop-a-cluster).
 
 If the original v1.0.x cluster is deployed by binary, you can stop the DM-worker and DM-master processes directly.