Index locking fix - in order to lock the writing to an index operation you have to obtain the lock explicitly
Attempt to restore index (map-only right now) from previously stored segment file.
Recovering map indexes based on stored commit points
Merge branch 'master' of git://github.com/ayende/ravendb into preventing-index-resets
For map/reduce index regenerate the entire index from already reduced results if index failure was discovered
Merge branch 'master' of git://github.com/ayende/ravendb into preventing-index-resets
Avoid nesting. Better names of commit point directories
Try to index recovery operation after we failed with CheckIndexAndTryToFix
Regenerate map/reduce index in single batch with the usage of pulsing transactions.
Adding max time interval for storing index commit points
fixing build
Storing keys that were deleted after saving commit point. This will be useful in index recovery scenario
Removing keys from recovered index
Map index recovery tests added
Fixing recovery of index deletes - avoiding problems with not fully initialized work context, making test passing
Fix an issue where the localBackupConfigs was different then the backupConfig, since it's updated on database.Put. This caused a changed to the Raven/Backup/Periodic/Setup document trigger a new backup operation in a loop.
Delete a commit point that if an index could not recover from it
Added a test that verifies the map/reduce index regeneration
Merge branch 'master' of git://github.com/ayende/ravendb into preventing-index-resets

Conflicts:
	Raven.Database/Storage/IMappedResultsStorageAction.cs
	Raven.Database/Storage/Managed/MappedResultsStorageAction.cs
Fixing serialization of etag value when using changes api to make the client to be able to deserialize it - needed to add EtagJsonConverter when sending the notification