Skip to main content

Azure Backup (Day 29 of 31)

List of all posts from this series:

Short Description 
How nice would be a feature that allow us to create automatically backups of our system and store them in a reliable location from where we can restore it when needed. This is called Azure Backup and can be used with success to create backups of our systems.

Main Features 
Operation System Supported
In the current version (in preview) we can create backups for Windows 8.1, Windows 8 and Windows 7 (64b with SP1).
Using management tools we can specify users that have access to this backups. In this way only authorized users can access the backup content.
Management Tool
We can manage the backups using different tools from Windows Server 2012, Windows Server 2012 essential or System Center 2012. For all of this, we are using DPM (Data Protection Manager) to manage the backups. The cloud storage that is used to create the backup itself can be seen like a local disk.
The current SLA for Azure Backup is 99.9% availability. For backup storage, I would say that this is more than enough for normal use cases.
Geo-Replication of backups
Because the storage that is used for backups is part of Azure Storage we have different features inherited from Azure Storage like geo-replication features. This mean that our backups will exist in more than one data center.
This mean that your backup is replicated in 2 different datacenters, having 6 different copies.
Incremental Backups
The backup mechanism is smart enough to store only the deltas of each backups. This mean that the size of our backups will not reach an astronomical size.
Secure connection
The connection between on-premises and cloud is a secure connection. In this way no one can stay on the wire and read the content of your backup.
All the content that leave your on-premises machines is encrypted.
No initial investment
You pay only the space you use. You don’t need to book X TB of space and pay in advance.
On top of a secure connection and encrypted content, the content is compressed to reduce the space that is required to store your backup.
Content protection
The connection that is establish between on-premises and cloud is based on a certificate and a set of credentials – so called vault credentials.
Volume format
The format of the volume that is backed can be only NTFS.

Azure backups cannot be used when:

  • Volume is locked by BitLocker Drive Encryption
  • Volume is not formatted with NTFS
  • Drive type is not fixed
  • Volume is read-only
  • Volume is not currently online
  • Volume is on a network share

Applicable Use Cases 
Azure Backups can be used with success in any use case when we need to create backups and to store them in a location where we are sure that backup’s content will not be lost.

Code Sample 

Pros and Cons 

  • Easy to use and manage
  • Secure
  • Incremental backups support
  • 6 copies of your backups in 2 different data centers
  • No extra charge for outbound traffic or transactions 

I don’t know if this is a real limitation but I would really like to be able to use it with network shares also.

When you calculate the cost of Azure Backups you should take into account:

  • The size of the backup

This is a service that can be very useful  not only for companies but also for end users that needs to create backups. On the top of all the features that Azure Backups has, the cost calculation is very simple because is only around the size of the backup.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

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 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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…