Hi there,

We're sometimes having the backup job keeping on running on our system. It
looks like it's because there are still users doing their stuff on the
machine (24*7 availability). When they're doing queries the system cpu is
used up fully at around 100%, while the backup only needs a percent or 10.
At moments like this during the night the backup jobs just keeps on waiting
until it gets some cpu (is it the case that sessions in the same queue get a
higher priority than jobs, as both the usersessions as well as the backup
job run in the c-queue?).

What I'm thinking of to prevent this is to put all the users currently
running temporary in the d-queue with "altproc" (ALTPROC
job=@s;pri=ds;anyuser) but how can make sure that all new users logging in
will also be placed in the d-queue for the time of the backup running (about
an hour normally, during heavy system use sometimes more than 10 hours!).
How can I temporary change the queue of (all) users logging in, to make sure
the backup runs smoothly (it's doesn't seem a good idea to run the backup in
the b-queue).

Could'nt it also be possible to put the backup in a fixed queue, sothat its
priority doesn't decay??? So it could take it's 10% and leave the rest for
the couple of users (or sometimes only userscripts running overnight) logged
in, they wouldn't mind at that time (during daytime we've got 250 users
logged in).

Thanx,

bArtoque