Dedicated Indexer Stops Updating Indexes (AREV Specific)
At 16 MAR 1998 10:41:05AM Rob Pietrobono wrote:
I have a dedicated indexer running Arev 3.11 which stops updating indexes at the start of a new day. I have to hit a key on the keyboard every morning to "wake-up" the indexer which then continues.
In a way, it's good thing since our network does back-ups between 12am and 4am. Which I assume would conflict with the indexer had it been updating while a back-up occurs.
Is there a fix for this?
If so, will back-ups occurring while the indexer is running cause any problems?
At 16 MAR 1998 10:54AM Aaron Kaplan wrote:
This is a known bug that was fixed in the Advanced Revelation 3.12 Maintenance Release.
At 16 MAR 1998 01:22PM Rob Pietrobono wrote:
Thanks…
So once I upgrade to 3.12 my indexer will be operating during a backup. Will this cause any problems? If so, how do I suspend it during scheduled backup times?
I know it sounds crazy. First I want the Indexer to operate continuously and now I want to stop it!
At 17 MAR 1998 09:28AM Aaron Kaplan wrote:
There's no real built-in way to stop the indexer. What you'll need to do is place in a post-index process. In there, you'll check to see it's between a set of times. If so, issue a SUSPEND and come back into ARev. That will close all open files. Then, sit in a loop until a specified time. The indexer will still be running, but it won't have files open and it won't process indexes until it leaves the post index process.
For the suspend, you'll probably have to call an empty batch file that has EXIT in there.
At 18 MAR 1998 01:46AM Matt Sorrell wrote:
Rob,
On our system, we are running Novell Netware 3.12. The way we handle this situation is that in our AREV application directory, we flagged all of the files as shareable. This way, even if an application has a file open, the backup program will still have access to the files. We don't seem to have any problem with this solution. Someone else may know of a problem this may cause, but it works for us.
Matt Sorrell
M.G.A., Inc.
At 18 MAR 1998 03:21PM Victor Engel wrote:
Unless you have specifically addressed this issue with respect to your backup process, you are likely to get a good backup yet not be able to restore. This is because, for example, the .LK and .OV files could be backed up separately with an update to the file being made in the mean time. If you try to restore such a file, you will get a GFE. To test this out, write a program to create a lot of records and then delete them, repeating until you are sure the backup has taken place. While this program is running, run the backup. Now try the restore and see if you get a usable file.
If you are sure no files are being updated during the backup, then this is not an issue.
At 18 MAR 1998 05:59PM Bob Lynch wrote:
I believe there is a way to put an indexer to sleep for a specified time for a specified duration. This way the indexer will not interfer with backups. I will have to look around for that program, but I know it is around.
Bob
At 18 MAR 1998 07:41PM Russell Causey @ Lifescan, Inc. wrote:
I use a shareware scheduling program called 'Painless Event Scheduler or PEP' to stuff an into the keyboard buffer of the indexer machine. From there the autoexec.bat of the indexer uses another shareware program called PCopy to backup all of my AREV directories. This takes about 2 hours. Then the autoexec goes back to indexing. Pcopy will, as an option, ignore any files that are busy but with the indexer down, and serveronly=true, there shouldn't be any files open and being updated.
Barring network failures this method has been pretty bulletproof for almost a year.
I tried using the post-index process but something in our application kept resetting it to blanks.
If you want a copy of this .bat file, Pcopy or PEP ask:
At 18 AUG 2000 12:54PM Cynthia Juhlin Lee wrote:
Syscomp is experienceing this problem for the first time on an AREV 3.12 installation running Windows 95. We have have many 3.12 installations with dedicated Index Servers and no problems reported.
The best way to describe the problem is that the index server seems to be asleep and you have to wake it up by pressing F5 or something. Kurt Baker mentioned trying a CTRL BREAK and checking the variables by typing @index.time and backgrnd.time at the debugger.
Cyndi Lee, Syscomp, Inc.