Unsolved
This post is more than 5 years old
1 Rookie
•
33 Posts
0
450
September 11th, 2008 08:00
Invalid Replica Warning, should I be worried?
After having successfully replicated three luns and my Oracle database to my second Clariion I moved the target luns from the storage groups "EMC Replication Storage" and "EMC RM SANCopy SG" to the storage group for my server "oracle1". RM then gives me "ERROR 000526" for each of the replicated luns.
What procedure should I follow if I don't want Replication Manager to do the mounting?
1. Ignore the warning and just move the replicated luns to the host's storage group?
2. Do I have to do a SANCopy to additional luns from my target luns?
My goal is to simply have a replicated copy of my Oracle server on my second CX3 at my secondary site. Then, when disaster strikes, mount the replicated copy on a server at the secondary site. My Oracle server is running Linux and I don't want to use auto-mount.
Thanks
What procedure should I follow if I don't want Replication Manager to do the mounting?
1. Ignore the warning and just move the replicated luns to the host's storage group?
2. Do I have to do a SANCopy to additional luns from my target luns?
My goal is to simply have a replicated copy of my Oracle server on my second CX3 at my secondary site. Then, when disaster strikes, mount the replicated copy on a server at the secondary site. My Oracle server is running Linux and I don't want to use auto-mount.
Thanks
0 events found
No Events found!
AranH1
2.2K Posts
1
September 11th, 2008 12:00
If you are talking about a true DR scenario where your primary array is down then add the replica LUNs into the mount host storage group without removing them from the RM storage group. Just make sure that the schedule for the SANCopy job is disabled while the mount host is accessing the replicas so that RM does not try to perform a synchronization while the mount host is accessing the replicas.
You can even script the process so that in a DR situation you just run a script to add the SANCopy clones into the mount host storage group.
Pasta_Fazole
1 Rookie
•
33 Posts
0
September 11th, 2008 13:00
Rob
JamesBEMC
257 Posts
0
September 12th, 2008 00:00
The reason you got the invalidated replica, is that periodically, RM performs storage discovery and ensures that its available storage is still there and also replica LUNs should be where they are...
So, you moved the replica luns from the storage group RM had them in and so, it declares that those luns have gone "missing" and invalidates the replica. This does affect restoreability. Even if you put the luns back in, RM wont re-valildate the replica because it cannot guarentee someone has not modified the data unknown to RM.
Cheers
James.