\\computername id

/delete /yes


Specifies a computer that the job should run on. If you don't specify another computer, then the job will run on the same computer that AT's running on.

This is the job ID assigned to a task when you've scheduled it with AT. Use the job ID to reference the task.

Deletes the task with that job ID (or all jobs, if you don't specify a particular ID) from the jobs list. If you delete a backup, it won't be run.

If you omit this switch, AT will ask you whether you're sure you want to delete the task in question from the jobs list. If you're sure and don't want to be prompted, use this switch.

Specifies the time when the task should run. AT uses a 24-hour clock, so add 12 to the hours after noon. 3:00 p.m. becomes 15:00, 7:30 a.m. becomes 19:30, and so forth.

Tells the job to interact with the desktop of the user logged on at the time the task is running. Normally, you won't want to use this option if you're automating a backup. The whole point of this exercise is to run the backup when no one's around to supervise it.

Runs the task on the specified days of the week or month. If you don't specify a date with this switch, then the task is scheduled for the current day (which means that you could potentially schedule a job to run before the time when you created it, meaning the job will never run). Dates use numbers; days of the week may be abbreviated thus: Su M T W Th F S.

Runs the task on the next occurrence of the specified day. If you don't specify a date, then it will assume that you mean the current day of the month. Dates use numbers; days of the week may be abbreviated thus: Su M T W Th F S.


This is the Win2K command or batch program to be run as specified.

NOTE If you don't specify a date at all, AT will add 1 to the current date and run the task on the next date that matches. So, if you create a job on June 28 but don't specify a date for the task, AT will schedule it for June 29. AT is smart enough to know how many days are in a month, so if you create a job on the 30th, it will schedule the job for the 1st or the 31st, depending on what month it is.

You can use AT with the full syntax of the NTBACKUP command, but I find it simpler to save the NTBACKUP settings you want as a batch file and then reference the batch file. First, it means less typing when it comes to scheduling the job. Second, unless you're backing up a network-accessible drive, you're going to want to stop and start the network before and after the backup to make sure that all files are backed up— again, NTBACKUP won't back up open files. A sample batch file might look like this: net stop server ntbackup h:\acmeV /m differential /f d:\system1.bkf /j ^■"Differential backup of Acme folder" net start server

Save this batch with a .bat extension in a text editor such as Notepad, naming it, say, differential.bat. You'll be able to reference it with AT like this:

at 5:47 /every:M,T,W,Th,F,S differential Every day but Sunday, the file differential.bat will run. (Sunday is the day I do full backups.) It will stop the Server service, run the backup with the settings you specify, then start the Server service when it's done.

If you want to be sure that a job is added to the list properly, type at from the command prompt to view the contents of the job list:

Status ID Day Time Command Line

If I wanted to delete task 2 from the job list, I'd use AT like this: AT 2 /delete

Was this article helpful?

0 0

Post a comment