This would be fairly easy, all you need to do is modify the cron settings.
one of two ways... either run a cron job to execute your Perforce checkpoint
program on a cron job x mins before the cron job for amanda happens knowing
that the perforce program takes x mins to complete (and of course some buffering
wouldn't hurt) and then have the cron job for amdump run after. Or, just make
your own shell script owned by user backup that can do both in the script for you
and then remove the amdump cron job and have the shell script do this for you.
i.e.
#!/bin/bash
# a shell script to execute command "command" before running the daily
# amanda dumps
command ;
amdump DailySet1;
That should do it really, you could do more complex coding to error check if
you wanted, but that should do what you want, and of course, in the previous example,
you need bash on your solaris machine, or you modify it to work w/ csh (not much
difference if I remember csh...) and then replace command w/ whatever the command is
that runs the
Perforce checkpoint program. Also you may have issues w/ needing to run the perforce
command as some other user than backup, in which case you may do better to use the cron
way mentioned first.
Hopefully this is a lead in the right direction
Phil
On Wed 13 Dec 2000 at 18:58:27 -0500, you wrote:
> Folks,
>
> I have a source code control system (Perforce) running on a Solaris Amanda
> Client (2.4.1p1). Perforce has the ability to "checkpoint" its metadata in
> journal files, essentially taking a human-readable snapshot of the metadata
> at that particular. I'd like to do this checkpoint and then backup the
> checkpoint
> with as short an interval as possible between the 2.
>
> Is there a way to run a "pre-backup" script or command prior to Amanda
> starting the backup?
>
> Thanks,
>
> Dave
--
Phillip Davis, MIS Department
415.354.4238 tel or x4238 @ 415.354.4878
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the Revolution.
