Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Neil Truby — — source: Usenet: comp.databases.informix
"sumGirl" <emebohw@netscape.net> wrote in message
news:a5e13cff.0409151450.245785df@posting.google.com...
> Just wondering if anyone knows of a way to check the progress of an ontape
backup?
If you zero out the stats with onstat -z then do an onstat -D you can see
which chunk it's on. You'll be able to tell then how far through that
dbspace it is. Telling the order of the dbspaces is more tricky.
If you don't zero out the stats onstat -u will show you how many reads the
archive session has done. Since the total number of pages it will read is
(allocated - free) pages for all your chunks you should be able to tell
from here how far through it is too.
↪ replying to Neil Truby
Dave Griffen — — source: Usenet: comp.databases.informix
"Neil Truby" <neil.truby@ardenta.com> wrote in message
news:2qss9nF13kr5eU1@uni-berlin.de...
> "sumGirl" <emebohw@netscape.net> wrote in message
> news:a5e13cff.0409151450.245785df@posting.google.com...
> > Just wondering if anyone knows of a way to check the progress of an
ontape> backup?
>
> If you zero out the stats with onstat -z then do an onstat -D you can see
> which chunk it's on. You'll be able to tell then how far through that
> dbspace it is. Telling the order of the dbspaces is more tricky.
Ontape order of dbspaces is dbsnum. This is also the same order they appear
in the online.log entries for ontape. If your following an ontape restore,
a checkpoint occurs after each dbspace.
>
> If you don't zero out the stats onstat -u will show you how many reads the
> archive session has done. Since the total number of pages it will read is
> (allocated - free) pages for all your chunks you should be able to tell
> from here how far through it is too.
>
>
Thats great info Neil. I'm betting something like thats the result of
years of experience, thanks!
"Neil Truby" <neil.truby@ardenta.com> wrote in message news:<2qss9nF13kr5eU1@uni-berlin.de>...
> "sumGirl" <emebohw@netscape.net> wrote in message
> news:a5e13cff.0409151450.245785df@posting.google.com...
> > Just wondering if anyone knows of a way to check the progress of an ontape
> backup?
>
> If you zero out the stats with onstat -z then do an onstat -D you can see
> which chunk it's on. You'll be able to tell then how far through that
> dbspace it is. Telling the order of the dbspaces is more tricky.
>
> If you don't zero out the stats onstat -u will show you how many reads the
> archive session has done. Since the total number of pages it will read is
> (allocated - free) pages for all your chunks you should be able to tell
> from here how far through it is too.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.