Invalid Replica

Hey Drozz

When a snapshot replica becomes invalid, it normally means that after the snapshot job is completed and the next scheduled array discovery runs, RM has discovered that either
it could not find the snapshot (array discovery fails for some reason)
or
the snapshot is not in the expected state, ie prehaps has been lost or reclaimed due to lack of free space in the reserved lun pool snapshot.

Does the replica become invalid some time after it is ran?
Is it for all snapshot jobs or for just some or even 1?
What is the number of replicas you are keeping?

Cheers
James.

Hello James! Hope all is well,

It was happening to my SQL SnapShots. I just added my Exchange environment to the rotation and now the SQL environment seems fine but a file server and the Exchange SG and logs are now becoming invalid.

It happens some time after the successfull job runs, it reports this every 6 hours..ie I get invalid replica emails

I am keeping 2 SnapShots of everything except the SQL database which I keep 3 SnapShots

I have 1 TB of 10GB LUNs in my RLP and 30 LUNs are currently free

I get 3 logs emailed to me for the 1 invalid replica and they are all the same session. The session is missing in Navisphere but it seems the SnapShot itself is still there.

Thanks

Hi Drozz,

Have you been able to clear the "stray" Snapshot Names without valid Sessions?
-- See emc160233
(Was this the primus you referenced earlier? )

Is there anything in the Array event logs that would indicate why this is occuring?
You might need to open an SR on this, supply the sp_collects and emcreports.

Regards,
Alan

Hello Alan,

I have cleared the stray SnapShots and reran the sessions. You might be correct as these were sessions created before the update to SP 3. I will keep you updated to see if this does the trick

Thanks,
DR

Had to delete the pre SP 3 SnapShots and have not recieved the error going forward.

Thanks to All!