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

Vrepair, corrupt data, precautions?

0 views
Skip to first unread message

Linda

unread,
Jan 26, 2004, 1:16:45 PM1/26/04
to
What are precautions that should be taken before running VREPAIR?

Does VREPAIR make any changes even when it finds NO ERRORS?

Could VREPAIR cause data corruptions or lost volumes?

How do we find out what the correct version of VREPAIR is for the
configuration that we are running?
For instance NW 5.1 with SP6.

Thanks,
Linda


Marcel Cox

unread,
Jan 26, 2004, 2:43:04 PM1/26/04
to
Linda,

> What are precautions that should be taken before running VREPAIR?

VREPAIR can only repair volume that are dismounted. So you can't use it on
a life system.

> Does VREPAIR make any changes even when it finds NO ERRORS?

You can chose whether VREPAIR does only write back the changed records to
disk or everything. The first option is the default and should not cause
any disk write in case of no error.

> Could VREPAIR cause data corruptions or lost volumes?

Personally, I have never had problems with VREPAIR. I can however imagine
that if a volume is too corrupted, VREPAIR might fail and make things
worse

> How do we find out what the correct version of VREPAIR is for the
> configuration that we are running?
> For instance NW 5.1 with SP6.

Only ever use the version of VREPAIR included with your Netware/support
pack version. You should always have the correct VREPAIR.NLM automatically
in c:\nwserver.

Note that VREPAIR is not a proactive maintenance tool but really a repair
tool to repair things when they are broken. Also, when mounting a volume,
Netware does a consistency check and runs VREPAIR automatically if needed.

--
Marcel Cox
http://support.novell.com/forums/


Linda

unread,
Jan 26, 2004, 3:40:22 PM1/26/04
to
Vrepair was ran with the default options. It sounds like no harm should
have been done.

I will rule this out as a cause for the intermittent data corruptions that
we are having and trying to correct.

thanks,
Linda


"Marcel Cox" <cim...@myrealbox.com> wrote in message
news:VA.0000592...@myrealbox.com...

0 new messages