| 10:03 am on May 25, 2007 (gmt 0)|
My response... leave it, Google will automatically filter out one set and it won't hurt nor harm you.
Forum's response (wait for it) .... this is a terrible thing, 301 redirect one to the other, you will get banned and thrown out into the supplemental index for ever and ever.
| 10:15 am on May 25, 2007 (gmt 0)|
thanx for ur reply.....tht i knew....m asking for some concrete solution...
coz we had hosted website on other server to fetch information when one is down.......
i thing re-direction will not work.....want something from server end....plz...do suggest
| 10:17 am on May 25, 2007 (gmt 0)|
I sincerely suggest that you handle it as a DNS solution. You should have the same hostname set up for both sites, and have your DNS with another server or a third party. If the primary site goes down, then make a change to your DNS to send it to the secondary site. Read up on 'round robin DNS' - it's more complex but more reliable.
| 10:40 am on May 25, 2007 (gmt 0)|
thanx vince.......this one sound's gr8!
| 5:19 pm on May 25, 2007 (gmt 0)|
Actually, round-robin DNS is not a solution to this, though it's a closely-related concept. Round-robin DNS is a simple load-balancing solution.
You want a DNS failover service. This will monitor your primary site, and if it goes down, will switch the DNS to point to the secondary site. When the primary site goes back up, it will switch back.