Skip to content

Commit 07ffb05

Browse files
authored
Merge pull request #68304 from sjhala-ccs/oadp-2671
OADP#2671: Added new assembly about Kopia
2 parents a3468a3 + bd07949 commit 07ffb05

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2831,6 +2831,8 @@ Topics:
28312831
File: oadp-scheduling-backups-doc
28322832
- Name: Deleting backups
28332833
File: oadp-deleting-backups-doc
2834+
- Name: About Kopia
2835+
File: oadp-about-kopia
28342836
- Name: OADP restoring
28352837
Dir: backing_up_and_restoring
28362838
Topics:
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="oadp-about-kopia"]
3+
= About Kopia
4+
include::_attributes/common-attributes.adoc[]
5+
:context: oadp-about-kopia
6+
7+
toc::[]
8+
9+
Kopia is a fast and secure open-source backup and restore tool that allows you to create encrypted snapshots of your data and save the snapshots to remote or cloud storage of your choice.
10+
11+
Kopia supports network and local storage locations, and many cloud or remote storage locations, including:
12+
13+
* Amazon S3 and any cloud storage that is compatible with S3
14+
* Azure Blob Storage
15+
* Google Cloud Storage Platform
16+
17+
Kopia uses content-addressable storage for snapshots:
18+
19+
* Each snapshot is always incremental. This means that all data is uploaded once to the repository, based on file content. A file is only uploaded to the repository again if it is modified.
20+
21+
* Multiple copies of the same file are stored once, meaning deduplication. After moving or renaming large files, Kopia can recognize that they have the same content and does not upload them again.
22+
23+
24+
[id="oadp-kopia-integration"]
25+
== OADP integration with Kopia
26+
27+
OADP 1.3 supports Kopia as the backup mechanism for pod volume backup in addition to Restic. You must choose one or the other at installation by setting the `uploaderType` field in the `DataProtectionApplication` custom resource (CR). The possible values are `restic` or `kopia`. If you do not specify an `uploaderType`, OADP 1.3 defaults to using Kopia as the backup mechanism. The data is written to and read from a unified repository.
28+
29+
.`DataProtectionApplication` configuration for Kopia
30+
[source,yaml]
31+
----
32+
apiVersion: oadp.openshift.io/v1alpha1
33+
kind: DataProtectionApplication
34+
metadata:
35+
name: dpa-sample
36+
spec:
37+
configuration:
38+
nodeAgent:
39+
enable: true
40+
uploaderType: kopia
41+
# ...
42+
----

0 commit comments

Comments
 (0)