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.
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.
Greetings friends, making several upgrades the other day I found the next error that breaks you in the morning if you are in a hurry and you are performing upgrades of ESXi, the error in question happened to me when I tried to update using an ESXi bundle:
[InstallationError] There was an error checking file system on altbootbank, please see log for detail. Please refer to the log file for more details.
Steps to troubleshoot the error easilyFortunately the problem is solved in just a few seconds, the first thing we will have to do is check that the partition is OK and see the information of it:
vmkfstools -P /altbootbank/This will return something similar to the following, be very attentive to the Partitions spanned part, as we will use this information later:
vfat-0.04 (Raw Major Version: 0) file system spanning 1 partitions. File system label (if any): Mode: private Capacity 261853184 (63929 file blocks * 4096), 87220224 (21294 blocks) avail, max supported file size 0 UUID: 2afcf7ef-53839aff-43f1-432714380654 Partitions spanned (on "disks"): naa.200049454505080f:5 Is Native Snapshot Capable: NOThe next command will be launched against the partition that has shown us the vmkfstools command:
dosfsck -a -w /dev/disks/naa.200049454505080f:5Which will show us something like the next:
dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/disks/naa.200049454505080f:5: 212 files, 42635/63929 clustersIf we try to launch the ESXi update command again using the bundle, we won't have any more problems. I hope it serves you well.
Greetings friends, Veeam has launched a few weeks ago the new Veeam Agent for Linux 2.0, which includes among many new features the possibility of performing a Backup to Cloud Connect, which was the missing piece of equipment to offer full service to Cloud environments where we have Linux, such as AWS, Azure, Digitalocean, etc...
Greetings friends, on certain occasions it is highly recommended to deploy an instance of VCSA 6.5 in our lab outside of our Homelab, using tools such as VMware Workstation or VMware Fusion, so that we have our own VCSA VM on our computer, and we can play with it, apply patches, test new features, or even bring an entire nested environment. Congratulations, since VMware Fusion 10 and VMware Workstation 12, we natively support the deployment of VCSA 6.5 on these tools (without having to edit complicated files, or use Converter), let's go with the Blog.
Critical, vital, indispensable step - DNS, DNS and DNSI have read in several articles, and lived in my own meats Castellanas, the failure to deploy VCSA 6.5. x in VMware Fusion without this step, it is indispensable to have a valid DNS entry for this new VM, and to have the PTR record also for the installation to be completed correctly:
Deploying VCSA 6.5. x on VMware Fusion 10 - in video
Greetings friends, the Zimbra Community has that magic that makes you keep writing every day, commenting in forums, or contributing to GitHub with Scripts. As many of you know, I created a Script called ZimbraEasyInstall some time ago that helped us to deploy a Zimbra instance on Ubuntu in a very simple way. The other day I received an update to this code (thanks to Luis Perez) and now it also supports CentOS/RHEL, so today I want to show you how easy it is to install Zimbra Collaboration 8.7. x, in CentOS/RHEL in a completely automated way, here we go.