694 votes
Enable backups
We need the ability to do backups. Just simple, standard backup files that we could create and download at the very least. It doesn't have to go directly blob storage or all these other suggestions. But we really, really need backups to use SQL Azure for production. Not data sync, not bcp, no... more
Status:
started
We have started delivering on this and the first step, Database Copy, was just enable in SU4. This feature satisfies a large portion of backup scearios and provides online access to those copies.
Roopesh Shenoy
Yeah, but it is a big change of mindset compared to how backups were handled earlier. Also we need backups to protect against user mistakes, data corruption due to application bugs, just a revert option that gives dbas a peace of mind :). Creating a new azure database everytime we want a backup is just not an option.
CuriousGeorge
This is an awesome first step. Thank you SQL Azure team! The next obvious step would be to allow a true backup to blob storage. Then, taking that a step further it would fantabulous if those backups could then be restored to SQL Azure OR a local SQL Server.
Bruno Alves
Backup/Restore and Blob fields would be extremely appreciated too.
Joannes Vermorel
Snapshotting/Restore toward/from the Blob Storage would be extremely appreciated.
William
Deploying a new application to Amazon's EC2 and was considering SQL Azure until I found out there were no easy backups. I really want the scalability and managed environment of a cloud solution but this was a deal breaker. Now we're going to run MySQL - despite the fact we have to workaround some features it lacks - and Microsoft will get none of our money. I can't believe MS expects this to be any sort of real production solution without backups.
dan
My clients all get a "yesterday.theirDomain.com" for their online systems. It simply points at a restored version of yesterday's backup. People log into it all the time to compare records or fix their own problems. On occassion I've messed up and had to go there myself. There is NO WAY i can put the clients who expect this service on Azure unless I can do this same thing. It is SO easy to do on my own machines, it is fully automated, it saves me phone calls, and I bill substantially for th... more
My clients all get a "yesterday.theirDomain.com" for their online systems. It simply points at a restored version of yesterday's backup. People log into it all the time to compare records or fix their own problems. On occassion I've messed up and had to go there myself. There is NO WAY i can put the clients who expect this service on Azure unless I can do this same thing. It is SO easy to do on my own machines, it is fully automated, it saves me phone calls, and I bill substantially for the service.
For now, I've got one little client running one little DB on Azure. It seems fine. If we can get backup-restore running, I'll push more over. I've got 10 servers ready for the scrap heap. Let's get this done!
kitterman
Wow, this is so critical. Nothing makes me more nervous than applying schema change scripts to production DB without a "quickly restorable" backup.
Dario Solera
There is an important reason for having access to a full database image: test migrations and upgrades on real-world data.
Simon Francesco
Could this also allow for an attach from Blob storage. This would ease the migration path.
Simon Francesco
This would also be a useful migration path, where by on-site dbs could be backed up to Azure Storage, then it would be trivial to attach or restore the db for a fully hosted option.
I can imagine offering our clients this 'off-site' backup service and then offer them a taste of cloud services by offering remote reporting etc.