This means there has been a problem with the SRL so it is no longer been used - see extract from VVR admin guide:

RVG PASSTHRU mode

Typically, writes to data volumes associated with an RVG go to the RVG’s SRL

first, and then to the RLINKs and data volumes. If the Primary SRL is ever detached

because of an access error, then the Primary RVG is put into PASSTHRU mode.

In PASSTHRU mode, writes to the data volume are passed directly to the

underlying data volume, bypassing the SRL. No RLINKs receive the writes. Use

vxprint -l on the RVG to see if the passthru flag is set. Associating a new SRL

will clear PASSTHRU mode, and the Secondary node RVGs must be synchronized.

vxvol -g DiskGroup aslog home-rvg home-srl

vxvol -g DiskGroup start home-srl

$ sudo vxvol -g sourcesafe aslog home-rvg home-srl
VxVM VVR vxvol ERROR V-5-1-3671 Volume home-srl is already associated with rvg home-rvg
 

Hmm so its means that we manually diassociated the SRL from RVG and associated again.

This resolved my problem. But the question is why its going in passthru mode. I faced this twice in last two working days. Does the life completed of DISK on which SRL is created.

This normally indicates there is a problem with the LUN(s) the SRL is on - have you checked system logs and for any errors on the array it is coming from or FC switches.

Don't know what "Does the life completed of DISK on which SRL is created" means - could you rephrase.

Mike

... so you're asking if the disk where the SRL has been created has reached the end of its life?

ie: when you've said this:

DIsk on which the SRL is created has completed its(DIsk) life. OR the Disk on which SRL exist is about to dead

you mean:

Has the disk on which the SRL has been created reached the end of its life; or is the disk on which the SRL is located about to die?

Note the question mark, indicating you are asking a question rather than making a statement.

As Mike said, passthru mode usually indicates there is a problem with the underlying disk for the SRL, the exact nature of the disk problem varies depending on your environment, so per Mike's suggestion ...

have you checked system logs and for any errors on the array it is coming from or FC switches

... ?

Thanks all for kind replies. one more question here. If the Replication is under Cluster. Detaching the SRL volume may cause any fault occurance at hagui ?

VCS monitors the RVG, not the SRL and if the SRL get detached because you have disk errors, then I think the RVG state (as in started and stopped, not PASSTHRU) does not change but if you tried to you to detach the SRL manually, you may have to stop RVG first to allow you to detach the SRL.

Mike

Doesnt SRL is the part of RVG ? when we see vxprint the SRL show in the rv session? (correct me if I am wrong)

So I have to mark the RVG resource as un critical from hagui, So that the cluster does not declare any fault which lead to Failover which I dont want at this time in my case.

Did the RVG resource show as offline when RVG was in PASSTHRU mode - I don't think it would of, because it was still started and RVG should only show offline if stopped - so this being the case you don't need to mark RVG as non-critical, but if you were to manually detach SRL, then I would freeze replication service group first.

Mike

Definitily we need to manually detach SRL in my case ?

Would you kindly share the steps what should I do in my case. As I feel I have to do the following things

• Freeze the Replication Service Group
• Stop RVG
• diassoc SRL volume                           (vxvol -g DiskGroup dis SRLname)
• detach the SRL volume
• Remove that SRL volume
• Create a new Volume on new fresh disk
• assoc this new SRL volume in the RVG (vxvol -g DiskGroup aslog RVGname SRLname)
• start RVG
• unfreeze Replication Service Group

This looks ok, except disassociated and detached seems to be used interchangably in the documentation, but they are one in the same for an SRL, so disassoc and detach SRL is one step.

Mike

So you mean that diassoc and detach is a single operation ?

• Freeze the Replication Service Group
• Stop RVG
• diassoc/Detach SRL volume                           (vxvol -g DiskGroup dis SRLname)
• Remove that SRL volume
• Create a new Volume on new fresh disk
• assoc/attach this new SRL volume in the RVG (vxvol -g DiskGroup aslog RVGname SRLname)
• start RVG
• unfreeze Replication Service Group

Thanks Mike for kind support. ALready given +thumb and marked your post solution :)