I want to unload the LH.NLM (1.10, soon to be 1.5) and LHIPXSER.NLM just prior to backup using the pre and restore with the post commands of Backup Exec, v8.0. Revelation is running on a Novell NetWare 4.2 server. I have time restrictions set up so that except for weekends, all users are disconnected before the backups. The application is called BOOST, and has been highly modified over the years. The indexer computer is already setup not to be indexing in the early AM hours when I want to do the backups. My problem is that on weekends, there are a few computers which we need to keep a live connection to the network all weekend so that users can dial in via the Shiva Lanrover and control their PC with PCAnywhere32 and do data entry. To do this the computer must have a live connection (logged in) to the network. The workstations are all running Win95 and Client 32, which we are upgrading to Client 3.02 and setting up Zenworks with Managewise. All tests so far with this setup are working fine, BTW. My qu

estions is, if I unload the NLM's while someone (and you KNOW that SOMEONE will…) either left the computer on with AREV running, or are getting brownie points by diligently working away at 1:10 AM when the backup kicks off and unloads the NLM's, what will be the affect on the data? Mind you, some of the data files are 3+ gigs in size if that makes a difference. Am I correct in assuming that all which could be lost is the changes to the record which the user happens to have open at the time? Is there any chance of corruption? Any insight into this would be helpful.

Scott Hammons

Exodus Communications, Professional Services

[email protected]

Sidestepping just a bit, you might make all these questions irrelevant after checking out Open File Manager

Victor,

I prefer not to use the open file option. Yes, I am using it now, but on the whole, would rather not, so that is why I want to unload the Revelation NLM's before backups and load them up again afterwards. Maybe I am too conservative, but when it comes to live data, I get real paranoid.

Scott

Exodus Communications, Professional Services

[email protected]

Scott..

Ever heard of playing Russian Roulette with a machine gun? Unloading the NLM with open sessions will practically guarantee one or more of the following:

1.  The desktop APP will fail, perhaps with partially written data in the case of updating multiple tables from a single transaction.

2.  Unless background indexing is turned off on every desktop, the app will hang and require a COLD BOOT

3.  The desktop may see the Lan Connection go away (depending on the client).  That's because the TSR will stop communicating with the server and return a Device Error reading Network ... error

You might, and I mean MIGHT, be able to copy the database to another server which is not running the NLM and then back up that, but with any activity at all, this probably won't work. Too many files will be skipped.

Victor's solution is probably the only genuinely workable one, but like you, I am paranoid about data.

Don Miller

C3 Inc.

View this thread on the forum...