Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Stumped

1 view
Skip to first unread message

bill.b...@revest.com

unread,
Nov 11, 2003, 7:42:07 AM11/11/03
to
Recently our backup job has gotten hung up on one of our Storage volumes.
We use Arcserve and all has been working fine for years. Within the past
month or so, one of the volumes has been taking 5 hours just for Arcserve
to recognize/read? this volume. After the five hour period, it begins to
backup. Of course by that time, people are starting to get into the system
and chaos takes place. I have dismounted this volume, ran VRepair several
times until zero errors came up, remounted and still the problem exists.
Anyone have any other ideas as to what the problem might be?

Dave Lunn

unread,
Nov 11, 2003, 9:11:44 AM11/11/03
to
I would be first concerned that the drive is going belly up. If it happens
repeatedly that you need to run VRepair and you keep showing errors Get the
data to a secure drive ASAP.
--
Dave Lunn
NSF SysOp
http://support.novell.com


bill.b...@revest.com

unread,
Nov 11, 2003, 1:54:31 PM11/11/03
to
If it were hardware, why would just one volume have an issue? There are 3
volumes on the RAID 5 array.

Dave Lunn

unread,
Nov 11, 2003, 2:31:16 PM11/11/03
to
> If it were hardware, why would just one volume have an issue? There are 3
> volumes on the RAID 5 array.

It might not be much data. Look at your redirected blocks, and if they are
going up look for a new drive.

Barry St.John

unread,
Nov 12, 2003, 12:18:26 PM11/12/03
to
I'm not as convinced as Dave that this is indicative of a hardware
problem, though he could be right. I'm more inclined to think there's
a volume problem that is beyond VREPAIR's ability to correct.

If you have space on the other volumes to accommodate it, try migrating
data off that volume so you can delete and re-create it, then move the
data back. If you don't have space available on the other volumes,
then tape is your only choice. Make a backup and verify it (do a test
restore to be sure) before you delete the volume.

One other thought: If compression is enabled for that volume and your
compression algorithms are scheduled to run concurrent with your
backup, that can be a problem.

--

-Barry. [Novell Support Forums SysOp]


0 new messages