How Do I Stop the Validation clashing with ABC
Some of the Premvet programs will lock the system, this is so they have exclusive access, such as the validation. When a validation is running when any other program tries to access Premvet it will freeze.
The simplest way to sort this is to schedule the jobs so that 'locking' type programs do not clash with others. However, sometimes this is just not possible, for example, the DataMajor re-build is usually run once a week, on Sundays, while the validation runs on the 27th of the month. Most of the time this will not cause a problem but when the 27th is a Sunday they will clash.
Is there a way to stop this?
Yes - All the unattended Premvet utilities support the -L command line options - the -L will apply a lock to the system, this lock is checked for when other programs start, if present they will not attempt to run.
If you use the Automation Manager, this will automatically add the -L to the job but if you are in the habit of manually editing the unattended jobs it is up to you to add it. e.g.
Before:
0 2 27 * * /usr/local/bin/vet -p valid
0 2 27 * * /usr/local/bin/vet -L -p valid
As you can see all you do is add the -L after the word vet. Now on the 27th at 2:00am the validation will run and any other programs that try to run will be stopped from doing so.
The -L option is not just for validations, take the following for example:
5 0 * * 0 /usr/local/bin/vet -p wdb 0 2 27 * * /usr/local/bin/vet -p valid
In this case the DataMajor rebuild starts every Sunday at 0:05am and runs till it is finished, if the 27th is also a Sunday the Validation will start at 2:00am. If the DataMajor rebuild is still running then it will be frozen out as the validation will take priority. - The tables will not be re-built correctly and you will have to re-run the wdb utility. If you change those to:
5 0 * * 0 /usr/local/bin/vet -L -p wdb 0 2 27 * * /usr/local/bin/vet -L -p valid
Therefore by using the -L option where appropriate you can save yourself some grief.
The Vet System and Other Applications
The above is fine if you are just concerned with Premvet utilities but what about other applications e.g. your backup (Edge).
Edge usually runs every night, however, if a validation is running at the same time your backup is not valid (the Validation has locked some files which the backup programs skips).
You can tell Edge about the -L option so it will also not start if a validation is running - yes it is possible to also tell edge to create the same lock file so a validation will not start if a backup is in progress but it is easier to schedule validations to run before edge starts. Contact Support if you want further details.
Setting up Edge to Honor Premvet Lock Files
- Login as root and type
ste /etc/edge.start - Go to the bottom of the document and insert the line shown in
bold below:
# ==================================================================== # Sample - Uncomment Next 2 Lines To Activate # /usr/lib/lpshut # $ECHO "Line Printer Spooler Shutdown Before Backup Started!" [ -f /tmp/vet.LCK ] && exit 1 # Exit normally and begin the backup process exit 0 - Press F2 to save the file
- If you are using Edge 01.02.xx then:
- Type
edgemenuto start up the menu for edge - Select Schedule
- Edit Domain
- Entire System
- In Start/Stop script add
/usr/lib/edge/bin/edge.bscript - Select Save then exit edgemenu
- Type