I have a 4.6 TB backup collection that I wish to restore.
Because the restore operation is taking a long time, there have been multiple interruptions along the way. I am aware that the restore can be restarted by choosing the same output folder and choosing “overwrite existing files” rather than versioning files.
However, each time I restart the restore the database has to be recreated and this takes a long time to complete.
Is there any way the database can be cached? Perhaps save it to tmp folder with a filename that is derived from the backup source in some way?
I don’t think feature exists. As UI says (or maybe used to), it’s a temporary file.
You can make a dummy job with basically any Source config, just to do restore.
Be careful not to do a backup or any maintenance that might affect Destination.
I think the first part is all you need. I don’t think it overwrites existing correct files.
If you originally like “Save different versions with timestamp in file name”, keep it.
Rationale is below, and if I misread new restore flow, maybe devs will correct me.
(see the part about checking the target files first to see if any work must be done)
EDIT 1:
You just recreate the database of the dummy job from a destination, then restore.
EDIT 2:
DB recreate will be slower, especially if you have a lot of versions. A workaround limiting to 1 version is CLI with --version option, but that’s more work to set up.