ntbackup crashes HARD

[Guest]

Howdy!

Here's the problem: i'm running xp pro sp2 and trying to back up to a
rev-disk with ntbackup. Ntbackup either crashes hard (no reaction at all from
the pc), or if it doesn't crash, the backup takes well over 16 hours for
about 30gb of data.

Just for the fun of it, i tried backing up to a temporary directory.
Ntbackup crashed again.

Thinking there must be a problem with the hard drive (a raid1 array, 2 120gb
Seagate drives), i ran chkdsk /r. Chkdsk seems to get stuck in phase 5 at
around 56%, then manages to finish but doesn't report any errors.

I'm assuming that the problem is not with the rev-drive, because i can xcopy
the 30gb in about an hour, and ntbackup seems to want to crash no matter
where i'm saving the data to.

Is this ringing a bell with anyone?

 

[Kerry Brown]

Howdy!

Here's the problem: i'm running xp pro sp2 and trying to back up to a
rev-disk with ntbackup. Ntbackup either crashes hard (no reaction at all
from
the pc), or if it doesn't crash, the backup takes well over 16 hours for
about 30gb of data.

Just for the fun of it, i tried backing up to a temporary directory.
Ntbackup crashed again.

Thinking there must be a problem with the hard drive (a raid1 array, 2
120gb
Seagate drives), i ran chkdsk /r. Chkdsk seems to get stuck in phase 5 at
around 56%, then manages to finish but doesn't report any errors.

I'm assuming that the problem is not with the rev-drive, because i can
xcopy
the 30gb in about an hour, and ntbackup seems to want to crash no matter
where i'm saving the data to.

Is this ringing a bell with anyone?

No bells ringing here. Are there any errors in the event logs? I simple
google search for "rev disk" found the following link.

http://msmvps.com/kwsupport/archive/2004/05/16/6552.aspx

Kerry

 

[Guest]

No bells ringing here. Are there any errors in the event logs? I simple
google search for "rev disk" found the following link.

http://msmvps.com/kwsupport/archive/2004/05/16/6552.aspx

Kerry

I found that site as well. There's no trouble starting the backup, its when
the pc freezes half way through that's bugging me. I backed p d: across the
network to a usb hdd attaached to my notebook (how the heck did that work?),
and i'm going to reformat d: and restore everything. I may also try the trick
with sharing the REV and then saving to the share, but that sound like more
overhead to me.

If that doesn't do the trick--

I'd rather not think about it...

 

[Kerry Brown]

I found that site as well. There's no trouble starting the backup, its
when
the pc freezes half way through that's bugging me. I backed p d: across
the
network to a usb hdd attaached to my notebook (how the heck did that
work?),
and i'm going to reformat d: and restore everything. I may also try the
trick
with sharing the REV and then saving to the share, but that sound like
more
overhead to me.

If that doesn't do the trick--

I'd rather not think about it...

From reading some of the links found via google it sounds like the problem
is with the rev disk rather than ntbackup. How is the rev disk formatted?
FAT32 only works with 4 GB files max in XP. To do larger backups you must be
using NTFS.

Kerry

 

[Guest]

From reading some of the links found via google it sounds like the problem
is with the rev disk rather than ntbackup. How is the rev disk formatted?
FAT32 only works with 4 GB files max in XP. To do larger backups you must be
using NTFS.

Kerry

The rev is formatted udf (whatever that is), and according to Iomega the
file size limitation is larger than the capacity of the rev drive (90gb at
2.6:1 compression). The problem is that ntbackup is hanging when i backup to
the hard drive as well. Of course, backing up to the drive that is being
backed up smells like trouble, although the *.bks file has this entry in it:
D:\temp\ /Exclude. Maybe ntbackup is still bummed about it. I might try
repartitioning the drive. Its not like i had plans this weekend...

 

[Kerry Brown]

The rev is formatted udf (whatever that is), and according to Iomega the
file size limitation is larger than the capacity of the rev drive (90gb at
2.6:1 compression). The problem is that ntbackup is hanging when i backup
to
the hard drive as well. Of course, backing up to the drive that is being
backed up smells like trouble, although the *.bks file has this entry in
it:
D:\temp\ /Exclude. Maybe ntbackup is still bummed about it. I might try
repartitioning the drive. Its not like i had plans this weekend...

Ntbackup doesn't like UDF. It will usually work as long as the backup fits
on one disk but the results are erratic at best. You should be able to
backup to the same drive as you are backing up. then copy the file to the
rev disk. If this doesn't work then there may be a problem with the file
structure on the drive or permissions for the user account doing the backup
or the drive doesn't have enough space. Did you get any errors in the event
logs or the ntbackup report?

Kerry

 

[Guest]

Ntbackup doesn't like UDF. It will usually work as long as the backup fits
on one disk but the results are erratic at best. You should be able to
backup to the same drive as you are backing up. then copy the file to the
rev disk. If this doesn't work then there may be a problem with the file
structure on the drive or permissions for the user account doing the backup
or the drive doesn't have enough space. Did you get any errors in the event
logs or the ntbackup report?

Kerry

I've reformatted the drive, and now i'm going to bed. I may give it one more
try this weekend, but if i can robocopy my files to the rev in less than an
hour, then that's the route i'm taking. Not pretty, but if it works...
Thanks!

 

[Kerry Brown]

I've reformatted the drive, and now i'm going to bed. I may give it one
more
try this weekend, but if i can robocopy my files to the rev in less than
an
hour, then that's the route i'm taking. Not pretty, but if it works...
Thanks!

Good luck with it. If you need more help please post if you found any errors
in the event logs or the backup report. It would be very helpful to know if
there were any errors and what the errors were if present. Personally for
data I always just copy it rather than backup if the destination is large
enough. It is quicker to restore and easy to see what got copied.

Kerry