Hi All,
I want to backup a huge container. I make a snapshot from the container and then publish it. after that i will export the image to a file.
However my question is it possible to store the publish on a different drive? I have not enough storage and want to write it to a usb drive.
stgraber
(Stéphane Graber)
June 13, 2024, 9:55pm
2
You can configure Incus to store its images and backups within a storage pool rather than directly on the host.
That’s done with the storage.images_volume
and storage.backups_volume
server config keys.
Hi @stgraber
How can i see where it us storing now? I want to write this one container backup to usb and want to revert to its original settings after that.
stgraber
(Stéphane Graber)
June 14, 2024, 5:37am
4
/var/lib/incus/images
and /var/lib/incus/backups
when i want to revert the storage to the deafult can i do this:
incus config set storage.backups_volume default /var/lib/incus/images ? Even if there is allredeay data in it?
stgraber
(Stéphane Graber)
June 14, 2024, 1:11pm
7
No, you’d just unset the keys:
incus config unset storage.backups_volume
incus config unset storage.images_volume
Scott_T
(Scott T)
June 14, 2024, 3:09pm
9
If you perform:
incus export c1
You get a c1.tar.gz in your pwd.
Why is it that there are redundant copies of all exports in this location as well?
/var/lib/incus/backups/instances
stgraber
(Stéphane Graber)
June 14, 2024, 3:15pm
10
Because incus export
is making use of the backup API.
It effectively triggers a server-side backup which lands in /var/lib/incus/backups/instances
, then gets downloaded by the client and deleted from the server.