Update uploader configuration design doc

Signed-off-by: Ming Qiu <mqiu@vmware.com>

site/content/docs/main/api-types/backup.md

@@ -124,6 +124,10 @@ spec:
   snapshotMoveData: true
   # The data mover to be used by the backup. If the value is "" or "velero", the built-in data mover will be used.
   datamover: velero
+  # UploaderConfig specifies the configuration for the uploader
+  uploaderConfig:
+      # ParallelFilesUpload is the number of files parallel uploads to perform when using the uploader.
+      parallelFilesUpload: 10
   # Actions to perform at different times during a backup. The only hook supported is
   # executing a command in a container in a pod using the pod exec API. Optional.
   hooks:

site/content/docs/main/api-types/restore.md

@@ -39,6 +39,10 @@ spec:
   # asynchronous BackupItemAction operations
   # The default value is 1 hour.
   itemOperationTimeout: 1h
+  # UploaderConfig specifies the configuration for the restore.
+  uploaderConfig:
+    # WriteSparseFiles is a flag to indicate whether write files sparsely or not
+    writeSparseFiles: true
   # Array of namespaces to include in the restore. If unspecified, all namespaces are included.
   # Optional.
   includedNamespaces:

site/content/docs/main/api-types/schedule.md

@@ -127,6 +127,10 @@ spec:
     snapshotMoveData: true
     # The data mover to be used by the backup. If the value is "" or "velero", the built-in data mover will be used.
     datamover: velero
+    # UploaderConfig specifies the configuration for the uploader
+    uploaderConfig:
+        # ParallelFilesUpload is the number of files parallel uploads to perform when using the uploader.
+        parallelFilesUpload: 10
     metadata:
       labels:
         labelname: somelabelvalue

site/content/docs/main/backup-reference.md

@@ -10,6 +10,11 @@ It is possible to exclude individual items from being backed up, even if they ma
 ```bash
 kubectl label -n <ITEM_NAMESPACE> <RESOURCE>/<NAME> velero.io/exclude-from-backup=true
 ```
+## Parallel Files Upload
+If using fs-backup with Kopia uploader or CSI snapshot data movements, it's allowed to configure the option for parallel files upload, which could accelerate the backup:
+```bash
+velero backup create <BACKUP_NAME> --include-namespaces <NAMESPACE> --parallel-files-upload <NUM> --wait
+```
 
 ## Specify Backup Orders of Resources of Specific Kind
 

site/content/docs/main/restore-reference.md

@@ -273,6 +273,12 @@ You can also configure the existing resource policy in a [Restore](api-types/res
 * Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
 * `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
 
+## Write Sparse files
+If using fs-restore or CSI snapshot data movements, it's supported to write sparse files during restore by the below command:
+```bash
+velero restore create <RESTORE_NAME> --from-backup <BACKUP_NAME> --write-sparse-files --wait
+``` 
+
 ## Removing a Restore object
 
 There are two ways to delete a Restore object: