[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eUpgrading a replication job in Cloud Data Fusion requires different steps depending on whether you're upgrading to version 6.7.0 or later, or version 6.6.0 or earlier.\u003c/p\u003e\n"],["\u003cp\u003eFor replication jobs upgrading to version 6.7.0 or later, use the same process as upgrading batch pipelines, which is detailed in the documentation.\u003c/p\u003e\n"],["\u003cp\u003eFor upgrading replication jobs to version 6.6.0 or earlier, you must stop the job, retrieve a generation ID, back up the existing Cloud Storage directory, perform the upgrade using the batch pipelines steps, and then start the job with the new generation ID.\u003c/p\u003e\n"],["\u003cp\u003eThe generation ID, crucial for jobs on version 6.6.0 and earlier, can be found by making a \u003ccode\u003eGET()\u003c/code\u003e request via the Cloud Data Fusion web interface or REST API, and it also serves as the bucket name for the Cloud Storage directory.\u003c/p\u003e\n"]]],[],null,["# Upgrade a Replication job\n\nThis page describes how to upgrade a replication job after\n[upgrading a Cloud Data Fusion instance](/data-fusion/docs/how-to/upgrading#upgrade-instances).\nThe process differs when you upgrade to version 6.6.0 and earlier. \n\n### Version 6.7.0 and later\n\nTo upgrade a replication job to version 6.7.0 or later, perform the\nreplication job upgrade using the same steps as you would to\n[upgrade batch pipelines](/data-fusion/docs/how-to/upgrading#upgrade-batch-pipelines).\n\n### Version 6.6.0 and earlier\n\nTo back up and upgrade the replication job to version 6.6.0 or\nearlier, follow these steps:\n\n1. [Stop the replication job](/data-fusion/docs/reference/replication-ref#stop-a-replication-job).\n\n2. Get the generation ID by making an HTTP `GET()` request in the\n Cloud Data Fusion web interface or REST API. The path is similar to\n the following:\n\n namespaces/\u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e/apps/\u003cvar translate=\"no\"\u003eREPLICATION_JOB_ID<\u003c/var\u003e/workers/DeltaWorker\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e: the string name of the\n namespace for the replication job. If your pipeline belongs\n to a Basic edition instance, the ID is always `default`.\n\n - \u003cvar translate=\"no\"\u003eREPLICATION_JOB_ID\u003c/var\u003e: the string name of the\n replication job.\n\n ### Interface\n\n\n To make the HTTP `GET()` request in the Cloud Data Fusion\n interface, follow these steps:\n 1. Go to your instance:\n 1. In the Google Cloud console, go to the Cloud Data Fusion page.\n\n 2. To open the instance in the Cloud Data Fusion Studio,\n click **Instances** , and then click **View instance**.\n\n [Go to Instances](https://console.cloud.google.com/data-fusion/locations/-/instances)\n 2. Click **System Admin** \\\u003e **Configuration**.\n 3. Click **Make HTTP calls**.\n 4. Select **GET** and enter the path described previously in step 2.\n 5. Click **Send** and find generation ID in the call response.\n\n ### REST API\n\n\n To make the `GET()` request in the API, see the [CDAP API reference](/data-fusion/docs/reference/cdap-reference).\n3. Back up the existing Cloud Storage directory.\n\n 1. To edit the directory in the Google Cloud console, go to the\n **Buckets** page.\n\n [Go to Buckets](https://console.cloud.google.com/storage/browser)\n 2. Click the bucket name to open the **Bucket details** page. The bucket\n name is the generation ID number.\n\n The Cloud Storage bucket path in the Google Cloud console has a format\n similar to the following:\n\n **Buckets** \\\u003e \u003cvar translate=\"no\"\u003eOFFSET_BASE_PATH\u003c/var\u003e\n \\\u003e \u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e \\\u003e \u003cvar translate=\"no\"\u003eREPLICATION_JOB_ID\u003cvar translate=\"no\"\u003e\u003c/var\u003e\u003c/var\u003e\n\n You can find the bucket by the `offsetBasePath` value for the job. To get\n the value, make a `GET()` request in Cloud Data Fusion with the\n following path: \n\n namespaces/\u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e/apps/\u003cvar translate=\"no\"\u003eREPLICATION_JOB_ID\u003c/var\u003e\n\n4. Perform the upgrade using the same steps as you would to\n [upgrade batch pipelines](/data-fusion/docs/how-to/upgrading#upgrade-batch-pipelines).\n\n5. The upgraded job has a new generation ID. Use the new ID as the\n Cloud Storage directory name.\n\n6. [Start the replication job](/data-fusion/docs/reference/replication-ref#start-a-replication-job).\n\nWhat's next\n-----------\n\n- Learn more about [Replication](/data-fusion/docs/concepts/replication).\n- Refer to the [Replication API](/data-fusion/docs/reference/replication-ref)."]]
