I need to put a ZIP drive in an NT4.0 Server, then share the drive to the Network and enable a Windows 95 client to run a batch file which does the following...
Pkzips up the .dbf database files
copys the new .zip file to a dir. somewhere
upload the zip file along with other files from the "somewhere" dir. onto the network drive. Which would be something like G: (\\saturnv\zip)
All permissions aside, these I don't believe would be the problem, but when I set this up on a peer-to-peer network a year ago with an internal 100Mb Iomega, with the sharing software it has it didn't work. None of the other computers on the LAN could see the share, even though they could see the share of the computers C drive.
I know I can just run AT on the server to schedule this batch file to run, and run it in an CMD window on the Server.
But firstly that means risking corruption by using DOS (kinda). Secondly the last thing the batch file does after backing up at the moment (to a SCSI Tape backup) is it runs the Database program with a switch which re-indexes the database. If this is not done at least every couple of days (backups done daily) the Database program slows to a halt, due to it's size.
Yet the database program can not be run on the Windows NT server.
The backup can only be done whilst no other workstations are logged in, and the backup must be done before the Indexing.
Please get back soon, and point out where you need more info, I have to let them know which sort of drive to get, it will either be Internal on the Server, or external on the Backup workstation (not preferred since this can not be locked away like the Server - This is a small multimillion dollar company, and the backup is not done for the sake of having the data, but so that no-one can tamper with it, i.e someone will always have an original copy should anyone diddle the books.)
Manager - Technician
Green Light Computing