Problem w/ NTBackup via LAN (2003 SBS)

[mmanna]

Hi, I've encountered a really strange issue w/ NTBackup and would appreciate any help or insight that anyone can offer. I've spent days Googling and trying different things but can't seem to find a solution!

Computer is an HP Proliant M3 server w/ Win 2003 SBS Server w/ SP2.

I am trying to use NTBackup to backup over the network to a WD MyBookWorld 1TB (which supports gigabit networking). I also installed a Cisco 8 Port Gigabit network switch and verified that the server's NIC supports and is running at Gigabit speed.

I've been doing all of my troubleshooting remotely, so everything that I describe below has been done via a terminal services session.

If I open ntbackup and use the backup wizard to manually run a full backup to the backup drive via its UNC path, it works great (resulting in a 50gb backup file). I read somewhere that backup via a UNC path is better than via a mapped network drive.

When I schedule an identical full backup via the same UNC path, it will not complete. The task is being scheduled to run as Administrator. The ntbackup log reports things such as:

Error: The device reported an error on a request to write data to media.
Error reported: Unknown error.
There may be a hardware or media problem.
Please check the system event log for relevant failures.

and

Error: C: is not a valid drive, or you do not have access.

Also, the event log shows:
5:00:00pm ntbackup "Begin Operation"
5:01:14pm ESENT "wins (2944) Shadow Copy 13 freeze started"
5:01:17pm ESENT "wins (2944) Shadow Copy 13 freeze stopped"
5:03:44pm ntbackup "Begin Backup of C:"
5:18:23pm ntbackup "End Backup of C: Warnings or errors were encountered"
5:18:24pm ntbackup "End Backup of C: Warnings or errors were encountered"
5:18:26pm ntbackup "End Operation: Warnings or errors were encountered"
5:18:28pm UserEnv "Windows cannot unload your classes registry file - it is still in use by other applications or services"


The resulting file size from the failed backup always seems to be in the ballpark of 1.3gb.

When schedule an incremental backup to run, it completes without errors (and is typically 3 to 4gb).

After many hours of googling, I've tried several things:
- Changed from a mapped network drive to a UNC path (made no difference)
- Added "Administrator" to the "Backup Operators" group. (made no difference).
- Disabled "Shadow Copies" for drives C & D (via the drive properties' "Shadow Copies" tab.)
- Verified that the server has latest service pack (SP2)
- Reviewed various MS KB's, none of which seem relevant.

I am really stumped here as things just don't seem to add up.

What's different between running backup manually and via scheduled task? Either way, the task is being run as Administrator.

Based on the fact that backup completes manually without a problem, I do not believe this is a network issue or a problem with the destination drive. However, the scheduled Incremental backups complete without error and have been scheduled the same way as the Full backups, so what gives?

I appreciate any suggestions or help you may have. I've attached a sample NTBackup Log file.
Thanks,
Marc

 

[14049752]

Hmmm...this is a complete shot in the dark, but how are the credentials set up on the WD drive? Can you add a user called "Administrator" with the same password?

The only thing I know that's similar to that, I had a backup job that failed when scheduled because the app didn't have network access. Since you're running as administrator, that shouldn't be a problem.

 

[mmanna]

I've already got the share permissions on the WD drive set up to match the administrator username and password on the server.

Besides, running it manually works fine, and scheduling the incremental works fine. It just won't run a scheduled full (normal) backup.

I really think it's got something to do with Shadow Copy or VSS or something, which I know very little about.

Even though I've turned off Shadow Copies on the local drives, the backup task still says it has shadow copying enabled and the checkbox to turn it off is grayed out.

Any more ideas?

Thanks,
Marc

 

[seedubya]

Not what you're looking for really, but if you download and install the 30 day trial of Backup Assist, it will interface with NTBackup and run the backups for you. Brilliant program. Since I found it a couple of years ago I have not installed or used any other program. It's not expensive either. www.backupassist.com

 

[mmanna]

Good news! (Well, from a diagnostic standpoint). I just tried another manual full backup, and it failed with the same error. So, at least that eliminates that one point of confusion. (Screenshot and backup log attached).

 

[anonymous Mac Tech]

I do not believe this is a network issue or a problem with the destination drive.

What about the source drive? Have you ran any checks on that?

 

[mmanna]

Hey guys, thanks for the continued ideas and efforts.

I know that the source (system) drive was fine last time I ran chkdsk/f in May. I have just run chkdsk/f again to make sure it's okay. It reported 705 index entries corrected and no bad sectors. I have just started another manual full backup and will let you know the outcome later on.

Thanks again,

Marc

 

[mmanna]

Sorry I didn't get a chance to check back in yesterday, but even after running chkdsk, the ntbackup full manual backup still failed again with the same error(s). I just thought of something else to try to narrow it down and will let you know the result later. I am doing a full manual backup of the "c" drive (approx 9gb) to a bkf file on the "D" drive which is a local partition with enough free space. If that works successfully, I will try to drag & drop the 9gb file to the network drive and see if it can copy it. Of course if it can't even finish the backup locally, then I'll know the problem isn't with the network or destination drive.

 

[Doctor Micro]

Your WD External drive isn't formatted FAT32 by any chance, is it?

 

[mmanna]

I just verified that the MyBooks is NTFS.

Yesterday's manual backup from drive "C" to "D" (both internal/local) completed successfully. I am now copying the bkf file from D: to X: (X is mapped drive to MyBook) via drag and drop and it failed saying "cannot copy (filename): The specified network name is no longer available"

Thanks to all for your ongoing efforts! Any more suggestions or ideas?

For what it's worth ... two observations:

I noted that when I went to properties on the "X" drive (mapped network drive to the MyBook) it said it's using DFS. I've never knowingly configured or used DFS, so I believe this was automatic or configured by the WD installation.

The server is running SEPM and SEP (11.0.4202.75). Has anyone noted any problems with SEP and ntbackup or gigabit-speed network transfers?

 

[mmanna]

I disabled "network threat protection" in SEP (even though it's logs don't show that it blocked anything) and re-tried copying the 7gb manual bkf file from D: to X: and it worked. I am not re-trying a manual full backup via the ntbackup wizard to X: (mybook) and will report back later.

 

[mmanna]

The manual backup I started on Friday (with SEP disabled) completed successfully. It looks like SEP might be the problem. I'm not 100% convinced yet as I was able to complete manual full backups a couple of other times without problems, so the real test will be tonight when the scheduled full backup runs. I will let you know tomorrow!