After copying DB files, documents not addressable by ID

[Keith Brown]

We just got a major surprise during a data center migration. We shut down Raven (build 701) on the old server, copied the files to the new server, and started up the same version of Raven on the new server. The studio came up just fine, and our collection list looked correct, but when we tried to look up some documents by their ID, they failed to come up.

We've written some code to traverse the entire collection (using DatabaseCommands.StartsWith) and we can see that all of the documents are there. However, we simply cannot look them up by ID (we're not even trying to use an index).

We're now smuggling data out of the old instance as a plan B, but that's going to take an awful log longer than we'd anticipated.

Any ideas on what we can do to make Raven serve up those documents by ID? Our website (pluralsight.com) is down while we work on this :-/

[Itamar Syn-Hershko]

Just copying the data folder betwren machines is not supported. Smuggling is the way to go

[Itamar Syn-Hershko]

Smuggling locally is much faster, btw

[Keith Brown]

 Thanks for the clarification. We've never had a problem copying the folder over in the past (it seemed to work just fine the other day when we tested). Guess we've just been lucky so far.

Keith

[Oren Eini (Ayende Rahien)]

The actual reason for the issue is that the two machines have different sort orders.

Newer versions of RavenDB will check for that and error when they see this.

You can resolve this issue by running:

 esentutl -d Data 

Inside the RavenDB data folder.

[Chris Marisic]

Make sure the raven server / iis app if asp.net hosted is entirely off.