NTBACKUP Again, Please Help

[Guest]

Still NTBACKUP does not start in Windows 2003 Server. I tried the command
line, by typing NTBACKUP and selecting it from the
Programs/Accessories/System Tools\Backup

 

[John John]

NTBackup never worked with anything including NT. It is an outdated,
antiquated, useless utility that never worked with anything. Get some
real backup software. Unfortunately Symantec has bought Veritas...
another one bites the dust. Find the last Veritas Release, get a
license and archive it, I have a feeling it will be hard to replace
after Symantec screws it right up! If you can afford to have Server
2003 you can afford quality backup software.

JOhn

 

[Pegasus \(MVP\)]

I'm glad you're sharing your knowledge with us. I now have to
find out what I did wrong on the dozen or so sites where ntbackup
has been working flawlessly for several years.

 

[Eugene Taylor]

Do you get an error like command not found or anything or does it just not
bring up the gui?
"Junior Network Administrator"

 

[abram]

Check the Task Manager to see if ntbackup.exe is running once you
started it. If so, and you can't see it on the screen, there might be
something wrong with your CD/DVD, tape or HDD drives. Make sure they
are all accessible. Let NTBackup run for 10 mins or so - sometimes,
when it can't access say a CDROM, it shows up after a timeout.

 

[John John]

Windows NT Backup Software
http://www.microsoft.com/technet/archive/winntas/maintain/backup.mspx

John

 

[Pegasus \(MVP\)]

The article you quote lists a number of well-known limitations of
ntbackup.exe. Some of them no longer apply under Win2000
(e.g. "The GUI cannot be used for scheduled backups" - it can!).
The article does not in the least support your sweeping claim
"NTBackup never worked with anything including NT."

 

[Enkidu]

Still NTBACKUP does not start in Windows 2003 Server. I tried the command
line, by typing NTBACKUP and selecting it from the
Programs/Accessories/System Tools\Backup

Abram suggests that you check if a prior ntbackup is still running.
This is good advice, and more than once I've had cases where a
previous scheduled ntbackup has failed (for instance by running out of
tape) and held up subsequent ntbackups. If it had been running
interactively, it would have popped up a message and you could have
responded to the message. If it is scheduled and disconnect from a
console, it can't popup a message. At least that's my guess.

I have had several failed NtBackups showing up in Task Manager. Some
could not be killed through the Task Manager but could be removed by
the "kill" program from the Resource Kit.

I'm not sure from your description in this and other threads if this
is the cause of your problem. However it is easily checked!

Cheers,

Cliff

 

[abram]

The article is at least 6 years old. It just doesn't apply to 2k and
later.