Skip to content

Commit 37ed343

Browse files
Remove restic
Signed-off-by: ArnauGabrielAtienza <[email protected]>
1 parent 74019d6 commit 37ed343

File tree

1 file changed

+1
-5
lines changed
  • source/management_and_operations/backups

1 file changed

+1
-5
lines changed

source/management_and_operations/backups/veeam.rst

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ A server should be configured to expose both the Rsync backup datastore and the
3939
Step 2: Create a backup datastore
4040
================================================================================
4141

42-
The next step is to create a backup datastore in OpenNebula. This datastore will be used by the oVirtAPI module to handle the backup of the virtual machines before sending the backup data to Veeam. You can choose to use either a :ref:`Rsync Datastore <vm_backups_rsync>` or an :ref:`Restic Datastore <vm_backups_restic>`. The following sections will describe how to create each of them.
42+
The next step is to create a backup datastore in OpenNebula. This datastore will be used by the oVirtAPI module to handle the backup of the virtual machines before sending the backup data to Veeam. Currently only :ref:`Rsync Datastore <vm_backups_rsync>` is supported.
4343

4444
.. note::
4545

@@ -72,10 +72,6 @@ Here is an example to create an Rsync datastore in a host named "backup-host" an
7272

7373
You can find more details regarding the Rsync datastore in :ref:`Backup Datastore: Rsync <vm_backups_rsync>`.
7474

75-
**Restic Datastore**
76-
77-
TODO
78-
7975
Step 3: Install and configure the oVirtAPI module
8076
================================================================================
8177

0 commit comments

Comments
 (0)