Stuart-

Didn't see an answer to your question posted on the list.   If there was,
my apologies.

Yes, just delete the db disk vol which contains the error.  The mirrored
dbvol will become the primary.  You can then OS delete the old db.vol file
and then run a DSMFMT to create/format it again.   Then just add it back
as a DBC volume and it will begin to resync.   If you have naming
conventions like I do (db.volx  versus dbm.volx) just go through the
process a second time after the first resync completes and you'll be back
to your original config.

That said, I'd first make sure there were no hardware errors which caused
the situation to begin with.

Regards,
Al




"Ward, Stuart" <Wards AT BMCMASK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/24/03 04:14 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Old Version ADSM Database problem


*smers - (apologies if this comes through twice - rejected first time)

Company is still running ADSM 3.1

I have seen a single page error in their database.  It has an ADSM
mirrored
volume, so is able to read from that.

Do I have to break and then recreate the ADSM mirror to fix this from the
good volume or is there a command line prompt to let ADSM fix the
erroneous
mirrored volume itself?

Any help is appreciated.

Stu



Confidentiality Notice:  The information contained in this e-mail and any
attachments may be legally privileged and confidential.  If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this e-mail is strictly prohibited.  If you
have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately.  You should not retain,
copy or use this e-mail or any attachment for any purpose, nor disclose
all
or any part of the contents to any other person.