Everything about Zimbra, VMware, Veeam and PRTG, etc.
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.
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:
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.
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.
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:
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.
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.
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: NO
The 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.
