Restore Start and End Time

Hi, what kind of restore job is this? When performing a CT or VM restore, there will be 2 (or more) reader tasks. The one you showed probably is just the fetching of the VM/CT config, which completes fast. You should see this from the task log itself as it will contain a download "/<absolute-path-to-your-snapshot>/pct.conf.blob"
 
As stated, there might be multiple reader tasks associated with one restore task. Please post the reader task log if unsure, but I guess you showed the container config reader task.
 
I am unsure. Do you want to see actual /mnt/datastore/s3-cache/ct/1004/2026-01-07T09:41:24Z/pct.conf.blob file?

If you look at the UI I pasted ^ it showed the same timestamps fro the Start and End and it looks like a bug to me regardless what is in the log. No?
 
I am unsure. Do you want to see actual /mnt/datastore/s3-cache/ct/1004/2026-01-07T09:41:24Z/pct.conf.blob file?
No, what I'm trying to tell you is that there might be multiple reader tasks which are started when performing a restore, not just one. You should be able to distinguish the these task by their difference in log content, that is the reason for suggesting to inspect the logs.

If you look at the UI I pasted ^ it showed the same timestamps fro the Start and End and it looks like a bug to me regardless what is in the log. No?
But that task seems to have been finished in under a second. Again. the 4 minutes restore task you see on the PVE side might have multiple reader tasks on the PBS side, the task reading the fixed index chunks will probably be around the 4 minutes, the task you showed is however most likely the config restore, which runs in a different reader task and completes within one second time resolution.