Apply automatic changes

Author: AnthonyTsu1984

docs/tutorials/backup-and-restore/backup-and-restore.md

@@ -3,21 +3,24 @@ title: "Backup & Restore | Cloud"
 slug: /backup-and-restore
 sidebar_label: "Backup & Restore"
 beta: FALSE
+added_since: FALSE
+last_modified: FALSE
+deprecate_since: FALSE
 notebook: FALSE
 description: "Data backup and restore for your data stored in Zilliz Cloud clusters. | Cloud"
 type: origin
 token: VvikwOKc9iZ5vBkgMnycrXKmnId
-sidebar_position: 7
+sidebar_position: 8
 keywords: 
   - zilliz
   - vector database
   - cloud
   - backup
   - restore
-  - vectordb
-  - multimodal vector database retrieval
-  - Retrieval Augmented Generation
-  - Large language model
+  - llm eval
+  - Sparse vs Dense
+  - Dense vector
+  - Hierarchical Navigable Small Worlds
 
 ---
 

docs/tutorials/backup-and-restore/backup-to-other-regions.md

@@ -0,0 +1,116 @@
+---
+title: "Cross-Region Backup | Cloud"
+slug: /backup-to-other-regions
+sidebar_label: "Cross-Region Backup"
+beta: FALSE
+added_since: FALSE
+last_modified: FALSE
+deprecate_since: FALSE
+notebook: FALSE
+description: "Cross-region backup in Zilliz Cloud enhances data protection by copying backups to multiple cloud regions. It safeguards against regional outages and supports disaster recovery, business continuity, and high availability by minimizing risks from localized failures. | Cloud"
+type: origin
+token: ESVGwTkn8iLfUakSSrkc5dWJnye
+sidebar_position: 3
+keywords: 
+  - zilliz
+  - vector database
+  - cloud
+  - backup
+  - files
+  - view
+  - Similarity Search
+  - multimodal RAG
+  - llm hallucinations
+  - hybrid search
+
+---
+
+import Admonition from '@theme/Admonition';
+
+
+import Supademo from '@site/src/components/Supademo';
+
+# Cross-Region Backup
+
+Cross-region backup in Zilliz Cloud enhances data protection by copying backups to multiple cloud regions. It safeguards against regional outages and supports disaster recovery, business continuity, and high availability by minimizing risks from localized failures.
+
+This guide walks you through how to use cross-region backup on Zilliz Cloud. 
+
+Currently, clusters on Azure do not support cross-region backup.
+
+<Admonition type="info" icon="📘" title="Notes">
+
+<p>This feature is available only to <strong>Dedicated</strong> clusters.</p>
+
+</Admonition>
+
+## Limits\{#limits}
+
+- **Access control**: You must be a **project admin**, **organization owner**, or have a **custom role** with backup privileges.
+
+- **Excluded from backup**:
+
+    - Collection TTL settings
+
+    - Password for the default user `db_admin` (a new password is generated during [restore](./restore-from-snapshot))
+
+    - Cluster dynamic and scheduled scaling settings
+
+- **Cluster shard settings**: Backed up but may be adjusted during restore if the cluster CU size is reduced, due to shard-per-CU limits. See [Zilliz Cloud Limits](./limits#shards) for details.
+
+- **Backup job restrictions**: Cross-region backup copy job will start after original backup job is completed.
+
+## Procedures\{#procedures}
+
+You can enable cross-region backup either when [creating a backup manually](./create-snapshot) or when [scheduling automatic backups](./schedule-automatic-backups).
+
+- **Manual backup:** If you choose cross-region backup during manual creation, all copied backups are permanently retained.
+
+- **Scheduled backup:** If you choose cross-region backup during scheduled backups, you must configure a retention period for the copied backup file in each region.
+
+<Admonition type="info" icon="📘" title="Notes">
+
+<p>You can select regions only for the same cloud provider as the original region.</p>
+
+</Admonition>
+
+The following demo shows how to use cross-region backup when manually creating a backup. For details about how to use cross-region backup while scheduling automatic backups, refer to [Schedule Automatic Backups](./schedule-automatic-backups).
+
+<Supademo id="cmgkg6um62deokrn973s89qfx?utm_source=link" title=""  />
+
+In the [Jobs](./job-center) list, you will first see the original backup job. Once it completes, additional jobs appear for copying the backup file to each selected region, with one record per region.
+
+## Billing implications\{#billing-implications}
+
+When you choose cross-region backup, two types of charges may apply:
+
+- **Storage cost:** Based on the region where the copied backup file is stored. To understand how storage cost is calculated, see [Storage Cost](./storage-cost).
+
+- **Data transfer cost:** Based on the traffic between the source region and the target regions. To understand how storage cost is calculated, see [Data Transfer Cost](./data-transfer-cost).
+
+For detailed rates, see [Pricing Guide](https://zilliz.com/pricing/pricing-guide).
+
+### Example\{#example}
+
+Suppose your cluster is deployed in **GCP us-west1 (Oregon)** and you need to copy the backup file of this cluster to two different regions, **GCP us-east4 (Virginia, USA)** and **GCP europe-west3 (Frankfurt)**:
+
+- **Original Backup File Size**: 20 GB
+
+- **Retention Period of Copied Backups**: 1 Month
+
+- **Unit Price**: 
+
+    - The unit price of backup storage on GCP is **&#36;0.02/GB per month**.
+
+    - Data transfer from GCP us-west1 (Oregon) to GCP us-central1 (Iowa) is billed at the same-continent cross-region rate of **&#36;0.02/GB**.
+
+    - Data transfer from GCP us-west1 (Oregon) to GCP europe-west3 (Frankfurt) is billed at the different-continent cross-region rate of **&#36;0.08/GB**.
+
+The following is the cost calculation:
+
+- **Storage cost:** `20 GB × $0.02/GB per month × 1 month × 2 copies = $0.80`
+
+- **Data transfer cost:** `(20 GB × $0.02/GB) + (20 GB × $0.08/GB) = $2.00`
+
+- **Total cost:** `$0.80 (storage) + $2.00 (data transfer) = $2.80`
+

docs/tutorials/backup-and-restore/create-snapshot.md

@@ -3,6 +3,9 @@ title: "Create Backup | Cloud"
 slug: /create-snapshot
 sidebar_label: "Create Backup"
 beta: FALSE
+added_since: FALSE
+last_modified: FALSE
+deprecate_since: FALSE
 notebook: FALSE
 description: "In Zilliz Cloud, a backup is a copy of the data that allows you to restore the entire cluster or specific collections in the event of data loss or system failure. | Cloud"
 type: origin
@@ -13,10 +16,10 @@ keywords:
   - vector database
   - cloud
   - backup
-  - Managed vector database
-  - Pinecone vector database
-  - Audio search
-  - what is semantic search
+  - vector search algorithms
+  - Question answering system
+  - llm-as-a-judge
+  - hybrid vector search
 
 ---
 
@@ -27,19 +30,19 @@ import Supademo from '@site/src/components/Supademo';
 
 # Create Backup
 
-In Zilliz Cloud, a backup is a copy of the data that allows you to restore the entire cluster or specific collections in the event of data loss or system failure. 
+In Zilliz Cloud, a backup is a copy of the data that allows you to restore the entire cluster or specific collections in the event of data loss or system failure.
 
-Backup creation incurs additional [charges](/docs/understand-cost#backup-cost), with pricing based on the cloud region where the backup is stored. All backup files are stored in the same cloud region as the source cluster. For example, a cluster in `AWS us-west-2` will have its backups stored in `AWS us-west-2`.
+Backup creation incurs additional [charges](./storage-cost), with pricing based on the cloud region where the backup is stored. All backup files are stored in the same cloud region as the source cluster. For example, a cluster in `AWS us-west-2` will have its backups stored in `AWS us-west-2`.
 
 This guide explains how to **manually create backups**. To automate backup creation, see [Schedule Automatic Backups](./schedule-automatic-backups).
 
 <Admonition type="info" icon="📘" title="Notes">
 
-<p>The backup and restore feature is exclusively available to <strong>Dedicated</strong> clusters. </p>
+<p>This feature is available only to <strong>Dedicated</strong> clusters.</p>
 
 </Admonition>
 
-## Limits{#limits}
+## Limits\{#limits}
 
 - **Access control**: You must be a **project admin**, **organization owner**, or have a **custom role** with backup privileges.
 
@@ -49,6 +52,8 @@ This guide explains how to **manually create backups**. To automate backup creat
 
     - Password for the default user `db_admin` (a new password is generated during [restore](./restore-from-snapshot))
 
+    - Cluster dynamic and scheduled scaling settings
+
 - **Cluster shard settings**: Backed up but may be adjusted during restore if the cluster CU size is reduced, due to shard-per-CU limits. See [Zilliz Cloud Limits](./limits#shards) for details.
 
 - **Backup job restrictions**:
@@ -61,17 +66,17 @@ This guide explains how to **manually create backups**. To automate backup creat
 
         - Automatic backups will still run if a manual backup is already in progress.
 
-## Create cluster backup{#create-cluster-backup}
+## Create cluster backup\{#create-cluster-backup}
 
-You can create a backup of an entire cluster and later restore either the whole cluster or selected collections.
+You can create a backup of an entire cluster and later restore either the whole cluster or selected collections. If you need to copy your backup file to other cloud regions for disaster recover, you can configure the copy policies while creating a backup. For details, refer to [Copy To Other Regions](./backup-to-other-regions).
 
-### Via web console{#via-web-console}
+### Via web console\{#via-web-console}
 
 The following demo shows how to create a cluster backup on the Zilliz Cloud web console.
 
 <Supademo id="cmcske0x90dpa9st802gnvbz9" title=""  />
 
-### Via RESTful API{#via-restful-api}
+### Via RESTful API\{#via-restful-api}
 
 The following example creates a backup for the cluster `in01-xxxxxxxxxxxxxx`. For details about the RESTful API, see [Create Backup](/reference/restful/create-backup-v2).
 
@@ -98,17 +103,17 @@ The following is an example output. A backup job is generated and you can check
 }
 ```
 
-## Create collection backup{#create-collection-backup}
+## Create collection backup\{#create-collection-backup}
 
-To back up a specific collection or a subset of collections in a cluster, create a collection-level backup.
+To back up a specific collection or a subset of collections in a cluster, create a collection-level backup. If you need to copy your backup file to other cloud regions for disaster recover, you can configure the copy policies while creating a backup. For details, refer to [Copy To Other Regions](./backup-to-other-regions).
 
-### Via web console{#via-web-console}
+### Via web console\{#via-web-console}
 
 The following demo shows how to create a collection backup on the web console.
 
 <Supademo id="cmcskksub0dra9st8cy34b2vi" title=""  />
 
-### Via RESTful API{#via-restful-api}
+### Via RESTful API\{#via-restful-api}
 
 The following example creates a backup for the collection `medium_articles` in the cluster `in01-xxxxxxxxxxxxxx`. For details about the RESTful API, see [Create Backup](/reference/restful/create-backup-v2).
 
@@ -142,12 +147,14 @@ The following is an example output. A backup job is generated and you can check
 }
 ```
 
-## FAQs{#faqs}
+## FAQs\{#faqs}
 
 **How long does a backup job take?**
+
 Backup duration depends on the size of your data. As a reference, backing up 700 MB typically takes about 1 second. If your cluster contains more than 1,000 collections, the process may take slightly longer.
 
 **Can I perform DDL (Data Definition Language) operations during a backup?**
+
 It is recommended to avoid major DDL (Data Definition Language) operations—such as creating or dropping collections—while a backup is in progress, as they may interfere with the process or lead to inconsistent results.
 
 **Will backup files be deleted if the original cluster is dropped?**

docs/tutorials/backup-and-restore/export-backup-files.md

@@ -3,11 +3,14 @@ title: "Export Backup Files | Cloud"
 slug: /export-backup-files
 sidebar_label: "Export Backup Files"
 beta: PRIVATE
+added_since: FALSE
+last_modified: FALSE
+deprecate_since: FALSE
 notebook: FALSE
 description: "You can export backup files to object storage using the Zilliz Cloud console. | Cloud"
 type: origin
 token: QUTDwkbTTiA2UlkWYDlc796ensf
-sidebar_position: 4
+sidebar_position: 5
 keywords: 
   - zilliz
   - vector database
@@ -17,10 +20,10 @@ keywords:
   - integrate
   - object
   - storage
-  - hallucinations llm
-  - Multimodal search
-  - vector search algorithms
-  - Question answering system
+  - milvus open source
+  - how does milvus work
+  - Zilliz vector database
+  - Zilliz database
 
 ---
 
@@ -33,21 +36,21 @@ You can export backup files to object storage using the Zilliz Cloud console.
 
 <Admonition type="info" icon="📘" title="Notes">
 
-<p>This feature is in <strong>Private Preview</strong> for clusters on the <strong>Dedicated-Enterprise</strong> plan. To enable this feature or learn about the associated costs, contact <a href="https://support.zilliz.com/hc/en-us">Zilliz Cloud support</a>.</p>
+<p>This feature is in <strong>Private Preview</strong> for <strong>Dedicated</strong> clusters in <strong>Enterprise</strong> projects. To enable this feature or learn about the associated costs, contact <a href="https://support.zilliz.com/hc/en-us">Zilliz Cloud support</a>.</p>
 
 </Admonition>
 
-## Before you start{#before-you-start}
+## Before you start\{#before-you-start}
 
-- You have integrated Zilliz Cloud with your object storage. For detailed steps, refer to [Integrate with AWS S3](./integrate-with-aws-s3) and [Integrate with Azure Blob Storage](./integrate-with-azure-blob-storage).
+- You have integrated Zilliz Cloud with your object storage. For detailed steps, refer to [Integrate with AWS S3](./integrate-with-aws-s3), [Integrate with Azure Blob Storage](./integrate-with-azure-blob-storage), or [Integrate with Google Cloud Storage](./integrate-with-gcp).
 
 - You have **Organization Owner** or **Project Admin** access to the project. If you do not have necessary permissions, contact your Zilliz Cloud administrator.
 
-## Procedure{#procedure}
+## Procedure\{#procedure}
 
 You can export backup files from Zilliz Cloud either via the Zilliz Cloud console or through the RESTful API. 
 
-### Export via Zilliz Cloud console{#export-via-zilliz-cloud-console}
+### Export via Zilliz Cloud console\{#export-via-zilliz-cloud-console}
 
 1. Log in to the [Zilliz Cloud console](https://cloud.zilliz.com/login).
 
@@ -65,17 +68,17 @@ You can export backup files from Zilliz Cloud either via the Zilliz Cloud consol
 
     - **Cloud Region of Cluster in Backup File**: Displays the cloud region where the backup file was created.
 
-    - **Integration**: Select the object storage provider integrated with Zilliz Cloud. Currently, AWS S3 is supported. For more information, refer to [Integrate with AWS S3](./integrate-with-aws-s3).
+    - **Integration**: Select the object storage provider integrated with Zilliz Cloud.
 
     - **Integration Configuration**: Choose the specific bucket you configured for the backup export.
 
     - **Directory**: Enter the directory path in your object storage bucket where the exported backup file will be stored.
 
 1. Then, click **Export**.
 
-![export-backup-file](/img/export-backup-file.png)
+![export-backup-file](/img/export-backup-file.png "export-backup-file")
 
-### Export through RESTful API{#export-through-restful-api}
+### Export through RESTful API\{#export-through-restful-api}
 
 Before you can export backup files from Zilliz Cloud via the [Export Backup Files](/reference/restful/export-backup-files-v2) RESTful API endpoint, you have to integrate one of your AWS S3 buckets with Zilliz Cloud and obtain its integration ID. For details, refer to [Obtain the integration ID](./integrate-with-aws-s3#obtain-the-integration-id).
 
@@ -106,7 +109,7 @@ The response to the above request would be a Job ID as follows:
 }
 ```
 
-## Monitor export progress{#monitor-export-progress}
+## Monitor export progress\{#monitor-export-progress}
 
 Once you click **Export**, an export job is generated automatically:
 
@@ -120,9 +123,9 @@ Once you click **Export**, an export job is generated automatically:
 
     - **ERROR**: The job failed. This can occur if a resource used by the export process, such as the Role ARN or the backup file, is deleted during the job execution.
 
-![monitor-export-job](/img/monitor-export-job.png)
+![monitor-export-job](/img/monitor-export-job.png "monitor-export-job")
 
-## Cancel export job{#cancel-export-job}
+## Cancel export job\{#cancel-export-job}
 
 If your job remains in the **IN PROGRESS** status and you decide not to proceed, you can cancel the job by clicking **Cancel** in the **Actions** column.