Skip to main content

Automated Backup - Windows Azure Web Sites

By
We have a new feature available for Windows Azure Web Sites – we can create backups automatically of our site and database that can be used later on.
To be able to use this feature, you will need to change the web site mode from free to standard. Only for standard web sites this feature is available. When you are in the standard mode you have multiple instance sizes and you can scale your site automatically.
From the cost perspective you should know that there are no additional cost to it (automatically backup feature). You only pay the space used by the backup on the storage. This is a nice think, we have another nice service that is free.
When we activate the automated backup feature we will need to specify the storage account where we want to make the backup and what is the frequency. In this moment we can specify only in days the frequency, but I don’t see this a real problem. In normal cases, you don’t want to make a backup every 5 minutes. Beside this, you can specify the time when the backup is made. In general we prefer to make the backup during the night, but based on your client location, night can mean 03:00 UTC or 14:00 UTC.
A nice feature available is the ability to include not only the site but the database that is used by your site. In general, the most important information can be found in the database. This is the place where data is changing very offer and you don’t want to lose it.
Any database that is linked to your site can be backup. What is nice is that you can create a backup for not only SQL but also for MySQL.
Once you configure all this, the last thing that you need to do is to hit “Save” button. And wait, we have something more. You can trigger the backup manually. To use manual backup feature you don’t need to activate the automated backup, you only need to configure what is backup and where.
The most complicated step is the restoring (or not). From the same tab we can navigate to the restore action that give us the ability to restore the web site and database from our storage account or from a file that is on another storage account.
I would recommend this feature especially for the database backup and how easily you can restore your web site. Please be aware, don’t use this feature if you write in the web site directory pictures or data uploaded by the clients. In this case you should store the data directly to Windows Azure Storage Blobs.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more