NTBackup verify taking a very long time

[Jack B. Pollack]

I have a single computer running WinXP SP3 that backs up to a NAS device
(over ethernet) using NTBackup. The actual backup of 20GB of data is taking
around 1.5 hours. The verify is taking 12+ hours.

I was previously doing the same exact thing with my old computer and the
entire process (backup & verify) was taking around 3 hours. The entire
network configuration is identical. The only thing that has changed is the
new computer.

I have tried clean booting the system and nothing is running including any
antivirus software.

Why would the verify be taking so long?

Thanks

 

[Donald]

What is the model type of your NAS system? What is the Internet browsing
speed on your new computer? What kind of networking device are you using to
connect your computer with the NAS system?

 

[Jack B. Pollack]

The NAS systems is a Buffalo LinkStation Pro connected to a NetGear Router.
The computer is also hard-wired to the router. All have fixed IP's. Internet
speed appears to be consistent with what it was in the past (fine). I also
remote desktop to and from this computer often and the speed is fine.

The only thing that has changed is the new computer. It has a fresh install
of XP on it and I have clean booted it to rule out antivirus etc.

 

[Twayne]

I have a single computer running WinXP SP3 that backs up to a NAS
device (over ethernet) using NTBackup. The actual backup of 20GB of
data is taking around 1.5 hours. The verify is taking 12+ hours.

I was previously doing the same exact thing with my old computer and
the entire process (backup & verify) was taking around 3 hours. The
entire network configuration is identical. The only thing that has
changed is the new computer.

I have tried clean booting the system and nothing is running
including any antivirus software.

Why would the verify be taking so long?

Thanks

Wow, that's a long time! And unacceptable, of course. Have you checked
to see if the whole system is slowing down? Or looked for a bottleneck?
Are other comms along that same channel also as slow when the verify
ends (or is killed). Do the verifies always indicate OK or are they
finding problems? Perhaps the backup itself is glitching somehow.

Since it's a new computer there could be some defaults/settings in
error, but I've no idea which ones might cause that sort of thing.

Time to put on some monitors, I guess; sounds like a strange one. Is
the old machine around and untouched, to make some comparisons with?
I'm thinking about things like MTU, etc..

Good luck,

Twayne`

 

[Jack B. Pollack]

Wow, that's a long time! And unacceptable, of course. Have you checked
to see if the whole system is slowing down? Or looked for a bottleneck?
Are other comms along that same channel also as slow when the verify ends
(or is killed). Do the verifies always indicate OK or are they finding
problems? Perhaps the backup itself is glitching somehow.

Since it's a new computer there could be some defaults/settings in error,
but I've no idea which ones might cause that sort of thing.

Time to put on some monitors, I guess; sounds like a strange one. Is the
old machine around and untouched, to make some comparisons with? I'm
thinking about things like MTU, etc..

Good luck,

Twayne`

The backups run at night. In the morning when the verify is (still) running
other apps and internet appear to be fine as far as launch speed, web page
loads, etc.

I think I only let one verify go to completion but and I think it was fine
although if I used the computer at all probably files had changes since the
original BU.

The old machine is around but has hard drive hardware problems. It does boot
to if I need to check a setting etc, but is running very slowly and poorly
(cant be used for speed comparisons at this point).

I don't know how much reading if any is done from the external drive during
the BU process, but it seams to be more of a READ issue during the verify.

I just had a thought, I'm going to copy the 20GB file from the external
drive and time it. Then copy it back after renaming it. I would think that
the copy time in either direction should be roughly the same (not 1 hr to 12
hrs)

 

[Twayne]

The backups run at night. In the morning when the verify is (still)
running other apps and internet appear to be fine as far as launch
speed, web page loads, etc.

I think I only let one verify go to completion but and I think it was
fine although if I used the computer at all probably files had
changes since the original BU.

The old machine is around but has hard drive hardware problems. It
does boot to if I need to check a setting etc, but is running very
slowly and poorly (cant be used for speed comparisons at this point).

I don't know how much reading if any is done from the external drive
during the BU process, but it seams to be more of a READ issue during
the verify.
I just had a thought, I'm going to copy the 20GB file from the
external drive and time it. Then copy it back after renaming it. I
would think that the copy time in either direction should be roughly
the same (not 1 hr to 12 hrs)

That's a good idea. BTW, if you use xcopy, it has a verify switch too;
you could test it out with a smaller file to get a feel of the
operation. But you need the Command Prompt to use Xcopy of course.
Even if it verifies it though, you still won't know whether it's a
slow send from the server or a slow read at your new computer station.
Are you certain it's not malware of some sort?

http://www.windowsreference.com/win...t-the-mtu-size-in-windows-xp-2003-2000-vista/

If the MTU were way off it would wreak havoc with timing.

HTH,

Twayne`

 

[Twayne]

PS
Recommended Values

a.. 576 - Dial-up Connections
a.. 1492 - PPPoE Broadband Connections
a.. 1500 - Ethernet, DSL and Cable Broadband Connections
Restart Windows for the change to take effect.

 

[Jack B. Pollack]

Thanks. Playing with MTU settings didn't help.

Copying the file 20GB file is very slooooow. I'm going to try a different
hub.