Maybe you already saw this video from a company has bean just bean acquired by Google.
both video and acquisition happen yesterday. interesting work this company is doing: “maintains an open database of things in the world”.
see the video
http://googleblog.blogspot.com/2010/07/deeper-understanding-with-metaweb.html
http://www.metaweb.com/
lool interesting observations about team building and project management..
…or simply about spaghetti and marshmallow
Marshmallow Challenge
..
Hay,
So I was working on Exchange 20210 and I thought of sharing this with you. As you all know Exchang 2010 comes with new database availability feature called “Database Availability Group” or DAG.This Clustering feature allow creating database copies across servers, data centers, or even across countries. DAG works as replication boundary for databases and it works per membership
. if a server is member of a DAG it can create and get copies of databases in the DAG when needed (you can specify which database or databases).

If you are working with Exchange 2010 and try to create Database Availability Group (DAG), then u may have come across this weird error message that does not tell you anything when you try to join the first node in the DAG. Ok, let’s recap a lab scenario:
- You installed 2 exchange servers.
- You already successful on creating the DAG.
- When u try to add the first node this error come up:
” A server-side database availability group administrator operation failed. Error: The operation failed with message: Error 0×6f7 (The stub received bad data) from cli_RpccCreateCluster
Error 0×6f7 (The stub received bad data) from cli_RpccCreateCluster
Warning:
The operation wasn’t successful because an error was encountered. You may find more details in log file
“C:\ExchangeSetupLogs\DagTasks\dagtask_XXXXXXXXXXXXXXXXXXX_add-databaseavailabilitygroupserver.log”

The solution: it is a small thing you missed actually. Just adding the default gateway on NIC will solve it. The second server I added was smooth I didn’t have to add the gateway!
The reason is that it seems the DAG creation is not complete (specifically the cluster related resources and configuration) until the first node is created.
I hope that was informative for you.
More Resources: