Hi there,
Welcome to RM Forums

Firstly, as you may know RM sets the BCV devices NR as soon as you include for use in the RM GUI. This is a safety protection mechanism, to avoid un-intentional writes/corruption to the BCVs when unmounted - most especially in a Windows environment.

Windows is very chatty to unprotected BCVs it sees, even though the dev may not be mounted - Windows will still actively ping/pong the sysvol with writes...

Ok, back on track, that was for the better good of anyone considering to use the variable which I am about I discuss, in a Windows environment.

In a Unix world, as long as the DG is deported/vary'ed off, the unix host has no reason as such to decide to write to any part of the disk, it will only perform, as such SCSI inquiries on demand from host/user initiated rescans. So, not setting the BCV NR is far safer..

In order to do what you would like to do, please persistenly set and export the following variable on your AIX ** Production ** host (not your mount host)

EMC_ERM_SKIP_SYMMDEV_NR

Restart IRCCD and give it a shot.

Let us know here how it works out for you.

Best of luck
James.

Cimbom

Can you do me a favour and set the variable on the mount host also and restart IRCCD and test? Prehaps the function call to set NR has shifted since I last visited this.

Thanks

Hi James,

Thanks for your response. I tried setting that environment and restarted IRCCD however, I still see the same error messages.

I typed "export EMC_ERM_SKIP_SYMMDEV_NR" and restarted IRCCD. Did I set it wrong?

Here's a sample error message:
-------------------------------------------
Description
DISK OPERATION ERROR

Probable Causes
DASD DEVICE

Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
PATH ID
0
SENSE DATA
0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0102 0000 7000 0200
0000 000A 0000 0000 0403 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 00D2 0001 AB80 0000 0646 0000 0000 0000 0000 0000 0000 0000
0000 0012 001A

Hi James,

The source and the mount host are the same AIX client. I'm basically mounting the target devices under /BCV/xxxx file systems on the same host.

Also, I have tried to unmount/varyoff/export the /BCV/xxxx volume groups before the next RM job runs but the system still detects the "Not Ready" state.

Hiya - sorry for the delayed response.

I recommend you open an EMC SR and we will deal with this issue as soon as possible via the right channels.

Thanks]
James.