How to export with disk almost used

1

Hey there,

How to do backup in the following situation:
zfs pool = 800GB
1 container uses 700GB
If i have to export it, it will need another 700GB for “exporting” and another <700GB to create the .tar.gz file. In that case export will be impossible.

However I can add additional disk which is several TBs. Is there a way to use the second disk to create the additional two 700GB needed?

Or second solution will be to create snapshot and copy it to another server? What would be the best scenario here. Backups should be done on a daily basis.

2

I learned about a way of doing this recently. I have not tested it yet.

You could try editing this sever config storage.backups_volume and have it point to your additional disk.

Please let us know if this fixes your problem. :slight_smile:

3

I had the same issue. The solution I found was to change the backups directory (/var/lib/incus/backups) to point to a different disk or a share on a different server. Then exports go to the other mount point directly and you don’t get duplication of data nor do you get a large copy operation after the export runs.

I set it up so that it mounts the backup location, runs incus export, and then unmounts that location. Right now it does NFS, but I’m planning to also add a regular disk mount option for airgapped disk rotations.

See “export_incus_to_remote.sh” at: GitHub - AJRepo/incus_tools: Tools for Incus

4

hi,

Maybe this new process of incus export : Incus 6.22 has been released

5

Oh wow. This is really great.