Created On: 30 Sep 1999 9:08 am Last Edited: 4 Mar 2013 9:32 am
Instructions for handling a corrupt database.
If you are running a 3.x or greater release, do a recovery from webxdb.1/webxroll.1. First read the "Backup and Recovery" section of your sysop documentation for a detailed understanding pertaining to your web crossing version (here for our most recent), but the overview is:
1. Stop Web Crossing.
2. Make safe copies in another location of webxdb.1, webxroll.1, and all other webxdb.n and webxroll.n files.
3. Rename webx.db to some other name.
4. Start Web Crossing.
5. Web Crossing will be unresponsive while the recovery takes place, but can be monitored by watching the end of the logRoll file.
6. If a recent control panel backup has been done the recovery will not take long, but if webxroll.1 is very large (several megabytes or more) it can take hours.