diff --git a/en/operations/data-management.html b/en/operations/data-management.html index a926eb0904..ababd779d2 100644 --- a/en/operations/data-management.html +++ b/en/operations/data-management.html @@ -7,18 +7,34 @@ ---

- This guide documents how to export data from a Vespa cloud application and how to do mass updates or removals. - See cloning applications and data - for how to copy documents from one application to another. + This guide covers data management operations for Vespa Cloud applications, + including automated backups, document export, feed, and bulk updates and removals.

+ +

Automated Backups

- Prerequisite: Use the latest version of the vespa - command-line client. + Depending on plan, content clusters are automatically backed up when a + <backup> element is specified in deployment.xml. + Vespa Cloud manages the backup schedule, storage, and lifecycle with no external tooling required. Backups will run at the configured frequency + while also respecting any block windows defined for the instance. +

+
{% highlight xml %}
+
+    
+    
+        aws-us-east-1c
+    
+
+{% endhighlight %}
+

+ If you prefer to manage backups yourself, documents can be exported manually using + vespa visit as shown in the + Google Cloud Function example.

-

Export documents

+{% include note.html content='The examples below use the Vespa CLI. Ensure you have the latest version installed.' %}

To export documents, configure the application to export from, then select zone, container cluster and schema - example: @@ -45,21 +61,9 @@

Export documents

Note that this normally does not speed up the exporting process, as the same amount of data is read from the index. The data transfer out of the Vespa application is smaller with fewer fields.

- - - -

Backup

-

- Use the visit operations above to extract documents for backup. -

- To back up documents to your own Google Cloud Storage, see - - backup for a Google Cloud Function example. +For copying documents between applications, see cloning applications and data.

- - -

Feed

diff --git a/en/reference/applications/deployment.html b/en/reference/applications/deployment.html index 1f7dbb5fb0..28e693ed10 100644 --- a/en/reference/applications/deployment.html +++ b/en/reference/applications/deployment.html @@ -40,6 +40,7 @@ days="mon,wed-fri" hours="16-23" time-zone="UTC" /> + aws-us-east-1c @@ -249,6 +250,62 @@

block-change

+

backup

+

+In <deployment>, or <instance>. +Configures scheduled backups of production content clusters. When present, backups will +be created at the specified frequency. Must be placed after any <test> and <staging> tags, +and before <prod>. +

+ + + + + + + + + + + + + + + + + + + + +
AttributeMandatoryValues
frequencyYesA positive integer with a suffix h (hours) or d (days), + e.g. 12h or 7d. Minimum 1h.
granularityNo, default cluster +
    +
  • cluster: all content nodes in the cluster
    • +
  • group: all content nodes in a single group
    • +
+
+

+ Backup activity does not affect service availability, but has costs in terms of performance. You can use granularity + to control the tradeoff between backup and restoration speed. +

+
+ In most situations we recommend cluster backups. +

+

+ Block windows also prevent new backups from starting in the given period. + If the available time is too short for a full backup to complete, the process will, however, extend into the block window. +

+

upgrade

In <deployment>, or <instance>. @@ -479,7 +536,7 @@

dev

In <deployment>. Optionally used to control deployment settings for the dev environment. -This can be used specify a different cloud account, tags, and private endpoints. +This can be used specify a different cloud account, tags, and private endpoints.

@@ -600,7 +657,7 @@

endpoints (global)

endpoints (dev)

In <dev>. This allows -zone endpoint +zone endpoint elements for cloud-native private network configuration for dev deployments. Note that private endpoints are only supported in prod.