Or if you want to use the proper Novell command, use:
MAP Q: /DEL
where Q: is your drive letter.
If the data was on a seperate volume, you could always configure a CRON job to dismount the volume on the server at 11pm, then a job to remount the volume at the required time in the morning. This way definately will mean the data is inaccessible as there are ways around the scheduler to stop it working. Both ways have their disadvantages because any open files at the time risk getting corrupted.
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
I have a problem with an old Foxpro application in a multiuser environment. We have a lot of user who leave the application open at night (the .dbf is on a Novell Server) Therefore, it is impossible for us to do the update automatically at night (File is lock). (The data is downloaded from a mainframe and uploaded in the dbase database)
I would say that your best bet is user education. Identify the users who keep the file open by checking who has the file open in MONITOR - then "educate" them to shut their PC down of a night.
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
You can also get those connections cleared by the watchdog if you put login time restrictions. If you are not a 24/7 shop I suggest putting the restrictions on all users so that you can get a complete backup(except for the backup user of course). We are 24/7 so we have the same issue.
Also, there are open file agents for most Backup programs which perport to backup open files. I've never had to restore one that was open so I cannot say if they really work or not.
Jon
There is much pleasure to be gained from useless knowledge. (Bertrand Russell)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.