topic Re: fbackup scheduling question in Operating System - HP-UX

fbackup scheduling question

Mark Greene_1 — Fri, 27 Sep 2002 14:16:32 GMT

On one of my HP systems we have an fbackup that runs nightly. I can see that the contents of /var/adm/fbackupfiles/dates changes daily:

STARTED: Thu Sep 26 23:56:21 2002 ENDED: Fri Sep 27 00:41:29 2002

However, when I go into sam and look at backups, it reports that no automatic backups are scheduled. So my question is, where else should I look to see from where this is being run? I've looked in all of the crontabs, and no fbackups there.

TIA
mark

Re: fbackup scheduling question

Paula J Frazer-Campbell — Fri, 27 Sep 2002 14:19:25 GMT

Mark

Have a look in cronlog - the owner info should be there.

HTH

Paula

Re: fbackup scheduling question

Rodney Hills — Fri, 27 Sep 2002 14:20:20 GMT

The only other scheduling system would be "at".

Try "at -l" to list scheduled jobs. Although an "at" job is run only once, the script could run "at" again to reschedule itself.

HTH

-- Rod Hills

Re: fbackup scheduling question

Paula J Frazer-Campbell — Fri, 27 Sep 2002 14:23:14 GMT

HI

/var/adm/cron/log

and /var/adm/at.allow

May help

Paula

Re: fbackup scheduling question

Ian Dennison_1 — Fri, 27 Sep 2002 14:26:53 GMT

How consistent is the Start Time?

I would put a check into crontab like so,....

01 00 * * * ps -ef >/tmp/psef

At 1 minute past midnight get a process list and the next working morning, find the PID and the PPID and trace back to whatever spawned the process.

If the start time is inconsistent, perhaps the application is triggering it? Perhaps at the end of each job, the script reschedules itself with an 'at' command?

Share and Enjoy! Ian

Re: fbackup scheduling question

James R. Ferguson — Fri, 27 Sep 2002 14:46:46 GMT

Hi Mark:

The name of the graph file used with the backup preceeds th line "STARTED...". Perhaps that may be of help.

Regards!

...JRF...

Re: fbackup scheduling question

Mark Greene_1 — Mon, 30 Sep 2002 20:56:57 GMT

Thanks to all who replied; it turns out that the fbackup is being explicitly called by the application, which is why I could not find it anywhere else.

mark