VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
About 2 years ago I decided to try out Nutanix and learn a little about how it worked along with Veeam. Like most people this started with a Google search and several blog posts of others who have deployed Nutanix CE in their home labs, mostly nesting inside their VMware environments to save on necessary hardware. So, why not. I downloaded CE, carved out a VM on my VMware host, went through the steps and before long I had a single node cluster running. I setup a couple small VMs on it, added to my Veeam server, setup backups and backup copy jobs, and was off and running. Over time I left it running and didn’t really think much about it. Occasionally, someone would ask about Veeam capabilities with Nutanix and Cloud Connect, or something else, and I could show them, or test out what they wanted to try, but otherwise just left it running. Not too long ago, Nutanix released CE 2.0, however I waited, no rush to change what was working. Then there was the IT crash heard around the world .
As many know I am a big fan of VRO, I mean how can you not be? Orchestrated DR with automated testing and built in reporting. What is not to like about that? Something I have struggled with though is Groups in plans. By default, systems are grouped based on Veeam BNR jobs or vSphere datastores. What does this mean? Well, if I have 20 VMs in a backup job, those 20 come into VRO in a group based on that backup job. I can add this group to a recovery plan to be restored into another vSphere environment or a cloud recovery plan to Azure. But what if I want to recover 10 to another vSphere location and 10 to Azure? I could break the job in half so that I get 2 groups based on new backup jobs with 10 each. However, that may not be practical for my retention requirements, or just more administrative overhead. So how can we solve this problem? Glad you asked. Since VRO relies on the embedded VeeamOne, we can use vSphere tags or Business View Categories to group systems together. Let’s look at
As the saying goes, save the best for last, or in this case the most complex . Make sure that you have performed part 1 and either part 2 or 3 before you tackle this last puzzle piece. Along with the previous parts, you will also need a VMware environment setup and connected to Orchestrator and VBR (can use the embedded VBR in Orchestrator), a local repository that you can perform backup copies from the Azure Blob. You will need to add this to Orchestrator as a recovery location. You will need to have the Azure Blob repository setup as an External repository on your VBR instance, then setup a backup copy job to your local repository. Although you can perform an instant recovery from Azure Blob into VMware, it was easier and performed better to use the local repository. For the scripting part, we will be using VMware PowerCLI on the VBR server, so you will need to have that installed as well. Our only option to recover into VMware from an Azure backup is an instant recovery, so our scr
This is a Powershell Script that can be used to install and configure Veeam AIX Agent without needing to log into the AIX system. Can be because of lack of AIX expertise or a large number of AIX systems. https://github.com/VeeamHub/powershell/tree/master/BR-AgentAIX-Install
As mentioned in Parts 1 and 2, the core component that needs to be deployed and setup is a Veeam Backup for Azure appliance. This is required to protect the restored workloads and makes it possible to recover them into another location. Without this, none of the rest matters. You can follow this link for instructions:https://helpcenter.veeam.com/docs/vbazure/guide/deploying_appliance.html?ver=60 You will also need to create a backup policy that will automatically backup the restored VMs with the tags setup in Part 1. For this part, we are going to focus on an appliance that is deployed and in the powered off state. If you are just using Azure as a DR site and do not have running workloads that need to be protected, then you can save money by having the appliance powered off. This way you only pay for the storage it is consuming and compute only when it is powered on for testing or DR events. To Power on the appliance, we will use PowerShell and the Azure cli. Currently we cannot use th
As mentioned in Part 1, the core component that needs to be deployed and setup is a Veeam Backup for Azure appliance. This is required to protect the restored workloads and makes it possible to recover them into another location. Without this, none of the rest matters. You can follow this link for instructions:https://helpcenter.veeam.com/docs/vbazure/guide/deploying_appliance.html?ver=60 In this part we are going to Enable a Policy that is in a Disabled state on a running Veeam Backup for Azure appliance. You may have other workloads in Azure that you want to protect which is why you would have it running and just have the policy disabled. Otherwise, it would be advised to power off the appliance for cost savings, and we will cover that in Part 3. You can leave it off, so you only pay for the storage consumed and not the compute resources. To Enable the policy, we will use Rest API calls to the VB Azure appliance inside of PowerShell. The Rest API will make calls to the Appliance to E
VRO has the built in capability to use Azure as a Disaster Recovery location, allowing customers to easily restore workloads into Azure in the event of an outage. However, this option has generated a few questions from users:Can I use VRO to get back to an On-prem infrastructure? If I can, how do I accomplish this? Let’s start to address these questions. Yes, it is possible with the current version to recover back into either VMware or Nutanix AHV. Yes, VRO can accomplish this with planning and customizing. This will take several steps and scripts, so I have broken this up into 4 posts . This is post 1 of 4 A core component that needs to be deployed and setup is a Veeam Backup for Azure appliance. This is required to protect the restored workloads and makes it possible to recover them into another location. Without this, none of the rest of this matters. You can follow this link for instructions:https://helpcenter.veeam.com/docs/vbazure/guide/deploying_appliance.html?ver=60 If you al
This is a very simple calculator that uses backup size from the Veeam official calculator, the tape capacity, and the number/ retention amount required. Based on this information, it will tell you how many tapes you will need. http://tape.skitchlab.com
A few times I have had partners/customers confused as to why their jobs failed when needing media and they have put media in the library. Well, the new media is in the Unrecognized Pool and needs to be moved. I created a Powershell script that can be used to automate this process to hopefully help this situation. https://github.com/VeeamHub/powershell/tree/master/BR-TapeMedia-FreePool
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
