Hi
because onbar -v is doing a completely different job.
onbar -b and onbar -r are "simply" reading kind of serial an object (either a dbspace object or a backup object in the storage manager) and the writing it (again either a dbspace object or a backup object). Being able handle more objects in parallel.
onbar -v does consistency checking. Which is more complex and also needs a "different" reading. I can't be expected that there is enough space to store the whole instance in the file system. So there will be rereads of backup objects and also a lot of reading in files on disk.
+ the checking
When your instance is huge I would suggest to run verification only on most important dbspaces - or at least one after the other
------------------------------
Hedwig Fuchs
------------------------------
Original Message:
Sent: Thu February 08, 2024 12:30 PM
From: Dennis Melnikov
Subject: Why is `onbar -v` so slow?
Hi,
While `onbar -b` takes 22 hours, `onbar -r` proceeds in 30 hours, `onbar -v` runs 7+ days.
What is wrong with it?
------------------------------
Sincerely,
Dennis
------------------------------