Justin Rich wrote:
Quote:
> i have a script that does a db backup and then copies itself over to another
> system when it gets to that system i'd like to run a db check on the file to
> verify it moved successfully.
>
> i cant run the db check from the DB server because it will basically pull
> all the data back over so basically i'd like to run one script on the DB
> server that does the backup and pushes it off and then another script one
> the backup server that verifies the file copied correctly.
>
> so basically how can i make the script on the backup server run as soon as
> the script on the db server finishes?
>
> Thanks
> Justin
>
>
Is there a way for the backup server to track on which DB server the
script is running on?
What I'm thinking is that script would create a temporary lock file when
starting, then delete it when done.
The script from the backup server will then loop for seconds, minutes,
hours depending on how long the script usually takes, and will check for
that temporary lock file. When the lock file is gone, then the script
runs whatever checks it needs to do. Then you can also use that to
watch for the lock file, and if the lock file remains for too long,
something might be locked up/running away.
That's if I'm following you properly...
Marco
--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp
PowerGadgets MVP
http://www.powergadgets.com/mvp
Blog:
http://marcoshaw.blogspot.com