Greetings friends, I continue with this very interesting series about Veeam and Microsoft Azure, we have already seen practically all the steps: from interconnecting Microsoft Azure with our Datacenter, deploying the VBR in Azure, launching the copy job jobs, and of course restoring Microsoft Azure, today I bring you how to bring those VM in Azure back to our Datacenter, as you can see in this illustration:
Greetings friends, we saw the other day how to configure Veeam Locations in our virtualization environment, Cloud providers and in our Backup elements. Today I bring you the next step, to be able to show you a report of all this that we have configured in a granular and simple way, and in PDF!
Veeam ONE Reporter - Data Sovereignty OverviewThe first thing we will do is to go to the URL of our Veeam ONE Reporter, remember https://veeamonefqdn:1239/ if we are in the Veeam ONE itself via RDP we will see an icon for quick access:
Greetings friends, with the upcoming launch of GDPR, many of the companies that use Veeam or service providers using Veeam are facing many new challenges, in this Blog I will not discuss all the challenges that a regulation like GDPR has, but how Veeam can help. Since the release of Veeam Backup & Replication v9.5 U3, Veeam has included a new feature called Locations, which will help us with the task of marking infrastructure elements and backup elements, so that we can visualize all this later. When we are performing Veeam tasks once we have the Locations configured, we will be able to see a warning in the jobs that will allow us to check if we are not sending backups to sites where the new regulation does not allow. The elements that we can assign Locations are the following:
- Elements in Virtual infrastructure: vCenter Servers, datacenters, clusters and hosts.
- Backup infrastructure elements: backup repositories, scale-out backup repositories, tape libraries and tape vaults.
- Elements in Agent management: protection groups.
- Veeam Cloud Connect for service providers: cloud repositories and hardware plans.
Configuring Veeam Locations in Veeam Backup & Replication v9.5 U3As mentioned before, we will need Veeam Backup & Replication v9.5 U3 or higher to configure the Locations. We will go to Home - Inventory and click on Locations:
Greetings friends, I continue with the series of blogs about how to move workloads from our Datacenter to Microsoft Azure, what we are going to see today is how to recover those backups that we have released in the previous series, using directly the functionality called Direct Restore to Microsoft Azure:
Greetings, I continue with the series on Veeam and Microsoft Azure, let's remember the diagram of the introduction where we presented the workflow. What I'm going to show you today, step by step, is the configuration in our Veeam Backup & Replication Server of our datacenter.
Adding the Microsoft Azure repository in our Data CenterThe first step of this blog, is to add the Microsoft Azure repository, in our local datacenter, remember that we have configured a new VBR in Microsoft Azure, and that we have inter-connected our datacenter and Azure. We will go to Backup Repositories - Add Repository
Greetings friends, I continue with the series about Veeam and Microsoft Azure, if we remember the drawing of the first entry, we will see that in Microsoft Azure we will deploy a Veeam Backup & Replication server, with the purpose of serving as a Backup Repository, and at the same time be able to operate and recover jobs directly to Azure, in case our main datacenter fails:
Deploying Veeam Backup & Replication directly from the Azure MarketplaceVeeam has been offering Veeam Backup & Replication 9.5 U3 directly from the Azure Marketplace for some time now, this is very convenient and includes:
- A fully functional and installed Windows Server 2016.
- An automatically pre-installed instance of Veeam Backup & Replication 9.5U3, with SQLexpress
Greetings friends, if we remember the introduction to this series on how to create a Disaster Recovery plan with Veeam in Microsoft Azure, we had the following diagram: In the diagram we can see how between the two locations we are using Veeam PN for connectivity, in this article today we will see the step-by-step steps to deploy and configure VeeamPN in both locations.
Deploy Veeam PN Network Hub to Microsoft AzureVeeam Powered Network can be deployed directly from the Microsoft Azure Marketplace, making it very simple and convenient to use. From the Microsoft Azure console, we will go to Create a resource and search for Veeam, among the results we can see Veeam PN for Microsoft Azure, we will select it:
Greetings friends, every day it is more common to move workloads to Microsoft Azure, or at least to have planned a certain level of Disaster Recovery to Microsoft Azure in case of a complete shutdown of our main data center, to be able to restore those most urgent applications for users or customers, reducing service downtime. Veeam has a number of specific products for moving workloads to Microsoft Azure, easily and fully integrated into the Veeam Backup & Replication console itself. The main functionality, available since March 2016, is called Direct Restore to Microsoft Azure, and although it used to come as a separate application it is now available on the Veeam Backup & Replication console itself to help with its integration.
Infrastructure topologyI would like to show you this diagram (thanks to Allan Hammond for his help with the diagram) so that we can understand Veeam's workflow between the local data center and Microsoft Azure and vice versa:
Greetings friends, a few days ago I finally finished a project that I had thought about months ago but I never had time to complete, it is about having the Visio forms of Veeam, or any other manufacturer, printed and magnetic so that we can use them in the increasingly common whiteboards, this can help us to:
- Create better presentations for face-to-face customers
- Create better presentations for our internal teams
- Create presentations for yourself for a more complete view of a solution or design
Final result and feedbackThe welcome on twitter has been more than good, observe the comments and number of RT and likes: https://twitter.com/jorgedlcruz/status/956337405740666880
Creation processThe process of creation is not very complicated, and it is also very economic, so any of you can do without spending a fortune, let's see the step by step.
Greetings friends, probably you have heard the news that told us how Veeam had acquired N2WS, a company that is dedicated to the protection of environments in Cloud on Amazon Web Services.
Why did Veeam acquire N2WS?N2WS is a leader in Infrastructure as a Service (IaaS) data protection, providing a native cloud backup solution specifically designed for AWS workloads, enabling organizations to back up data and applications as often as needed and recover them in seconds. As Veeam customers seek to move more workloads into the cloud, especially towards AWS, protection and availability of their data is a primary concern for Veeam. Veeam's goal is to give its customers the confidence that Veeam ensures that their information is protected no matter where it resides, and this acquisition gives us the #1 solution we need for data and application protection at AWS.
Amazon Web Services at a glanceFor those of you who are not up to date on Amazon Web Services, we have several elements in the Computing and Storage part. At the moment of storage of the Instances we have:
- Block: Storage the block provided by Amazon EBS that is persistent and Amazon EC2 Instance that is ephemeral and is destroyed when the Instance is destroyed.
- File: Amazon offers us Amazon EFS that we can connect to our instances and launch files there.
- Object: The already known Amazon S3 for access to non-continuously used items and Glacier for very cheap storage that we access only for archiving.