Discussion Locked
0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have 2 clients with the exact same problem. I created a cmd file to run nt backup and then I have that file scheduled to run at 11pm using the scheduling service. My problem is that everything works great for about 2 weeks then stops working. When I show up onsite and check the event viewer there are no error messages. Then when I try to launch nt backup I get and hourglass for about 3 seconds and then nothing happens. I check the task manager and is does not show NT Backup Running. If I restart the server the backup will work fine for another 2 weeks but then fail again in the same way. Any Ideas?
6 replies
1. When you schedule tasks be sure to include the /Interactive switch. If you are logged on the task will not run.
2. Re-run the Service Pack intstall.
3. Buy a Basckup Solution--They're Cheap.
by gniazdo
Thanks it #1 was the problem. Thanks
by halleyc
Go to task manager's processes tab to see if there are ntbackup.exe is running. According to my experience, If ntbackup.exe process not total 'killed' and you start ntbackup.exe again, this symptom appear.
If the above message can't solve your problem, create another batch to shutdown your server weekly/daily at mid-night
by gniazdo
by xiopus
Additionally - make sure your clients keep a tape in the backup unit - if ntbackup tries to run and there is not a tape available it will crash and take the ntbackup process with it, the service can only be restarted after a reboot.
by gniazdo
Thanks This is exactly what caused the problem
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
1 helpful
20 replies
0 helpful
6 replies
0 helpful
12 replies
1 helpful
9 replies
Discussion
Do you think that business directories are relevant to Local SEO And Lead Generation today
0 helpful
14 replies