mirror of
https://github.com/cupcakearmy/autorestic.git
synced 2026-04-02 20:05:23 +00:00
copy docs
This commit is contained in:
@@ -14,6 +14,7 @@
|
|||||||
> > [Overview](/location/options)
|
> > [Overview](/location/options)
|
||||||
> > [Excluding Files](/location/exclude)
|
> > [Excluding Files](/location/exclude)
|
||||||
> > [Forget Policy](/location/forget)
|
> > [Forget Policy](/location/forget)
|
||||||
|
> > [Copy](/location/copy)
|
||||||
>
|
>
|
||||||
> [Cron](/location/cron)
|
> [Cron](/location/cron)
|
||||||
> [Docker Volumes](/location/docker)
|
> [Docker Volumes](/location/docker)
|
||||||
|
|||||||
31
docs/markdown/location/copy.md
Normal file
31
docs/markdown/location/copy.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
# Copy
|
||||||
|
|
||||||
|
Instead of specifying multiple `to` backends for a given `location` you can also use the `copy` option. Instead of recalculating the backup multiple times, you can copy the freshly copied snapshot from one backend to the other, avoiding recomputation.
|
||||||
|
|
||||||
|
###### Example
|
||||||
|
|
||||||
|
```yaml | .autorestic.yml
|
||||||
|
locations:
|
||||||
|
my-location:
|
||||||
|
from: /data
|
||||||
|
to:
|
||||||
|
- a #Fast
|
||||||
|
- b #Fast
|
||||||
|
- c #Slow
|
||||||
|
```
|
||||||
|
|
||||||
|
Becomes
|
||||||
|
|
||||||
|
```yaml | .autorestic.yml
|
||||||
|
locations:
|
||||||
|
my-location:
|
||||||
|
from: /data
|
||||||
|
to:
|
||||||
|
- a
|
||||||
|
- b
|
||||||
|
copy:
|
||||||
|
a:
|
||||||
|
- c
|
||||||
|
```
|
||||||
|
|
||||||
|
Instead of backing up to each backend separately, you can choose that the snapshot created to `a` will be copied over to `c`, avoiding heavy computation on `c`.
|
||||||
Reference in New Issue
Block a user