Windows

You might want to try WINAT.EXE from the NT Server Resource Kit - it's much more intuitive than the basic AT.EXE.

We use WINAT on about 52 servers and it works quite well. If you would like a copy of the specific batch file we use, I would glad to send it to you.

paul

The AT service must logon as a user with backup privilages. It does not by default. Change it to logon as administrator to test, then use a backup operator account for the service and it should work.

Yes you have to use AT (this is the scheduler service which you can find on the NT disk. After you add this you have to reapply patches.). But at will run an exe without parameters. In this case you make a batch file in which you use NTBackup.exe with your parameters (you can find those in the Windows NT help). You can find AT parameters by running AT /?. Run this non-interactive (put errors in a log) and you will have no problems with users. To make sure everything run smoothly you can put thescheduler service on automatic startup (so it runs whenever your server restarts).
I used this method and it works. You can have different batch files for different backups (even of other machines on the network (for which you have to map a drive on the server).

Luck

Before we had a budget for software we used a batch file called by the AT Scheduler as recommended by Gicu Artistu. However running non-interactively, if we had a problem with a backup - which was not that uncommon with nt's backup, we could not stop it without resorting to the resource kit kill command or rebooting. Our severs are in a locked room so we ran the command with the interactive switch and had better performance.

This question was auto closed due to inactivity