I’ve started a test backup on a system which will take some time and I want to stop for them time being and continue it later.
Can that be done without corrupting the backup and forcing it from scratch when I want to resume?
Nothing will be corrupted. Can it start from where it stopped? For sure when you set --checkpoint-interval - see docs. I am not sure whether it is set by default.
I am running it from the UI and when I click on Snapshots it leads me to a list of tasks, and when I click on the Details link to a the Tasks panel there is a red button that says Stop and an orange one that says Return.
That Stop button looks dangerous to me. I expected something like Pause rather than Stop.
Will pressing it allow me to resume it?
Check source code or try:)
I think I have seen “incomplete snapshots” when using kopia so most likely it is set and saves checkpoints. Worst case you will lose last 45 min of backup max.
1 Like
For what its worth… all uploaded data up to the point of interruption - no matter the reason for the interruption, will already be in the repo and will not be uploaded again on the next run. As @kapitainsky mentioned, this would be an incomplete snapshot, which will get cleaned up, once the complete snapshot finishes.
This is what is showing after I stopped it and started it because it got stuck at a point.
Before I stopped it the Processed and Uploaded bytes stood at roughly 127GB.
I can’t remember what the Cached bytes was.
Which of these bytes values give a good idea of what is currently stored on the server?
127 + 4.4 GB. As I said, Kopia will not uplaod anything again, which it has uploaded before already. I wonder though, what’s the holdup is…? 218 GB shouldn’t be a problem in an hour, unless the connection or the underlying storage is slow.