Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

All restored files are 32 Kb or smaller.

Status
Not open for further replies.

mikkopel

Technical User
Feb 14, 2005
7
0
0
US
I'm having trouble restoring files with
Arcserve 2000. I'm running it on a Win2k
server, with a Seagate Travan tape drive.

Everything goes fine, backup shows no
errors, and even restore (file) shows
no errors.

But when I go look at the restored file,
it is only 32 Kb. Every file that is
restored, that is bigger than 32 Kb
ends up being that. Smaller files seem
fine.

It's baffling, since even when restoring
it, the file size counter shows the
right file size, and bytes processed...

Any ideas?
 
Ok, I will take a look at the updates. The
restore and the back up were done on the same
system, though I tried the restore also on
another system, with same results. Although
with the same tape drive.

No agent was used, and like I said everything
looks fine, file sizes, everything, up
until after the restore.

For example, I just tried to restore a whole
session on one sitting, instead of one file.
And I get this in the Activity Log:
14.02.05 18:31:59 1 600 Directories 33 426 Files (1 378,48 MB) Restored to Disk
14.02.05 18:31:59 1 880,75 MB Read from Media

I guess the 880,75 MB is the amount of data after compression. Anyway, when I look at the
drive, the total amount of data is only 253 MB.

It took about 16 minutes, if that's any clue
to the real amount of data transferred. At
stated 83,88 MB/min it seems about right.

And I've tried this on a NTFS and FAT32 partition, but that didn't make a difference.
 
Now I tried backup-restore on the same
computer, except I replaced the tape drive
and tape.

And the result is still the same... I was
pretty sure it would've been a bad drive,
but I guess not.
 
Ok, thanks for the help. I think the SP
downloaded from CA did the trick. But
I still can't understand why all this
happened...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top