Backup Solution for DocumentDB
It seems that there is no backup for DocumentDB. You should provide a backup solution for DocumentDB.
Two automatic backups are retained for 8 hour. Please see more here
Heard this recently:
Backup Interval can be anything >=60 minutes. Default is 4 hours.
Backup retention can be anything <=720 hours. Default is 8 hours.
Backup Copies must be >=25. Combination of above two options must be less than 25.
To change the defaults, open a call with Microsoft Support via the Azure Portal.
Cost of additional backups, Free, as long as within limits above.
For Cosmos DB restores, when opening a support request, include the exact time for the restore point in UTC. Seems that there is some sort of PointInTime functionality in the restores now.
All of the above requires a Microsoft Support request to complete.
Connor Dickson commented
Would it be possible to have a backup solution similar to SQL? Where we have a PITR or a backup retention policy (weekly/monthly/yearly)?
Greg Turner commented
Please explain why we as users cannot retain the automatic backups for how ever long we want like we can with Sql Server. After all, we are paying for the storage. Using data migration tool is silly since the backups are already sitting there.
This is not acceptable for a serious use case. My partner calls and says they accidentally deleted/updated data yesterday so i have to tell them that they should have called me 7 hours ago? no way.....
The doc say only last backups are retained. So, if we take backup at t-4 and t-8 interval what happens to older t-12 and t-16 ? are they deleted. What if we wanted to restore from older backup ?
We need point-in-time restore to consider Cosmos DB as a serious contender for a few big clients we have.
We would like to use Cosmos DB in our customers' solutions, but the lack of an equivalent to Azure SQL's point-in-time restore is preventing us from doing so. Unfortunately, until Cosmos DB gets this feature we cannot include it in production solutions.
Our current hourly snapshots using the Data Migration Tool take 40 minutes to save a 6GB DB and heavily consume our RU/s - seems like giving open access to configurable snapshots to the subscription admins would be a huge win. SQL Azure has this backup/restore strategy down already - hope we can get this into cosmos soon! Not sure we can keep 1 hr RPO for much longer as our database is growing rather quickly.
8 hours of RPO is really not enough.. this should be at least a week
Is there any update as to when backup and restore will be available from inside the portal?
Tom Makin commented
Backup via the portal would be a huge win for us. Currently we have had to roll our own solution as the support plans are prohibitively expensive. Data factory is good option for backup but less convenient for restore.
Isaac McNaughton commented
Is there any plan to increase the frequency of backups. The current process of every 4 hours is still much too limiting as it really only gives 2 restore points within an 8 hour business day.
Some customers (and I'm working with one for last 6 months on a long Azure First project) are adamant to have an RPO of 15 minutes. Which is only possible if we back collections up every 15 minutes. Would this feature be ever available, without having to resort to double write or some other custom implementation pattern.
This has been fixed - on Sep 23 2016. We take continuous backups, and you can call us to restore. We will continue to improve the functionality based on feedback. https://azure.microsoft.com/en-us/documentation/articles/documentdb-online-backup-and-restore/
Status was changed to planned on 20 May 2015, over a year passed, no updates?
Also a easy way to clone a partition and all its data (Replicas)
Oscar Elfving commented
This needs to get done. The data factory pipeline isn't cutting it.
Very essential. There are many scenarios. that a application is in complete shutdown mode for major part of a year is only launched for one or two months. Season application need backup and restore so as to create the database at a latter point of time
We really need a backup solution in order to use DocumentDB for production.
Tuukka Haapaniemi commented
This is a deal breaker for us. We have to have a backup of the customers data, to whom we provide software as a service. If that cannot be done with DocumentDB, then we'll be forced to switch to other options, such as RavenHQ.