Wrong host show up in Storage Scope Device Allocation Report

Hi Allen, Thanks a lot for the quick reply and for your time...

Well none of these hosts are boot from Sans. There are many hosts that have this problem, let me give you an example by taking one host NYABC whose DR server is NJABC. The R2 devices on NJABC show NYABC as their host name . I have also observed that in some cases even the non replicated devices do the same, ie., instead of showing the host name, display the name of the replicated host.
In this example the hosts are Solaris 2.8.
This is all I knew about these hosts as I am myself new to this environment and trying to getting accustomed to it. If there is anything in particular that you need , please let me know so that I can gather the required information.

Thanks again.

Message was edited by:
ajitnayak

Hmmm... another possibility since these aren't boot from SAN is that the ECC Master Agent got installed on a replicated file system. That would possibly account for it.

Give me a minute to dig up the files you would be looking for on a solaris host.

Is your host booting from SAN and your DR host doing the same off replicated devices? Or are you rebuilding the DR host from replicated info?

If so, this is an issue that we have run into in which ECC gets confused about the identity of a host that is using replicated data. ECC recognizes a host from it's registration with the server, and it stores some files on the local host pertaining to that identity. If you copy those files to a different host with the ECC Agent on it and start the agent, ECC will think the new host is the old one.

This can get rather confusing. You can also run into this if you clone a host image (using something like Ghost) and it picks up these registration files.

In you case (and lacking any additional detail) I kind of suspect that the times SS picked up data from your DR host was when that host was active on the network.

If you can confirm any of this I'll dig up the details of where those registration files are located so you can try to deal with them. If you could also provide some info on the Host OS, and anything more around this occurrence that you might think appropriate we'll see if we can come up with another possible answer.

BTW - Welcome to the Forums!

I'm having some trouble with the Knowledgebase Search right now. I'll keep trying, but if anyone else happens to know this one off the top of your head, please feel free to jump in.

Sure... in the mean while, I will try to gather as much information as possible. I just took one example randomly, I will have to check on what other hosts this is happening on!